Guide
A practical guide for board support, chairs, attendees, and service providers using private review links and comment decisions.
Guide · 20 min
A practical guide for board support, chairs, attendees, and service providers using private review links and comment decisions.
Review works best as a decision workflow.
Boardmate guide
The guide explains how private links, selected passages, uploads, no-comment confirmations, and chair decisions work together.
Share it with attendees, service providers, chairs, and board support before the first review round.
Guide sections
Run the review
Use this when board support is preparing a review round with chairs, attendees, directors, lawyers, or service providers who need a simple way to comment without seeing each other's feedback.
Result of the exercise
Opened, commented, uploaded support, confirmed no comments, outstanding, or revoked.
Accepted, rejected, held, and chair-instructed feedback before regeneration.
Which draft was reviewed, which comments shaped the next version, and what remains unresolved.
Boardmate view
A draft-minute review can fall apart even when the first draft is strong. Comments arrive in email replies, Word markups, calls, side notes, and late uploads. Some reviewers rewrite style. Some correct facts. Some say nothing, and silence then has to be interpreted.
Boardmate's reviewer experience should make the job clearer. A reviewer reads the relevant draft, comments on selected passages, uploads support where needed, or confirms no comments. Board support sees activity. The chair or delegate decides which feedback becomes source material for regeneration.
Review detail
Draft-minute review often fails in the space between a good draft and a controlled next version. Feedback arrives by reply, markup, call, forwarded note, and late support document. Some comments are review input, some are preference, and some need chair authority.
Boardmate's review workflow makes those states visible. Reviewers comment on selected passages, upload support, or confirm no comments. Board support triages the set. The chair or delegate decides which feedback becomes source material for regeneration.
An attendee, administrator, lawyer, and chair are not asked to perform the same vague review. Their invitation names the check expected.
Selected-passage feedback reduces interpretation work and helps the chair distinguish fact, style, sensitivity, and record.
The next version is based on accepted comments and chair instructions, with held or rejected items still visible.
How to run it
The point of the workflow is not more commentary. It is cleaner review input for the next draft and a better record of how approval was reached.
Tell each reviewer the meeting, draft version, deadline, expected contribution, and whether uploads or no-comment confirmation are expected.
A useful comment says what is wrong, why it matters, and whether supporting material exists. This gives triage something concrete to work with.
No response, link opened, comment submitted, and no comments confirmed are different states. The review record treats them differently.
Group duplicate points, conflicts, style preferences, factual corrections, and legal sensitivities before asking for the regeneration basis.
The final record shows who reviewed, what changed, what was held, which draft was regenerated, and which files left the system.
Worked scenario
A director corrects an action responsibility. The administrator uploads a late report clarification. Legal marks a sensitive passage. Another reviewer asks for a broader rewrite that would overstate discussion. Board support groups the comments and asks the chair to decide the regeneration set.
The chair accepts the action correction, accepts the report clarification, holds the legal passage for a short call, and rejects the broad rewrite. The record now explains the next draft without relying on a chain of emails.
Action responsibility correction accepted.
Late report clarification uploaded and accepted.
Legal passage held for chair discussion.
Broad rewrite rejected as inconsistent with style.
A good result
Reviewers know what to check and how to respond.
Comments, uploads, opens, and confirmations are tied to the review history.
The chair or delegate controls what changes the next draft.
The exported minutes can be read beside the review history.
Boardmate review
Each reviewer receives narrow access to the relevant draft, with activity visible to the authorised team.
Comments stay attached to the wording they challenge, so reconciliation does not depend on inbox interpretation.
Reviewer comments, chair instructions, and structure decisions are counted separately when the next version is generated.
Silence is not guessed. A reviewer can confirm no comments and that response remains part of the review history.
Worked example
A board support lead sends private links to two attendees, the chair, an administrator contact, and a legal reviewer. The attendees check attendance and actions. The administrator checks report wording and uploads a late clarification. The legal reviewer marks one sensitive passage. The chair accepts two factual corrections, holds the sensitive wording for discussion, and rejects a broad rewrite that conflicts with house style.
The point of the review workflow is not to make every comment automatic. The product value appears when Boardmate shows what arrived, what was accepted, what was held, what was rejected, and which version consumed the accepted inputs.
Correction, clarification, or supporting material submitted through the review workflow.
Authorised direction that can shape the next draft even without attendee comments.
A judgement on whether a draft section, expected paper, or resolution placement should be treated a particular way.
Decision ledger
Does each reviewer know what they are being asked to check?
Reviewer role, draft version, private link, deadline, and allowed actions.
Issue links only when the review task is narrow enough to complete.
Is feedback attached to record?
Selected-passage comments, uploads, issue types, and no-comment confirmations.
Ask for support where a comment changes substance or creates legal sensitivity.
Which feedback needs chair authority?
Open comments, duplicate points, conflicts, outstanding reviewers, and held items.
Group and prepare the decision set before regeneration.
Can the next version explain its inputs?
Version provenance, accepted reviewer comments, chair instructions, and structure decisions.
Generate only when the accepted input set is clear enough to defend.
Watch points
Open-ended invitation If reviewers are asked for anything at all, they often send style rewrites instead of record.
Invisible silence No response and no comments are different states; the workflow should not confuse them.
Automatic consumption A comment should not change formal minutes until the chair or delegate accepts it.
Boardroom wording
To reviewers Please comment on the passage, upload support if needed, or confirm no comments.
To the chair Your decision set controls the next draft.
To board support The close-out should show who responded, what changed, and which version consumed the accepted input.
Boardmate toolkit
The review guide makes the difference between feedback and decision clear. Boardmate collects reviewer record, but the chair or delegate decides which input changes the formal record.
Briefing note
Reviewers respond better when they know exactly what to check. An attendee may verify attendance and their own contribution. A service provider may check report wording. Legal may mark a sensitive passage. The chair owns the accepted set.
Draft version, deadline, review role, expected checks, upload permission, and no-comment option.
Factual correction, support upload, style preference, legal sensitivity, duplicate, conflict, or chair instruction.
Accepted, rejected, held, consumed by regeneration, or carried forward.
A reviewer does not need a full portal account to check one draft. The link is focused, attributable, and revocable.
A comment attached to a passage is easier to triage than a broad email saying the section needs changing.
If a reviewer changes substance, they can supply the report, note, or correction that supports the change.
Regeneration consumes the approved source set, not every comment that happened to arrive.
Role by role
Check attendance, attributed points, actions, and whether any passage needs correction.
Passage comments, action corrections, support uploads, or no-comment confirmation.Check report wording, data points, late clarifications, and attachments.
Source upload, report reference, factual correction, and response confirmation.Identify sensitivity, privilege, legal wording, or over-recording without redrafting the whole minute.
Marked passage, reason, and recommended controlled wording.Accept, reject, or hold comments before regeneration.
Decision queue, accepted set, held issues, and version history.Decision route
Reviewers send replies, tracked changes, calls, and side notes with no common view of the round.
Do not regenerate until feedback is triaged.Most comments arrive through private links and are attached to passages.
Group duplicates and conflicts for chair review.The chair can see responses, uploads, no-comment confirmations, and pending issues.
Regenerate from the accepted set.The exported minutes can be read beside who reviewed, what changed, and what was held.
Use the workflow as the review standard for the next batch.Record note
A good close-out does not say only that review is done. It explains how the next version was reached.
Chair, administrator, legal, and two attendees responded; one attendee confirmed no comments.
Action responsibility correction, report clarification, and one factual attendance correction.
Sensitive discussion wording for chair and legal agreement.
Broad rewrite that conflicted with approved house style.
Avoid
Vague ask Please review invites broad rewriting rather than focused record.
Silent approval No response is not the same as reviewed, no comments.
Automatic edits Reviewer comments become minutes only after the authorised person accepts them.
Lost support A correction without its source may be hard to defend later.
Reviewer brief
A director, attendee, service provider, lawyer, and chair may all read the same draft for different reasons. The review invitation should make that difference clear. An attendee might check factual accuracy and actions. A service provider might check report-specific wording. A lawyer might focus on sensitivity and legal restraint. A chair might decide the basis for the next version.
The simpler the task, the better the response. Ask reviewers to identify factual corrections, missing context, sensitive wording, or action responsibility. Discourage broad rewriting unless the reviewer has explicit authority over style.
Checks facts, presence, discussion, actions, and missing context.
Checks technical wording, report references, and support record.
Accepts, rejects, holds, or instructs feedback before regeneration.
Passage record
A loose comment creates reconciliation work because the drafter must infer which words it affects. Selected-passage comments make the record smaller and more precise. They also help the chair see whether a comment is a factual correction, a style preference, a legal concern, or a request to add context.
The best reviewer comments say what is wrong, why it matters, and what supports the change. If an upload is needed, it should be attached to the issue rather than sent separately. If the reviewer has no comments, that should be captured as an explicit status.
Received and visible to board support for triage.
Approved as source material for regeneration.
Needs chair, legal, or service provider clarification.
Moderation
Board support often knows which comments are easy corrections and which ones need authority. A triage step lets the team group duplicate points, identify conflicts, spot late support material, and prepare the chair's decision. This keeps the review round orderly without removing the chair's control.
The review queue should show opens, comments, uploads, no-comment confirmations, outstanding reviewers, and revoked links. That visibility replaces the manual chase list that normally lives in email, memory, or a separate spreadsheet.
Decision and audit
The next draft should be based on accepted feedback and chair instructions. Rejected comments should not disappear into silence. Held comments should remain visible with a reason. This is how the team can explain why a passage changed, why a suggestion was not used, and which draft consumed which feedback.
At close-out, the review history becomes part of the approval record. Links issued, opens, comments, uploads, confirmations, decisions, regeneration, DOCX export, PDF export, actions, and audit history should sit beside the final minutes rather than scatter across systems.
Questions to settle
Carry forward
Reviewer role map, link activity, passage comments, uploads, no-comment confirmations, and decision history.
Run one real review round and compare reconciliation effort against the current email process.
Board support triages, chair or delegate decides, reviewers supply focused record.
Reviewer job
A review round works better when reviewers know exactly what is being asked of them. They should read the draft, comment on specific passages where needed, upload support if requested, or confirm they have no comments.
Checks factual accuracy, attendance, discussion points, and any action attributed to them.
Checks technical or report-specific wording and may upload supporting material.
Decides what feedback should shape the next draft.
Passage comments
Selected-passage comments are more useful than loose emails because they keep the feedback attached to the text being discussed. That makes moderation and regeneration less dependent on memory.
Board support
Board support should be able to see which comments are factual corrections, which are style preferences, which conflict with each other, and which need chair judgement. The review queue should make that work easier to perform.
Names, dates, attendance, apologies, resolutions, figures, or report references.
How much discussion to record, whether a concern is material, or how sensitive language should be expressed.
Two reviewers disagree, a comment contradicts the pack, or a late update changes the source position.
The reviewer confirms no comments or the comment does not affect the formal record.
Chair control
The decision point stays visible. Reviewer comments are not the final authority by themselves. The chair or delegated owner decides which comments are accepted and which instructions should shape the next draft.
Audit trail
For formal minutes, review record matters. The team should be able to answer who received a link, who opened it, who commented, who confirmed no comments, what was accepted, and what was exported.
Links issued, expiry, revocation, and permitted review actions.
Open events, comments, uploads, confirmations, and outstanding reviewers.
Accepted, rejected, held, and chair-instructed feedback before regeneration.
DOCX, PDF, actions, and audit history kept beside the final minutes.
Working norm
A review process feels mature when it has a clear ending. Before export, board support should know which reviewers have responded, which comments remain open, and whether the chair has approved the basis for the next version.
Common questions
No. Reviewers comment on the draft, upload support where needed, or confirm no comments. Board support and the chair decide what shapes the next version.
Yes. Private reviewer links let attendees, directors, service providers, or advisers complete a focused review task without joining the full workspace.
A no-comment confirmation closes the loop. It shows that the reviewer had the chance to respond and did not leave outstanding changes.