Sample
Ordinary, complex, short, adjourned, and imperfect meetings reveal style, exceptions, source quality, and reviewer behaviour.
A clean single-meeting demo rarely shows portfolio reality.
Evaluation
A practical evaluation for formal minutes teams.
A first evaluation usually starts with a small representative batch, confidentiality terms, and a practical review of quality, time saved, and house style.
01 Scope
Five to ten meetings across ordinary, complex, short, adjourned, and imperfect cases.
02 Material
CSV, transcripts, recordings, board packs, support notes, separate reports, and reviewer contacts.
03 Review
Board support, chair, attendees, and service provider reviewers assess quality and control.
Evaluation
A representative evaluation can be small, real, and reviewable.
A useful evaluation tests representative meetings, source assumptions, reviewer activity, outputs, security questions, and house style together.
Before material moves Confirm the workspace, users, source types and reviewer access for the sample.
Review documents
Ask for current data-flow, retention, deletion, subprocessor and contract documents where needed.
Record
Manifest, source folder, source check, draft minutes, comments, accepted feedback, exports, and audit history stay together.
The team judges workflow quality alongside drafting quality.Decision
Proceed, retest, pause, or widen the scope, with reasons tied to quality, control, security, time saved, and output usefulness.
Keep this note for team sign-off.Evaluation record
A representative sample shows quality, house style, reviewer control, and time saved.
Enough variety to test house style, exceptions, reviewer control, and timing.
A first drafting run can be reviewed while board support and the chair control sign-off pace.
Compare current workflow against Boardmate output, source handling, and audit clarity.
Confidentiality and data-flow questions are handled before real files move.
Typical evaluation
Five to ten meetings, drafted in a day.
Board support and the chair set the review pace from there: reviewer feedback, style notes, and sign-off.
Confidentiality and data handling
Agree the security review and data-handling terms before sample material is loaded.
Sample selection
Choose 5 to 10 representative meetings across ordinary, complex, short, and adjourned cases.
Sample import
Upload the CSV manifest and source folder, then walk through preflight and matching together.
Draft, review, regenerate
Generate drafts, request reviewer comments, and use chair decisions to shape the next version.
Side-by-side review
Compare Boardmate drafts against the current workflow for house style, time saved, source handling, and audit clarity.
Drafting time
Inside a day for a 5 to 10 meeting sample.
Review pace
Set by the organisation's board support and chair review pattern.
First-run scope
Agreed before confidential material is loaded.
Start with a representative batch
The best evaluation uses enough variety to be meaningful without requiring the team to upload an entire archive. It should show ordinary work, edge cases, source gaps, reviewer behaviour, and house style.
Ordinary
Routine board meetings with the expected agenda, pack, transcript or recording, and prior minutes.
Complex
A meeting with reports, decisions, service provider input, or sensitive drafting judgement.
Short
A short, adjourned, or sparse meeting that tests whether the minutes remain proportionate.
Imperfect
One example with missing, late, ambiguous, or revised source material so preflight can be judged.
Prepare the right material
A CSV, transcripts or recordings, board packs, support notes, prior minutes, action lists, and any separate reports give Boardmate a fair test. The source folder should resemble the material a human minute-taker would use.
- The CSV manifest should identify each meeting, date, entity, and expected source files.
- Prior approved minutes should show house style and recurring board language.
- Reviewer names, roles, chair or delegated decision owner, and expected review route should be known before the review round.
Measure what matters
The review covers formal quality, house style, chair control, reviewer experience, time saved, and export usefulness. A useful evaluation closes with a practical decision about scope, rollout, security, and any style improvements still needed.
Minutes quality
Do the drafts reflect the pack, transcript, prior wording, decisions, and appropriate level of detail?
Review control
Can comments, uploads, no-comment confirmations, and chair decisions be managed without email reconstruction?
Output
Are DOCX, PDF, actions where available, and audit history useful for the team that files and circulates minutes?
Decision
Choose a wider Lite run, a Full board cycle discussion, a tighter retest, or security documentation before material expands.
Common questions
Questions to settle before evaluation.
What makes a first sample useful?
A useful sample includes ordinary, complex, short, adjourned, and imperfect meetings so the team can judge quality, house style, source handling, and reviewer control.
What material should be ready before the sample starts?
Prepare the meeting list, recordings or transcripts, board packs, previous approved minutes, support notes, reports, actions, and known source gaps.
Who should review the output?
Board support, the chair or delegated approver, and the people who normally review the minutes should compare the output against the current workflow.