01
The Context Gap
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
pages.rolesEngineering.heroBadge
pages.rolesEngineering.heroHeadline
StandIn aggregates your team's GitHub commits, Linear tickets, and Slack decisions into structured handoffs. Engineers review a pre-filled wrap and publish. The next shift gets answers from the record — no late-night pings, no 45-minute standup, no morning archaeology.
Last updated: March 2026
01pages.rolesEngineering.sectionPain
02
PR Limbo
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
03
Staying Online Just In Case
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
04
Dead Docs
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
05
Decisions that evaporate
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
02pages.rolesEngineering.sectionValues
Built the way engineers want tools to work.
i
No monitoring
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
ii
Silence is respected
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
iii
No speculation
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
iv
Your tools stay the source of truth
Context resets every time a shift changes. Amsterdam wakes up and spends two hours figuring out what San Francisco did yesterday.
03pages.rolesEngineering.sectionHow
Better handoffs, not better processes.
Replace “being online” with “having left a good wrap.”
# before you close the laptop
@sarah (amsterdam) wrapped at 18:00.
done today:
— auth api refactor complete.
— pr #482 ready for review.
blocked on:
— waiting on ops for new jwt secret.
done today:
— auth api refactor complete.
— pr #482 ready for review.
blocked on:
— waiting on ops for new jwt secret.
i · close cleanly
Close the laptop cleanly.
Your wrap drafts itself from today's commits and ticket updates. Review three fields, add anything the tools missed, publish. It's a commit for your workday — and most of it writes itself. Once you publish it, your team knows where things stand and you can actually go offline.
ii · answers overnight
Close the laptop cleanly.
Your wrap drafts itself from today's commits and ticket updates. Review three fields, add anything the tools missed, publish. It's a commit for your workday — and most of it writes itself. Once you publish it, your team knows where things stand and you can actually go offline.
#project-atlas · 09:15 am est
alex (ny): is the auth refactor ready to merge?
standin: yes. sarah's wrap (18:00 gmt) confirms it is complete.
ref: pr #482 (open)
ref: pr #482 (open)
04pages.rolesEngineering.sectionCoverage
Know where the gaps are before handoff.
Two views that read from published wraps. No data entry. No status meetings.
Coverage board
Who's published today and who hasn't. Not a leaderboard. Not surveillance. Just a heads-up so you know if someone's state is missing before your shift starts.
Gaps show up as “no state declared.” People fill it in because they see the gap, not because something blocks them.
Project health
Who's published today and who hasn't. Not a leaderboard. Not surveillance. Just a heads-up so you know if someone's state is missing before your shift starts.
Gaps show up as “no state declared.” People fill it in because they see the gap, not because something blocks them.
05pages.rolesEngineering.sectionTeamReps
Team Representatives
Team Representatives roll up every engineer's wrap into a single queryable surface. Your sprint status is a query, not a meeting. Ask the Team Representative what shipped overnight, what's blocked, or who owns the next action. It answers from what the team published and cites every source.
Your wrap drafts itself from today's commits and ticket updates. Review three fields, add anything the tools missed, publish. It's a commit for your workday — and most of it writes itself. Once you publish it, your team knows where things stand and you can actually go offline.
How Representatives work— Worth knowing
When NOT to use StandIn
StandIn is not designed for teams that require real-time synchronous availability, like L1 incident response rooms.
Diagnose your team's handoff problem