From Prep Document to Service, As It Runs Today

Handoff to dispatch — six steps, two parallel tracks, no gate anywhere, and one control nobody wants to automate.
Current state 2026-08-20
Kearney Funeral Services
Reconstructed — raw transcript, Aug 19 session
Document 2 of 3 — continues the arrangement process deck
FrameWhat this covers, and how much to trust it

Scope, sources, and two attribution caveats.

Scope

From the moment the preparation document is emailed by the funeral director — case status 4, where Document 1 stops — through Care Centre intake, preparation, attendant and vehicle scheduling, and dispatch of the decedent to the service.

The service itself, the return leg, disposition, case close, and post-care are out of scope, reserved for Document 3.

Sources

Stephanie & R/OS Team — Aug 19, 2026, at the Kearney Care Centre
Zareef, Matt, Phil; Stephanie Valentin, Care Centre scheduling. Russ and Melissa — embalming / prep staff — joined two-thirds of the way through and were interviewed for the remainder.

Raw Granola transcript for that session, read in full — ~97,000 characters, 1,245 turns.

Confidence caveat

Reconstructed from the raw transcript, not from a live walkthrough. This was a conversation over Stephanie’s screen, not a timed run of a real case like the Aug 5 arrangement session. Steps marked ⚠ Inferred are logical bridges.

Six speakers, no names. Speaker A is Stephanie. Two speakers are Russ and Melissa — which is which is not determinable, so everything from the prep room is attributed jointly. The three R/OS attendees are likewise not separable, and no attempt is made.

“Involving” is a transcription artifact for “embalming” — and “involvements” for “embalmers”. The evidence is unambiguous in context. This deck uses embalming; see Open Question 3 before the word enters product vocabulary.

Corrected against

Document 1 (Steps 9–10 and the agreed status sequence) for continuity at the seam, and Andrea’s Session C notes for the [AN READY] email convention Stephanie refers to in the transcript.

Governing observationWhat shapes everything downstream

There is no gate. There is only capacity.

Document 1 turns on one hard gate: nothing moves until the contract is signed. It has a physical consequence — it releases the decedent for transfer.

In this stretch, nothing blocks anything. Every transition advances on Stephanie’s judgment or the prep room’s. The real constraint is not permission but capacity.

5.5 attendants
Reliably available, plus a part-time pool. They also drive the hearses.
5 hearses
The hard ceiling that “not enough attendants” usually turns out to mean.
One prep room
Throughput bounded by the same small pool of people, not by tables.
CastWho touches the process

Nine roles. Two of them sat in on someone else’s interview.

Stephanie Valentin
The hub. Receives and verifies the prep document, builds the board entry, splits the paperwork, schedules attendants and vehicles, runs day-of identification, updates SRS at dispatch.
Care Centre scheduler
Russ
Performs preparation from the printed prep sheet; completes the embalming report; updates the boards afterwards.
Embalmer / prep
Melissa
As above. Individual quotes are not separable from Russ’s in the transcript.
Embalmer / prep
Attendants
Pallbearers and chauffeurs, assigned per service. Can decline a shift. The same people drive the hearses.
5.5 main · plus part-time pool
Transfer drivers
Distinct from attendants. Bring the decedent into care. The only role using the SRS barcodes today.
Kingsway / transfer
Funeral Directors
Originate the post-signing prep email. Completeness and structure vary director to director.
Aaron ⚠ Inferred
Trained the concise six-document email style Stephanie holds up as the standard; specifies which service sheets a service needs.
Senior funeral director
Andrea
Built the forms, the SRS setup, the barcode conventions, and the [AN READY] convention. No longer employed — cited repeatedly as a gap.
Former Care Centre staff
Megan’s team / Kingsway
Coordinate transfers, and handle cases that bypass the Care Centre entirely. Share the transfer board with Stephanie.
Separate pathway
SubstrateSystems in play

Nine systems. Four of them are a spreadsheet with a colour code.

SRS
Barcode scan-in at intake; decedent record; wristband and form printing. Manually updated at dispatch. Explicitly not a lifecycle tracker — prep staff call it “a tool to put data into a document.”
Care Centre · transfer drivers
Prep board / combined board
Colour-coded by prep category; also carries casket-order status; entries go bold a few days out. Maintained by hand.
Stephanie · prep · FDs
Cooler spreadsheet
Manual slot assignment, colour-coded by days in care — turning red past a threshold.
Care Centre
Turnaround-time spreadsheet
Date of death → into care → date of prep, with a computed average. After-the-fact reporting, not a live queue.
Prep staff
Transfer board (MS Planner, in Teams)
Inbound transfers and driver assignment; shared with Kingsway. Prep staff can read it but cannot assign.
Stephanie · Kingsway · prep (read)
Scheduling spreadsheet
Stephanie’s own. Service date/time, funeral director, assigned attendant, assigned hearse. Carries her “almost full” marker.
Stephanie · printed once finalised
Email
The channel for the prep document. [AN READY] subject convention signals ready for service or release. No enforced template.
All
SharePoint
Funeral director availability calendar, rebuilt monthly by hand; storage for scanned prep and service sheets after the fact.
All
Mortware
Generates the base service sheet from the GPL package. Slow enough that Stephanie avoids opening it. Prep staff never touch it.
FDs · Stephanie (rarely)
MapThe process, end to end

Six steps, two parallel tracks, one convergence.

Step 1
Prep Document Received & Verified
Stephanie · category verified against the paperwork every time
▼
Step 2 · where the bundle forks
Paperwork Split & Prep Board Entry
Five documents printed · four to the prep room, service sheet retained
▼
Decedent track
Step 3
Transfer Intake & Cooler Assignment
Barcode scan · manual slot
▼
Step 4
Preparation
Russ / Melissa · prep sheet in hand
Logistics track — runs in parallel
Step 5
Attendant & Vehicle Scheduling
One service sheet per attendant · email out, initials back
▼
Step 6 · the two tracks converge
Day of Service — Identification & Dispatch
Two-person wristband check before the decedent leaves the building
▼
Out of scope
Document 3 — service, return leg, disposition
Ordinary step Runs in parallel, invisible to the other track Convergence · the one strictly-observed control

⚠ Inferred Steps 2 and 3 are shown in the order the transcript describes, but are not strictly sequenced — on the home / hospice pathway from Document 1 the decedent is already in care before the prep document exists. Nothing today depends on the order.

At a glanceEvery step and the gate it must clear

Soft everywhere — but “soft” is doing a lot of work.

#StepPrimary toolsGate to next step
1Prep Document Received & Verified Email, SRS, MS Planner, physical case file Case confirmed as the Care Centre’s; prep category identifiedsoft
2Paperwork Split & Board Entry Prep board, printer, colour-coded folders Five documents printed; four handed off, service sheet retainedsoft
3Transfer Intake & Cooler SRS barcode scan, cooler spreadsheet Decedent scanned in, cooler slot assignedsoft
4Preparation Printed prep sheet, effects inventory, embalming report Prep complete; sheet filled but not yet scannedsoft
5Attendant & Vehicle Scheduling Printed service sheets, email, scheduling spreadsheet Attendants confirmed, initials returned, FD cc’dsoft
6Day of Service — ID & Dispatch Wristband + file cross-check, SRS Two-person identification before the decedent leaves — soft in the system, absolute in practice
Step 1Prep Document Received & Verified

An email that may or may not tell you what you need.

What happens

Once the arrangement is signed, the director scans and emails the prep-document package. Stephanie checks it before her working day starts — “even before I get to work” — so a short-turnaround case can be printed and the prep room briefed first thing.

She verifies the paperwork against the stated category every time, because the category is not reliable: directors mark “minimum prep” on cases needing nothing, or “no preparation” on a casket-only graveside case that still needs Care Centre logistics. When she cannot tell whether the decedent is coming into Care Centre custody at all, she checks the transfer board — Kingsway and the Care Centre now cover for each other.

Resolved here: full prep = embalming; anything less is minimum prep; casket-only = no preparation.

EmailSRSMS Planner — transfer boardPhysical case file
Friction
  • No enforced email template. Aaron-trained directors send a tight six-document package with a summary. Others send an email whose most useful line, read off the screen in session, is “Hi Sarah” — Stephanie then opens the file and hunts.
  • Directors vary in how much they attach. She needs exactly five documents and often gets the whole case file or an incomplete subset. She is explicit: “if I could just get the minimum of it and then move on.”
  • The same complaint Megan makes about receiving the full package when she needs three forms. Two roles, same failure, different recipient.
  • Because the category cannot be trusted, the verification step is unavoidable today.
Gate → Step 2 Case confirmed as the Care Centre’s to prep, and prep category identified.
Signal for Requiem Generate this email from the case record rather than having the director compose it — a structured, mandatory-minimum notification carrying only the documents the recipient’s role needs. Stephanie and Megan described the same want independently.
Step 2Paperwork Split & Prep Board Entry

Five documents in. One stays on her desk.

What happens

Stephanie enters the case on the prep board, translating the director’s service details into a disposition category, and prints the five documents. She keeps the service sheet — the seed of the entire logistics track — and hands the other four to Russ: prep sheet, authorization / DNA, personal-effects inventory, photo.

The prep board also carries casket-order status; she keeps the entry open until the casket is confirmed in. Folder colour at intake encodes prep category independently — blue for minimum or casket-only.

Prep boardPrinterColour-coded foldersEmail
Friction
  • A re-entry of data already captured at arrangement. Asked what she would automate, Stephanie answered directly: “when a paperwork comes through, it just automatically pre-pops into my thing.”
  • Prep category is asserted in three independent places — the email, the board, the folder colour — with no single source.
  • Casket-order tracking rides on a spreadsheet column. When it fails, it fails silently.
  • Neither track can see the other’s state in any system from this point forward.
Gate → Steps 3 and 5 Bundle split and physically handed off. Both tracks now proceed independently.
Signal for Requiem One case record that drives the board entry, the folder, and the document package — so the category is asserted once and the two tracks stay visible to each other.
Step 3Transfer Intake & Cooler Assignment

A barcode, a wristband, and a spreadsheet beside them.

What happens

The transfer driver brings the decedent in. Intake staff scan the SRS barcode on the wristband, and the decedent is manually assigned a cooler slot in a separate spreadsheet, colour-coded by how long they have been in care — turning red past a threshold.

That spreadsheet used to be re-printed daily until a computer was installed outside the prep room. It is live now, but still a spreadsheet.

SRS barcode scanCooler spreadsheetColour-coded folders
Friction
  • SRS does not model cooler occupancy. The product already carries a morgue / slot concept, built generally enough to serve the coroner’s morgues and Megan’s operation — it is simply not in use here.
  • Scanning cooler → prep room was considered and rejected by prep staff as disproportionate: “we’re not that big of an organisation.” The one thing they want the slot record for is knowing which crypts are empty when a transfer arrives.
  • The turnaround spreadsheet is explicitly after-the-fact. It surfaced a case that sat 50+ days from date of death — a PGT case — but it explains rather than schedules.
  • Barcodes are used by transfer drivers only. Attendants do not scan; Stephanie updates SRS by hand later.
Gate → Step 4 Decedent scanned in, cooler slot assigned, prep category confirmed against the paperwork.
Signal for Requiem Make cooler slot a first-class field on the case rather than a parallel spreadsheet — and drive it from the transfer driver’s existing scan, not a second scan the prep room has already refused.
Step 4Preparation

The face sheet’s cousin — and four places to write the same date.

What happens

Prep staff start each morning on the combined board and the transfer board — confirming today is done, then working tomorrow so nothing surprises them, then looking a week out.

Prioritisation is date of death against service date, not service date alone: an older date of death jumps a nearer service, because of deterioration. Embalming is done early to “lock things in”; sanitary-care-only cases are deliberately left closer to the service. PGT cases run materially longer and skew the averages.

The prep sheet is kept physically in hand throughout, because it is where date of death, date into care, and date of prep converge. The effects inventory is initialled and dated — deliberately not a done/checked pair. A standard embalming report follows.

The sheet is scanned only once the decedent has left for the service.

Printed prep sheetEffects inventoryEmbalming reportCombined boardTurnaround spreadsheet
Friction
  • The four-place update. Completing a prep means updating the prep board, the turnaround tracker, SRS, and the SharePoint scan — plus flicking to a fifth surface to look up the date the decedent came in. Asked whether they would like that to be one place: “that would be great.” The prep room’s single largest complaint.
  • Incomplete prep sheets. Named as their biggest struggle: blanks and TBDs. The most commonly missing field is the PHN. “There’s no point in us having that paperwork if there’s a TBD.”
  • Effects gaps surface after the fact — items under the body, hearing aids, the occasional wallet found only during a hunt. There is no independent second check, and prep staff do not want one.
  • Jewellery disposition jams things up. Whether a rosary goes to the crematorium or comes out for the urn is a recurring delay — “one thing that always jams things up.”
  • The chemicals field is free text every time. Asked for unprompted: “I would love a drop-down menu with the chemicals instead of having to write it every time.”
  • Because the sheet is scanned only after departure, nothing on it is available to anyone else while the case is live.
Gate → Step 6 Prep complete; effects inventory initialled and dated; jewellery disposition decided.
Signal for Requiem One entry point for date of death / into care / of prep that propagates everywhere. A checklist chemicals field. An explicit disposition flag per effects line. And critically — capture the prep sheet when it is filled, not when it is filed, by reading back the paper the prep room wants to keep using.
Step 4aThe mandatory-field pass — live output of this session

Asked what must be filled in, they colour-coded it on the spot.

CriticalityFieldsRationale given
Critical First event date/time and location · Container / casket type · Preparation type · Pacemaker or implanted device “We need to know what to do and by when.” Pacemaker is a cremation-safety requirement
Medium Expected arrival of clothing Needed to plan dressing even for a direct cremation
Flexible Church / cemetery confirmation · Location of the decedent Legitimately unknown at arrangement — the family may not have spoken to the parish yet, and the stated location is sometimes simply wrong
Agreed in the room Hard-block the critical fields. For the flexible ones, allow an override that requires a written reason, and log the exceptions so operations can see whether the thresholds are set correctly. The same shape as the first-call gating pattern already being designed.
Left open Implanted radioactive seeds are never removed; the only current operational effect is potentially holding the decedent until the half-life elapses. Whether embalming drainage creates an exposure concern was raised and not answered — Open Question 11.
Step 5Attendant & Vehicle Scheduling

One service, four attendants, four different pieces of paper.

What happens

Running in parallel with Steps 3–4, off the service sheet Stephanie kept at Step 2.

She builds one service sheet per attendant per service. A four-vehicle Italian service — coach, flower van, two limousines — produces four separate printed sheets, each highlighted in a different colour so an attendant sees only their own role, and so a two-day service is not mistaken for a one-day one.

Assignment is deliberate fit-matching, not availability-filling: an experienced attendant paired with a newly-qualified director; an attendant experienced with Catholic mass to a Catholic service. She fills in start times, emails out to ask availability, writes in initials and hearse once accepted, and emails back cc’ing the director. Attendants can decline.

Printed service sheetsEmailScheduling spreadsheetSharePoint calendar
Friction
  • No accept / decline mechanism. Confirmation happens over email, phone, or in person, tracked in her own notes. The recent failure: she forgot to send a sheet, and the attendant did not show up.
  • Who is part-time, who is out, who suits which service, who is senior — all of it lives in Stephanie’s head and her private notes, kept explicitly “for someone that’s going to be covering my role.”
  • Casket not ordered. Always the same way: the director thought the assistant ordered it, the assistant thought the director did, or the casket company was the one party not cc’d. It is on the post-arrangement checklist and still slips.
  • Attendants have “very variable technological abilities” — a stated design constraint on any replacement.
  • Service-type labels don’t map cleanly onto the six GPL packages — an open naming question.
  • The attendant / driver / hearse overlap surfaces here as the actual bottleneck.
Gate → Step 6 Attendants confirmed, initialled sheets returned, funeral director cc’d.
Signal for Requiem Stephanie described the mechanism herself, from a previous care-home job — click the open shift, it texts the pool in seniority order, wait ~30 minutes, move to the next. Pair it with a per-attendant view reproducing her highlighting logic: date, time, location, role, nothing else, linked back to the common service sheet.
Step 6Day of Service — Identification & Dispatch

The one check nobody wants to digitise away.

What happens

Attendants check in with Stephanie. Before the decedent leaves the building, two people independently identify the decedent by reading the wristband and cross-referencing it against the file. Stephanie then updates the SRS record by hand — “she’s already on her way to the cemetery” — and the decedent and vehicle are dispatched.

The control exists because of a past incident. Stephanie’s account: “we had a case where one clothing got cremated instead of buried. It was a big thing… that’s why we needed to do a second eyes identification.” Ryan has described the same incident to the team separately. The wording leaves the actual failure ambiguous — see Open Question 10.

WristbandPhysical case fileSRS
Friction
  • The dispatch status update is a second manual entry into the same barcode record used at intake, with no trigger tied to the attendant’s confirmed departure.
  • Attendants are not in the barcode system at all, so the moment of departure is invisible until Stephanie types it in — often during a later cleanup pass.
  • Clothing arrives on its own timeline, frequently at the wrong branch. It is always redirected to the Care Centre, and tracked on a rack.
  • After a burial, Stephanie must remember to remove the case from the combined board so it does not conflict with what is still shown as in care.
Gate → out of scope (Document 3) Decedent dispatched to the service.
Signal for Requiem Preserve the two-person, wristband-based, no-photograph identification as a deliberate design choice — Document 1 records that photographing a decedent, including a wristband on the body, was flagged as unethical in the profession. But make the status change a one-tap consequence of the attendant’s own check-in, and retire the “remember to clear the board” step entirely.
SynthesisCross-cutting friction themes

Eight patterns that cut across the whole stretch.

Theme 1 · Step 4

The four-place update

One completed prep means touching the prep board, the turnaround tracker, SRS, and the SharePoint scan — and consulting a fifth surface for a date already recorded. Document 1’s Theme 1, recurring on the Care Centre side, and the prep room’s single largest complaint.

Theme 2 · Steps 2, 5

The shared capacity constraint is invisible

Attendants, hearse drivers, and prep-room throughput draw on substantially the same small pool. “Not enough attendants” is frequently “not enough hearses.” Nothing models the pool as shared, so the constraint is legible only to the person holding it in her head.

Theme 3 · Step 1

Inbound quality depends on who trained the sender

Aaron-trained directors send the tight six-document package; others send an email whose most useful content is the greeting. The mirror image of Document 1’s Theme 5 — outbound handoff is a manual email, so inbound quality is whatever the sender chose to make it.

Theme 4 · Steps 4, 6

Some manual steps are deliberate

Prep staff were explicit that the effects log does not need a done/checked pair — “we just date and sign it” — and the two-person identification answers a real incident. Both are considered professional and ethical choices. Any redesign must preserve their intent, not treat them as unautomated leftovers.

Theme 5 · Steps 1–6

Nothing in this stretch is gated by a system

Document 1 has exactly one hard gate, with physical consequences. Here there are none. Workable at this volume and completely opaque at any larger one — nobody can see a stalled case except by noticing a colour change on a spreadsheet.

Theme 6 · Step 5

Scheduling knowledge lives in one head

Stephanie keeps private notes on availability, fit, and seniority explicitly for whoever covers her role. The cautionary precedent is already in the building — Andrea built the forms, the SRS setup, the barcode conventions, and has left. “Now there’s no Andrea.”

Theme 7 · Step 4

The prep sheet is the prep room’s face sheet

Kept physically in hand throughout the work, because it is the only surface where date of death, into care, and of prep converge. Document 1 found the same relationship between directors and the Mortware pre-pop — and the same warning applies to any single-surface replacement.

Theme 8 · Steps 4, 6

Data flows backwards through paper

The prep sheet is scanned only after the decedent leaves, so everything captured during preparation is unavailable to anyone else for the entire time the case is live. The information exists; it is held in a drawer until it no longer matters.

OpenQuestions to resolve

Nine open. The session itself closed two.

#QuestionOwnerSource
1Resolved, in session. “Minimum” vs “full” prep. Full prep = embalming. Anything less than embalming is minimum prep. Casket-only = no preparation. Genuinely unclear to the R/OS team across several prior sessions.ResolvedAug 19, Stephanie
2Resolved, in session. PGT = Public Guardian and Trustee. PGT cases run materially longer because the province must trace and verify next of kin, and they skew the turnaround averages.ResolvedAug 19, Stephanie
3Is “involving” a real term in local use, or purely a transcription artifact for “embalming”? Evidence points strongly to the latter — confirm before the word enters product vocabulary.ZareefAug 19 transcript
4Confirm the service-type labels in use (sani burial, sani cremation, viewing burial, viewing cremation, graveside, memorial) and how they map to the six GPL packages. “Sani” appears to be sanitary care — bathing and dressing without embalming — but that is inferred from context, not stated.Matt / PhilAug 19 transcript
5Obtain a blank copy of the embalming report. Would a chemicals drop-down need a fixed taxonomy, and who owns it? A copy was offered in the session.ZareefAug 19, offered
6Russ to walk the prep sheet field by field and mark everything that must be filled before work begins. The critical/flexible pass was started live but not captured field-by-field.Russ → ZareefAug 19, offered
7What does the ship-out process look like end to end? Consulate delays against fixed airport windows were named as a worst-case day, and the prep team reports being left without director updates through it.MattAug 19 transcript
8Is the SRS cooler / morgue-slot model — already built for morgue support — worth piloting here, given prep staff explicitly do not want to scan cooler → prep room? The one use they named is knowing which crypts are empty on arrival.RyanAug 19, Step 3
9Pull a test wristband barcode from SRS’s fake records (Jaime) to prototype phone-based scanning without touching a real case.ZareefAug 19, agreed
10The two-person identification control originated in an incident described as “one clothing got cremated instead of buried.” Confirm what actually happened — the control’s design should follow the real failure, and Ryan has described the same incident independently.Zareef → RyanAug 19 transcript
11Does embalming drainage create an exposure concern for implanted radioactive seeds? Raised in the room, not answered. Seeds are never removed; the only current operational effect is potentially holding the decedent until the half-life elapses.ZareefAug 19 transcript
ReferenceAgreed case status sequence

This document picks up at 4 and stops partway through 6.

1IntakeDocument 1
2ArrangementDocument 1
3Contract signedDocument 1 · the hard gate
4Preparation document sent← this document begins here
5Preparations completeSteps 3–4
6Moving to dispositionCovered to dispatch only
7Case closedDocument 3
8Post-careDocument 3

The service itself and the return leg sit inside status 6 but are explicitly out of scope here. Document 3 picks up from the point of dispatch.

NextHow this document gets validated

Three things still turn this from reconstruction into record.

Remaining gap

No live walkthrough

Unlike the Aug 5 arrangement session, nobody ran a real case start to finish through this stretch. A live run — prep document receipt through dispatch — would confirm or correct the step order, particularly the parallel-track structure.

Missing cast

Russ and Melissa, properly

They were not expected at this session and joined partway through; the framing stayed Stephanie’s. A dedicated prep-room session was promised in the room and would likely revise Steps 4 and 4a substantially. Their contributions are also not separable in the transcript.

Handoff forward

Document 3

This document ends at dispatch. The next should pick up at the service itself and run through return of remains — the remainder of status 6, plus statuses 7 and 8.

Source · docs/discovery/post-arrangement/fd-post-arrangement-to-service-current-state.md
← → navigate  ·  P print