People leave.
Their work shouldn't.

Relay reads the systems where someone actually worked — mail, calendar, Slack, Jira, GitHub, Notion — and hands their successor a complete, evidence-backed handover. Every relationship. Every open promise. Every recurring obligation. In a day, not a quarter.

Before

Handover_notes_final.docx

2 pages · written on her last day

After

Handover — Priya Raghavan

63 findings · 91% coverage · 4 actions before transfer

  • Give notice on the Gong contract4 days
  • Raise the $4,200 Halvorsen creditthis week
  • Move the pricing workbook off her Drive30 Sep

Know what walks out the doorbefore it does

Reconstruct

Every relationship, promise and obligation — rebuilt from the evidence.

Relationship

Tom Bradshaw, Halvorsen — weekly call, sole contact

41 sources

Open promise

$4,200 credit promised 14 Aug, not raised

3 sources

Recurring

Renewal re-pricing Flow, 1st of month

12 sources

Access

Only Salesforce admin; owns 14 Flows

5 sources

Relay reads the work, not the notes. Who they dealt with, what they committed to, what runs monthly, which system only they could log into.

Day-1 copilot

Ask the role anything. Every answer cites its source.

What did we promise Halvorsen?
A $4,200 credit for double-billed August seats, promised in writing on 14 Aug. Tom has followed up twice; it hasn't been raised.E-201E-209

No guessing. The successor asks in plain language and gets the email, ticket or message behind the answer.

HowRelay works

Connect the accounts the person actually used. Read-only, scoped to a date window, revocable any time.

GmailConnected
Google CalendarConnected
Google DriveConnected
SlackConnected
JiraConnected
GitHubConnect

Every claim,backed by evidence

Evidence-linked

Click any finding. See the email behind it.

Open promise

$4,200 credit promised to Halvorsen E-201

Email · 14 Aug 2026

…I'll raise a $4,200 credit against the August invoice before your renewal opens in November…

Nothing is asserted without a source. Managers verify, successors trust, auditors can trace.

Explicit gaps

Relay tells you what it couldn't find.

Who approved the three overrides in the comp-plan table?

No trail in mail, Slack or Jira.

Asked in the exit interview

How is the quarterly sandbox refresh done?

“Six steps — I never wrote them down. Here they are…”

Answered by Priya · folded into the handover

Then it asks the one person who knows. Gap questions become a short voice interview; answers are folded back in and marked human-confirmed.

Obligation radar

Renewal notices, promised credits, filing deadlines: everything with a date, counted down before it's missed.

Access that actually transfers

Every account and elevated permission, including the ones IT never recorded, ordered by what breaks first.

Relationship cards

Per counterpart: cadence, channel, tone, last contact, and whether anyone else has ever spoken to them.

Reads what you authorise.Nothing more.

Works with

  • Gmail
  • Google Calendar
  • Google Drive
  • Slack
  • Jira
  • GitHub
  • Notion

How access works

  • Read-only OAuth, scoped to a date window you choose
  • Tokens encrypted at rest (AES-256-GCM)
  • Reported per role, never as surveillance
  • Disconnect and delete at any time

The cost of not knowing

42%

of what an employee knows is known only to them.

Panopto, Workplace Knowledge and Productivity Report

90–120 days

is what a proper handover takes. Most teams get two to four weeks of notice.

Operator interviews on role transitions

3 / 6 / 12 months

of retention buffer paid while teams work out what someone actually did.

Typical M&A and key-person retention terms

Start with one role.

Connect the accounts today. Read the handover tomorrow.

Start a handover