GAIM · AI in Action · Scenario 1

From Scrawlto the Record

Raw meeting notes into official minutes under Robert’s Rules — and why the polished draft AI hands you first is the one that gets you in trouble.

Live Copilot demo RICCE EVERY ~35 minutes Bring your laptop
01

Why this scenario

Most AI demos ask the tool to summarize something. This one asks it to restrain itself — and that’s a much harder ask.

Minutes under Robert’s Rules are a record of what was done, not what was said. No debate summaries. No characterizing how someone acted. No filling in gaps to make it read smoothly.

Every one of those is something AI is built to do. Hand Copilot a pile of notes and it will give you minutes that look professional, read beautifully, and are wrong in ways your secretary would catch and your chair might not.

The gap between “looks right” and “is right” is the entire lesson. Everything else today is a variation on it.

The principle travels. Swap minutes for a purchase requisition, an accreditation narrative, a job posting, or an incident report and the shape is identical: a document with a standard, where the AI knows the format but not your standard — and won’t mention the difference.

02

The notes you were handed

Tasha took these on her laptop during the July Staff Council meeting. They’re typical — which is to say, they’re a mess. Read them once as yourself. Then flip Trap Radar on.

Adds what shouldn’t be there Drops what must be there Invents what nobody knows
Staff Council — raw notes — T. Grant

Staff Council, reg mtg, Tues 7/7. started 2:04ishT9 — Marcus chaired, I took notes Barker 210 (I think? sign said 210)T10 Here: Marcus Whitfield (chair), Dana Rivera, Priya Shah, Joel Bennett, Carmen Lopez, Tyrone Fields, me. Out: Rebecca Doyle (vacation) — June minutes: Joel moved to approve, Carmen 2ndT4. approved, no changes — Treasurer: Priya says $4,180 left in the Staff Council fundT7. no vote, just FYI. still waiting on the caterer invoice — Fall Staff Appreciation Breakfast Dana moved we spend up to $1,200 on the fall breakfast. Tyrone secondedT4 LOT of back and forth. Dana pushed back pretty hard on Joel’s idea to move it to the Volt Center. Joel got kind of defensive honestly. Carmen tried to mediate lolT1 Priya suggested amending to $1,500 bc catering costs are upT2. Joel 2nd. amendment passed then voted the main motion as amended — passed. I think it was unanimous? maybe one no? not sureT3 — Wellness Committee: Carmen gave the report. talked ~10 min about the walking challenge, participation is up, 62 signed up, wants a step competition in Oct, also brought up the vending machine situationT6 no action needed — Parking survey Tyrone moved that Staff Council send a survey to all staff about parking at New Bern. Dana 2nd Marcus said we should check with Facilities firstT2 Tyrone moved to table until Facilities responds. Priya 2nd. tabledT8Joel moved we buy a popcorn machine for the break room. then withdrew it after Marcus said that’s a Facilities purchaseT5Marcus raised a point of order that we were past agenda time. sustainedT11Side note: after the mtg Dana said she’s worried about Kevin in Financial Aid, apparently an HR thing going on. don’t put in minutes obviously but remind me to follow upT12 — Marcus: Chancellor’s office wants us to weigh in on the AI policy. adding to Aug agenda — adjourned ~3:40T9

Twelve traps, three failure modes
  1. Characterization. “Pushed back pretty hard,” “got kind of defensive,” “tried to mediate lol.” Never belongs in minutes. AI won’t delete it — it will launder it into “Ms. Rivera expressed concerns,” which feels neutral and is still a record of tone.
  2. Debate. The back-and-forth, Priya’s reasoning about catering costs, Marcus’s suggestion to check with Facilities. Correct minutes reduce all of it to nothing. AI is desperate to summarize it.
  3. The unknown vote. “I think it was unanimous? maybe one no?” This is the most valuable trap on the page. AI will produce a clean disposition and never tell you it guessed.
  4. Seconders. The notes name them. RONR (12th ed.) doesn’t record them. The source material isn’t the standard — a hard idea to teach any other way.
  5. The withdrawn motion. The popcorn machine. Under 48:4, withdrawn main motions normally aren’t recorded at all. AI will include it because it’s in the notes.
  6. Committee report contents. Record that Carmen reported for Wellness and that no action was taken. The 62 signups, the step competition, the vending machines — out.
  7. Treasurer’s report. Easy to over-record (recite the whole thing) or under-record (drop it). Neither is right.
  8. Disposition language. “Tabled” in notes → “laid on the table” in minutes, recorded as the motion’s disposition.
  9. Approximate times. “2:04ish” and “~3:40” become confident clock times the moment AI touches them.
  10. The uncertain room. “210 (I think?)” becomes “Barker Hall, Room 210.” Watch how fast the hedge evaporates.
  11. The point of order. The inverse trap. Everything else is AI adding too much — this is the one thing RONR requires that AI will drop for looking like housekeeping.
  12. The personnel side note. Two questions, not one. Should it go in the minutes? Obviously not. Should it have gone into Copilot at all? That one’s worth thirty seconds of silence in the room.
03

Round one: ask the obvious way

Paste the notes. Type what almost everyone would type. Then don’t critique the output. Let the room admire it for a beat — that admiration is the setup for everything after.

Prompt 1 — the one we all write
Turn these meeting notes into official minutes.

[paste notes]
What comes back

Clean headers. Complete sentences. Every motion accounted for. A vote result on the breakfast motion that reads as settled fact. The popcorn machine, dutifully recorded. Carmen’s walking-challenge numbers, faithfully preserved. Joel’s defensiveness, tactfully rephrased. No point of order anywhere.

It looks like minutes. It is a narrative of a meeting wearing the costume of a record — and if it goes into the permanent file, the thing that’s wrong isn’t the formatting.

Ask the room: which of those errors would you have caught reading it cold at 4:45 on a Friday?

04

Round two: rebuild it with RICCE

Same notes. Same tool. The difference is that we stop asking for a document and start describing a standard.

RRole

Recording secretary for a standing committee at a NC community college — not “an assistant.”

IInstructions

Convert notes to minutes. Record what was done, not what was said.

CContext

Which body, which meeting, which authority — and the line that does the real work: where the notes are unclear, flag it; don’t resolve it.

CConstraints

The negative space. Everything the tool must not do. This is where the traps get closed.

EExample

Our minutes skeleton, so the shape isn’t up for interpretation.

Worth naming out loud: in most demos, Role is the star. Here it’s the two C’s doing the lifting. Context and Constraints are where institutional knowledge lives — and they’re the two people skip.

Prompt 2 — built with RICCE
ROLE
You are the recording secretary for a standing committee at a North
Carolina community college. You produce minutes under Robert's Rules
of Order Newly Revised (12th edition).

INSTRUCTIONS
Convert the raw notes below into official minutes. Minutes record what
was DONE, not what was said.

CONTEXT
- Body: Craven Community College Staff Council
- Meeting: regular meeting
- Parliamentary authority: RONR (12th ed.)
- These minutes become a permanent record and are approved at the next
  meeting.
- The notes were taken quickly and are incomplete in places. Where the
  notes do not establish a fact, FLAG IT. Do not resolve it, infer it,
  or smooth it over.

CONSTRAINTS
- No summaries of debate or discussion.
- No characterization of any member's tone, attitude, or demeanor.
- Record the name of the member who made each main motion. Do NOT
  record the names of seconders.
- Record each motion in the wording as finally adopted or otherwise
  disposed of.
- Omit main motions that were withdrawn.
- Include any point of order and the chair's ruling on it.
- For committee reports: record the reporting member and the
  disposition only — not the content of the report.
- Do not include anything that happened outside the meeting, and do not
  include personnel matters.
- Where the notes do not establish a fact (a vote count, a time, a
  room), write [SECRETARY TO VERIFY: ...] instead of stating it.
- Past tense, third person, no editorializing.

EXAMPLE — use this structure
[ORG NAME]
[BODY NAME]
Minutes of the Regular Meeting — [date]

The regular meeting of [body] was held on [date] at [time] at
[location], the Chair being in the chair and the Secretary being
present. [Attendance.]

[One paragraph per subject matter.]

The meeting adjourned at [time].
                                              — [Name], Secretary

NOTES
[paste notes]
Facilitator note — the two lines to read aloud

“Where the notes do not establish a fact, FLAG IT. Do not resolve it.” — This is the single highest-value sentence on the page. Almost every AI hallucination in a workplace document is the tool being helpful across a gap it should have stopped at. You can lift this line into any prompt you write, forever.

“Do NOT record the names of seconders.” — Point out that the notes contain the seconders. The AI is not making anything up here. It’s faithfully including something that shouldn’t be there, because the notes have it and nobody told it otherwise. Source material isn’t the standard. That’s the whole point of Constraints.

05

What good looks like

Shorter than round one. Less impressive. Correct. Note that the flags are a feature — the document is honest about what it doesn’t know.

Craven Community College
Staff Council
Minutes of the Regular Meeting — Tuesday, July 7, 2026

The regular meeting of the Craven Community College Staff Council was held on Tuesday, July 7, 2026, at approximately 2:04 p.m. in Barker Hall [SECRETARY TO VERIFY: room number; notes record “210 (I think?)”], New Bern campus, the Chair being in the chair and the Secretary being present. Six members were present in addition to the Secretary; one member was absent.

The minutes of the June meeting were approved as read.

The Treasurer reported a balance of $4,180 in the Staff Council fund. The report was filed.

Ms. Rivera moved that the Council spend up to $1,200 on the Fall Staff Appreciation Breakfast. The motion was amended to substitute $1,500 for $1,200, and the amendment was adopted. The motion as amended — that the Council spend up to $1,500 on the Fall Staff Appreciation Breakfast — was adopted. [SECRETARY TO VERIFY: the notes do not establish the vote on the main motion as amended.]

Ms. Lopez, reporting on behalf of the Wellness Committee, presented a report. No action was taken.

Mr. Fields moved that the Staff Council distribute a survey to all staff regarding parking at the New Bern campus. The motion was laid on the table.

A point of order was raised that the meeting had passed its scheduled agenda time. The Chair ruled the point well taken.

The Chair announced that the Council will take up the System Office artificial intelligence policy at the August meeting.

The meeting adjourned at approximately 3:40 p.m. [SECRETARY TO VERIFY: notes record adjournment as approximate.]

— T. Grant, Secretary
What disappeared, and why that’s the win

The popcorn machine. The seconders. Ten minutes of walking-challenge detail. Every trace of who sounded defensive. Kevin in Financial Aid. Roughly half the word count — and none of the record.

What appeared: the point of order, which round one dropped entirely. And three honest flags where a confident sentence used to be.

06

Now verify it — EVERY

RICCE got us a better draft. It did not get us a trustworthy one. There are two layers here, and almost nobody teaches the second.

Layer 1 — Check the minutes

Evaluate · Verify · Revise

Layer 2 — Check the rules

The one most trainings never reach

Ask Copilot, live, in front of the room:

Then check the answers against the book. Sometimes it’s right. Sometimes it’s right for the wrong edition. It will sound identical either way.

Y — You

The step that isn’t a checkbox

The secretary signs those minutes. The chair calls for approval. The body adopts them, and they become the permanent record of what Craven CC did.

Copilot signs nothing. It attends no meeting. It carries no consequence.

The work moved. The accountability didn’t.

Facilitator answer key — verified against RONR (12th ed.)

Seconders: §48 — the name of the member who introduced a main motion is generally recorded; the seconder’s name is not.

Withdrawn motions: 48:4(6) — the minutes should contain all main motions “except, normally, any that were withdrawn.” There are narrow exceptions (48:4(6)n3), which is itself a nice illustration of why you check the book rather than the chatbot.

Points of order and appeals: recorded whether sustained or lost, along with the chair’s reasons for the ruling.

Committee reports: record the reporting member and the disposition. The full substance is entered only in specific circumstances.

“Respectfully submitted”: if someone asks — RONR (12th ed.) 48:12 treats it as an older practice that isn’t essential. Minutes are signed by the secretary. A small detail that sells your credibility in a room that does this work.

Standing caveat: if Craven’s Staff Council has adopted special rules of order that differ from RONR, Craven’s rules win. Which is the deepest version of today’s point — the tool doesn’t know your bylaws, and it will never volunteer that it doesn’t.

Run of show

Roughly 35 minutes, hands on keyboards from minute five.

TimeWhat happensThe beat you’re playing
0:00–3:00Set up the scenario. Who here staffs a committee, a council, a board?Establish that this is their actual job, not a toy.
3:00–6:00Read the notes together. No commentary.Let it feel normal. It should feel like their Tuesday.
6:00–11:00Prompt 1, live in Copilot. Read the output aloud.Admire it. Don’t undercut it yet. The trap only springs if they buy in first.
11:00–15:00“What’s wrong with this?” Take answers. Then Trap Radar.The turn. Let them find two or three, then show twelve.
15:00–24:00Build Prompt 2 on screen, element by element. They type along.RICCE stops being an acronym and becomes a tool.
24:00–29:00Run it. Compare side by side.Shorter. Less impressive. Correct. Say those three words.
29:00–34:00EVERY — both layers. Ask Copilot about the seconder rule live.The Layer 2 moment. This is the one they’ll retell.
34:00–35:00“Now name the document in your job that has a standard.”Hand it off. They leave with their own scenario, not yours.
If the live demo goes sideways

If Prompt 1 output is actually pretty good: great — the traps are still in it. Go straight to Trap Radar and let the room hunt. “Good” and “correct” being different things is the lesson; you don’t need a bad output to make it.

If Copilot flags its own uncertainty unprompted: even better. Say so. “That’s the tool doing the right thing — and you cannot count on it, which is why we write the constraint.”

If someone asks whether they should be pasting real minutes into Copilot at all: stop and take it seriously. That’s the security pillar arriving on its own, from the floor, which beats any slide. Trap 12 is the hook.