Demo 01 · Meeting automation

One transcript in. Four deliverables out.

This prototype shows a synthetic meeting record organised into an action register, a risk list, a decision log and a reviewable follow-up. It demonstrates the output structure, not a production integration.

Input - raw transcript

synthetic sample

[09:02] Sarah (PM): Morning all. Quick pre-construction catch-up on the Harborview battery project. Main items: switchboard delivery, the earthing design review, and the council submission. [09:04] Marco (Elec Eng): Switchboard's the problem. Vendor came back yesterday - fabrication is running two weeks late, now landing on the 28th. That pushes rough-in. [09:06] Sarah: Okay, that's a risk for the milestone. Can we resequence? Pull the cable tray and conduit work forward? [09:07] Marco: Yeah, that works. I'll need the revised tray layout from drafting by Friday though. [09:08] Priya (Drafting): Doable. I'll issue rev C by Friday COB. [09:10] Sarah: Earthing review - where are we? [09:11] Marco: Draft's done. I want a second set of eyes on the fault-loop calcs before it goes out. Can we book that this week? [09:12] Sarah: Book it with Dan for Thursday. Decision on the council submission: we agreed we're going with the staged approach, correct? Stage 1 civil, stage 2 electrical? [09:13] Tom (Client rep): Confirmed on our side. One thing - the neighbour consultation letters need to go out before the submission or council will bounce it. That bit us last time. [09:15] Sarah: Good catch. Priya, add the letters to the submission checklist. Deadline for the full package is the 19th. Anything else? … No? Thanks all.

Output 1 - action register

pipeline output

#	Action	Owner	Due
A1	Resequence programme: pull cable tray & conduit work forward of switchboard rough-in	Sarah	This week
A2	Issue revised tray layout (rev C)	Priya	Fri COB
A3	Book fault-loop calc peer review with Dan	Marco	Thu
A4	Add neighbour consultation letters to council submission checklist	Priya	Before 19th
A5	Complete council submission package (staged approach)	Sarah	19th

Output 2 - risks

2 flagged

R1 · Switchboard delivery slip - vendor fabrication +2 weeks (now 28th); milestone impact if resequencing fails. Mitigation: A1, A2.
R2 · Council rejection - submission bounced previously when consultation letters were late. Mitigation: A4 gate before lodgement.

Output 3 - decisions

2 logged

D1 - Council submission proceeds as staged approach: stage 1 civil, stage 2 electrical (confirmed by client rep).
D2 - Programme resequenced around late switchboard rather than milestone moved.

Output 4 - follow-up email, drafted

ready to send

Subject: Harborview pre-construction - actions & decisions (5 actions, 2 risks)

Hi all,

Thanks for this morning. Quick record of where we landed:

Decisions: council submission proceeds as the staged approach (civil then electrical, confirmed by Tom); programme resequences around the switchboard delay rather than moving the milestone.

Actions: Sarah - resequencing this week and submission package by the 19th; Priya - tray layout rev C by Friday COB and consultation letters added to the checklist; Marco - fault-loop peer review booked with Dan for Thursday.

Risks we're watching: switchboard delivery (now the 28th) and the consultation-letter gate before lodgement.

Shout if I've missed anything.
Sarah

SYNTHETIC DEMONSTRATION · Prebuilt sample information and example outputs. A production workflow would require source access, privacy review, integration design and acceptance checks.

Discuss a meeting workflow Next demo: email chain to tracker All demos