AIforBC source-backed guide

Turn meeting notes into actions without inventing decisions

Separate decisions, proposals, owners, and deadlines in a fictional meeting, then use a reusable action register.

Editorial date: October 13, 20269 minute read + optional practicePrimary sources listed below

By AIforBC, operated by Boost Commerce Group. AI-assisted educational material; no individual expert review is claimed. Editorial policy and corrections →

Practical answer

An action list should distinguish an agreed decision from a suggestion. Copy confirmed owners and dates; leave unassigned work explicitly unassigned. Ask the meeting owner to approve the list before people rely on it.

Free practice / about five minutes

Notes are not decisions.
Make the difference visible.

Rewrite a deliberately flawed action register from three short notes. Keep what is agreed separate from what still needs a question.

Fictional information only. No uploads, model calls or account required. Edits stay in this page's memory until you leave or reload; only copying or downloading keeps your draft. Quick checks do not automatically review what you write.

02 / Repair the draft

Your practice register

These fields start with intentional mistakes. Edit them against S1–S3; use source references such as [S1].

What was actually decided? Keep suggestions out of this group.

Task · owner · due date · source. Preserve any uncertainty.

Ideas that have not become decisions.

Missing owners, dates and confirmations that still need a person.

Compare with a checked example

This is an authored reference, not an analysis of your draft. It does not replace the meeting owner's review.

Confirmed decisions
No confirmed decisions in these notes. [S2]
Agreed actions
Alex — check current supplier lead time — Friday; calendar date to confirm. [S1]
Proposals
Move launch to June, suggested by Morgan. Not decided. [S2]
Open questions
Installation checklist update: owner and due date unassigned. Confirm which Friday is intended for Alex's action. [S3][S1]

03 / Check your judgment

Three checks before handing it on

These questions check the distinction—not whether your edited register is correct.

Was moving the launch to June decided?
Who is confirmed for the checklist update?
Can Friday become 16 October from these notes?

Keep your practice. Keep the checks.

Your file includes the original notes and current edits, not the checked example. Your draft is not sent, stored by this exercise or approved. Limited usage events record activity, not your draft contents. Privacy details →

A fictional example you can check

Source

Fictional notes: Alex will check the current supplier lead time by Friday. Morgan suggests moving the launch to June, but no decision is made. Someone should update the installation checklist; no owner or date is named.

Reviewable result

Confirmed action: Alex — verify supplier lead time — Friday (calendar date to confirm). Proposal, not decision: move launch to June. Open action: installation checklist update — owner and due date unassigned. No approved launch-date change.

A polished summary might accidentally convert Morgan's suggestion into a decision or assign the checklist to the person mentioned nearest it. Preserving the unresolved fields is more useful than completing every row.

Original AIforBC teaching example. No customer record, field test, or measured business result is represented.

Practice / compare with the source above

What would you change before using this?

Read the draft before the corrections. These are deliberately flawed authored examples, not model output. Use the corrected draft for practice. It does not authorize operational use.

Deliberately flawed draft

Decision: launch moves to June. Alex will confirm supplier lead time on 16 October. Morgan will update the installation checklist by Friday. All owners and dates are confirmed.

Trace each correction

“Launch moves to June”

Why it fails: Morgan suggested a change, but the source expressly says no decision was made.

Checked position: Proposal: move launch to June. No approved launch-date change.

“16 October”

Why it fails: The source says Friday without a meeting date. The draft invents a calendar date.

Checked position: Alex will check supplier lead time by Friday; ask which calendar date was intended.

“Morgan will update the checklist”

Why it fails: No owner is named for the checklist. Mentioning Morgan elsewhere does not assign responsibility.

Checked position: Checklist update: owner and due date unassigned; ask the meeting owner to resolve both.

“All owners and dates are confirmed”

Why it fails: The notes cannot support a completed register. Unresolved assignments must remain visible.

Checked position: Draft register awaiting meeting-owner review and confirmation of unresolved fields.

A corrected practice draft

Draft for meeting-owner review. Confirmed action in the notes: Alex checks current supplier lead time by Friday; calendar date still to confirm. Proposal: move launch to June; no decision made. Open action: update installation checklist; owner and due date unassigned. Questions: Which Friday? Who owns the checklist update, and when is it due? Has the launch-date proposal been decided since these notes? Do not enter proposed changes or unresolved assignments into the task system as approved work.

Review before handing it on

  • Keep decisions, agreed actions, proposals and questions in separate groups.
  • Retain a source phrase for each action or claimed decision.
  • Do not turn relative dates into calendar dates without confirmation.
  • Leave missing owners and deadlines explicitly unassigned.
  • Have the meeting owner check the register before distributing it or updating a task system.

Put the method to work

1. Decide what information can be used

Follow meeting confidentiality, recording, retention, and approved-tool rules. Do not upload a full transcript simply because it is available. Start with fictional notes or a minimized, approved extract. Employee and customer details can remain sensitive in apparently routine meetings.

2. Use four categories

Ask for confirmed decisions, agreed actions, proposals, and open questions as separate groups. Require a source phrase or timestamp for each material entry. Keep a disagreement visible instead of choosing the cleaner interpretation.

3. Normalize dates with confirmation

Do not guess which Friday was intended. Record the meeting date and confirm the calendar date and time zone where relevant. If the note says ‘soon,’ keep it as an unresolved deadline rather than creating an arbitrary due date.

4. Have the chair validate ownership

The meeting owner checks decisions and asks action owners to confirm their responsibilities. An AI-generated assignment is not consent or authority. Correct the register before it is copied into a task system or shared beyond the original audience.

5. Keep a lightweight correction trail

Record corrections to decisions, dates, and owners. Check whether follow-up questions decreased and whether the register remained current. If the team disputes the list repeatedly, improve note capture or decision confirmation before introducing more automation.

Reusable worksheet

Copy this into an approved workspace. Start with fictional information; do not paste confidential records into an unapproved AI tool.

Meeting date / approved source:
Confirmed decisions and source reference:
Action | owner confirmed? | calendar date confirmed? | source:
Proposals (not approved):
Open questions / unresolved assignments:
Meeting owner approval:
Audience and retention rule:

Where this method stops

Do not use this method as an authoritative legal record, investigation summary, personnel decision, or substitute for required formal minutes. Transcription errors and incomplete notes can survive a careful summary. Confirm disputed or consequential statements with the responsible people.

Your next action

Source trail

Primary sources used in this guide

  1. Principles for responsible, trustworthy and privacy-protective generative AICanadian privacy authorities

    Privacy principles for accountable AI use. The right legal requirements depend on the organization, information, and use.

  2. Generative artificial intelligence — ITSAP.00.041Canadian Centre for Cyber Security

    Context for protecting sensitive information and checking generated output. It does not validate these fictional examples or promise business results.

AIforBC uses official and primary sources where practical. This guide provides general operational education, not legal, privacy, cybersecurity, or financial advice.

Try the method

Work from the source. Keep the decision.

Try a workflow