2026-09-05
The agenda packet problem — how to merge, order, and number a board meeting PDF before the 72-hour deadline
September puts a lot of part-time boards back in session at once — school committees, condo and HOA boards, library and planning commissions, nonprofit boards that skipped August. A few days before each of those meetings, somebody produces the same artifact, and outside a clerk's office almost nobody has a name for it: the agenda packet. It is the agenda plus every document the members will actually be looking at while they vote — the treasurer's report, the bid comparison, last month's minutes, the engineer's letter, the site map. Assembling it feels like secretarial busywork. In a lot of jurisdictions it is a legal deadline with a clock on it.
California's open-meeting law is the most-quoted version of that clock. Under Government Code section 54954.2(a)(1), "at least 72 hours before a regular meeting, the legislative body of the local agency, or its designee, shall post an agenda" carrying "a brief general description of each item of business to be transacted or discussed at the meeting" — a description that "generally need not exceed 20 words." The stack behind that agenda is governed separately. Section 54957.5 makes agendas "disclosable public records under the California Public Records Act … and shall be made available upon request without delay," and it puts writings distributed to a majority of the body about an open-session item less than 72 hours before the meeting on the same footing: they "shall be made available for public inspection … at the time the writing is distributed." Agencies satisfy that either by naming an office on the agenda where the public can read the packet, or by posting it on the agency's website immediately. Read together, the two sections describe a single deliverable: one file, complete, on time, and public the moment the board sees it.
The duty is not a California eccentricity, and it is not only about elected bodies. In Korea, 공동주택관리법 Article 14 requires that a resident representative council, "having held its meeting, shall prepare minutes and have the management entity keep them," and that in apartment complexes of 300 or more households the management entity "shall disclose the minutes to the residents," responding to inspection requests and to copy requests made at the resident's own expense. Seoul's model management bylaws put dates on it: the minutes record each agenda item as approved, opposed or abstained, carry the signatures of the building representatives who attended, go to the management entity "within 3 days of the meeting (counted in management-office working days)," and are then posted "for a period of at least 14 days from the day they are received" on the building notice boards and the city's shared information portal. Different country, different body, same shape of problem: a set of documents, a fixed deadline, and an audience entitled to read exactly what the decision-makers read.
Why it has to be one file
The temptation is to skip the assembly step and attach nine PDFs to an email, or drop nine links on a web page. It fails for one reason, and the reason only shows up during the meeting: nine documents have nine page 1s. When a member says "the number on the bottom of the table," half the room is looking at a different table. When a resident later asks which page the vote was based on, there is no way to say. A packet is not a folder — it is a coordinate system. Its real product is not the pages, it is the fact that "page 23" means one thing to everyone holding it, including the person reading it six months later from an archive.
Building it: one grid, then subtraction
Drop every source PDF into NearPDF at once and their pages all land in the same grid, in the order the files were added. That single behavior is what makes packet assembly bearable, because it collapses merging and ordering into one pass instead of two: drag a page anywhere, including between pages that came from a different file, so the engineer's letter can sit directly behind the agenda item it belongs to rather than at the back with the rest of its own document. The grid is fully keyboard-operable — Tab to a page, arrow keys to move it, Delete to drop it, Enter for a full-size preview — which matters more than it sounds like when the packet is 180 pages and you are doing this every month.
Then subtract, because most of the work in a good packet is removal. Scanned attachments arrive with cover sheets nobody needs and, if they came off a duplex feeder, blank reverse sides (the blank-pages post covers why those appear and how to spot them). Sideways budget tables get fixed with the per-page rotate control, which changes a page property rather than re-rendering the page as a picture, so the numbers in the table stay sharp and selectable — the rotation post explains why fixing orientation in the file beats hoping the next reader tilts their head. And duplicate signature pages, superseded drafts and the second copy of last month's minutes come out entirely. Every page you keep is a page somebody has to page past.
Numbering is not decoration
This is the step people skip, and it is the one that decides whether the packet works in the room. NearPDF's page-number tool stamps a small gray number at the bottom centre of every page, starting at 1 and following the order of the grid at the moment you save. Two behaviours make it specifically a packet tool rather than a document tool. First, you can add several PDFs and the numbering runs continuously across all of them, treating the whole stack as one document — which is exactly the point. Second, each number matches its own page's orientation, so the landscape bid comparison you rotated is numbered along its bottom edge rather than sideways in the margin. Pages you deleted are skipped entirely, so the sequence has no gaps to explain.
There is one trade-off to make with your eyes open: the tool does not detect or replace numbers a document already has. Staff reports usually arrive pre-paginated, so a stamped packet shows both sets — the report's own "4 of 9" near the footer and the packet's "31" at the bottom centre. For a packet that is genuinely worth it, because the second number is the only one that is unique across the whole file, and the convention of citing "packet page 31" is exactly how clerks and courts already talk (the same reasoning drives the numbering rules in court e-filing). If you would rather avoid the double numbering, the fix is upstream: ask contributors for un-paginated PDFs, or strip the paginated version and re-export it. And if the cover page must stay unnumbered, there is no "start at 5" setting, but there is a clean two-step: remove the cover, number the body, then use Merge to put the unnumbered cover back in front.
The pages that must not be in the public copy
Packets are where confidential material leaks, because the same stack circulates in two versions. Section 54957.5 anticipates this precisely, and the wording matters: "this section shall not apply to a writing, or portion thereof, that is exempt from public disclosure." Portion. Real agencies redact paragraphs inside pages they otherwise publish — a name in a personnel item, a figure in a litigation memo.
NearPDF does not do that, and it is important to be blunt about it: NearPDF has no redaction tool. What it does is page-level, and page-level is genuinely strong at what it covers. When you delete pages and save, the file is rebuilt by copying only the pages you kept, so a removed page is not marked hidden or left recoverable in the output — it simply is not there. That is a better outcome than the black rectangle people usually reach for, which in most PDF editors leaves the text underneath selectable. So the workable rule for a public packet is structural: keep confidential material on its own pages from the start, so removing it is a page operation. A closed-session memo, a delinquency list with unit numbers, a resident's medical note supporting a hardship request — each of those belongs on separate pages, not tucked into the bottom of a page you intend to publish. If sensitive content is already sitting mid-page in something you must publish, that is a redaction job for a redaction tool, and no amount of deleting will do it.
For the draft that circulates internally before the meeting, the watermark tool will stamp DRAFT or NOT FOR DISTRIBUTION diagonally across every page. Treat it as labelling rather than protection — the watermarking post is explicit about what a watermark can and cannot do — and note one hard limit: the stamp uses Helvetica, a font every PDF reader has built in, which covers Latin-based scripts only. It will refuse Korean, Japanese, Chinese, Cyrillic, Arabic or Thai text and tell you which characters it cannot draw before anything is processed, so a Korean council cannot stamp 대외비 with it. That is a deliberate trade: shipping CJK font files would mean megabytes of downloads in a tool whose entire premise is that nothing is fetched and nothing is sent.
Getting it out the door
The finished packet is often the largest file the organisation emails all month, and it is usually scanned, which means large. NearPDF has no compression — the only way it makes a file smaller is by removing pages — so the real levers are upstream: scan at a lower resolution, or in black and white, before the pages ever reach the packet. The merge itself runs in your browser's memory, which sets a practical ceiling: up to 500 MB on a normal desktop, or 50 MB per file and 100 MB in total on phones and low-memory machines. If the assembled packet is too heavy for the mailing list that has to receive it, the splitting post covers getting it under an attachment limit, though for a packet the better answer is almost always to post the single file and email the link — which is what the open-meeting rules contemplate anyway. One more thing worth knowing before deadline day: if a contributor sends a password-protected PDF, NearPDF cannot open it, and rather than silently dropping it from the merge it names the file in a notice. Ask for an unlocked copy; do not discover the gap after the packet is posted.
The honest limits
NearPDF takes PDFs only, so photos of a signed page have to go through a scanning app first. It has no OCR, so a scanned budget table stays a picture of a table — the packet will not be searchable, and nothing NearPDF does changes that. It does not generate bookmarks or a clickable table of contents, so the numbered agenda at the front is doing that job by hand. It cannot open an encrypted file, it cannot redact, and it has no opinion whatsoever about whether your board is following its own open-meeting law — that question belongs to your agency counsel, your state's statute, or your complex's management bylaws, all of which outrank this page. What it does is the mechanical middle, and it does it without an upload: a pile of contributions from a dozen people goes in, one ordered, trimmed, correctly-oriented, continuously numbered packet comes out, and the draft board documents never touch anyone's server on the way to being published.