Published September 25, 2026 · Edition v4. Video-source attribution clarified September 25, 2026. Requester identity redacted September 25, 2026. Correspondence through September 23, 2026; dated public-information update September 24.
This story begins with a useful answer. On August 17, 2026, a county resident asked the Development Authority of Appling County, or DAAC, for records identifying its properties. The next afternoon, DAAC President/CEO Matt Carter emailed a list of seven properties, with parcel numbers, locations, acreage and descriptions of their use.
The requester considers that property-identification need answered. The parcel numbers gave him what he needed to look up the properties through QPublic. This account therefore does not treat separate maps or ordinary parcel information as an outstanding problem. That is the requester's assessment of what met his needs; the original request and Carter's reply remain available in their own words.
The questions that followed were different: What records did DAAC have about data-center inquiries and electric capacity? What was planned for a September 15 Georgia Power event? And what rules and board membership govern DAAC today? Two later requests, dated August 18 and September 8, addressed those subjects.
On September 22, DAAC sent six PDFs: five document attachments and one invoice. The next day, Carter said all requested documents had been provided. The requester had thanked him for the delivery and asked for more records and clarification. This account shows both positions and the documents behind them.
Read the source: August 17 original property request [P01] • August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01] • The data-center request [A01] • The September request [A05] • DAAC sends six PDFs [A14] • DAAC says all requested documents were provided [A16]
1. The property question received a useful answer
The August 17 request sought existing records identifying property DAAC owned, leased, optioned, controlled, held for development or marketed. It listed several possible record types, including parcel lists, inventories, maps and databases. It did not ask DAAC to create a new map or report.
Carter replied on August 18 at 2:31 p.m. with seven property entries in the body of his email. There were no attachments. His reply supplied the parcel identifiers that the requester needed for his own property research.
The requester later explained in project discussions that the parcel numbers should be credited because the information could be looked up in QPublic. For this account, the property-identification and ordinary map-information issue is answered. We are not counting a missing map or a missing duplicate parcel inventory as a continuing deficiency.
This does not make the parcel list an answer to every later question. A list of land being marketed does not tell a reader whether anyone asked about a data center, what a utility said, or what DAAC's current board rules are. Those subjects belong to the later requests.
Credit the property reply, then move on to the different questions raised in the later requests.
Read the source: August 17 original property request [P01] • August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01]
2. The next request asked about data-center activity
On August 18 at 3:02 p.m., after Carter's property reply, the requester sent a separate request about data-center development and site marketing. It covered records from January 1, 2025 through the request date. Its ten categories included inquiries, possible sites, utility communications, incentives and official actions.
Three days later, on August 21, Carter acknowledged the request and said he needed a couple of days the following week. On August 24, three days after that acknowledgment, Johnson replied for DAAC.
Johnson said DAAC had received limited data-center inquiries and had contacted SREMC about electrical capacity. He also said that, to DAAC's knowledge, there was no site under consideration or proposed or marketed for a data center, and no described studies, evaluations, proposals or requests for proposals. He concluded that DAAC had no meeting minutes or other documents related to those matters.
That reply answered several points as DAAC's official position. It also left a practical question: if inquiries and a utility conversation had taken place, were there existing emails or other records of those contacts? The requester asked for clarification on September 8, fifteen calendar days after Johnson's reply.
The follow-up concerned records of acknowledged past contacts. It did not depend on proving an active data-center project.
Read the source: The data-center request [A01] • DAAC acknowledges the request [A02] • DAAC describes inquiries, but says it has no related documents [A03] • The requester asks what the August reply covered [A04]
3. The hearing announcement led to a new request
The announcement that prompted this request was made at the September 1, 2026 Appling County Board of Commissioners public hearing on a 180-day moratorium. The requester identifies Matt Carter as the speaker who described a September 15 Georgia Power session, invited commissioners and said the public could not attend. The requester says hearing that announcement led him to request the event records on September 8.
Watch the September 1 hearing at 39:16. The relevant discussion runs approximately 39:16–39:51. This is the hearing where the later September 15 session was discussed.
Video source: 2026 09 01 Appling Co Board of Commissioners Called Mtg Public Hearing 180 Day Moratorium, published on YouTube by Appling County GA Commissioners.
The saved captions for that passage describe a Georgia Power data-center meeting two weeks later, for community leaders, and use the words 'not open to the general public.' The captions do not reliably identify every speaker or the precise invitation to commissioners; those details are attributed to the requester. The original audio has not been independently verified for this account.
For the requester, the question was straightforward: if public officials were being invited to learn about data centers, why could the public not listen too? His records request sought the invitation, expected attendance and explanation for excluding the public.
Seven calendar days after the hearing, on September 8, the requester submitted the new records request. It sought records about a planned September 15 Georgia Power presentation, who was expected to attend, public access and confidentiality. It also sought historical inquiries, utility communications, records within the stated East River Road scope, current governance records, and any existing records documenting the earlier search. The event-related categories were marked as priorities.
Quorum means the minimum number of members needed for a board to conduct business. Attendance matters because a quorum hearing or discussing its public business generally triggers open-meeting rules, even without a vote. There are exceptions, including the regional-training exception Johnson cited.
On September 11, three days later, Johnson said the event had been canceled. He attributed that decision to the prospect of a one-sided debate and rally, described the planned event as a regional information meeting, cited the regional training/information exception in Georgia's Open Meetings Act, and said there was no need to respond further on that point. Those are Johnson's explanation and characterization of the event.
He also stated that DAAC had no records related to a proposed data-center site in Appling County, specifically East River Road. He said governance records would be provided after his return from travel and estimated $500 if a point-by-point response was wanted.
The requester replied that he wanted existing records, rather than a newly written report or legal argument. He acknowledged DAAC's East River Road statement, kept his $25 cost authorization in place, and asked for the event records and a production timetable. On September 12, Johnson said he could not provide a cost estimate until he returned and met with DAAC staff.
The requester followed up on September 16 and September 19. He asked for available records to be released in installments and for a clear answer about anything still outstanding: when it would arrive, whether no records existed, or whether a particular legal exception prevented release. He expressly said he was not asking for duplicate work or records already supplied.
The request was meant to find out what was planned, who was invited and what supported excluding the public. The records let readers examine the answer.
Read the source: September 1 public-hearing video and the requester's account [C05] • The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07] • An estimate is deferred [A08] • The requester asks for dates, without duplicate work [A09] • The requester gives a requested correction date [A10] • Georgia Open Meetings Act, AG-posted text [L2] • Georgia open-government guide, meeting rules [L3]
Quorum: why the number in the room matters
How many people make a quorum?
Use that body's governing rule. For example, if a seven-member board requires a majority, four is enough: half of seven is 3.5, and four is the smallest whole number above half. That is an illustration, not a finding about DAAC's current roster.
When does the public get to attend?
A quorum receiving or discussing the body's public business generally means an open meeting, unless a legal exception applies. No vote is necessary. Count DAAC and the Commission separately; an official committee can also have its own quorum. Fewer members does not automatically settle every access question.
What about training?
Georgia excludes qualifying statewide, multijurisdictional or regional training/information gatherings where members take no official action. Johnson relied on this provision. Calling something training alone does not establish the exception; the event's actual arrangements matter. The exclusion cannot be used primarily to evade the law.
When may a covered meeting be closed?
A lawful executive session needs a permitted subject and the required closure procedure: a majority vote of a quorum present, public minutes recording the reason and closure vote, and a notarized affidavit. The parts without an exception stay open.
Why ask for the records?
The requester sought the documents needed to understand the invitation, expected attendance and claimed exception. The supplied record does not establish the expected number from each body or settle that classification. It does not prove an unlawful closed meeting occurred. Cancellation and access to existing planning records are separate questions.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • DAAC bylaws [B02] • Georgia Open Meetings Act, AG-posted text [L2] • Georgia open-government guide, meeting rules [L3]
4. Six PDFs arrived on September 22
On September 20, Carter said DAAC had no data-center projects and invited a conversation about economic development. Johnson offered meeting availability. The requester said he was open to talking after receiving and reviewing the records.
Two days later, Carter sent six PDFs in one email. That was 35 calendar days after the August 18 request and 14 calendar days after the September 8 request. These are elapsed calendar days, not findings about a legal deadline.
The delivery contained DAAC's historical creation records, a bylaws file, a training-planning email, industrial site-selection correspondence, a utility capacity email and a $100 invoice. Carter also said he had received no presentation information from Georgia Power and, to DAAC's knowledge, Black Ink had not continued looking in Appling County.
That evening, the requester thanked Carter, described the delivery as partial, asked for continued release of records within his authorization, and offered to arrange the conversation. On September 23, Carter replied that all requested documents had been provided and that DAAC was not working with a data-center client. He separately stated a rate for future estimates of $20 per hour plus legal costs.
This is where the positions differ. DAAC said the work was complete. The requester believed specific questions about the records and the handling of the requests remained. The comparisons below explain those questions without treating either party's conclusion as an independent finding.
There was one September delivery. It must be credited once, with each document connected to the subject it addresses.
Read the source: Carter invites a conversation [A11] • Johnson offers meeting availability [A12] • The requester welcomes a conversation after reviewing records [A13] • DAAC sends six PDFs [A14] • The requester thanks DAAC and asks for continued release [A15] • DAAC says all requested documents were provided [A16] • DAAC creation records [B01] • DAAC bylaws [B02] • Georgia Power training-planning email [B03] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05] • Records invoice [B06]
What arrived on September 22?
The August property list was supplied in an email. The later September 22 delivery was six PDFs: 6 + 6 + 1 + 3 + 1 + 1 = 18 PDF pages. That total includes a one-page invoice and one blank bylaws page. Our summaries and repeated correspondence are not additional DAAC records. Separately researched documents are in a different PDF.
Five document attachments + one invoice = six files. Their pages add up to 6 + 6 + 1 + 3 + 1 + 1 = 18. The property email was a separate, earlier answer.
DAAC creation records
6 original PDF pages | Sent by DAAC on September 22
Historical activation and certification documents from 1973.
What it answers: Helps establish DAAC's origins and powers.
Read the source: DAAC creation records [B01]
DAAC bylaws
6 original PDF pages | Sent by DAAC on September 22
Five pages of text and one blank page. The filename says 2016; the adoption statement says April 19, 1974.
What it answers: Supplies rules on the board, powers, meetings, committees, officers and amendments.
Read the source: DAAC bylaws [B02]
Georgia Power training-planning email
1 original PDF page | Sent by DAAC on September 22
An August 24, 2026 email arranging a call about upcoming training and an EMC representative.
What it answers: Provides an actual planning record for the event described in the delivery.
Read the source: Georgia Power training-planning email [B03]
Black Ink site-selection correspondence
3 original PDF pages | Sent by DAAC on September 22
October 2025 emails asking about industrial land and substantial power capacity, followed by Carter's site information and utility introduction.
What it answers: Documents a prospect inquiry, DAAC's reply and utility coordination.
Read the source: Black Ink site-selection correspondence [B04]
Satilla's Park West capacity email
1 original PDF page | Sent by DAAC on September 22
An October 21, 2025 email describing 4-5 megawatts then available and studies and construction needed for more.
What it answers: Documents a real limit on immediately available capacity and a two-to-three-year construction timeline for more.
Read the source: Satilla's Park West capacity email [B05]
Records invoice
1 original PDF page | Sent by DAAC on September 22
Invoice 1116: five hours at $20 per hour, totaling $100.
What it answers: States the hours, rate and amount billed for records work.
Read the source: Records invoice [B06]
What is answered, and what still needs an answer?
Open any question below. Each explanation starts with what DAAC supplied, then shows what that answer does and does not settle.
What is settled for this review?
Property-identification need answered
What was asked
Which properties did DAAC identify, and could the requester locate them?
What came back
Carter supplied seven parcel entries the next afternoon. The requester says those identifiers were sufficient for his QPublic research.
What that tells us
The article credits that answer. Separate maps and ordinary parcel details are not being presented as missing answers. This is the requester's stated practical resolution, not a rewrite of the original email.
What would clear it up
No additional map or duplicate parcel-list demand is made in this account.
Read the source: August 17 original property request [P01] • August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01]
Which past inquiries do the later emails explain?
Records supplied; connection still needs explanation
What was asked
What records existed of data-center inquiries and DAAC's utility contact?
What came back
Johnson acknowledged limited data-center inquiries and an SREMC contact. The later delivery included Black Ink's industrial site inquiry, Carter's reply and Satilla's Park West email.
What that tells us
These are useful records. They do not expressly identify Black Ink's intended use as a data center, so we cannot assume they are the same inquiries Johnson described. The September request also covered other large electric loads, which gives the supplied utility correspondence a clear place in that request.
What would clear it up
Identify which supplied records answer the acknowledged inquiries, and give a clear response for any remaining existing records.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • The requester asks what the August reply covered [A04] • The September request [A05] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
What about the two site PDFs named in an email?
Specific files named, but not included
What was asked
Existing site-selection and utility records within the requests' stated scope.
What came back
Carter's October 3, 2025 email names Parcel 0021 0041.pdf and Park West Spec Building Flyer.pdf. Neither is one of the six delivered files or reproduced or embedded in the three-page correspondence PDF.
What that tells us
This is a question about two identifiable files in a particular exchange. It is separate from the requester's acceptance of the August parcel list. We do not know whether the parcel PDF merely duplicates information the requester can obtain from QPublic or whether either file contains additional material.
What would clear it up
Explain whether the files are still held and covered by the request; supply them, identify a lawful reason for withholding, or explain any duplication already satisfied. Do not count their absence as proof of deliberate withholding.
Read the source: August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01] • The September request [A05] • DAAC sends six PDFs [A14] • Black Ink site-selection correspondence [B04]
What did the utility actually say?
Capacity limit documented; broader statement needs support
What was asked
Records about available power, expansion requirements and service timing.
What came back
Satilla said a 4-5 MW load could be served at Park West then. More would require studies and major construction, with a two-to-three-year timeline. Carter later said Georgia Power and EMCs would not provide grid upgrades for the prospect.
What that tells us
A megawatt, or MW, is a measure of power. The email supports a capacity and timing constraint. That could prevent a prospect from getting service when it needs it. It does not, by itself, establish that no upgrade would ever be offered or who would pay. Carter's earlier 8.5 MW description may refer to a different measure or condition; it should not be subtracted from 4-5 MW or applied to the entire county.
What would clear it up
Identify the additional communications or technical context supporting the broader statement about upgrades.
Read the source: DAAC sends six PDFs [A14] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
Why do the board numbers differ?
Historical documents differ; current voting roster unconfirmed
What was asked
Current bylaws, amendments, board membership and director terms.
What came back
The supplied bylaws say seven directors. A separate 2007 public assessment describes nine. A separate June 2024 announcement names a chair and nine others as board members: 1 + 9 = 10. A December 2025 County record documents a County-seat reappointment.
What that tells us
These sources describe different dates and are not a current voting roster. The nine- and ten-person descriptions came from C.L.O.C.K. research, not the six-file delivery. The later reappointment cannot simply be added to the 2024 list to claim eleven members. Johnson's appearance as a board member in 2024 and as counsel in the emails also does not, by itself, establish a conflict. The current membership and governing quorum rule also matter when deciding how many directors would have to gather for open-meeting requirements to apply.
What would clear it up
Provide the current roster, director terms and voting or advisory roles, with the governing documents and appointment records that explain the differences.
Read the source: The September request [A05] • DAAC creation records [B01] • DAAC bylaws [B02] • June 2024 appointment announcement [C01] • January 2007 community assessment [C02] • December 2025 County appointment minutes [C04] • Georgia Open Meetings Act, AG-posted text [L2]
Are these the rules DAAC uses today?
Rules supplied; current completeness not explained
What was asked
Current governing documents and operating rules.
What came back
DAAC supplied its creation records and bylaws. The bylaws filename says 2016, while the signed adoption statement says April 19, 1974. They contain real provisions on powers, meetings, officers and amendments.
What that tells us
An old document can still be in force. Age alone is not evidence that it is invalid or that an amendment was withheld. But readers cannot tell from this delivery whether it is the complete current version. The bylaws describe a regular January meeting, while a separately obtained 2026 schedule lists monthly meetings. A committee paragraph also ends with an unfinished sentence; that warrants checking the governing copy, not alleging alteration.
What would clear it up
Confirm the complete rules currently in force and identify any retained amendments, meeting resolutions or specific operating authorizations that apply.
Read the source: The September request [A05] • DAAC creation records [B01] • DAAC bylaws [B02] • 2026 meeting schedule, separately obtained [C03]
Did canceling the September 15 event answer the records request?
One planning email supplied; several subjects remain unclear
What was asked
Existing planning, invitation, attendance, public-access and confidentiality records for the proposed event.
What came back
Johnson said the event was canceled and characterized it as a regional information meeting. DAAC later supplied an August 24 training-planning email. Carter said he had received no presentation information from Georgia Power.
What that tells us
The planning email should be credited, and so should Carter's statement about presentation materials. Cancellation does not tell a reader what planning records were already held. The supplied record does not settle the full invitation list, expected attendance, public-access arrangements or whether other requested records existed. Records created after September 8 must be assessed against the actual request dates and scope.
What would clear it up
Give a clear answer for the remaining requested subjects, distinguishing records not held from records withheld or still to be supplied.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07] • DAAC sends six PDFs [A14] • Georgia Power training-planning email [B03]
What was said about confidentiality?
A statement appears; no agreement established by it
What was asked
Existing confidentiality agreements, restrictions and policies within the request's scope.
What came back
Black Ink's email says the company would treat information shared with it as confidential. Johnson also cited legal provisions when discussing the event and hypothetical records.
What that tells us
The sender's assurance is not the same as an agreement signed by DAAC or a DAAC policy. Likewise, the legal classification of a gathering and the release of its records are different questions. The cited economic-development provision concerns specified state Department of Economic Development project documents; its application to any particular DAAC-held record was not explained.
What would clear it up
Identify any actual responsive agreement or restriction, or clearly state what records are not held. For any withholding, identify the record or portion and applicable legal basis.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07] • Black Ink site-selection correspondence [B04] • Georgia Open Records Act, AG-posted text [L1] • Georgia Open Meetings Act, AG-posted text [L2]
Why was a timetable still being requested?
Delivery occurred; the earlier scheduling question remains
What was asked
Release available records in installments and provide a timetable for the rest.
What came back
Johnson tied governance production to his return from travel and a cost estimate to a later staff meeting. Those replies gave no definite date. The requester followed up. The six PDFs arrived September 22.
What that tells us
The delivery resolved the question of whether those six files would arrive. It did not explain what had prevented earlier release of available records. The issue is the agency's process, not a criticism of personal travel. The requester's September 23 checkpoint was a date he requested for correction; it was not a new statutory deadline.
What would clear it up
Clarify the processing steps and timing for any remaining records. Any legal assessment must also account for the actual request, available records, exemptions and lawful cost arrangements.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • An estimate is deferred [A08] • The requester asks for dates, without duplicate work [A09] • The requester gives a requested correction date [A10] • DAAC sends six PDFs [A14]
What records show how the search was conducted?
No additional search record identified in the delivery
What was asked
Existing instructions, custodian requests, search terms or logs if maintained, and nonexempt records of the August search.
What came back
The correspondence describes the responses. The invoice reports five hours of work. No additional existing search instructions, logs or similar records were identified in the six PDFs.
What that tells us
A bill for time does not prove a search log existed. The requester asked for records already maintained, not for DAAC to create a new search report. The question is whether any such existing records were held and what happened to that part of the request.
What would clear it up
State whether responsive existing search records were found, supplied, withheld or not held.
Read the source: The September request [A05] • DAAC sends six PDFs [A14] • DAAC says all requested documents were provided [A16] • Records invoice [B06]
How did a $25 authorization become a $100 invoice?
Amount billed is clear; basis and authorization need explanation
What was asked
Advance cost notice in August. In September, no costs above $25 without prior written approval, with an estimate before exceeding that limit.
What came back
Johnson estimated $500 for a point-by-point response on September 11, then said an estimate required a later staff meeting. The September 22 invoice billed 5 hours x $20 = $100. There is no separate attorney-fee line. Carter's September 23 statement addressed future estimates.
What that tells us
The invoice exceeds the September authorization by $100 – $25 = $75. That difference is a documented question, not a decision about the amount legally owed. The record does not show how time was divided between requests, whose rate was used, or whether the billed hours already excluded the first free quarter-hour. The $500 discussion, $100 invoice and future-rate statement are three different things.
What would clear it up
Explain the authorized work, rate and time calculation, and identify the nature and basis of any proposed legal charge. Do not automatically subtract another $5 without knowing how the five hours were calculated.
Read the source: The data-center request [A01] • The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07] • An estimate is deferred [A08] • The requester gives a requested correction date [A10] • DAAC sends six PDFs [A14] • The requester thanks DAAC and asks for continued release [A15] • DAAC says all requested documents were provided [A16] • Records invoice [B06] • Georgia Open Records Act, AG-posted text [L1]
Follow each exchange from start to finish
The short story above covers the turning points. These timelines include the intervening replies, clarifications and follow-ups. The dates tell you when a message was sent; “days later” is measured from the preceding displayed entry. Counts are calendar days, not legal-deadline findings.
August 17 property request: the lookup need was answered
August 17: the requester asks for property records
Request sent | Day 0
The request asked for existing records identifying property DAAC held or marketed.
Read the source: August 17 original property request [P01]
August 18: Carter sends seven properties
Next calendar day | About 20 hours after the request
The reply contains parcel numbers, locations, acreage and use descriptions. The requester considers these sufficient for his QPublic lookup needs.
Read the source: August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01]
August 18 data-center request: every reply in order
August 18, 2026 at 3:02 PM Eastern — The data-center request
Request sent | 0 calendar days from August 18
The requester asks for existing records about data-center sites, inquiries, infrastructure, incentives and official actions.
Read the source: The data-center request [A01]
August 21, 2026 at 9:37 AM Eastern — DAAC acknowledges the request
3 days after the preceding entry | 3 calendar days from August 18
Carter says he needs a couple of days the following week because of the length of the request.
Read the source: DAAC acknowledges the request [A02]
August 24, 2026 at 3:39 PM Eastern — DAAC describes inquiries, but says it has no related documents
3 days after the preceding entry | 6 calendar days from August 18
Johnson acknowledges limited data-center inquiries and a utility contact. He gives DAAC's no-site and no-related-records position. Read the exact qualifications in his reply.
Read the source: DAAC describes inquiries, but says it has no related documents [A03]
September 8, 2026 at 10:12 AM Eastern — the requester asks what the August reply covered
15 days after the preceding entry | 21 calendar days from August 18
The requester asks whether the reply was complete. He seeks records of the acknowledged inquiries and utility contact, while preserving the August request.
Read the source: The requester asks what the August reply covered [A04]
September 11, 2026 at 6:56 AM Eastern — Event canceled; records and costs discussed
3 days after the preceding entry | 24 calendar days from August 18
Johnson says the event was canceled, states that DAAC has no proposed-site records including East River Road, promises governance records after travel, and discusses a $500 point-by-point response.
Read the source: Event canceled; records and costs discussed [A06]
September 11, 2026 at 11:01 AM Eastern — the requester explains what he is asking for
Later the same day | 24 calendar days from August 18
The requester asks for existing records, acknowledges the East River Road statement, keeps the $25 authorization and requests a timetable. He preserves both later requests.
Read the source: The requester explains what he is asking for [A07]
September 12, 2026 at 11:06 AM Eastern — An estimate is deferred
1 day after the preceding entry | 25 calendar days from August 18
Johnson says he cannot provide a cost estimate until he returns and meets with DAAC staff.
Read the source: An estimate is deferred [A08]
September 16, 2026 at 4:28 PM Eastern — the requester asks for dates, without duplicate work
4 days after the preceding entry | 29 calendar days from August 18
The requester asks when outstanding records will be sent, or whether none exist or some are withheld. He says he is not seeking duplicate work or records already supplied.
Read the source: The requester asks for dates, without duplicate work [A09]
September 19, 2026 at 1:10 PM Eastern — the requester gives a requested correction date
3 days after the preceding entry | 32 calendar days from August 18
The requester again seeks records, a timetable and cost information. He requests correction by September 23 at 5 p.m. before possible further review. This is his checkpoint, not a new statutory deadline.
Read the source: The requester gives a requested correction date [A10]
September 20, 2026 at 8:57 AM Eastern — Carter invites a conversation
1 day after the preceding entry | 33 calendar days from August 18
Carter says DAAC has no data-center projects and invites the requester to discuss economic development.
Read the source: Carter invites a conversation [A11]
September 20, 2026 at 9:35 AM Eastern — Johnson offers meeting availability
Later the same day | 33 calendar days from August 18
Johnson offers Thursday or Friday availability. This is a scheduling reply.
Read the source: Johnson offers meeting availability [A12]
September 20, 2026 at 1:28 PM Eastern — the requester welcomes a conversation after reviewing records
Later the same day | 33 calendar days from August 18
The requester agrees to talk after receiving and reviewing the requested records. He says a conversation does not replace the records response.
Read the source: The requester welcomes a conversation after reviewing records [A13]
September 22, 2026 at 9:35 AM Eastern — DAAC sends six PDFs
2 days after the preceding entry | 35 calendar days from August 18
Carter sends five document attachments and a $100 invoice. This is one combined delivery for the ongoing exchange, not a separate set for each request.
Read the source: DAAC sends six PDFs [A14]
September 22, 2026 at 8:02 PM Eastern — the requester thanks DAAC and asks for continued release
Later the same day | 35 calendar days from August 18
The requester describes the delivery as partial, requests more records within his authorization, and offers to arrange the conversation.
Read the source: The requester thanks DAAC and asks for continued release [A15]
September 23, 2026 at 4:16 PM Eastern — DAAC says all requested documents were provided
1 day after the preceding entry | 36 calendar days from August 18
Carter states that the response is complete and DAAC is not working with a data-center client. He separately states terms for future estimates.
Read the source: DAAC says all requested documents were provided [A16]
September 8 request: every reply in order
September 1: the hearing announcement raises a question
Seven calendar days before the request
The announcement that prompted this request was made at the September 1, 2026 Appling County Board of Commissioners public hearing on a 180-day moratorium. The requester identifies Matt Carter as the speaker who described a September 15 Georgia Power session, invited commissioners and said the public could not attend. The requester says hearing that announcement led him to request the event records on September 8.
Watch the September 1 hearing at 39:16. The relevant discussion runs approximately 39:16–39:51. This is the hearing where the later September 15 session was discussed.
Read the source: September 1 public-hearing video and the requester's account [C05]
September 8, 2026 at 10:24 AM Eastern — The September request
Request sent | 0 calendar days from September 8
The requester asks for records about the planned September 15 event, historical inquiries, utilities and DAAC's current operating rules. He prioritizes the event categories and requires approval before costs exceed $25.
Read the source: The September request [A05]
September 11, 2026 at 6:56 AM Eastern — Event canceled; records and costs discussed
3 days after the preceding entry | 3 calendar days from September 8
Johnson says the event was canceled, states that DAAC has no proposed-site records including East River Road, promises governance records after travel, and discusses a $500 point-by-point response.
Read the source: Event canceled; records and costs discussed [A06]
September 11, 2026 at 11:01 AM Eastern — the requester explains what he is asking for
Later the same day | 3 calendar days from September 8
The requester asks for existing records, acknowledges the East River Road statement, keeps the $25 authorization and requests a timetable. He preserves both later requests.
Read the source: The requester explains what he is asking for [A07]
September 12, 2026 at 11:06 AM Eastern — An estimate is deferred
1 day after the preceding entry | 4 calendar days from September 8
Johnson says he cannot provide a cost estimate until he returns and meets with DAAC staff.
Read the source: An estimate is deferred [A08]
September 16, 2026 at 4:28 PM Eastern — the requester asks for dates, without duplicate work
4 days after the preceding entry | 8 calendar days from September 8
The requester asks when outstanding records will be sent, or whether none exist or some are withheld. He says he is not seeking duplicate work or records already supplied.
Read the source: The requester asks for dates, without duplicate work [A09]
September 19, 2026 at 1:10 PM Eastern — the requester gives a requested correction date
3 days after the preceding entry | 11 calendar days from September 8
The requester again seeks records, a timetable and cost information. He requests correction by September 23 at 5 p.m. before possible further review. This is his checkpoint, not a new statutory deadline.
Read the source: The requester gives a requested correction date [A10]
September 20, 2026 at 8:57 AM Eastern — Carter invites a conversation
1 day after the preceding entry | 12 calendar days from September 8
Carter says DAAC has no data-center projects and invites the requester to discuss economic development.
Read the source: Carter invites a conversation [A11]
September 20, 2026 at 9:35 AM Eastern — Johnson offers meeting availability
Later the same day | 12 calendar days from September 8
Johnson offers Thursday or Friday availability. This is a scheduling reply.
Read the source: Johnson offers meeting availability [A12]
September 20, 2026 at 1:28 PM Eastern — the requester welcomes a conversation after reviewing records
Later the same day | 12 calendar days from September 8
The requester agrees to talk after receiving and reviewing the requested records. He says a conversation does not replace the records response.
Read the source: The requester welcomes a conversation after reviewing records [A13]
September 22, 2026 at 9:35 AM Eastern — DAAC sends six PDFs
2 days after the preceding entry | 14 calendar days from September 8
Carter sends five document attachments and a $100 invoice. This is one combined delivery for the ongoing exchange, not a separate set for each request.
Read the source: DAAC sends six PDFs [A14]
September 22, 2026 at 8:02 PM Eastern — the requester thanks DAAC and asks for continued release
Later the same day | 14 calendar days from September 8
The requester describes the delivery as partial, requests more records within his authorization, and offers to arrange the conversation.
Read the source: The requester thanks DAAC and asks for continued release [A15]
September 23, 2026 at 4:16 PM Eastern — DAAC says all requested documents were provided
1 day after the preceding entry | 15 calendar days from September 8
Carter states that the response is complete and DAAC is not working with a data-center client. He separately states terms for future estimates.
Read the source: DAAC says all requested documents were provided [A16]
Want the question-by-question comparison?
These are plain-language summaries of the original numbered requests. The full emails preserve the exact wording and date limits.
August 18: the ten requested subjects
Was land being considered or marketed for a data center?
What came back
DAAC said it knew of no site under consideration, proposed or marketed for that use. The later industrial-site emails do not expressly name a data center.
How to read the answer
Credit DAAC's stated answer. Do not label an industrial land inquiry a data-center project without evidence.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Event canceled; records and costs discussed [A06] • Black Ink site-selection correspondence [B04]
Had DAAC's own or controlled property been considered for a data center?
What came back
The earlier seven-parcel list identified owned property and marketing status. It did not identify data-center use. The later Park West correspondence adds site information.
How to read the answer
The basic property lookup is answered for the requester's purposes. Any remaining question is about the requested data-center activity, not another ordinary parcel map.
Read the source: August 18 property-list response [P02] • The requester's clarification: parcel lookup answered [R01] • The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Black Ink site-selection correspondence [B04]
Was a data center being considered in an industrial park?
What came back
The supplied emails discuss Park West and available power, but do not expressly identify a data-center end use.
How to read the answer
Credit the park information. Ask how it relates, if at all, to the data-center inquiries described in August.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
What inquiries had developers or site selectors made?
What came back
Black Ink's inquiry and Carter's reply were supplied. Johnson had earlier acknowledged limited data-center inquiries.
How to read the answer
Useful correspondence arrived. Whether it accounts for the earlier acknowledged data-center inquiries is not explained.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • The requester asks what the August reply covered [A04] • Black Ink site-selection correspondence [B04]
What did infrastructure studies or utility messages show?
What came back
The Park West utility email describes 4-5 MW then available, with studies and construction needed for more. The site email also discusses utilities.
How to read the answer
These answer part of the infrastructure question. Their connection to the particular SREMC contact described in August remains unclear.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
What incentive programs or policies were available for data centers?
What came back
No document specifically addressing this category was identified among the six PDFs.
How to read the answer
A statement that no current client exists does not tell the reader whether a general policy exists. A clear answer for this category would help.
Read the source: The data-center request [A01] • DAAC sends six PDFs [A14] • DAAC says all requested documents were provided [A16]
Were incentives or public assistance discussed for a particular project?
What came back
No specific incentive or assistance record was identified. DAAC's statements about the absence of proposed sites and current projects must be credited.
How to read the answer
Do not assume an offer or commitment existed. Clarify whether any existing records answered this category or whether none were held.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Event canceled; records and costs discussed [A06] • DAAC says all requested documents were provided [A16]
Was incentive availability being advertised for data-center development?
What came back
No document specifically answering this category was identified in the delivery.
How to read the answer
This asks about existing marketing material within the request's data-center scope. It is not proof that incentives were promised.
Read the source: The data-center request [A01] • DAAC sends six PDFs [A14] • DAAC says all requested documents were provided [A16]
What communications took place with utilities, developers or other parties?
What came back
Black Ink and Satilla correspondence was supplied. It does not expressly identify a data-center end use.
How to read the answer
Credit the emails and clarify whether they cover the acknowledged data-center contacts.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
Were there meeting records, agreements or official actions about data centers?
What came back
Johnson expressly said there were no related minutes or other documents. No data-center agreement or final action was identified in the delivery.
How to read the answer
Record the no-records position. The historical creation documents and bylaws do not prove a project was approved.
Read the source: The data-center request [A01] • DAAC describes inquiries, but says it has no related documents [A03] • DAAC creation records [B01] • DAAC bylaws [B02]
September 8: the nine requested subjects
What was arranged for the September 15 event?
What came back
One Georgia Power email arranged a planning call and an EMC representative. Carter said he had received no presentation information.
How to read the answer
That is a real planning record. It does not settle the complete invitation, RSVP, attendance, coordination or materials record requested.
Read the source: The September request [A05] • DAAC sends six PDFs [A14] • Georgia Power training-planning email [B03]
What records explain public access and how the event was classified?
What came back
Johnson described a regional information meeting and cited the Meetings Act. The planning email calls it training.
How to read the answer
Those descriptions do not show all the requested decisions about public access, expected official business or attendance by enough members to conduct board business.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07] • Georgia Power training-planning email [B03] • Georgia Open Meetings Act, AG-posted text [L2]
Which officials were expected to attend?
What came back
The planning email identifies its recipients and seeks an EMC representative. It is not a complete list of expected directors or commissioners.
How to read the answer
No attendance commitments or count sufficient to settle the quorum question were identified in the delivery. Their existence remains unconfirmed.
Read the source: The September request [A05] • Georgia Power training-planning email [B03]
Were confidentiality restrictions or agreements involved?
What came back
Black Ink offered to treat shared information confidentially. No executed DAAC agreement is established by that sentence.
How to read the answer
The sentence must be credited, but should not be described as a DAAC-signed agreement. Other requested restrictions or records remain unexplained.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • Black Ink site-selection correspondence [B04]
What records show past data-center inquiries?
What came back
The delivery includes industrial site-selection correspondence. Johnson had acknowledged data-center inquiries; Carter later denied a current data-center client.
How to read the answer
Past inquiries and a current client are different things. The link between the acknowledged inquiries and the supplied emails needs explanation.
Read the source: The September request [A05] • DAAC describes inquiries, but says it has no related documents [A03] • DAAC says all requested documents were provided [A16] • Black Ink site-selection correspondence [B04]
What did utilities say about data-center or other large power demands?
What came back
The Black Ink and Satilla emails directly address large power loads. Two site PDFs named in Carter's reply were not included.
How to read the answer
This category expressly includes other large loads, so these records fit without guessing Black Ink's end use. Clarify the two named files and any remaining utility correspondence.
Read the source: The September request [A05] • Black Ink site-selection correspondence [B04] • Satilla's Park West capacity email [B05]
Did DAAC hold relevant East River Road records?
What came back
Johnson expressly stated DAAC had no records about a proposed data-center site, specifically East River Road. The requester acknowledged that statement.
How to read the answer
Credit it as DAAC's stated answer within its wording. It is not a finding about all activity on privately owned land.
Read the source: The September request [A05] • Event canceled; records and costs discussed [A06] • The requester explains what he is asking for [A07]
What rules and board information govern DAAC now?
What came back
Creation records and bylaws were supplied. They provide useful rules and powers, but no current named board roster or director-term list was identified.
How to read the answer
Use the governance checklist below to separate the provisions received from the current records still needing an answer.
Read the source: The September request [A05] • DAAC creation records [B01] • DAAC bylaws [B02]
What existing records document the August search?
What came back
Response emails were already held. No additional search instructions, custodian requests, maintained logs or collection messages were identified in the six PDFs.
How to read the answer
The later invoice does not prove those records existed. This remains a question about existing records, not a demand for a new report.
Read the source: The September request [A05] • DAAC sends six PDFs [A14] • DAAC says all requested documents were provided [A16] • Records invoice [B06]
The current-rules checklist
Current bylaws and changes
What came back
The bylaws were supplied. The adoption statement is dated April 19, 1974; the filename says 2016.
How to read the answer
Confirm that this is the complete version in force, and identify any amendments. An old adoption date alone does not invalidate it.
Read the source: The September request [A05] • DAAC bylaws [B02]
Current directors and their terms
What came back
No current named roster or term list was identified. The supplied text says seven directors; separate historical sources describe nine and name ten.
How to read the answer
Provide today's roster and explain voting, advisory or other roles. The dated descriptions do not establish today's board size.
Read the source: The September request [A05] • DAAC bylaws [B02] • June 2024 appointment announcement [C01] • January 2007 community assessment [C02] • December 2025 County appointment minutes [C04]
The 2026 meeting schedule
What came back
The schedule was not among the six files. C.L.O.C.K. obtained a public copy separately.
How to read the answer
Credit the public schedule as information already found. The question is its current status and relationship to the governing meeting rules, not a claim that no schedule was available.
Read the source: The September request [A05] • 2026 meeting schedule, separately obtained [C03]
Rules for regular and special meetings
What came back
The bylaws include meeting rules and a January regular meeting. The separate annual schedule lists monthly meetings.
How to read the answer
Confirm the current rules or resolutions that explain the schedule and meeting place.
Read the source: The September request [A05] • DAAC bylaws [B02] • 2026 meeting schedule, separately obtained [C03]
Public attendance and comment policies
What came back
No distinct policy was identified in the delivered documents.
How to read the answer
Explain whether a responsive policy exists. Internal notices to directors do not answer the public-attendance question.
Read the source: The September request [A05] • DAAC creation records [B01] • DAAC bylaws [B02]
Procedures for closed executive sessions
What came back
No distinct executive-session procedure was identified.
How to read the answer
The bylaws discuss an executive committee. A committee is not the same thing as a closed session. Clarify whether the requested procedure is held.
Read the source: The September request [A05] • DAAC bylaws [B02]
Delegated authority
What came back
The bylaws allow powers to be conferred and committees to be created.
How to read the answer
That supplies general authority. It does not identify a particular current resolution assigning powers to someone.
Read the source: The September request [A05] • DAAC bylaws [B02]
Who may enter or sign contracts
What came back
The supplied records describe general Authority, board and officer powers.
How to read the answer
Identify any existing specific authorization that answers who can bind DAAC today. No unauthorized contract is established by this gap.
Read the source: The September request [A05] • DAAC creation records [B01] • DAAC bylaws [B02]
Confidentiality policies, if any
What came back
No DAAC policy was identified. Black Ink's confidentiality statement is in the correspondence.
How to read the answer
A company's statement is not DAAC's policy. Clarify whether a responsive policy exists.
Read the source: The September request [A05] • Black Ink site-selection correspondence [B04]
Records officer and request policy, if any
What came back
No formal designation or request policy was identified. Johnson's emails show that he represented DAAC.
How to read the answer
Representation by counsel does not identify a formal records-officer designation. Clarify what responsive records are held.
Read the source: The September request [A05] • DAAC describes inquiries, but says it has no related documents [A03] • DAAC creation records [B01] • DAAC bylaws [B02]
A separate update about meeting information
Separate public-information update, observed September 24: DAAC's Facebook agenda post displayed 3:33 p.m. and identified a September 28 meeting at noon in the DAAC Office Meeting Room. The Page listed 305 West Parker Street, Baxley. The street address was not printed on the agenda itself. At approximately 10 p.m. Eastern, the checked economic-development webpage still linked an annual schedule without a meeting place; a meeting-specific agenda or update timestamp was not found on that page. These observations do not establish when a physical notice appeared or why the Facebook post was made. The requester's earlier check has no exact verified time.
Read the source: September 24 Facebook agenda post [W1] • DAAC Facebook Page and office address [W2] • Economic-development webpage checked September 24 [W3] • 2026 meeting schedule, separately obtained [C03]
Read the record and draw your own conclusions
The property reply and the later records deserve clear credit. So do DAAC's statements that it had no proposed-site records within the stated scope, no current data-center client and no received presentation information. The remaining questions concern identifiable records, how the answers fit together, current governing information and costs. Readers can examine the original requests and replies and decide how well the response explains those matters. This account does not establish a hidden project, an unlawful board or anyone's motive. Additional records and factual corrections should be added with their dates and sources.
Legal references, if you want to look them up
Georgia's Records Act addresses prompt access to existing records, release of available portions, a timetable for records not initially available, cost estimates and specific grounds for withholding. It does not require a newly created report. Meeting-access rules address a different question from whether related records may be released. These standards explain the questions in this account; they do not turn this review into a legal ruling.
Read the source: Georgia Open Records Act, AG-posted text [L1] • Georgia Open Meetings Act, AG-posted text [L2]
People and terms used in this account
DAAC
The Development Authority of Appling County, the agency that received these requests.
The requester
The person who submitted the requests. This account is prepared for public review by C.L.O.C.K. Accountability.
Matt Carter
DAAC President/CEO and the sender of the property list and September records delivery.
Alex Johnson
The attorney responding on DAAC's behalf.
Satilla / SREMC
Satilla Rural Electric Membership Corporation, the utility discussed in the correspondence.
Black Ink Development
The company whose October 2025 industrial site inquiry appears in the September delivery. The supplied emails do not state its intended end use was a data center.
The requests, replies and records
You do not have to take a summary on trust. Open the message reading copy below or use the reading PDFs. The source labels simply help connect a statement to the record behind it.
Read the story and question guide (PDF)August requests, replies and records (PDF)September request, replies and records (PDF)Separate C.L.O.C.K. research (PDF)August 17 original property request [P01]
August 18 property-list response [P02]
The Development Authority of Appling County owns the following properties:
065 001 | Entrance to Rail Park (Hwy 341)
Acreage: 1.05. Use: DAAC is marketing the property
0050 073 | Rail Park
Acreage: 330. Use: DAAC is working with Robert's Civil Engineering & State on GRAD Certification.
0021 041F | West Ind. Park (Hwy 341)
Acreage: 15.04. Use: DAAC is marketing the property & site is GRAD Certified.
0021 041 | West Ind. Park (Hwy 341)
Acreage: 104.78. Use: DAAC is marketing the property & site is GRAD Certified.
0021 041E | West Ind. Park (Hwy 341)
Acreage: 15. Use: DAAC is marketing the property & site is GRAD Certified.
0021 041A | West Ind. Park (Hwy 341)
Acreage: 16.33. Use: DAAC is marketing the property & site is GRAD Certified.
0002 032 | Graham Industrial Park
Acreage: 72. Use: DAAC acquired from County in 2026.
Read August 18 property-list response in the August history, page 4The requester's clarification: parcel lookup answered [R01]
The requester considers the August 17 property-identification request answered for his practical research needs. He says the supplied parcel numbers were sufficient to locate information in QPublic. Separate maps and ordinary parcel information are not carried as outstanding issues in this review. His earlier project discussion and current clarification support this reading; the original August 17 email did not contain the QPublic explanation. This note records his assessment and does not amend a sent request or withdraw any later request.
Read the requester's clarification: parcel lookup answered in the August history, page 5The data-center request [A01]
DAAC acknowledges the request [A02]
DAAC describes inquiries, but says it has no related documents [A03]
The requester asks what the August reply covered [A04]
The September request [A05]
Event canceled; records and costs discussed [A06]
The requester explains what he is asking for [A07]
An estimate is deferred [A08]
The requester asks for dates, without duplicate work [A09]
The requester gives a requested correction date [A10]
Carter invites a conversation [A11]
Johnson offers meeting availability [A12]
The requester welcomes a conversation after reviewing records [A13]
DAAC sends six PDFs [A14]
The requester thanks DAAC and asks for continued release [A15]
DAAC says all requested documents were provided [A16]
DAAC creation records [B01]
DAAC-supplied attachment received September 22.
Historical activation and certification documents from 1973.
What it answers: Helps establish DAAC's origins and powers.
What it does not settle: Does not supply a current named board roster or establish that no changes occurred afterward.
Read DAAC creation records in the September history, page 24DAAC bylaws [B02]
DAAC-supplied attachment received September 22.
Five pages of text and one blank page. The filename says 2016; the adoption statement says April 19, 1974.
What it answers: Supplies rules on the board, powers, meetings, committees, officers and amendments.
What it does not settle: Needs confirmation that this is the complete version in force today, together with any changes.
Read DAAC bylaws in the September history, page 31Georgia Power training-planning email [B03]
DAAC-supplied attachment received September 22.
An August 24, 2026 email arranging a call about upcoming training and an EMC representative.
What it answers: Provides an actual planning record for the event described in the delivery.
What it does not settle: Does not provide the full invitation, attendance, public-access or event-material record requested.
Read Georgia Power training-planning email in the September history, page 38Black Ink site-selection correspondence [B04]
DAAC-supplied attachment received September 22.
October 2025 emails asking about industrial land and substantial power capacity, followed by Carter's site information and utility introduction.
What it answers: Documents a prospect inquiry, DAAC's reply and utility coordination.
What it does not settle: Does not identify a data-center end use. Two named site PDFs were not included in the September set.
Read Black Ink site-selection correspondence in the August history, page 28Satilla's Park West capacity email [B05]
DAAC-supplied attachment received September 22.
An October 21, 2025 email describing 4-5 megawatts then available and studies and construction needed for more.
What it answers: Documents a real limit on immediately available capacity and a two-to-three-year construction timeline for more.
What it does not settle: Does not itself explain a blanket refusal to upgrade, who would pay, or whether this is the inquiry Johnson described in August.
Read Satilla's Park West capacity email in the August history, page 32Records invoice [B06]
DAAC-supplied attachment received September 22.
Invoice 1116: five hours at $20 per hour, totaling $100.
What it answers: States the hours, rate and amount billed for records work.
What it does not settle: Does not allocate the work by request or explain how the charge relates to the $25 authorization.
Read Records invoice in the August history, page 34June 2024 appointment announcement [C01]
Separate C.L.O.C.K. research. Not part of DAAC's six-file delivery.
A June 2024 announcement names David Douglas as chair and nine others as board members. It is a dated published list, not a current voting roster.
Read June 2024 appointment announcement in the separate research PDF, page 2January 2007 community assessment [C02]
Separate C.L.O.C.K. research. Not part of DAAC's six-file delivery.
The 2007 assessment describes nine members. The research PDF includes the cover and original PDF page 87 / printed ED-35. It is not a current governing amendment.
Read January 2007 community assessment in the separate research PDF, page 42026 meeting schedule, separately obtained [C03]
Separate C.L.O.C.K. research. Not part of DAAC's six-file delivery.
The independently obtained annual schedule supplies dates and a noon meeting time. The reviewed copy does not state a meeting place.
Read 2026 meeting schedule, separately obtained in the separate research PDF, page 6December 2025 County appointment minutes [C04]
Separate C.L.O.C.K. research. Not part of DAAC's six-file delivery.
County minutes from December 2, 2025 record a County-seat reappointment on original page 2. It does not establish a complete current board.
Read December 2025 County appointment minutes in the separate research PDF, page 7September 1 public-hearing video and the requester's account [C05]
Separate hearing source and requester explanation. Not supplied in DAAC's six PDFs.
The announcement that prompted this request was made at the September 1, 2026 Appling County Board of Commissioners public hearing on a 180-day moratorium. The requester identifies Matt Carter as the speaker who described a September 15 Georgia Power session, invited commissioners and said the public could not attend. The requester says hearing that announcement led him to request the event records on September 8.
Watch the September 1 hearing at 39:16. The relevant discussion runs approximately 39:16–39:51. This is the hearing where the later September 15 session was discussed.
Video source: 2026 09 01 Appling Co Board of Commissioners Called Mtg Public Hearing 180 Day Moratorium, published on YouTube by Appling County GA Commissioners.
The saved captions for that passage describe a Georgia Power data-center meeting two weeks later, for community leaders, and use the words 'not open to the general public.' The captions do not reliably identify every speaker or the precise invitation to commissioners; those details are attributed to the requester. The original audio has not been independently verified for this account.
Seven calendar days after that hearing, the requester sent the September 8 records request. The invitation, expected attendance and public-access records were priorities because the event was scheduled for September 15. Three days after the request, on September 11, Johnson said it had been canceled and relied on the regional-information-meeting exception.
Read September 1 public-hearing video and the requester's account in the September history, page 2Watch the cited hearing passage on YouTube, starting at 39:16
September 24 Facebook agenda post [W1]
Separate public-information update, observed September 24: DAAC's Facebook agenda post displayed 3:33 p.m. and identified a September 28 meeting at noon in the DAAC Office Meeting Room. The Page listed 305 West Parker Street, Baxley. The street address was not printed on the agenda itself. At approximately 10 p.m. Eastern, the checked economic-development webpage still linked an annual schedule without a meeting place; a meeting-specific agenda or update timestamp was not found on that page. These observations do not establish when a physical notice appeared or why the Facebook post was made. The requester's earlier check has no exact verified time.
DAAC Facebook Page and office address [W2]
Separate public-information update, observed September 24: DAAC's Facebook agenda post displayed 3:33 p.m. and identified a September 28 meeting at noon in the DAAC Office Meeting Room. The Page listed 305 West Parker Street, Baxley. The street address was not printed on the agenda itself. At approximately 10 p.m. Eastern, the checked economic-development webpage still linked an annual schedule without a meeting place; a meeting-specific agenda or update timestamp was not found on that page. These observations do not establish when a physical notice appeared or why the Facebook post was made. The requester's earlier check has no exact verified time.
Economic-development webpage checked September 24 [W3]
Separate public-information update, observed September 24: DAAC's Facebook agenda post displayed 3:33 p.m. and identified a September 28 meeting at noon in the DAAC Office Meeting Room. The Page listed 305 West Parker Street, Baxley. The street address was not printed on the agenda itself. At approximately 10 p.m. Eastern, the checked economic-development webpage still linked an annual schedule without a meeting place; a meeting-specific agenda or update timestamp was not found on that page. These observations do not establish when a physical notice appeared or why the Facebook post was made. The requester's earlier check has no exact verified time.
Georgia Open Records Act, AG-posted text [L1]
Official legal reference, kept separate from the documents sent by DAAC. This account is not an Attorney General or court finding.
Georgia Open Meetings Act, AG-posted text [L2]
Official legal reference, kept separate from the documents sent by DAAC. This account is not an Attorney General or court finding.
Georgia open-government guide, meeting rules [L3]
Official legal reference, kept separate from the documents sent by DAAC. This account is not an Attorney General or court finding.