The completed review moves C02/P01 from B01 version1 into the separate D02 discussion queue and produces B01 version2 containing C01/M01 and C03/D01. The count stays three original items: two remaining plus one pulled. It leaves actual decisions blank and never treats a pull request as rejection or approval.
Confirm eligibility before treating candidates as a consent package
BoardSource describes consent agendas as grouping routine items and allowing an item to be removed for discussion before the remaining package is considered together. That is the reference concept for this preparation exercise, not confirmation that a particular board or item can use the procedure. BoardSource: Board Meetings FAQs
Record the applicable policy and procedure reference, actual chair or responsible review, and any required meeting/decision conditions. Leave quorum, voting rules, authority, eligibility decisions, and participants blank until the responsible review supplies them. A template should not choose a quorum number or imply that the absence of a question establishes approval.
Use a candidate field for each item rather than a prefilled “approved” status. A title such as “routine program report” does not establish that it needs no discussion or that the intended action is appropriate. Record the actual requested action and supporting scope before preparing the final package.
Build a versioned item-to-reference manifest
The original fictional proposal is bundle B01 version 1:
| Candidate ID | Original candidate description | Supporting reference | Eligibility and intended action |
|---|---|---|---|
| C01 | Prior-minute review | M01 | TO CONFIRM |
| C02 | Routine program report | P01 | TO CONFIRM |
| C03 | Office-contact update | D01 | TO CONFIRM |
M01, P01, and D01 are illustrative reference IDs, not real documents inspected here. The working packet needs the actual document version, location, and review evidence. Keep those references attached to the item when its agenda location changes.
The manifest should include bundle ID/version, item ID, supporting document/version, proposed agenda location, requested action, eligibility review, and actual outcome reference. Do not rely on a filename alone to show which revision participants reviewed.
Preserve B01 version 1 as history. It describes the original three candidates; it is not evidence that the board approved them.
Record the pull request without duplicating the current item
In the fictional exercise, Q01 requests separate discussion of C02. Record Q01's item target, reason when supplied, requester and time when supplied, and the applicable handling procedure. Actual person, timing, and authority remain unfilled in this preparation packet.
Prepare B01 version 2 as the proposal reflecting that request:
| Item | B01 version 1 location | B01 version 2 proposed location | Reference retained |
|---|---|---|---|
| C01 | Consent candidate | Remaining consent candidate | M01 |
| C02 | Consent candidate | Separate discussion queue D02 | P01 |
| C03 | Consent candidate | Remaining consent candidate | D01 |
The current proposed consent manifest contains C01 and C03. C02 appears in D02 with its original P01 reference. D02 is a queue entry for discussing C02, not a fourth substantive item or a replacement supporting report.
The count reconciliation is three original items = two remaining consent candidates + one pulled item. Do not display three current consent candidates plus a duplicate C02 in the discussion queue.
The historical manifest may still contain C02. Label it historical so its presence does not imply current package membership. The revised proposal implements the exercise's requested scope change; the actual board's pull procedure and eligibility still require confirmation.
Keep the outcome scoped to the remaining version
Prepare a blank outcome record linked to B01 version 2 and its exact C01/C03 manifest. Leave the proposed motion text, actual motion, actual decision, result, participants, authority and supporting meeting evidence blank until supplied.
Referencing B01 alone is insufficient when both versions exist. A record should identify which version and items an actual decision covered. C02 must not inherit an outcome from the remaining C01/C03 package.
Use a separate blank discussion/outcome record for D02/C02. Discussion itself does not establish approval, and pulling an item does not establish rejection. The board may later make a decision; record the actual scope and result when it happens rather than completing the template with an assumed successful vote.
For a later revision, apply the same rule: preserve the old version, record the change, update current membership, and attach any eventual outcome to the version actually considered. A document edit after a meeting does not retroactively change the scope of its recorded decision.
Copy a prompt for this example
Create a self-contained HTML comparison for a fictional board consent agenda. B01 version 1 contains three candidate items: C01, prior-minute review with document M01; C02, a routine program report with P01; and C03, an office-contact update with D01. Eligibility and requested actions have not yet been confirmed.
Q01 requests discussion of C02. A Pull C02 button should prepare B01 version 2 with C01/M01 and C03/D01 remaining. Put C02/P01 in discussion queue D02. It remains the same substantive item, so display the reconciliation as three original candidates equals two remaining plus one pulled. Keep version 1 visible as historical membership, clearly separate from the current proposal.
Provide controls to inspect the versions, apply the pull, and reset. Update current membership, the discussion queue and the scope of the blank outcome record together. C02 must not inherit an outcome from version 2. Pulling an item does not reject it, and moving it to discussion does not approve it. Leave actual decisions, authority, quorum and voting conditions unresolved; this comparison does not conduct a vote or establish legal validity.
Show an illustrative 30-minute budget: 5 minutes to open, 5 for scope, 12 for discussion, 5 for questions and 3 for readback. Keep supporting document versions and actual review details available to complete in the governed packet. Place the original membership beside the current proposal on a wide screen and stack the comparison on a phone. Use readable labels and clear pull/reset buttons.
For a sanitized packet-preparation review, NOS can display this prepared HTML manifest. Pull C02, read back B01 version2 with C01 and C03, and keep actual eligibility, motions and outcomes in the organization’s governed agenda and minutes.