Committee Meetings and Minutes¶
| Field | Value |
|---|---|
| Reference | PROC-002 |
| Type | Procedure |
| Version | 1.00 |
| Status | Approved |
| Owner | Secretary |
| Approver | Board |
| Approval Reference | MIN-2026-08-02 |
| Effective Date | 2026-08-05 |
| Next Review | 2027-08-05 |
| Review Requirements | As defined in STD-001 |
| Classification | Internal |
Purpose¶
This procedure sets out how often the Committee meets, what counts as quorate, and how meetings are minuted.
Scope¶
This procedure exists alongside, and does not duplicate, Constitution Section 5 (The Committee) - the Constitution establishes the Committee and its majority/casting-vote decision rule; this document covers the operational detail underneath that, and can be amended by the Committee without a Constitutional amendment.
Meeting Frequency¶
The Committee shall meet monthly, until a resolution is passed by the Committee to change this frequency. A fixed default is used deliberately, rather than a minimum such as "at least quarterly", to avoid the frequency quietly drifting downward over time without a conscious decision to change it.
Quorum¶
Quorum is a simple majority of the full Committee.
Where exactly half the Committee is present, the meeting remains quorate provided the Chair (or an officer holding the Chair's casting vote under Constitution 5.4) is among those present.
Where a Committee member steps back from a specific item due to a declared conflict of interest, this does not by itself reduce quorum for the meeting as a whole - see POL-006 for how declared interests are handled, including the case where stepping back would leave too few members to decide that item.
Meetings Without Quorum¶
A meeting may still be held and business discussed without quorum present. However, no decision, resolution, or approval may be made or ratified in the absence of quorum. Any matter arising from a non-quorate meeting must be brought to the next quorate meeting for formal decision.
No Meeting Held¶
If, in a given month, the Committee agrees that no matters require a
meeting, this is recorded rather than left silent - a minimal
MIN-yyyy-mm-dd entry noting that no meeting was held and that this
was agreed, with the means of agreement (e.g. "agreed by email
exchange between all Committee members"). This is the exception, not
the norm, and should not become a routine substitute for meeting.
Recording a deliberate skip, rather than leaving a gap, matters for the Association's own governance record: without it, a missing month is indistinguishable from a meeting nobody got round to holding.
Minutes: Classification and Naming¶
Two distinct document types are used, to avoid the record of what happened being tangled up with material that shouldn't be widely seen:
- Committee Minutes (
MIN-yyyy-mm-dd, Classification: Internal) - the official record of the meeting: attendees, apologies, declarations of interest, decisions, actions, reports received, policy approvals, and resolutions. They do not contain sensitive discussion. - Confidential Minutes (
CONF-yyyy-mm-dd, Classification: Board) - a separate document, created only when necessary, covering matters such as disciplinary issues, complaints, safeguarding, personal data, legal advice, commercial negotiations, security vulnerabilities, or anything whose disclosure would harm BRSA or individuals.
Both use the meeting date as the reference, since a date is a natural,
unique identifier for a meeting. Where a confidential item arises from
a specific Committee meeting, its CONF- reference uses the same date
as that meeting's MIN- reference, so the pairing is visible from the
filenames alone. If a single meeting produces more than one
confidential item, a sequence suffix is added (CONF-yyyy-mm-dd-b),
and the Committee Minutes' own "Related Committee Minutes" field is
used to keep the link explicit regardless.
Templates: TMP-003 (Committee Minutes) and TMP-004 (Confidential
Minutes), held in internal/templates/.
Confidential Business¶
Every Committee Minutes entry carries a standing agenda item, Confidential Business. If there is none, it reads:
No confidential business.
If there is, it reads:
The Committee considered confidential business. A separate confidential minute was recorded. See Confidential Minutes CONF-yyyy-mm-dd.
The open minute never discloses what the confidential business was - only that it occurred and where the record of it lives.
Minutes: Location and Lifecycle¶
Committee Minutes are filed in internal/minutes/. Confidential
Minutes are filed in board/minutes/. Both start life there as
Status: Draft while being written up.
Minutes are ratified - approved as an accurate record - at the following meeting, under that meeting's "Approval of Previous Minutes" item. Once ratified, the minute's status is set to Approved using:
change-doc-status -d MIN-yyyy-mm-dd --approve
change-doc-status -d CONF-yyyy-mm-dd --approve
This sets the Effective Date and moves the file into
internal/minutes/approved/ or board/minutes/approved/
automatically. Minutes are not on a review cycle the way a policy is,
so change-doc-status does not apply a Next Review date to them, and
they do not carry their own Change History table - the record of the
Draft to Approved transition lives in the git history and
logs/change-doc-status.log instead.
Related Documents¶
- Constitution, Section 5 (The Committee)
- POL-006` Conflicts of Interest Policy
- TMP-003` Committee Minutes Template
- TMP-004` Confidential Minutes Template
- STD-001` Document Standard
Review Requirements¶
As defined in STD-001.
Change History¶
| Version | Date | Author | Summary |
|---|---|---|---|
| 0.10 | 2026-07-23 | DC | Initial draft |
| 0.10 | 2026-07-23 | DC | Version format corrected to N.NN; heading numbers removed for consistency with the rest of the repo; Review Requirements section added; cross-referenced new POL-006 in Quorum and Related Documents |
| 0.50 | 2026-07-24 | DC | Version -> 0.50; Status -> Review |
| 0.50 | 2026-08-05 | DC | Status -> Approved; Effective Date -> 2026-08-05; Last Reviewed -> 2026-08-05; Next Review -> 2027-08-05 |
| 0.50 | 2026-08-05 | DC | Approval Reference -> MIN-2026-08-02 |
| 1.00 | 2026-08-05 | DC | Version -> 1.00; Approval Reference -> MIN-2026-08-02; Status -> Approved; Effective Date -> 2026-08-05; Last Reviewed -> 2026-08-05; Next Review -> 2027-08-05 |