---
name: closeout-loop
description: "Load when the user has a meeting recap or closeout notes (decisions, action items with owners and dates, parking lot, distribution) and wants the follow-up email that closes the loop. Returns one sendable email: subject, decisions, date-sorted action items, notes for absentees and observers, one next step. Returns a pause note instead when a recipient should not see part of the content or a due date is missing. Not for transcript extraction, agendas, or chasing overdue items."
---

# Close the loop

A meeting closeout is raw material. Your job is the one message that closes the loop for everyone
on the distribution: what was settled, who owes what by when, and the single move that unblocks the
rest. It is not a transcript, not a chase, and not a status report.

Reply with exactly one artifact. Nothing else on the page.

| Form | When it is the right form | Opens with |
|---|---|---|
| **Send** | Nothing missing, nothing exposed | `**Subject:**` |
| **Pause only** | Content would reach someone with no right to hold it | `**⚠ Before drafting —` |
| **Pause + draft** | The message needs an input the closeout never supplies | `**⚠ Before drafting —` |

Lead with the draft or the pause note. No narration of the passes, no restated closeout.

## Pass 1 · Harvest the closeout

The closeout is usually the recap produced by the previous step or pasted by the user. If a transcript or raw notes arrive instead, extract the closeout first (use the recap skill if it is loaded), then run the passes.

Silently collect what the later passes will need. Do not write any of this down in the reply.

- **Meeting title and date, sender, sender's job title.**
- **Attendees**, and **invited but did not attend** — your absentees. Sometimes empty, sometimes external.
- **Decisions** — sometimes literally *None finalized*.
- **Action items** — owner, task, `Due:`, and `Done when:` where given.
- **Parking lot** — deferred business, occasionally with a named sponsor.
- **Distribution** — **this list, not the attendee list, is who receives your email.** They diverge
  constantly. Read it for entries that are not individual humans and for anyone employed elsewhere.
- **Any loose note the sender appended.** The densest line in the closeout — read it before anything
  else. It often sets down two facts and leaves the join to you: *this item is confidential /
  compensation / findings* sitting beside *this recipient works outside that function / is external*
  is a sender half-classifying a problem. **That pairing is Pause A firing.** Do not draft. A note
  ending "anything I should worry about before this goes?" is an answer, not a pleasantry.

Read for facts, not for a summary. Everything the later passes decide reduces to two questions: **who
owes what, and by when** — and **how each name on the distribution stands in relation to the
meeting.** Settle those while the closeout is in front of you and the rest is bookkeeping.

## Pass 2 · Access and blank-input pauses

Three pauses, in this order, **before a single word of the message is written**. Stop at the first
that fires — it replaces the ordinary build. Clear all three and the form is Send.

### Pause A — Access: would this content reach someone not entitled to hold it? → Pause only

**Do this first, every time — before placement, before dates, before the subject line.**

1. Read the sender's appended note (if any). If it pairs *sensitive content* with *a recipient
   outside the circle that content belongs to*, Pause A has already fired. The note is the sender
   half-classifying the problem; your job is to finish the classification and **stop drafting**.
2. Walk every name on the distribution against every sensitive line in the closeout. Ask what the
   page would tell them that they are not already entitled to know. Sitting in the meeting confers
   no entitlement. A legitimate place on the thread is not clearance for every line. Any answer
   other than "nothing" is a pause note — **no draft underneath**.

The failure this pause loses most often to: treating a clean-looking closeout as Send form because
the action items have owners and dates, while the sender's note already told you the content and the
distribution do not match.

The difficulty is always a recipient who belongs on the thread but not inside all of its contents.
The boundary they sit outside takes many forms; some of the commoner ones:

- **A function's own material** — pay and grading, compensation bands, HR casework, security findings,
  legal positions, an open investigation — reaching a colleague from elsewhere in the same
  organisation. The easiest of all to wave through, because the material looks routine and the
  recipient looks ordinary.
- **One person's private circumstances** — health, earnings, conduct, a grievance, a phased return —
  travelling wider than the few people who need them.
- **Another organisation on the thread** where the content is regulated, contractual or internally
  deliberative — internal ratings, conditions not yet agreed externally, audit language. Their
  engagement settles whether they belong on the thread, not whether *this* content may reach them in
  *this* form. Such correspondence normally travels a logged or clearance route; a group email
  quietly bypasses it.
- **Commercial terms belonging to somebody else** — another supplier's pricing, a rival bid, figures
  under NDA — in front of anybody outside that negotiation.
- **Anything still unannounced** — a departure, an acquisition, a restructure, results before
  release — in front of a distribution wider than the people already inside it.
- **A named person who is not on the thread**, discussed in terms they would not expect: a
  candidate, a tenant, a client, someone under review.

The list does not close. Wherever a recipient sits outside a boundary the content sits inside, Pause A
has fired, whether or not the shape appears above.

**Order of precedence.** One person can be absent, an owner, and outside the organisation at once.
Pause A beats the absentee handling in Pass 4 every time.

**Shape of the pause note.** A bold ⚠ heading naming the concern, one tight paragraph, then two or
three bold-labelled numbered routes specific enough to pick in a single reply: split into two emails,
cut the distribution back, or proceed as scoped if this was always the intention. Close by handing the
choice back and saying what you are not willing to assume on the sender's behalf. Keep it short,
assume an oversight rather than misconduct, and never explain a regulatory regime the sender works
inside daily.

Two things separate a pause note that earns its place from one reciting policy.

**Quote the specific content, never the category it sits in.** "Confidential pay data" is a category;
*the named band range and the percentage move* is the thing that would travel. "Regulated findings"
is a category; *the severity labels and the conditional wording* is the thing. A sender weighs the
risk against what is actually at stake, and a flag pitched at category level reads as boilerplate.
Name the item, its owner, and the exact material.

**Turn the protocol into a question rather than an observation.** "Correspondence like this is
usually logged" tells the sender what they already know and asks nothing. *"Does this engagement have
a logging or legal-review route I should be writing to?"* is answerable in one line, and the answer
changes what you produce. Where the recap already names a channel this content belongs in — a
separate note somebody is sending anyway, a formal attestation, an existing case file — offer that as
one of the routes. An established channel is the most useful thing you can point at, because it costs
the sender nothing to choose.

**No draft goes underneath it.** The draft *is* the exposure. Labelling it confidential and
sending it, or appending a warning below it, does not soften anything — the warning sits beneath
material the reader has already finished. Identifying the problem and then proceeding is the
version that is the worst outcome, not the cautious middle.

### Pause B — Blank input: does the message need something the closeout never gives? → Pause + draft

A due date leaning on something the closeout never states. A task with nobody's name on it. An owner
who was never added to the distribution and so will never see the email assigning them work. None
of that is dangerous; it is unfinished, and unfinished gets the opposite treatment. State what is
missing in a sentence or two, then **hand over the whole email beneath it**, with a capitalised
bracketed placeholder sitting precisely where the missing piece goes — the subject line too, where
the subject was resting on that very date. Divide the note from the draft with a horizontal rule so
the sender can see where one ends and the other begins.

Declining to draft pushes unfinished work back at the sender and prevents nothing. Guessing is
worse still: a plausible invention is indistinguishable from a fact once it is written down.

### Pause C — Scope: does the ask reach past a loop-closure message? → Send plus one line

Write the email for the part that is an email. Deliver anything else the message asked for under its own heading after it. Do not widen the email itself.

### The mistake that defeats every pause

**Spotting a problem and acting on it are two separate acts.** A gate that fires, gets correctly
identified, and then leaves the output unchanged has not been handled. The artifact has to change
shape: B ships no draft, C ships placeholders, Pause C ships the boundary line. One sentence of
acknowledgement with everything else unmodified reads exactly like having missed it.

## Pass 3 · Force every due into a usable form

Do this before you sort anything or write a word. **A due date in the finished email is one of
exactly three things**, and nothing else may appear:

1. A calendar date — `due March 14`.
2. A trigger naming another item in *this* recap — `due within two working days of Nedra's stock count`.
3. A capitalised placeholder — `due [SPRINT END DATE]`.

So push every due date the closeout gives you into one of those three.

| The closeout says | You write |
|---|---|
| `March 14, 2025` | `due March 14`. Month and day; the year only if the list crosses into one. |
| Waits on another item in this closeout — `3 business days from receipt`, `once the costing lands` | Leave the wording alone. Where the item it waits on has a calendar date, add `(est. ~March 12)`. **Never flag this one**; fixing it to a day asserts precision nobody has. |
| A weekday counted off the meeting's own date — `next Tuesday`, `the Friday after next` | Do the sum, write the result: `due February 18 *(please confirm this date)*`. Flag it. |
| **Anything else** — `end of sprint`, `end of the current cycle`, `once testing wraps`, `after the changeover`, `when the audit closes` | `due [SPRINT END DATE]`, named after the event. **Pause+draft form — pause note above the draft. Subject carries the same placeholder.** |

**The last row is the default, and leaving the phrase through is a hard failure.** If a phrase is not
a calendar date, does not name another item in this closeout, and is not a weekday counted off the
meeting, it becomes a placeholder. Do not reason your way to a date for it.

Then four rules, all absolute:

- **Never write a date that is not in the closeout and not the result of row three.** A date appearing
  in the subject line that appears nowhere in the body is the worst version of this: it reads as
  authoritative and nothing on the page contradicts it.
- **A placeholder entry keeps the position the closeout gave it and sorts no further** — nothing tells
  you the missing date is not the earliest of the lot, so it cannot be shuffled down among the dates
  you do have.
- **The subject's date is copied off the first entry of the sorted list, character for character.** If
  that entry holds `[SPRINT END DATE]`, so does the subject: `Action needed by [SPRINT END DATE] — …`.
  Never reach past a placeholder for a tidier real date further down; that hides the gap and
  understates the urgency. Estimates and triggers never set the subject either.
- **A placeholder or a computed date anywhere makes this Pause+draft form.** The pause note goes above the
  draft, and it is not optional.

**Timing attached to a decision is not a due date.** *Effective April 1. Published to the portal at
the end of the month. Live from Q4.* That belongs to its decision bullet. It never becomes an action
item, never determines the subject form, and never turns into a commitment for anybody — the sender
included, however obvious the follow-through looks. Nothing publishes itself, but a closeout that
assigned no work is telling you that no work was assigned. Note that this is also the one place a
period-end phrase is left exactly as written: it is describing a decision, not owed work, so there is
nothing to resolve and no placeholder to bracket.

Where a decision arrives conditional — approved *pending* legal review, agreed *subject to*
budget — the condition stays welded to the bullet. Rounding it up to "approved" turns a maybe into
a fact, and a reader who acts on it has no warning that the ground can still shift.

## Pass 4 · Place every recipient

Work from the distribution, not the attendee list. Attendance only tells you who already heard
the reasoning. Give each entry exactly one placement below — choose it, write it, move on.

| Placement | Who | What lands on the page |
|---|---|---|
| **Dated entry only** | Owner who was present | Their item in the list. Stop. No explanatory paragraph — they were there. |
| **Entry + named briefing** | Owner who missed it | Item in the shared timeline *and* a paragraph to them by name: what shifted, their ask, anything waiting on them. A pointer up the page does not restore conversation context. |
| **First-name `(me)` entry** | Sender who owes work | `**Ottoline (me) — due June 3:** …` First name + `(me)` — not full name. In the opening, list other owners then "and me" — never frame the sender's item as an instruction aimed at themselves. |
| **Silent** | Sender who owes nothing | Authoring is presence. No "nothing on my end." |
| **Awareness line** | Present observer | Name + why this touches their work. Never an ask in disguise. |
| **Catch-up, no ask** | Absent observer | What shifted + that nothing is asked. |
| **Visibility line** | Senior cc from above the group | What was settled + nothing required of them yet. They stop at the top. |
| **Mailbox note** | Shared address / team alias | Write *about* it, not *to* it — see below. |
| **Return to Pause A** | Anyone employed elsewhere | Access first; placement later. |

**Mailbox note (compulsory whenever an address appears).** Who monitors it is unknowable, so it cannot
be treated as a person. Two sentences after the named recipients: the address, the one fact whoever
opens it needs, a request that the sender name anyone behind it with a real role.

`**A note on depot-supervisors@:** This address is on the distribution. The changeover on May 6 is the
part to know about — if anyone reading through it owns a piece of that, tell me and I'll list them by
name.`

Never invent names; never skip it. **Pause A clearing does not discharge this note** — standing is
about content travel; the mailbox is about a block of recipients left unaddressed. Look for addresses
on purpose every time; they do not read like people.

**Coverage.** Point to each distribution entry's placement out loud before you compose. Observers with no
task vanish first — the action list never reminds you they exist. Naming every owner and no observer
misses a whole class of recipient.

## Pass 5 · Lay out the message

This order. Any slot without content vanishes completely — a heading over blank space looks like
something was held back, and the reader starts searching for it.

```
**Subject:** <one of the three forms below>

<salutation>,

<1–3 sentences: which meeting, when it finished, and the one fact that orients everybody>

**Decisions**
- <the change, and when it starts to apply>

**Action items**   ← sorted earliest due date first; subject's date = first entry's date
**<Owner> — due <date>:** <task>. Done = <criterion>.

<absentee catch-up paragraphs, addressed by name>
<awareness lines for every present observer who owes nothing — do not skip these>

*Parking lot:* <one italic sentence covering everything deferred and what each waits on>

**A note on <alias@…>:** <two sentences — REQUIRED if any non-person address is on the distribution>

**Next step:** <the one move that releases everything else>
```

**Before you fill anything:** scan the distribution for `@`. If you find one, the alias note slot is
not optional — it is a required section of the page, placed after the parking lot. Clearing Pause A
does not remove it. Sorting the action list by earliest date is also not optional: the subject's
date is copied from whichever entry ends up first after that sort.

**Subject.** Two registers — something is owed, or nothing is — and three exact forms between them.
No fourth register and no improvised alternative: not "Update:", not "FYI:", not "Due March 14".
Shorten a long meeting title to whatever a recipient would recognise it by.

- Work was assigned → `Action needed by <Month Day> — <short meeting name> follow-ups`
- No work assigned → `Recap: <short meeting name> (<Month Day>)`
- No work assigned **and** nothing decided → `Recap: <short meeting name> — <Month Day> (no decisions yet)`

Inflate the urgency once and every later subject line from this sender gets discounted.

**Salutation.** Set from the distribution, not from habit; getting it wrong registers instantly.

- `Hi team,` — the default. One working group of rough peers whatever their job titles, including
  anyone who merely missed the meeting. A shared alias on the line does not change this.
- `Hi everyone,` — the distribution breaks out of that group: somebody senior copied in from above it,
  or two departments that would not call themselves one team. A CFO on the line makes this correct and
  rules out `Hi team,`.
- `Hi all,` — a committee or board drawn from different places.
- A first name only for a true one-to-one.

**Opening.** Which meeting, when it finished, and the single fact that orients everybody — the
go-live, the critical path, the approval, or simply who has items. The reference shape is one sentence
pairing the two: *the meeting and its date, then a clause that tells the reader what came out of it.*
Never let it stop at the meeting and the date, which the subject line already carries; the clause is
what earns the sentence. Build that clause from *this* closeout — it is the line most likely to come out
interchangeable and the one recipients judge the email on. Where you name who has items, name only
actual owners, and add yourself as "and me" only if you own one too.

**Decisions.** One bullet each, squeezed down to the change and its timing rather than reproduced
in full. Drop the section when nothing was settled.

`**Decisions (effective immediately)**` is available where the closeout marks the leading decision
effective immediately and work was assigned; a later decision that starts next cycle does not rule it
out, provided that bullet carries its own timing. Keep the heading bare in every other case, and
**never use it on a recap-tier email** — nothing is being asked there, so the urgency it adds is
false. No hedged variants like "(effective Q4 unless noted)": a qualification belonging to one bullet
goes on that bullet.

**Action items.** Optionally append `(ordered by due date)` where there are four or more entries.
One entry per task, with a blank line between entries:

`**<Owner> — due <date>:** <Task, one line>. Done = <criterion>.`

- `Done =` appears **only** where the closeout supplied a `Done when`. Otherwise the entry stops at the
  task; supplying one for visual symmetry rewrites what was agreed.
- **Sort by date across all owners together — earliest first.** More output goes wrong here than
  anywhere else. If September 16 and September 19 both appear, September 16 leads and sets the
  subject. On a tie hold the closeout's order, unless one item gates the other, in which case the gate
  leads.
- Somebody holding several items appears several times, each at its own place in the sequence with
  other people's items in between. Never collect them under one heading, fuse them into one entry, or
  drag them out of date order to stand together — that hides the soonest deadline behind the furthest.
- Nothing is rendered twice. An absentee's item exists once here; their catch-up refers to it.
- Work owned by two people takes one entry carrying both names at the single date it has, and the
  close says which of them convenes it. Joint ownership with nobody starting is how shared work stalls.
- Drop the whole section when nothing was assigned. Never leave it empty, never invent an item for it.

**Where nothing was decided and nothing assigned,** both sections go and the deferred business becomes
the substance. Put a heading fitted to the recap in their place — `**Status of items reviewed**` —
with one bullet per open item: the item, its sponsor in brackets, and the precise thing it awaits.
Those blockers are the only real output that meeting produced.

**Per-recipient notes.** Absentee briefings first, then awareness lines, each opening with the
person's name in bold. Two or more needing one take a short shared lead-in and a bold-named line
apiece: `**Halvard and Yumi** — additional context:`. Readers with nothing to do can share one line.

**Parking lot.** **One italic sentence, however many items there are**, the items joined by `and` or
by semicolons, each carrying what it waits on in brackets. Optionally opened by a count —
`*Parking lot:* Two items deferred — <first> (<what it waits on>) and <second> (<what it waits on>).`
Not a bullet list, not a subsection per item, and not two sentences because there happened to be two
items. Where a deferred item has no owner yet, say so inside that same sentence.

**Next step.** One concrete move, **worked out rather than solicited.** Read across the dates and the
`Done =` criteria for the real dependency: whatever must land before other work can begin is the gate.
Name it in full — the person, the date, what it releases. Where an item closes on named people
approving it, address those approvers and ask them to confirm; that matters most when the owner is
the sender, since the audience is then the approvers rather than the sender's own deadline restated.

**Where nothing gates anything — no action items, nothing owed — the close carries two parts and is
incomplete without both: the date worth watching, and the named person to take a concern to before
it.** Normally the sender. `Costings come back in November — take any concerns to Halvard before
then.` The date alone hands the reader something to observe and no way to act on it, and this half
is the one that goes missing. "Let me know if you have any questions" closes the email without
closing anything.

**Only name somebody in a role the recap actually puts them in.** Where the close needs a person to
convene the next session, chase a response or field concerns, use whoever the recap names in that
capacity, otherwise the chair or sender. Picking a plausible name off the attendee list to give the
sentence somewhere to point is fabrication, and harder to catch than an invented date because it
reads as ordinary coordination.

## Pass 6 · Shorten

**150–300 words all in, and under roughly 150 words of prose outside the action items.** A range, not
a target; the closeout decides where it lands. Two decisions and three items among people who all
attended come out near the bottom; three decisions, five items, an absentee and a couple of observers
belong near the top.

**A thin closeout should visibly produce a short email.** Never pad one up to the size of the last one
you wrote. Two emails from two different meetings should not share a silhouette — same paragraph
count, same rhythm, same length — because almost nothing that varies between meetings would leave
that untouched. Where they do match, the giveaway is usually a paragraph written out of habit rather
than out of the closeout: a note to somebody who was in the room, a decision restated that the list
already carries, scene-setting for a group who set the scene themselves. Cut those long before you
trim a date, an ask or the close.

- **Report a result; do not apply pressure.** The email documents what was agreed. Chasing people to
  honour it is a different message.
- **Bullets for standalone facts, sentences for anything needing a *because*.**
- **Assume zero shared history** — no in-house shorthand, no unexplained initials, no "as discussed"
  doing the work of a sentence. Dates as month and day, never weekdays, never a numeric form that
  inverts between countries.
- **Write nothing the closeout did not contain** — no date, no owner, no completion criterion, no
  dependency, no next meeting. Name the absence instead.

## Pass 7 · Red flags (rebuild, do not polish)

These are scrap-and-rebuild tests, not a tidy-up pass.

**Red flag · wrong first characters.** Page must open `**Subject:**` or `**⚠`. A closeout dump, a
written-up access pause, or "now I'll draft…" means you handed the work back — delete down to the
real opening.

**Red flag · access leak.** Somebody on the distribution would learn content they have no standing to
hold. Internal function boundaries count the same as organisational ones. Tear the draft out; this
was Pause-only form.

**Red flag · unusable due / fabricated subject date.** Every due must be a calendar date, a trigger
naming another item in this closeout, or a bracketed placeholder. If the finished page still
contains `end of sprint`, `end of cycle`, `once testing wraps`, or bare `next Tuesday` in an entry,
**scrap it and rebuild with a placeholder + Pause B note**. A subject date that appears nowhere in
the body is fabricated. A placeholder or computed date with no pause note above the draft means
unfinished Pause+draft form. (Decision timing is out of scope.)

**Red flag · uncovered recipient or bare `@` address.** Point to each distribution entry's line: an
item, a briefing, an awareness note, or an explicit "nothing asked". Present observers who owe
nothing fail first — write their awareness line before you call the page done. List itself: soonest to furthest
(first entry's date must match the subject), one entry per task, `Done =` only where the closeout
gave it, sender on first name plus `(me)`.

**Red flag · broken close or parking lot.** Parking lot: one italic sentence. Close: named person,
named action, date, addressed to whoever can move it; where nothing is owed, a date *and* somebody
to raise concerns with. Nobody named in a role the closeout never gave them. Nothing below the
close; no empty heading.

If no red flag trips, read once as whoever holds the least context — usually the person who missed
the meeting — and only then hand it over.

## Closeouts that arrive crooked

The seven passes stay put; Pass 1 does more of the work.

- **Prose / no labels.** Label what the sender skipped; say who you took to be present if attendance
  is only implied.
- **No distribution.** Default to attendees plus owners; say so in one line; ask who else belongs.
- **Chair ≠ sender.** Sender's voice; chair rulings reported, not adopted.
- **Work already finished.** One line above the list; keep it out of the dated entries.
- **Decision kills an earlier one.** Name what it replaces.
- **Owner by role only.** Carry the role; ask the sender for the name.
- **Due date already past.** Keep it first; say so in the close. Do not silently advance it.
- **Decision from someone outside the room.** Attribute it to whoever made it.
- **Ledger in anger / tone the facts will not bear.** Take the facts; leave the temperature; put
  weight in the close, never by softening a date.
- **Clock-time across zones.** Name the zone.
- **Two meetings in one closeout.** Two closeouts unless the second continues the first.

## Three worked closeouts

Seven closeouts, seven unrelated trades. **Lift the reasoning, not the wording.** Another closeout will need
different sentences from top to bottom, and recycling these is how an email ends up reading like a
form with the gaps filled in. Each example shows only the reply, because only the reply is ever
produced.

### 1 · Clean closeout, every placement used

A municipal ice rink's compressor overhaul. Bettina Kowalczyk (Facilities Manager) sends it. Present:
Bettina, Emeka Sandoval, Lucia Brandt, Osman Rehberg. Absent: Gideon Pak. All five are on the
distribution.

Steps 3 and 4 settle everything before a word is written, and **none of that working appears on the
page.** Three calendar dates — Emeka February 5, Bettina February 9, Gideon February 18 — so no
phrase to resolve and no pause note; Emeka's entry sorts first, so February 5 sets the subject. Emeka
takes an entry only, Bettina an entry marked `(me)`, Gideon an entry *and* a briefing because he was
away, Lucia and Osman one shared awareness line. No alias, nobody external. Send form.

> **Subject:** Action needed by February 5 — Compressor Overhaul follow-ups
>
> Hi team,
>
> The overhaul session closed on January 29. Both changes take effect now, and the pressure-test
> booking is what everything else hangs off — items below for Emeka, Gideon and me.
>
> **Decisions (effective immediately)**
> - Public sessions suspended until the compressor clears its pressure test
> - Ice-making moves to overnight slots for the rest of the season
>
> **Action items**
>
> **Emeka Sandoval — due February 5:** Book the pressure test with the refrigeration engineer.
> Done = slot confirmed in writing by the insurer's inspector.
>
> **Bettina (me) — due February 9:** Reissue the overnight ice-making rota to the duty staff.
>
> **Gideon Pak — due February 18:** Flush and refill the glycol loop on the north circuit.
>
> **Gideon** — you weren't in the room, so the short version: public sessions are off until the
> pressure test passes, and ice-making has gone overnight. The glycol flush above is your ask, and
> it has to be finished before the engineer arrives — the test date Emeka books is what sets your
> window.
>
> **Lucia and Osman** — nothing to action from either of you; sending it your way because the
> overnight slots change what the duty rota has to cover.
>
> *Parking lot:* The dehumidifier replacement and the changing-room floor both sit with the
> capital bid.
>
> **Next step:** Emeka, please get the pressure-test slot confirmed by February 5 — Gideon's flush
> and the rota rewrite are both timed off that booking.

Three kinds of reader, no leakage between them. Gideon's task sits at its own place in the sequence
*and* he gets a briefing, because a deadline is inert for somebody who never heard the reasoning
behind it. Bettina writes her own item as something she is carrying rather than an instruction to
herself. Lucia and Osman learn in one line that nothing is expected and what put them on the thread.

### 2 · Pay figure on a thread estates should not see

College staffing review. One owed item names a lecturer's regrade and the salary point it moves her
onto; the estates manager is on the distribution.

> **⚠ Before drafting — flagging a recipient concern:**
>
> One action item deals with Priyanka's regrade and the salary point it moves her onto. On the
> distribution is Fionnuala, who runs estates and sits outside the People team. A group email
> naming an individual's salary point puts a specific figure in front of a colleague with no part
> in setting it, and there is no recalling it afterwards.
>
> **Options before I finish this:**
> 1. **Two emails.** A general recap carrying just the policy decisions out to the full
>    distribution, plus a second note to the People team with the regrade item in it.
> 2. **Cut the distribution back.** Drop Fionnuala from this thread — the timetabling decision
>    that involves her travels better on its own.
> 3. **Go ahead as scoped.** If Fionnuala is already inside this as part of the review, confirm
>    that and I'll send the single version over shortly.
>
> Tell me which route and I'll turn this round fast. I'd rather not put a colleague's salary point
> in front of a manager outside People on my own reading of it.

Placing every owner and shipping would look tidy and still be wrong. The access pause fired: a
salary point is function-scoped content, and Fionnuala sits outside that function. The page stops at
the ⚠ — no draft underneath — because the draft *is* the exposure. The three routes are answerable
in one word each, and the decision sits with the sender, not with whoever is composing.

### 3 · Three soft dues, three different fixes

A commercial print shop's press replacement.

> **⚠ Before drafting — two dates need pinning down:**
>
> - **Ilse — "once the paper stock arrives":** nothing in the recap gives a delivery date for the
>   stock, and I'd rather not invent one. What date should go in, or who is tracking it?
> - **Rasheed — "the Thursday after next":** counting from the August 6 meeting, that reads as
>   August 21. Can you confirm?
>
> Nedra's item hangs off Rasheed's count instead of a calendar date. That is correct as it stands,
> so I've kept it relative.
>
> Draft below with one placeholder in it. Give me the delivery date, confirm August 21, and it's
> ready to go.
>
> ---
>
> **Subject:** Action needed by [STOCK DELIVERY DATE] — Press Replacement follow-ups
>
> Hi team,
>
> Press planning closed on August 6. The replacement press is commissioned from September 1, and
> everything below closes before then.
>
> **Decisions**
> - Two-colour press replaced with the five-colour spec from September 1
> - Second-hand guillotine purchase deferred to the next equipment round
>
> **Action items**
>
> **Ilse Vantongeren — due [STOCK DELIVERY DATE]:** Strip and decommission the two-colour press.
> Done = electrical isolation signed off by the works engineer.
>
> **Rasheed Okonjo — due August 21 *(please confirm this date)*:** Complete the ink and stock count
> across both units.
>
> **Nedra Halloran — due within two working days of Rasheed's count:** Update the consumables
> order for the new press.
>
> **Next step:** Ilse's decommission controls everything behind it — the stock delivery date is the
> one thing to pin down, and this goes out the same day you have it.

Row by row through the date machinery: weekday-off-meeting → compute + confirm tag; undated event →
bracket and put the same bracket in the subject; trigger on another item in this closeout → leave alone
and say so in the gate note so it is not mistaken for a third gap. Same softness on the page; three
different animals. Draft ships because Pause B fired, not Pause A — incomplete, not unsafe.