River
Y CombinatorBacked by Y Combinator
Log InStart Free
FREE TEMPLATE

Cross-Team Handoff Agreement Template

Four documents and five sheets that turn your rejection history into a definition of done, so a bounced handoff produces evidence instead of an argument.

Edit with AIDownload (.docx + .csv)

Free download  ·  No account needed

What you get

Pack of 9 files: 4 documents, 5 spreadsheets

Cross-Team Handoff Agreement Template
  • How the Definition of Done Is DerivedDocument
  • What This Does Not FixDocument
  • Handoff AgreementDocument
  • Dispute NoteDocument
  • Rejection LogSpreadsheet
  • Definition of Done EconomicsSpreadsheet
  • Handoff ChecklistSpreadsheet
  • Cycle Time by HandoffSpreadsheet
  • Dispute RegisterSpreadsheet
RiverCross-Team Handoff Agreement Template

Handoff Checklist

Pennard Systems, Sales to Implementation

Derived from214 handoffs, 68 rejection events, two quarters
Candidates priced9, tested against the check each one would impose
Adopted4, twenty-one minutes total, owned by the account executive

What must be true before the deal is marked closed-won

CodeWhat has to be trueEvidenceMin
SI-1Signed order form lists the modules soldForm, module lines visible3
SI-2Named client sponsor with sign-off authorityName, title, email, confirmation4
SI-3Pay frequency and pay group count recordedBoth values in the deal record6
SI-4Go-live date confirmed by implementation firstDated reply naming the date8

Five more causes fired in the same log. Three became required fields on the order form, one became implementation's own task, and one is accepted at half a day a quarter: none of the five may bounce a handoff.

Every handoff template on the market hands you the same blank field: write your acceptance criteria, filled in from a meeting where both teams remember the last argument differently. A definition of done built that way survives exactly as long as the next disagreement. Once a process map or an ownership matrix has settled where one team's part ends, this pack settles what 'ended completely' means at that exact seam. It's derived from what the receiving team has actually sent back, not from what either side remembers.

Every rejection cause in the history becomes a candidate, adopted only when the rework it prevents beats the cost of checking every handoff for it, the same cost-benefit test Executive Order 12866 has required of federal rule-making since 1993. The Rejection Log is the input, and the Definition of Done Economics sheet runs the test on every candidate. The Handoff Checklist holds what survives, and Cycle Time by Handoff prices the result in days, with the checking time added back in rather than hidden.

Pennard Systems, a payroll and HR vendor, ran the derivation across two crossings and two quarters: 390 handoffs, 99 rejection events, 13 candidates, 7 adopted. Twenty-one minutes of checking on the Sales to Implementation crossing removed 262 of the 370 calendar days bounces had added, and mean time to kickoff fell from 4.83 days to 3.65. The agreement also borrows a verdict from conditional acceptance in federal procurement: the receiving team starts the work anyway, and the sender still owes one named item by a set date.

Four sheets from one derivation

The Rejection Log, the Definition of Done Economics test, Cycle Time by Handoff, and the Dispute Register.

Cross-Team Handoff Agreement Template
RiverRejection Log

Rejection Log

Eight of ninety-nine rejection events across two crossings and two quarters at Pennard Systems.

DateClientCodeCauseDays added
1 AprSanderby Academy TrustSI-5Report commitment lived only in the AE's email5.5
13 AprMarchwood DentalSI-1Signed order form omits the modules sold4.2
25 AprFenwick LegalSI-4Go-live date never agreed with implementation11.4
27 AprPinegate RetailSI-6Outgoing provider's export format unknown8.0
24 AprTrelow FoodsIS-2Client admin never trained on reversing a pay run1.5
15 AprThorne and BlyIS-1No record of which custom reports were built3.0
8 MayAshcombe EngineeringSI-2No named sponsor with authority to sign off6.1
29 MayBeddowes Pharmacy GroupSI-7Third-party integrations in scope never listed3.4

Every row is an event, not a handoff. A handoff that bounces twice contributes two rows, which is why 57 bounced handoffs produce 68 rejection events on this crossing alone.

RiverDoD Economics

Definition of Done Economics

The test run on all nine Sales to Implementation candidates. Adopt only if rework avoided beats check cost.

CodeCauseRejectionsCheck costRework avoidedNetVerdict
SI-2No named sponsor11856 min3520 min+2664In the DoD
SI-4Go-live date not agreed91712 min4320 min+2608In the DoD
SI-5Report commitment in email72568 min1820 min-748Becomes a form field
SI-6Export format unknown65350 min1440 min-3910Receiver's own work
SI-9Headcount discrepancy13210 min90 min-3120Accepted

SI-6 is the cautionary row. Confirming the export format takes 25 real minutes, and only 6 of 214 handoffs ever needed it, so checking every one of them would have spent 5350 minutes to save 1440.

RiverCycle Time

Cycle Time by Handoff

Sales to Implementation, mean elapsed days from closed-won to kickoff, by month.

MonthHandoffsBouncedBounce rateMean days
2025-04371027.0%4.85
2025-0534926.5%4.82
2025-06361027.8%4.90
2025-0735925.7%4.77
2025-08361027.8%4.90
2025-0936925.0%4.72
Total2145726.6%4.83
Projected with the DoD214——3.65

The checking time is added back in, not hidden. Twenty-one minutes on every one of 214 handoffs is 9.4 working days on its own, and the projected 3.65 already includes it.

RiverDispute Register

Dispute Register

All six disputes raised in two quarters. Most bounces are never contested.

DateClientWhat the receiver saidRuling
14 MayTrelow FoodsBounced for an incomplete data mappingWithdrawn: mapping is SI-6, the receiver's own task
2 JunDraymoor HotelsBounced because the recorded sponsor had leftUpheld: SI-2, sponsor re-confirmed
27 JunFenwick LegalBounced for a go-live date it had never seenUpheld: SI-4, date moved three weeks
19 JulAshcombe EngineeringClient kept calling the implementer instead of supportWithdrawn: real problem, no DoD shape
8 AugVerity Home CareAdmin had watched a reversal but never done oneUpheld: IS-2 reworded that week
11 SepKestrel FabricationReopened an accepted headcount discrepancyWithdrawn: SI-9 is already accepted

Two of six disputes found a defect in the agreement itself, not in the work. IS-2's rewording and the running cost of SI-9 both came out of this register, not out of the original derivation.

Edit with AI

What's in the pack

01

Rejection Log

Every bounced handoff for two quarters and two crossings, with the cause code, the calendar days it added, and who bounced it, kept as one row per event rather than per handoff.

02

Definition of Done Economics

Prices every candidate cause by the rework it avoids against the check it would cost on every handoff, then rules: in the definition of done, a form field instead, the receiving team's own work, or accepted outright.

03

Handoff Checklist

Only the items that survived the test, plus the ones that failed it, flagged so nobody mistakes a required form field for a reason to bounce a handoff.

04

Cycle Time by Handoff

Mean days from tender to acceptance, clean against bounced, with the checking time added back in rather than left out of the after picture.

05

Dispute Register

What a receiving team said when it bounced work back, whether the agreement covers it, the ruling, and whether the dispute found a defect in the work, the agreement, or nothing at all.

06

Handoff Agreement

The signed document for both crossings: the definition of done, the three responses to a tendered handoff, and what a bounce has to name. An escalation matrix covers what breaks; this covers what's merely incomplete.

07

Dispute Note

The ten-minute procedure for a contested bounce, naming who rules on it and the difference between a defect in the work and a defect in the agreement's wording.

08

How the Definition Is Derived, and Its Limits

The four-figure test behind every adopted item, plus what it cannot do: find a cause nobody logged, run on a crossing that happens twice a year, or settle a genuine scope dispute.

How to use it

  1. 1

    Open in River, or download it

    Install the pack and hand River your rejection history, or download all four documents and five sheets blank and run the derivation yourself.

  2. 2

    Send the rejection history

    A queue export with status changes, a shared inbox, the channel where work gets bounced, or just the handoff count for the period and the causes the receiving team is sick of chasing.

  3. 3

    Price each candidate cause

    For every rejection cause, name roughly how many minutes a check would cost on every handoff and how many minutes the rework actually costs when it happens, then let the test decide.

  4. 4

    Sign the checklist, log disputes

    The surviving items become the Handoff Checklist both sides work from, and every contested bounce afterward goes in the Dispute Register instead of back into an argument.

Frequently asked questions

Is this free, and what do I get?

Free, with no signup on the download: four documents and five spreadsheets. The AI half is optional. Send River your rejection history and it derives the definition of done and prices every candidate cause for you.

Why not just write the acceptance criteria in a meeting?

Because a list written from memory is always too long. A cause that fires on 6 of 214 handoffs still imposes its check on all 214 of them, and that ratio is invisible to anyone sitting in the meeting where the list gets written.

What happens to a rejection cause that fails the cost test?

It does not disappear. Depending on what it actually needs, it becomes a required field on the sending team's form, moves to the receiving team as their own task, or is accepted outright with the arithmetic written down next to it.

How is a disputed bounce different from an ordinary one?

An ordinary bounce cites a code from the checklist and gets fixed. A disputed one is ruled on by whoever owns that crossing, in about ten minutes, and the ruling records whether the defect was in the work, the agreement's wording, or neither.

Does this work for a handoff that only happens a few times a year?

Below a few dozen handoffs a year, the pack has you skip the arithmetic and write the definition of done from what you remember failing. Six rejections against six handoffs is an anecdote, not a rate the test can run on.

What does Edit with AI actually do?

Creates a free account, installs this exact pack as a private space, and primes the agent to read whatever rejection history you send. Nothing gets written until you send something, and the blank pack is always there to download instead.

Sources

  1. reginfo.govExecutive Order 12866 (opens in a new tab)
  2. Acquisition.gov46.101 Definitions (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

LinkedInGitHubX

Reviewed by

Brian Joseff, Co-founder, River

LinkedInX

Related workspaces

RACI matrix template

Assigns who owns each step inside a process, once this settles what a complete handoff at its boundary actually requires.

Escalation matrix template

Says who gets called and how fast once something breaks, rather than what a receiving team is owed at a routine handoff.

More free templates

Decision Rights Policy Template

Free decision rights policy template: authority set from your own escalation history, so a rule only stays mandatory where it changes outcomes.

Incident Escalation Matrix Template

Free escalation matrix template with severity levels written around your real past incidents, plus the no-answer ladder every other template leaves out.

Internal Service SLA Template

Free internal SLA template: response targets set from your team's own historic response times per request type, not a flat guess.

Operating Cadence Design Template

Free operating cadence template: cost every recurring meeting in real salary hours, then cut or merge the ones sharing a job.

Stop settling the same bounce twice

Take the four documents and five sheets blank, or install this pack in River and send your rejection history.

Edit with AI