Palm Coast
storylines...

Independent Reporting · Palm Coast, Florida
Published

Is McGlothlin Going Full Monty?


We’re in the middle of writing a three-part series wrapping up Cascades, and part one tells the story of the land. One question in it was still open: which piece was “the hook”?

It’s about 44 acres, the piece council cut out of the Cascades land-use plan at its first meeting of 2024. The ordinance and the maps from that night would settle it, so we went to get them.

The City’s agenda for that meeting is online. The Cascades item is in it, a three-page cover memo that lists ten attachments: the ordinance, the request for a rehearing, the staff report, the maps.

None of them are in the file that sits on the City server.

Then the page numbers caught our eye. The memo is printed as pages 107 through 109, and the next page in the file is 166. More than fifty pages of the packet sit between them, and not one made it into the file.

We checked the other Cascades meetings and found the same gaps. To rule out bad copies, we downloaded all five agendas again, fresh from the City’s site. Same files, same gaps.

Across five meetings, the eight Cascades items are missing . Council and the planning board had those pages in front of them. They never went online.

Truth is, we’d brushed past this once before. Back in the summer we asked the clerk for a single page missing from a Cascades item. She sent it, and mentioned it was . We never stopped to ask why the full agenda packet wasn’t online.

For years, that’s just how it worked here, for every item on every agenda. The public got the cover, and council got the book.

Not anymore.

Since April, the City posts the whole packet, the same one council reads before it votes. That was City Manager Mike McGlothlin’s call.

“Residents shared that having access to the full agenda packets was important to them, and we listened.”

— Mike McGlothlin, City Manager  ·  City of Palm Coast announcement, April 2, 2026

Whatever you think of the City Manager, this one goes on his side of the ledger.

What’s crazy is that the old way actually took more time and effort.

When , we learned the full agenda packet was built first, and the public version was cut down from it. So staff was keeping two versions of the same packet.

Think about doing that job. Before every meeting, staff built the whole packet for council, then cut a smaller one for the rest of us. That’s a long way from the sunshine, and nobody goes into public service hoping to work that way.

The City is in rough shape. We’ll be paying for decisions made in the Alfin, Danko and Klufas years for a long time, and for a lot of developer-friendly calls made long before them. The loop road alone moved a developer’s bill onto taxpayers.

Maybe we’ve turned the corner.

Consider the from the fight over westward expansion. They probably weren’t meant for public eyes, but a copy found its way to us.

These comments sound just like what people were saying at the mic.

The jury’s still out. But at least now the jury has the whole book.

— Johnny Diamond  ·  PalmCoastStorylines.com

Eight Cascades Items, 358 Missing Pages


Each cover memo in the City’s posted agendas still carries the page number it had in the full packet. Where one item’s memo ends and the next item’s begins, the numbers jump. The jumps are the missing pages.

MeetingItemMissing pagesCount
Jan. 2, 2024, City CouncilF.4110–16556
Dec. 19, 2023, City CouncilF.3571
Nov. 7, 2023, City CouncilH.1166–10439
Nov. 7, 2023, City CouncilH.12108–18780
Sept. 19, 2023, City CouncilI.898–12427
Sept. 19, 2023, City CouncilI.9128–21386
Aug. 16, 2023, Planning BoardD.212–3827
Aug. 16, 2023, Planning BoardD.341–8242
Total358

The items are the Cascades land-use amendment and rezoning at each stage: the planning board in August, council’s two readings in September and November, the request for a rehearing in December, and the rehearing in January.

The gaps weren’t limited to Cascades. Every item on these agendas was posted the same way.

We asked the City for the missing pages in a public records request on Oct. 12, 2026.

The public saw the cover memos. The pages behind them were not online.


Source: City of Palm Coast posted agenda files, downloaded Oct. 12, 2026: Jan. 2, 2024 · Dec. 19, 2023 · Nov. 7, 2023 · Sept. 19, 2023 · Aug. 16, 2023. Page ranges are the printed packet page numbers.

The Dec. 19, 2023 Agenda File, Read From the Inside


The City posted a 47-page file for the Dec. 19, 2023 council meeting. It held the agenda, then a cover memo for each item, and nothing behind the memos.

Every page still carries a printed page number. They run 1 through 5, then 53, 55, 56, 58, 59, 94 … 1105, 1119, 1121. A 47-page file has no page 1,121.

Its own name gives it away

Every PDF carries a few lines of information about itself, like a label on a folder. This file’s title line reads “AgendaPacket_2023-12-19_Final.pdf.” The name says packet. The City posted it as the agenda.

The page numbers were stamped by Adobe Acrobat

Acrobat’s Header & Footer tool tags every number it adds with the word “Pagination.” Those tags are in this file.

Acrobat numbers the document it’s working on. So the numbers were stamped across a document at least 1,121 pages long.

It was assembled from 26 files

The file’s bookmarks are named 00.pdf through 25.pdf. That’s how Acrobat’s Combine Files tool labels the pieces it joins: the agenda, plus one file per agenda item.

Each bookmark points to the first page of an item. The pages after it, the ordinances, staff reports and maps, aren’t in the posted file.

What the file can’t tell us

It keeps no edit log. It doesn’t record who removed the pages, how, or why.

The likeliest sequence is that the full packet was built, numbered, then trimmed. That’s an inference from the numbers, not a logged event. The other possibility is that each item’s memo pages were copied out of the numbered packet and put back together. Either way, the full packet came first.

The file was created and saved 53 seconds apart on Dec. 15, 2023, four days before the meeting. That fits a routine step. It doesn’t prove anything else.

Title: AgendaPacket_2023-12-19_Final.pdf
Created: Dec. 15, 2023, 5:11:19 p.m.
Saved: Dec. 15, 2023, 5:12:12 p.m.
Made with: Acrobat Distiller 23.0 (Windows)
Pages: 47
Last printed page number: 1121

The public file was cut from a full packet the City had already built.


Source: City of Palm Coast, agenda file for the Dec. 19, 2023 City Council Business Meeting, 123_A_City_Council_23-12-19.pdf (1,952,592 bytes), downloaded Oct. 12, 2026. Byte-for-byte the same as our library copy. The City’s file → · Our copy →

The Dec. 19, 2023 Agenda File: Technical Notes


TECHNICAL: the posted Dec 19, 2023 agenda file
(123_A_City_Council_23-12-19.pdf, 1,952,592 bytes. It's byte for byte the same as library/docs/cascades-cc-agenda-packet-2023-12-19-full.pdf.)

Document metadata (XMP and the Info dictionary):

dc:title
AgendaPacket_2023-12-19_Final.pdf
dc:creator
(author field: a staff name, withheld from publication until identified)
xmp:CreatorTool
Microsoft Office Word
pdf:Producer
Acrobat Distiller 23.0 (Windows)
xmp:CreateDate
2023-12-15T17:11:19-05:00
xmp:ModifyDate
2023-12-15T17:12:12-05:00 (53 seconds later)
xmpMM:DocumentID
uuid:83dece9d-91e6-4d20-a95e-c0939df4c7d8
xmpMM:InstanceID
uuid:e51579e4-3f22-4653-81eb-19be4d3bdd4e
xmpMM:History
none (the file keeps no edit log)
Pages
47
Tagged
yes. Structure tree present, 1,921 lines in a structure dump. That's thorough tagging for 47 pages.

Page numbers:

  • The printed numbers run 1-5, 53, 55, 56, 58, 59, 94, 95, 145 ... 1105, 1119, 1121.
  • In the page content, each number is written inside a marked-content block that looks like this (page 7): /Artifact <</Attached [/Bottom /Right] /BBox [531.1 28.95 539.98 35.19] /Subtype /Footer /Type /Pagination>> BDC ... (55) Tj ... EMC That's the signature of Acrobat's Header & Footer tool, a page number stamped onto the PDF. It isn't text typed into the Word document.
  • A simple scan finds this footer on 30 of the 47 pages. The other 17 print their numbers in a way the scan didn't catch, probably the agenda pages, since their numbers also appear in the text.

Bookmarks:

  • 26 bookmarks named 00.pdf through 25.pdf, pointing to pages 1, 5, 6, 7, 9, 11, 13 ... 47. Each points to the first page of the agenda or of an item's cover memo.
  • Acrobat's "Combine Files" names bookmarks after the source files. So the packet was built by combining 26 separate PDFs (the agenda plus one per item).

What follows, as fact:

  1. The numbers were stamped across a document of at least 1,121 pages. Acrobat numbers the pages of the document it's working on, so a 47-page file can't produce a "1121".
  2. The posted file holds only 47 of those stamped pages: the agenda and each item's first pages, the cover memos.
  3. So the posted file was derived from the full numbered packet. Either pages were removed after stamping, or each item's memo pages were extracted from the stamped master and recombined.
  4. The file's internal title is the full packet's name, ending "_Final".

What does NOT follow:

  • The metadata keeps no edit history, so it doesn't record a "delete pages" step or who performed it. "Created, then pages deleted" is the most likely sequence, but it's an inference from 1-3, not a logged event.
  • The 53-second gap between create and modify doesn't tell us which steps happened when. Acrobat can keep the original creation time through later saves. The gap fits a quick routine as well as a one-off edit.
  • Nothing in the file shows why it was done.

Source: our technical notes on the City’s Dec. 19, 2023 agenda file, Oct. 12–13, 2026, read with pdfinfo and pypdf. The technical notes (PDF) →

City Staff Comments on the Westward Expansion MPD Agreement


Before the agreement went to the planning board, City departments reviewed it and wrote up their concerns. A few of them, in staff’s own words:

“The only entry/exit point to the westward expansion is Matanzas Woods Pkwy for at least the first 2 phases and then Palm Coast Pkwy.”
“Impacts on existing infrastructure are not addressed.”
“Schools – School mitigation is not clear at this time (there is no mitigation agreement).”
“Agreement language implies that MPD supersedes, Charter, Comprehensive Plan, and Code of Ordinances.”

From the senior planner:

“This removes public agency entirely and sets up approvals in a backroom outside of the sunshine.”
“The City does not need more Residential coming online before we add more Industrial lands.”

Staff raised the same concerns residents raised at the mic.


Source: “Comments on the Westward Expansion Master Planned Development Agreement,” City of Palm Coast staff, 2026. Evidence Locker: raydient-mpd-staff-comments-2026.