01 / PLANNED
Keep open threads visible
Planned briefs would distinguish an active incident from a resolved issue that still needs a follow-up.
On-call handoffs · Early research
Start your shift with the context that matters.
A planned on-call handoff brief for small engineering teams, with open incidents, temporary workarounds, and acknowledged next steps. Join the waitlist.
Get early access ↗In research · Join the waitlist · No payment required
Designed around engineering teams rotating responsibility for a running service.
Concept preview · fictional example
| Open thread | Context | Next action |
|---|---|---|
| Queue delay | Retry limit raised | Review after peak |
| Noisy latency alert | Known threshold issue | Track tuning task |
| Database warning | Investigation open | Check replica metrics |
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION
The schedule says who is on call. It does not explain which alert is noisy, which workaround is temporary, or what the previous responder was about to check.
THE PRODUCT WE’RE EXPLORING
ShiftRelay, in three parts.
ShiftRelay would prepare a short handoff record from selected incident notes. The outgoing responder would verify it, and the incoming responder would acknowledge the open work.
Three planned capabilities we want to validate with early users.
02 / PLANNED
Name temporary workarounds
Proposed fields would capture the reason, owner, and review time for a workaround that remains in place.
03 / PLANNED
Confirm the handoff
Planned acknowledgment would show which incoming responder reviewed the brief and which questions remain.
AN INTENDED WORKFLOW
A clearer next step.
Less work around it.
A focused approach for engineering teams rotating responsibility for a running service.
- 01
Gather the shift context
A pilot would start with permitted incident links and concise responder notes; paging would stay in your existing system.
- 02
Review the brief
The outgoing responder would check status, temporary changes, and the next action for each open item.
- 03
Acknowledge and continue
The incoming responder would accept the brief and record any missing context before taking over.
HELP SHAPE THE FIRST VERSION
A better workflow starts with your experience.
Join the ShiftRelay waitlist for early-access updates and an optional research conversation.
This product is in research. Planned features and integrations are not available yet.
NO PAYMENT · NO COMMITTED LAUNCH DATEYOU’RE ON THE LIST
Thanks for raising your hand.
Your signup has been received for ShiftRelay. There is no confirmation email to look out for.
Manage your data ↗GOOD TO KNOW
A few useful answers.
Does ShiftRelay page responders?
No. This is a waitlist, and the proposed scope is handoff documentation. It would not replace paging, escalation, or your live incident response system.
Can I connect incident accounts today?
No. Account connections and automated brief creation are not available. Pilot integrations would be confirmed before access is requested.
How is this different from a project handoff?
This concept covers recurring operational shifts for running services, with unresolved incidents and temporary workarounds. It does not manage website delivery or client project transfer.