The Arrangement Process, As It Runs Today

First call to signed contract to handoff — ten steps, one hard gate, and a branch that decides everything.
Current state 2026-08-06
Kearney Funeral Services
Reconstructed — live walkthrough observed, Aug 5
FrameWhat this covers, and how much to trust it

Scope, sources, and one honest caveat.

Scope

From the moment a first call is received through to the point where the signed contract is handed off and transfer / preparation is initiated.

Everything downstream of “preparation document sent” — preparations complete, disposition, case close, post-care — is out of scope.

Sources

Kearney FDs and R/OS Team — Aug 5, 2026
Zareef, Phil, Matt, JC / Jay Robinson, Jeanette

Mortware pre-pop form — data mapping, field density, and power user design — Aug 6, 2026 (Zareef)

Jaycee’s “Meeting Follow Up” email thread — Aug 6, 2026, resolved package/service-type duplication and included a fully filled, colour-coded pre-pop

Confidence caveat

This is reconstructed from meeting summaries, checked against the raw Granola transcript and Jaycee’s Aug 6 email correspondence where it mattered most.

Steps marked ⚠ Inferred are logical bridges between things that were discussed but never explicitly sequenced.

The Aug 5 session turned into a live walkthrough mid-meeting — JC ran a timer while Jeanette worked a real, already-in-progress arrangement start to finish in front of the group. That run is the primary source for Steps 3–7 and 9–10 below (see Open Questions, #1). Two granular field-level questions in Steps 4 and 5 were separately closed out by Jaycee’s follow-up email (#2, #5). Still unobserved: the signing conversation itself (downstairs, off camera) and a case starting from first call.

Corrected against

The Jeanette, Megan, and Miriam / finance sessions. Those three establish the payment-and-authorization gating on transfer — which the two meetings above do not cover.

CastWho touches the process

Nine roles, one of them still unobserved.

First call staff
Take the incoming call, capture the first-call form, fill available arrangement slots.
Funeral Director
Owns the arrangement meeting through contract signing.
JC · Jeanette
Manager
Pre-blocks arrangement slots a week out; runs the 8:15 manager huddle.
Transfer team
Brings remains into care. May create the SRS record if the body arrives before the arrangement.
Megan
Care centre staff
Preparation work. Operate on SRS + the comm board.
Registrar
Manually submits vital statistics forms to the province.
Sarah
Andrea
Receives operational notifications — prefers Teams.
Crematorium
Receives disposition documents.
Stephanie
Identified as a pivotal role in this chain.
Not yet interviewed
SubstrateSystems in play

Eight systems. Three of them maintained by hand.

Mortware (remote desktop)
System of record. Case creation, vital stats, service details, financials, contract, document generation.
Vancouver, West Shore, Fraser Valley FDs · not the transfer centre
Mortware pre-pop / face sheet
Single-screen view of the case. Front of every physical file; auto-populates downstream docs.
FDs
SRS
Location tracking, barcode scan in/out, transfer & cremation certificates. Per JC, FDs don’t need it — but they enter into it anyway.
Care centre · transfer · crematorium
Comm board
Communication / status board. Maintained by hand.
FDs + care centre
Cremation board
Cremation-specific tracking, JC-built. Maintained by hand.
FDs
SharePoint calendar
Arrangement slots, service scheduling, vacation blocking.
All
Email & Teams
First-call form intake; every notification to care centre, transfer, registrar, crematorium. Email is the audit trail; Teams is Andrea’s preference.
All
QuickBooks
Accounting. Not integrated with SRS.
Finance
MapThe process, end to end

Ten steps. One branch. One hard gate.

Step 1
First Call & Intake
Where is the decedent?
Step 2a · home / hospice / NH
Immediate Transfer
Verbal authorization only
Step 2b · hospital / coroner
Decedent HELD
No pickup permitted — blocked until Step 8
Step 3
Scheduling & Assignment
The arrangement meeting — steps 4 to 7, one sitting
4
Vital Statistics
5
Service & Merchandise
6
Financials & Payment
7
Documents & Review
Step 8 · the only hard gate
Contract + Payment Terms + Authorizations Signed
Releases the decedent for transfer
Step 9
Record Propagation
SRS + boards
Step 10
Handoff
Transfer dispatched · prep document sent
Ordinary step Proceeds on verbal authorization Blocked / hard gate
At a glanceEvery step and the gate it must clear

Gates are soft everywhere except one.

#StepPrimary toolsGate to next step
1First Call & Intake Phone, email, first-call form, Mortware, SRS Case exists with deceased name + branch; decedent location determinedsoft
2aImmediate Transfer Verbal authorization, SRS, barcode scan Decedent in care, location loggedsoft
2bDecedent Held No gate — blocked until Step 8
3Scheduling & Assignment SharePoint calendar, 8:15 / 8:30 huddles Slot filled, director assigned, family confirmedsoft
4Arrangement — Vital Statistics Mortware tabbed modal, pre-pop PDF Vital stats complete or explicitly marked unknownsoft
5Arrangement — Service & Merchandise Mortware, printed / verbal catalogue Service type + disposition type selectedsoft
6Arrangement — Financials & Payment Mortware, QuickBooks (separate) Payment received or terms agreedsoft
7Document Generation & Review Mortware pre-pop, PDF, gov’t forms Director attests documents reviewedhuman
8Contract + Authorizations Signed Paper contract, cremation auth, payment terms Signed contract — releases the decedent for transfer
9Record Propagation SRS, comm board, cremation board SRS record complete — contract #, name, weight, dispositionsoft
10Handoff Email, Teams Transfer dispatched; prep document sent; parties notifiednone
Step 1First Call & Intake

A case opens on two fields.

What happens

A call comes in — from a family, hospital, care home, hospice, or coroner. First call staff capture the details on a first-call form. Some arrive as emailed forms rather than live calls. A case is opened in Mortware.

Minimum viable record is deceased name + branch. Date of death is explicitly optional and may be unknown at this point.

PhoneEmailFirst-call formMortwareSRS (if transfer dispatched)
Friction
  • Emailed first-call forms are re-keyed by hand into Mortware — no ingestion path.
  • This is the first of 4–5 separate entries of the same data across Mortware, comm board, cremation board, SRS, and vital stats.
  • No people lookup. Existing records — pre-need contracts, prior family members — aren’t surfaced as the name is typed, so prior relationships are missed or re-entered.
  • Unknown fields can block progression rather than being parked.
Gate → Step 3 A case record exists with deceased name and branch assigned. Nothing else is strictly required to proceed.
Signal for Requiem Email intake that auto-opens a case and pre-populates fields; a family portal link that lets the family self-enter vital stats directly into the case; an “unknown, revisit” checkbox instead of a hard block.
Step 2aImmediate Transfer — home, hospice, nursing home

Custody taken on a verbal yes.

What happens

There is no morgue at these locations, so the decedent cannot remain. Transfer proceeds immediately on verbal authorization only — no signed contract, no payment.

The transfer team is dispatched, the decedent is brought into care, and location is logged. Because the arrangement hasn’t happened yet, the transfer team or Megan’s team creates the SRS record.

Phone — verbal authorizationEmailTeamsSRS barcode scanPhysical transfer paperwork
Friction
  • The firm has taken on cost and custody with nothing signed. Verbal authorization is the only thing standing behind an immediate transfer — and the family may not arrange with Kearney at all.
  • The transfer centre has no Mortware access. Everything reaching them is manually emailed by a director.
  • The SRS record gets created by whoever arrives first, so ownership is ambiguous and the FD later enters into a record they didn’t open.
  • Chain of custody is fragmentary — SRS barcodes cover crematorium scan in/out, not the journey from first transfer.
Gate → Step 3 Decedent physically in care, location recorded, SRS record created.
Signal for Requiem End-to-end chain of custody with mobile scanning (no app install, Requiemos credentials + MFA, zero PHI on device); permit backfill under audit. Photo capture off by default — JC flagged photographing a decedent, including a wristband on the body, as unethical in the profession.
Step 2bDecedent Held — hospital, coroner’s morgue

Nothing happens. That is the point.

What happens

The facility holds the decedent and no pickup occurs until the family comes in for a full arrangement and signs. This applies even to coroner cases.

The case sits at intake until an arrangement is scheduled and completed.

None — this is a waiting state
Friction
  • There is no gate to clear here, and that’s the point — the case is blocked on the family’s availability to attend an arrangement.
  • The decedent’s holding location and elapsed time aren’t tracked in any system during this window. The case simply sits.
  • ⚠ Inferred If the family delays scheduling, there is no visible ageing or escalation signal today.
Gate → Step 3 Arrangement scheduled. Transfer remains blocked until Step 8.
Signal for Requiem Decedent location should be a first-class field captured at first call — it determines the entire downstream path. Cases in this holding state need visible ageing.
Step 3Scheduling & Assignment

The calendar has run out of colours.

What happens

Managers pre-block arrangement slots for all directors roughly a week out; key people’s vacations are blocked so capacity is visible at a glance. First call staff fill the available slots.

Managers meet at 8:15; the full team huddles at 8:30 and pulls up the calendar — who’s doing what, and what’s changed since yesterday.

SharePoint calendarMorning huddle — verbalComm board
Friction
  • The SharePoint calendar has literally run out of colours. Each location needs at least two — arrangement vs. service — and there aren’t enough distinct ones left.
  • Colour-blind staff can’t reliably distinguish location and event types.
  • Calendar events don’t link to the case — no hover context, no click-through.
  • Changes since yesterday are communicated verbally at the huddle, so anyone who misses it is out of date.
Gate → Step 4 Slot filled, director assigned, family confirmed for the arrangement time.
Signal for Requiem Weekly calendar as the default landing view; event-type colour + location icon/badge rather than location-specific colours; tenant-admin-configurable to match the existing SharePoint scheme for familiarity; hover tooltip or click-to-expand linking directly to the case.
Step 4Arrangement Meeting — Vital Statistics

Forty minutes of dead air, with the family downstairs.

What happens

The family arrives. Per JC, the standard arrangement order — sourced from the Canadian College of Funeral Services curriculum — is vital statistics → rapport / service type → merchandise → payment → signing.

Vital stats go in first. The director works in Mortware’s tabbed modal (10+ tabs) as the primary entry surface, while the pre-pop face sheet serves as the visual reference — scanned top to bottom, familiar by muscle memory.

Mortware via remote desktopPre-pop face sheet (PDF)Physical file
Friction
  • Mortware runs on remote desktop — slow and crash-prone, and degrades further when multiple directors are in it at once. One arrangement lost 40 minutes waiting for Mortware to respond with the family still downstairs.
  • The pre-pop bundle gets edited as a PDF on the fly, and someone has to go back and update Mortware separately afterward.
  • Tabs and expanding sections slow the director down when a family is waiting or a disposition changes mid-meeting.
  • Conditional / hidden fields: Mortware hides fields based on another field’s state, so the director can’t see why something is unavailable.
  • 174 fields on the pre-pop alone (checkboxes counted as enums), only some filled in a typical arrangement. Resolved — Jaycee sent a fully filled example (Aug 6 email), colour-coded yellow (entered manually into the pre-pop) vs. green (pulled from Mortware), which is exactly the primary/secondary split needed.
Gate → Step 5 Vital statistics captured, or the gaps explicitly marked unknown / to-revisit. In the current process this gate is soft — director’s judgement, not enforced.
Signal for Requiem Replicate the face sheet as a single editable screen, not a tabbed / scrolling form — this is JC’s core ask. If sections are unavoidable: max 3 tabs (Vital Statistics · Purchaser/NOK · Services · Financials), or a left nav to jump between them. Two-tier field model — primary always visible, secondary behind an expand. Tab-key navigation for speed. Surface restrictions plainly rather than hiding fields.
Step 5Arrangement Meeting — Service Type & Merchandise

Selling from memory, not from pictures.

What happens

Rapport-building and service type discussion, then merchandise selection to build the package.

Disposition type — cremation, graveside, and so on — is determined here. That choice is what drives which downstream parties get notified.

MortwarePrinted materialsVerbal descriptionPhysical showroom
Friction
  • No visual merchandise catalogue. Compass / SEI shows directors photos while building a package — it reduces wrong-item errors and lets families see what’s being ordered. Kearney directors don’t have this.
  • Any screen-based catalogue has a human-factors problem: the solution shouldn’t require a screen facing the family.
  • “Package type” and “service type” are confirmed duplicate fields. Per Jaycee’s Aug 6 email: no difference, interchangeable across the company, the profession, and Mortware — “I am not sure why it is in two places, it has just always been that way.”
Gate → Step 6 Service type and merchandise package selected; disposition type determined.
Signal for Requiem Collapse to one field, not two. That single selection should pull the relevant GPL package and derive required vs. suggested services on its own (e.g. transfer fee always required; embalming isn’t a legal requirement in BC but is bundled into “FULL” today).
Step 6Arrangement Meeting — Financials & Payment

The commercial gate on a physical release.

What happens

Payment is discussed and collected or committed. Kearney’s stated target is payment up front, with no outstanding AR beyond 30 days — payment is expected at or before the arrangement. Payment terms are signed in this same session.

Cash advances — clergy, musicians, other third-party pass-through costs — are collected from the family on the invoice and later disbursed by cheque. Any cash advance over $500 requires customer payment before the cheque is issued.

MortwareQuickBooks — separately, downstream
Friction
  • SRS is not compatible with QuickBooks, so financial data doesn’t flow cleanly between location / disposition tracking and accounting.
  • The $500 disbursement threshold is a manual check with no system enforcement — nothing prevents a cheque being cut before the family has paid.
  • Cash advance pass-through means the same amounts are tracked in two places with different meanings — family-facing invoice line vs. payable to third party.
  • How a shortfall or refused payment is handled mid-arrangement isn’t formally documented — but per Kearney, this resolves offline regardless of what any system tracks, so it isn’t a gap Requiem needs to design for.
Gate → Step 7 Payment received or payment terms agreed. This is the commercial gate that, once signed at Step 8, releases the decedent for transfer in the hospital / coroner pathway.
Step 7Document Generation & Review

Forms are outputs of the case, not inputs to it.

What happens

Forms are generated as outputs of the case data, not inputs. The pre-pop auto-populates the downstream bundle — correcting one field on the face sheet corrects the whole bundle. Government vital statistics forms are produced here.

The director reviews before anything is sent. JC checks documents 7–8 times before sending.

Mortware pre-popPDFGovernment vital stats formsPrinter
Friction
  • Garbage in, garbage out — acknowledged and accepted, because it’s easy to jump back, fix a field, and reprint. This depends entirely on the correction loop staying fast.
  • No legal programmatic submission path for vital statistics. The system generates a filled form and the registrar (Sarah) submits it manually. Compass reportedly achieved programmatic submission to the BC provincial site, returning a confirmation code within minutes — feasibility and cost unconfirmed.
  • Handwritten forms have to be re-keyed; nothing reads them back into the system.
  • Not everyone reviews before sending. JC does; the process assumes it but can’t verify it.
Gate → Step 8 Director attests documents are reviewed. This is a human gate — the system can prompt (“have you reviewed the documents?”) but can’t force honesty.
Signal for Requiem Review gates that prompt without bypassing; OCR to read handwritten forms back in; investigate the Compass programmatic vital stats path.
Step 8Contract, Payment Terms & Authorizations Signed

The only hard gate — and the only one with a physical effect.

What happens

The family signs everything in one session: the contract, the payment terms, the cremation authorization where applicable, and all optional consents. This is the hard milestone in the agreed status sequence — everything before is Arrangement, everything after is Contract signed.

This is also the moment the decedent is released for transfer. For hospital and coroner cases, the transfer that has been blocked since first call can now be dispatched.

Paper contractCremation authorizationPayment termsConsent forms
Friction
  • Post-signing edits affect the reconciliation invoice. Nothing warns a director that they’re making a consequential change to a signed case.
  • Multiple distinct documents are signed in one sitting with no checklist confirming the set is complete — a missing cremation authorization isn’t caught until later.
  • Because signing releases the transfer, any delay or missing signature has a physical consequence, not just an administrative one. The decedent stays in the hospital morgue.
Gate → Steps 9 & 10 Signed contract on file. The first genuinely hard gate in the process — everything before it is soft and director-judgement-based — and the only gate with a physical-world effect.
Signal for Requiem A completeness check on the signature set before the case can advance; warn on significant edits after signing, with the reconciliation-invoice consequence stated explicitly; make the transfer release an explicit, visible action triggered by signing rather than something the director has to remember to initiate.
Step 9Record Propagation — SRS + boards

The fourth or fifth time this data is typed.

What happens

The director enters the SRS record at arrangement: contract number, name, weight, disposition type. If the body arrived before the arrangement was done, the transfer team or Megan’s team has already created it.

Comm board and cremation board are updated separately, by hand.

SRSComm boardCremation board
Friction
  • This is the 4th / 5th entry of the same data. Nothing propagates.
  • Per JC, FDs don’t actually need SRS access — it’s care centre staff who work in it. Directors are entering into a system that isn’t theirs because nothing else carries the information forward.
  • SRS is used mainly for location tracking and printing transfer / cremation certificates — functions Requiem could absorb. Ryan has expressed interest in not renewing SRS.
Gate → Step 10 SRS record complete — contract number, name, weight, disposition type. Boards updated.
Step 10Handoff — Transfer Dispatched & Preparation Document Sent

Fire and forget, one recipient at a time.

What happens

Two things happen together. For hospital and coroner cases, the transfer is dispatched — the first physical movement of the decedent, waiting on Step 8 since first call. Simultaneously, the director manually emails the care centre, transfer centre, registrars, and crematorium with the documents each needs.

The case moves to Preparation document sent and ownership passes to the care / prep team. For home / hospice cases the decedent is already in care, so this step is documentation-only.

Email — primaryTeamsSRS
Friction
  • Everything is manually addressed and sent by the director, one recipient at a time.
  • The crematorium complains about receiving too many irrelevant documents — the director sends the whole bundle rather than the relevant subset.
  • Recipients want different channels. Megan wants email specifically for the audit trail, and only the 3 forms she actually needs. Andrea prefers Teams. There’s no way to honour both without the director tracking preferences in their head.
  • Internal status-update emails proliferate because there’s no in-product notification.
  • No acknowledgement loop — the director doesn’t know the prep team received or opened anything.
Gate → out of scope Prep document sent and relevant parties notified. There is currently no confirmation gate — the handoff is fire-and-forget.
Signal for Requiem Workflow engine routes only the relevant documents to each role, respecting per-recipient channel preference — email for audit-trail roles, Teams / in-product for others. Internal status emails should largely disappear.
SynthesisCross-cutting friction themes

Eight patterns that cut across the whole process.

Theme 1 · Steps 1, 4, 9, 10

The 4–5× entry problem

The same data is entered into Mortware, comm board, cremation board, SRS, and the vital stats forms. The single most repeated complaint in every session.

Theme 2 · Step 4

Mortware’s performance is a live-family problem

Not just an annoyance. 40 minutes of dead time during an arrangement is a service-quality failure the family experiences directly.

Theme 3 · Steps 4, 7

The face sheet is the mental model

Both JC and Jeanette treat the pre-pop as input and output. It’s the front of every physical file and known by muscle memory. Any replacement that abandons single-screen density will fight the users’ habits.

Theme 4 · Steps 1–7

Gates are soft everywhere except signing

Steps 1–7 advance on director judgement. Workable — but it means chain-of-custody and review gaps are invisible until someone goes looking.

Theme 4b · Steps 3, 4, 8

Contract signing is a physical gate

For the hospital / coroner pathway — the majority — nothing moves until the family signs. Time-to-arrangement is time-the-decedent-sits-in-a-morgue, which makes scheduling friction and Mortware’s 40-minute stalls costlier than they first appear.

Theme 4c · Step 2

The two pathways carry opposite risks

Hospital / coroner cases risk the decedent being held while the family delays. Home / hospice cases risk the firm having taken custody and cost on a verbal authorization that may never convert. Both need visibility; neither has it.

Theme 5 · Steps 2, 7, 9, 10

Every handoff is a manual email

Four separate steps depend on a director remembering who needs what.

Theme 6 · Step 4

The pre-pop is a reference surface, not an entry surface

Confirmed Aug 6 — JC uses it to scan and spot-correct while primary entry happens in the tabbed modal. Replicating the face sheet as the primary entry screen is a change to how it’s used today, not just a re-skin.

OpenQuestions to resolve

Five open questions remain. JC’s last email closed two more.

#QuestionOwnerSource
1Resolved, live. JC ran the timer while Jeanette worked a real, in-progress arrangement start to finish for the group — vital stats, service/merchandise/financials review, document generation, printing, the handoff bundle, and propagation into the comm board, cremation board, and SRS. Not covered: the signing conversation itself (downstairs, off camera) and a case starting from first call.ResolvedAug 5, live
2Resolved. Package type and service type are the same thing — interchangeable across the company, the profession, and Mortware, kept in two places for no clear reason. One selection should drive GPL pull and required/suggested services.ResolvedJaycee, Aug 6 email
3Why is the “funeral director” field crossed out on Andrea’s copy of the pre-pop?Aug 6
5Resolved. Jaycee sent a fully filled example (Traditional/“FULL” service), colour-coded yellow (manual entry) vs. green (pulled from Mortware) — the primary/secondary split this question asked for.ResolvedJaycee, Aug 6 email
7Is programmatic vital stats submission to the BC provincial site feasible, and at what cost? Compass reportedly does thisAug 5
8Identify and capture the missing Mortware tab screenshotsZareefAug 6
9Priority call: SRS replacement vs. case management / arrangement streamliningRyanAug 5
11Stephanie’s part of the workflow is unobserved and may change this mapMatt → RyanAug 6
ReferenceAgreed case status sequence

This document covers the first four statuses.

1IntakeFirst call taken
2ArrangementMeeting in progress
3Contract signedStep 8 · the hard gate
4Preparation document sent← this document ends here
5Preparations completeOut of scope
6Moving to dispositionOut of scope
7Case closedOut of scope
8Post-careOut of scope

Agreed in the Aug 5 session. The sequence matters because status 3 is the only transition with a physical-world effect — it is what releases the decedent for transfer.

NextHow this document gets validated

Three things still turn this from reconstruction into record.

Remaining gap

What the walkthrough didn’t cover

The Aug 5 session covered Steps 3–7 and 9–10 live. Still unobserved: the signing conversation itself, and a case followed start-to-finish from first call.

Missing cast

Stephanie’s workflow

Named as pivotal, still unobserved. Her part of the chain may change this map — particularly around Steps 9 and 10.

Priority call

SRS or arrangement first

Ryan’s call: replace SRS (location tracking, transfer / cremation certificates) or streamline the arrangement itself.

Source · docs/discovery/arrangement/fd-arrangement-process-current-state.md
navigate  ·  P print