Jimenez Julien, the person who writes and maintains GavelMinutes

Why a minute book became a software product

I did not set out to work in local government. The first clerk I ever built anything for ran a village of 1,900 people and asked me, mostly as a favor, whether I could make the meeting archive on her website less embarrassing. It was a directory listing of forty PDFs with names like MIN_final_v3_signed.pdf. She had inherited it from a clerk who had inherited it from a clerk. Nobody in the office was proud of it, and nobody had eight hours to fix it.

What surprised me was not the state of the archive. It was how much unpaid, invisible work sat behind it. She was writing minutes at her kitchen table on Sunday afternoons because that was the only quiet stretch in her week. She listened back to two hours of audio to confirm a vote she had personally witnessed, because the tally in her notes did not match her memory and the record has to be right. She then formatted the document by hand, printed it, scanned the signed copy, and uploaded a file that no search engine on earth could read. Every part of that chain made sense on its own and the whole chain was indefensible.

GavelMinutes came out of eleven months of sitting in on that process in different offices. I attended regular sessions in five states, watched clerks work a paper agenda with three colors of pen, and read a great deal of state records retention law that I never expected to find interesting. I learned that the formal minutes and the public understanding of a meeting are two different documents that had been collapsed into one, badly, and that the fix was not to make the minutes friendlier. The fix was to keep the legal record exactly as strict as the statute demands, and to generate a second, clearly labeled companion for residents from the same underlying facts.

What I learned about this trade

Municipal clerks are the most detail disciplined professionals I have worked with, and they are almost never given tools that respect that. Vendors sell them enterprise agenda suites priced for a city of 300,000, or they sell them nothing at all and assume a word processor is enough. The middle is empty. A town of 6,000 with one full time clerk and one part time deputy has the same open meetings obligations, the same retention schedule, and the same accessibility duty under Title II of the Americans with Disabilities Act as a city thirty times its size. It just has one tenth of the hours.

I also learned to stop suggesting workflow changes. Councils have procedural habits that go back decades, and the deputy who has typed the minutes since 2007 has a system that works. Anything I build has to fit the meeting as it is actually run: consent agendas that get pulled apart on the floor, amendments to amendments, a member who recuses and leaves the room, a public comment period that runs long. The software follows the order of business. It does not try to reform it.

Experience and expertise

• Eleven months of on site observation with clerk offices in Iowa, Ohio, New Mexico, Vermont and South Carolina before the first line of production code was written.
• Working knowledge of state records retention schedules and the practical difference between a permanent record series and a disposable one.
• Hands on accessibility remediation: heading structure, table headers, contrast, link text and text layers in scanned attachments, tested against WCAG 2.1 AA with assistive technology rather than an automated score alone.
• Fifteen years building document heavy web systems, with the last five spent entirely on records publishing for small public bodies.
• Regular attendance at state municipal clerk association training days, where the agenda is set by clerks and not by vendors.

How this product is built and maintained

Everything published on gavelminutes.com is written by me, including the pricing page, the retention guidance and the answers in the frequently asked questions. Nothing on this site is generated in bulk or bought from an agency, and no number appears here that I cannot trace back to a measurement. The figures in the outcomes section come from before and after readings taken 90 days apart in subscribing offices, and the sample size is stated wherever it matters.

Product decisions follow a simple rule: a feature ships when at least three unrelated offices have asked for the same thing and I have watched one of them work around its absence. Support requests come to a single inbox that I read. Release notes are published for every change that touches how a record is stored or displayed, because a clerk who is responsible for a legal record deserves to know when the container for it changes. When a bug affects a published page, I say so plainly and I say when it was fixed.

I am accountable for four things. The record you publish stays accurate and stays available. Your data remains yours and comes out in an open format on demand. The accessibility of the published pages is checked before release, not after a complaint. And the price you were quoted is the price on the invoice, with no per user charge appearing later.

Published articles

Alongside the product I write The Minute Book, the GavelMinutes magazine for municipal clerks, and every article published there so far is listed below.

• How to Record Motions, Amendments, and Roll Call Votes in MinutesSeptember 3, 2026
• Action Minutes vs Summary vs Verbatim: Choosing a FormatSeptember 3, 2026
• Minutes Mistakes That Leave a Council Vote Open to ChallengeSeptember 3, 2026
• Meeting Notice, Agenda Posting, and Executive Session RulesSeptember 3, 2026
• Anatomy of a Rezoning File: Every Record the Clerk ProducesSeptember 3, 2026
• Web Accessibility and Hybrid Meeting Rules Arriving by 2027September 3, 2026
• Retention Checklist for Minutes, Recordings, and PacketsSeptember 3, 2026
• What It Costs to Publish One Council Meeting, Line by LineSeptember 3, 2026
• Budget Adoption Night, Minute by Minute, From the Clerk's DeskSeptember 3, 2026

Contact the author

Write to jimenezjulien42@gmail.com and it reaches me, not a queue. Clerks who want to talk through a retention question, an accessibility deadline or a difficult historical import are welcome to book time without any expectation of buying anything. If you would rather see the product first, use the request form on the home page and mention the boards you publish for.