Home/Blog/How to Draft a Board Consent Agenda from a Packet (Not Legal Advice)
Blog

How to Draft a Board Consent Agenda from a Packet (Not Legal Advice)

P
promptstudio
How to Draft a Board Consent Agenda from a Packet (Not Legal Advice)

Consent agendas fail when they invent a 2/3 vote and a bank resolution that was not in the packet. This is not minutes and not legal advice.

The matching generator is the Board Consent Agenda from a Packet (Not Legal Advice, No Invented Votes) (Board Consent Agenda From A Packet Not Legal Advice No Invented Votes) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Banner not legal advice, not minutes

Turn a pasted board packet into a consent agenda. Not legal advice. No invented votes, quorums, or resolutions. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Entity and meeting date I may print: [Entity]
Pasted packet excerpts (items, attachments, prior minutes): [Packet]
What the bylaws excerpt says about consent (or NONE): [Bylaws]
Items already flagged as discussion (must not sit on consent): [Discuss]
People I may name (roles if names missing): [People]
Quorum or notice facts I can prove (or NONE): [Quorum]
What I must never claim: [Never]
Words I must not use: [Banned]
Word budget: [Budget or 350]
Advice banner: [Banner]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Consent only what the packet marked routine

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Banner: not legal advice, not minutes of a future vote. Quote Banner.
  2. Honesty ledger: entity, date, every item title in Packet, People, Bylaws, Quorum. Forbidden: vote counts and resolutions not in Packet.
  3. Consent list: items that Packet marks consent or routine, minus Discuss. Quote the packet title for each.
  4. Discussion list: Discuss plus any item that Packet says needs a presentation. Do not move them to consent.
  5. Vote line: only if Packet or Bylaws states a threshold. If NONE, write vote threshold not specified.
  6. Quorum/notice: only Quorum. Do not invent a 2/3 rule.
  7. Draft agenda block under Budget. Leave signature lines blank rather than inventing a chair signature.
  8. Compliance pass: quote Banned words, invented votes, legal-advice tone. Cut them. Print word count vs Budget.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Keep discussion items off the consent list

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Consent agenda from a packet. Not legal advice. Not minutes. Not a board narrative memo.
  • Never invent a vote, quorum, or resolution text.
  • Items in Discuss stay off consent.
  • If Bylaws is NONE, do not cite a section.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Do not invent quorum or a chair signature

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (board consent agenda, board packet consent list, not legal advice) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.