Extracting Governing Board Resolutions From Corporate Minutes

Most of a set of board minutes is narrative and none of it is operative. The parts that authorise anything are the resolutions, they have a recognisable grammar, and their exact wording is the thing that matters — a paraphrased resolution is not a resolution.

What makes minutes hard

General meeting-notes extraction pulls out decisions and action items. That is the wrong target here. A board resolution is the instrument by which a company authorises an act — opening a bank account, issuing shares, appointing an officer, approving a merger — and third parties rely on the wording. A bank asked to open an account will want a certified extract of the resolution text, not a summary of what the board decided.

So the constraint that shapes everything is verbatim capture. Wherever a normal extraction would summarise, this one must quote. A model that renders “RESOLVED, that the Chief Financial Officer be, and hereby is, authorized to execute and deliver, in the name and on behalf of the Corporation, a credit agreement in a principal amount not to exceed Five Million Dollars ($5,000,000)” as “approved a $5M credit facility” has produced something that reads correctly and cannot be used for the purpose the extraction exists to serve.

The second difficulty is that minutes contain proposals that were not adopted. Discussion of a resolution, a motion that was tabled, an item deferred to the next meeting, and a resolution that was amended on the floor before adoption all look similar in the text and only one of them authorises anything.

Recitals, resolutions and everything else

Formal minutes and written consents share a drafting convention that is the single most useful signal available:

WHEREAS, the Board has reviewed the proposed form of the Amended
and Restated Certificate of Incorporation attached hereto as
Exhibit A; and

WHEREAS, the Board has determined that the adoption of the
Amendment is advisable and in the best interests of the
Corporation and its stockholders;

NOW, THEREFORE, BE IT RESOLVED, that the Amendment, in
substantially the form attached hereto as Exhibit A, be and hereby
is approved and adopted; and it is

FURTHER RESOLVED, that the officers of the Corporation be, and
each of them hereby is, authorized and directed to take all such
further actions and to execute and deliver all such further
instruments as any such officer may deem necessary or advisable to
carry out the intent of the foregoing resolution.

The WHEREAS clauses are recitals. They are context and they are not operative; nothing in a recital authorises anything. The text after “RESOLVED, that” is operative. The classification rule is therefore mostly structural, and structure is a far more reliable signal than semantics for this document type.

FURTHER RESOLVED clauses are the modelling decision. That second clause above is an omnibus authorisation, and it belongs to the first — it has no independent subject and means nothing on its own. Elsewhere, a FURTHER RESOLVED clause introduces a genuinely separate act. The workable representation is a resolution object containing an ordered list of clauses, with the whole block sharing one adoption event and one vote, rather than either flattening every clause into a separate resolution or merging them into one string.

Cross-references to exhibits are load-bearing and frequently dangling. “In substantially the form attached hereto as Exhibit A” means the resolution is incomplete without Exhibit A, and the exhibit is often a separate PDF or missing from the copy you were given. Carry an explicit list of referenced attachments with a resolution status per reference; an authorisation whose exhibit cannot be produced is a finding, not a successful extraction.

The vote is part of the resolution

A resolution without its adoption record is an unadopted draft. The fields that decide whether it took effect sit in the surrounding narrative rather than inside the resolved clause:

• Quorum. Minutes usually open by noting the directors present and that a quorum was present. If quorum failed, nothing adopted at the meeting is valid, and the quorum requirement itself comes from the bylaws rather than from the minutes.
• The tally. “Unanimously approved”, “approved by a vote of 5 for, 2 against, 0 abstaining”, or “approved by all directors present” — which is not the same as unanimous, because it excludes absent directors. Store the counts where given and the verbatim phrase where not.
• Abstentions and recusals. These are different things and the difference matters. An interested director who recuses on a related-party transaction is usually recorded as having disclosed an interest and left the room; the resolution may require approval by a majority of disinterested directors. A record that flattens recusal into “abstained” loses the compliance fact.
• Outcome. Adopted, rejected, tabled, deferred, withdrawn or amended-and-adopted. This is an enumeration, and it is the field that stops a proposal being recorded as an authorisation.

Written consents in lieu of a meeting are a distinct document type that arrives in the same pile and needs a flag. They have no quorum and no vote; instead they require signature by the requisite number of directors, and the effective date is the date the last required signature was obtained. Extract the signature dates individually rather than a single document date, since the operative date is the maximum of them. Determining who actually signed is a signature-block problem rather than a text one.

Minutes are draft until approved

This is the fact that most surprises teams building a resolution register. Minutes are prepared after the meeting and are conventionally approved at the following meeting, where a resolution approving the prior minutes is itself recorded. Until that happens, the document is a draft record of what happened, and it is routinely amended before approval.

So every resolution record needs two dates and a status: the meeting date, the minutes-approval date, and a status of draft or approved. The approval date lives in a different document — the next meeting’s minutes — which means the register is only correct if ingestion links consecutive meetings. That link is usually available: the approving resolution names the date of the meeting whose minutes it approves.

The resolution itself is generally effective from the meeting date regardless, because the board acted at the meeting and the minutes are evidence of the act rather than the act. But the document you are extracting from may not be final, and a register that cannot say which of its entries came from unapproved minutes cannot be relied on for the purpose people build these registers for. Where an item is a ratification of a prior act — a common pattern, especially for share issuances signed before the board formally met — carry the ratified act’s own date too, since the effective date and the resolution date differ deliberately.

What the record has to carry

{
  "meeting": {
    "entity": "Example Holdings, Inc.",
    "body": "board_of_directors",
    "date": "2026-02-18",
    "kind": "regular",              // regular | special | written_consent
    "quorum_present": true,
    "directors_present": 6,
    "directors_total": 7,
    "minutes_status": "draft",
    "minutes_approved_on": null
  },
  "resolutions": [
    { "ref": "R-2026-02-18-03",
      "subject": "credit_facility_authorization",
      "clauses": [
        { "kind": "resolved",
          "text": "RESOLVED, that the Chief Financial Officer be, and
                   hereby is, authorized to execute and deliver ..." },
        { "kind": "further_resolved", "text": "FURTHER RESOLVED, ..." }
      ],
      "recitals": ["WHEREAS, the Board has reviewed ..."],
      "outcome": "adopted",
      "vote": { "for": 5, "against": 0, "abstain": 0, "recused": 1,
                "phrase": "approved by all directors present, Director
                           Nakamura having recused" },
      "attachments": [ { "label": "Exhibit A", "resolved": false } ],
      "page": 3 }
  ]
}

Two design points are worth defending. Recitals are kept rather than dropped, because they are frequently the only place the transaction is described in enough detail to classify the resolution, and because areviewer checking an authorisation wants the context. And the vote carries both structured counts and the verbatim phrase, because the phrases used in practice do not map cleanly onto counts — “approved by all directors present” has no numbers in it and yet is entirely determinate given the attendance list.