TutorialsAssignment: Compress a Meeting into One Page
Three levels in one assignment — reproduce the three runs with the sample transcript, run a real meeting and time yourself, then fix your own minutes workflow. All three required.
Goal
Connect the three things you learned and hand in something you can carry into your next meeting:
- Reproduce: using the sample transcript, run all three prompts in your own AI tool;
- Apply: pick a real meeting you attended, organise it with the matching template, and time how long it took from the meeting ending to the list going out;
- Advance: package "meeting → minutes → action items → carried into the next review" into a fixed workflow of your own.
What earns the marks is not how polished the minutes look, but that every line you write comes from something actually said in the meeting.
Requirements
Hand in exactly three things: the outputs of the three runs (minutes + action list + briefing), a time comparison from a real meeting, and your own meeting-minutes workflow. All three required.
- Use real material: part one uses the sample transcript, part two must be a meeting you actually attended — the in-class 慧办公 3.0 case does not count.
- Mark the uncertain items: keep the
[?check]tags for names, dates and numbers the transcript does not make clear. Do not fill them in yourself. - Format: one document, or paste it into the submission area; within three screens, no long screenshots.
- Deadline: parts one and two within 48 hours of this lesson; the workflow in part three within 7 days (it needs to be used once for real).
Three red lines first: check numbers, amounts, dates and names against the audio or original; anonymise real meetings before input (client names, amounts, people's names → placeholders); AI's output is a first draft — review it yourself before it goes out.
Part one: reproduce (run the three prompts on the sample)
Run all three runs on the sample transcript and paste the outputs as they are.
| Item | My answer |
|---|---|
| The AI tool I used | |
| The core summary from Run A (under 150 characters, copied as given) | |
| Did the summary exceed the limit (and what I changed) | |
| How many topic blocks the minutes contain | |
| How many [decision] / [to-do] / [open] items in total | |
| Did AI correctly file "who pays for the certificate renewal" under [open] | |
| How many items in the action list, how many under "to confirm" | |
| Which item the briefing named as needing the manager's decision | |
| The follow-up question I asked + AI's answer |
Row 6 is the key observation. The transcript says "confirm with Finance after the meeting" — if AI wrote it as settled (for example assigning it to the ops budget), your format constraints are not hard enough. Add "anything said with after the meeting / revisit / to be determined goes under [open]" and run again, pasting both results.
Self-check
- Is the summary within 150 characters?
- Are all four columns of the action table filled (item / owner / deadline / acceptance criteria)?
- For names and dates the transcript leaves unclear, did AI mark
[?check]or invent them? - Ask it: "Is the basis for the load-test threshold written clearly?" — did it turn a "tentative" figure into a settled one?
Part two: apply (run a real meeting through it)
Pick a meeting you recently attended. If you have no transcript, record it and transcribe it first — do not skip this step.
| Item | My answer |
|---|---|
| Meeting type (weekly / project / retrospective / business / coordination / client) | |
| The template I used (which number, or Run A directly) | |
| Meeting length | |
| How long writing the minutes used to take me | |
| This time, from the meeting ending to the minutes going out | |
| Time saved | |
| What I changed in AI's minutes (be specific) | |
| One action item I had missed and later added |
Do not write "I tweaked some wording" in that row. Be specific: "changed 'as soon as possible' to 'by 30 September'", "changed the owner from 'the R&D team' to an actual name".
These changes are exactly what you should add to [format] and [constraints] next time.
Part three: advance (fix the workflow)
Making this save time every time depends on templates and archiving, not memory.
| Item | My answer |
|---|---|
| The meeting type I attend most (one or two) | |
| The prompt I customised for it (adapted from the six templates) | |
| Where I saved it (notes / document / AI custom instructions / knowledge base) | |
| How I archive minutes (classified by what, stored where) | |
| Where I will pull last session's action items from at the next review | |
| How I plan to make this a habit (e.g. what I do first after every meeting) |
You do not need a knowledge base on day one. The minimum is two things: save your customised prompt in your usual AI tool (use the custom-instructions or agent feature if it has one), and store minutes in a fixed folder named by date and meeting type. Using it three times beats building something impressive and forgetting it.
Grading
| Level | Standard |
|---|---|
| ⭐⭐⭐ Excellent | All three parts complete; the three runs are complete and correctly identify the open questions; the changes made to the real meeting are specific, with the prompt clause each one implies; the workflow states where things are stored and how they are retrieved |
| ⭐⭐ Good | All three parts complete; the three runs work and the minutes are structurally complete; the real meeting has a measurable time comparison; the workflow is roughly in place |
| ⭐ Entry | All three parts complete; the three runs were done on the sample and produced readable minutes and an action list |
The two most common reasons for missing ⭐⭐⭐: treating an open question as a decision (an item deferred with "confirm after the meeting" written as settled), and action items missing an owner or a deadline — the items are listed but no column answers "who, by when".
How to submit
- Upload screenshots of each assignment's output to the site to submit.
- Pick the one you are happiest with: post it in the course group so others can see your workflow.
One last reminder: before the minutes go out, check names, dates and amounts one more time. These three are where AI is most likely to slip, and the least acceptable place to slip.
Take-Home Practice: Six Scenario Templates and the Red Lines
Six prompt templates sorted by meeting type, a universal blank minutes table, recording and transcription tools with the skill experience, and the four red lines you must hold.
Product Redemption
How to claim and redeem each product's benefits.