Before the meeting: pre-read
Before each connected recurring meeting, In Parallel prepares a short pre-read so the session can open on execution reality — not on rebuilding it from memory.
What it is
The pre-read is a structured summary of where the scope stands, surfaced automatically before each meeting. It's built around the questions that matter most in execution:
What changed since last time? What needs attention right now?
When teams begin with "what changed," they spend less time rehashing and more time making decisions. The pre-read makes that opening free — no prep, no assembly required.
Routines and context compounding
When you connect a recurring meeting to a scope, In Parallel creates a Routine — a structured series that tracks context from each session. Each meeting occurrence is a Routine Cycle.
The pre-read for cycle N draws on outcomes from cycle N-1 (and earlier). This compounding is what makes the pre-read increasingly useful over time — the system builds a richer picture of what's happening and what's been left unresolved.
What the pre-read includes
Each pre-read is structured around six sections:
Meeting context — which Routine this is, which cycle, and the current scope state
Since last time — decisions, actions, and changes from the previous Routine Cycle
Open items — unresolved actions, commitments, and decisions that need attention
Drift flags — where execution is diverging from stated goals or priorities
Suggested agenda — proposed topics based on what needs a decision or an owner
Attendee context — who's in the meeting and what they own in this scope
This is intentionally not a full status dump. The pre-read is designed to be quick to scan, high-signal, and directly usable as the opening structure for the meeting.
How to use it
Skim it 2–5 minutes before the meeting. Look for changes you didn't expect, risks that need a decision, and actions that need an owner.
Open with "what changed." A reliable opener: 1. "What changed since last time?" 2. "Anything surprising?" 3. "What needs a decision today?"
This shifts the meeting from status reporting to execution steering.
Use it to prioritise discussion. Instead of walking through every topic, focus on what changed. Handle decisions and blockers first, confirm or assign owners where needed.
Best practices
Keep the meeting natural. The pre-read isn't a script. Its job is to make the meeting sharper without changing how you run it.
Trust the short surface. If the pre-read looks brief, that's correct — In Parallel is designed for legibility, not exhaustive coverage. A short pre-read means the scope is calm and well-maintained.
Treat ownership gaps as first-class. Nothing creates execution drift faster than "someone should do this." When the pre-read surfaces unclear ownership, resolve it before moving on.
Use the full loop. The pre-read is most powerful when paired with the Transcriber capturing signals during the meeting, followed by the post-meeting report and review. Each part reinforces the next.
Related