From work in progress to a handoff someone can act on.
When work changes hands, the why comes with it. Eight steps, from the moment work changes hands to the moment the next person carries on — and a person approves before anything leaves IL Co.
- 01
Connect
An admin connects Slack, Linear, Jira, GitHub and GitLab, picks the channels and repositories IL Co may read, and chooses which Linear statuses start a handoff.
- 02
Trigger
A Linear issue is reassigned or moves into one of those statuses, someone types /handoff in Slack, sets an out-of-office status with issues still open, or has opted into an end-of-day handoff.
- 03
Gather
IL Co reads the issue, its comments and status history, the Slack messages about it, and the pull requests, merge requests, reviews and commits linked to it.
- 04
Draft
The sources become claims under each section of the handoff. Every claim cites what it came from. The owner suggestion says why.
- 05
Review
Only the author can see the draft. IL Co sends them a Slack message when it is ready; they approve it there, or reword or remove claims in IL Co first — or reject it with a reason.
- 06
Publish
The approved handoff is posted as a comment on the Linear issue and to Slack. If a write fails, the handoff says so — it is never shown as published.
- 07
Receive
The new owner gets it in Slack and their Inbox, accepts it, and asks the author questions on it. It can be reassigned if it went to the wrong person.
- 08
Continue
Search finds the handoff and its sources later — in IL Co, or from an AI agent over MCP.
Every sentence says where it came from.
IL Co builds a handoff from the sources themselves, so each claim carries one of three states.
- Known
- Backed by the Slack messages, Linear or Jira issues, or pull and merge requests it cites. Each source opens where it lives.
- Unknown
- The sources don’t say. The claim is marked as unknown rather than filled in with a guess.
- Source unavailable
- A tool couldn’t be reached while the handoff was drafted. The gap is shown, not hidden.
Hand off the work, and the why.
Handoff is where context matters most. IL Co turns the conversation, the work, the code and the decisions around it into a handoff the next person can act on — and its author approves it first.
Around the work
- The conversation · Slack thread
- The issue · Linear
- The code · GitHub pull request
- Ownership · who has it, who gets it
IL Co context
Read from the Slack thread, the Linear issue and the GitHub pull request, and kept together.
Handoff
What was done, why, and what is left — every claim citing its source. Its author reviews and approves it first.
The next person continues
With the why, not just the what: accepted in Slack or the Inbox, with questions asked right on it.
- Every claim links to the Slack message, Linear issue or pull request it came from.
- What the sources don't say is marked unknown — never filled in.
- Nothing is posted to Slack or Linear until its author approves it.
Request beta access. Upgrade when handoffs are how you work.
Free for up to 10 people and 7 handoffs a month. No card. Works with Slack, Linear, Jira, GitHub and GitLab.