01
The late message
Someone on the West Coast sends a question at 22:00 your time. You see it. Now you can't unsee it. You reply because you feel responsible.
For everyone who goes offline
Close the laptop. Stay closed.
StandIn builds your wrap from what you already did today — your commits, tickets, and captures. You review it, add anything missing, and publish. Then you close the laptop. Your teammates get answers while you're away.
01What wears you down
The quiet pressure of distributed work
It doesn't announce itself. It builds slowly, until you're checking Slack at midnight "just in case."
02
Staying on just in case
You could close your laptop at 17:30. But there's a handoff happening in San Francisco. You stay online until 20:00 waiting for a question that never comes.
03
Explaining the same thing every morning
Every morning begins the same way — describing what you did yesterday to the next shift. You've said the same thing about PR #482 five times this week.
04
Being the only one who knows
You hold context no one else has. This makes you feel important and trapped at the same time. Any question about your area requires you personally.
05
Interruptions that follow you home
You've left the office. Your phone hasn't. The boundary between work and offline has dissolved into a permanent state of mild availability.
06
On call without the pay
You're accountable 24 hours a day but you're only paid for eight. The implicit expectation is always-available, always-responsive.
02The flow
Your work already happened. Now it works for your team while you're offline.
Review three fields. Add a handoff note. Publish. Full coverage while you're gone.
Before you close the laptop
done
auth api refactor complete. pr #482 ready for review.
blocked
waiting on ops for jwt secret.
owner
dave owns next action.
next
back online 09:00 gmt tomorrow.
i · Step 1
Review your wrap.
Your wrap starts pre-filled from today's work — PRs merged, tickets moved, things you captured during the day. Scan three fields: what you did, what's blocked, what's next. Add a handoff note if something needs context. Publish.
Connected integrations feed your draft automatically. The browser extension captures anything the tools miss. Nothing publishes without your approval.
ii · Step 2
Close the laptop. Stay offline.
Silence your notifications. Your representative stands in for your overnight hours — answering questions about your work from what you actually published, not from guesses. Teammates who would have pinged you get a cited answer instead.
Once you've left a clear wrap, your team can keep working without you.
Notifications off — update published
alex (ny): “is the auth refactor ready?” → Answered by your representative.
dave: “who owns ticket #482?” → Answered by your representative.
priya: “what did sarah leave?” → Answered by your representative.
You are offline. You are not being pinged. Work is moving.
Your morning summary
Answered while you were offline
2 questions resolved. No action required.
Moved forward without you
PR #482 reviewed by Alex. Merged at 02:14 GMT.
Still needs you
JWT secret from Ops. One item outstanding.
iii · Step 3
Start your day knowing where things stand.
A single summary shows what your Representative handled overnight, what moved forward in your absence, and what actually needs your attention today. You're not catching up on hours of Slack — you're reading a short list.
03Hard limits
What StandIn never does.
Previous availability tracking tools got killed by engineering teams for one reason: they felt like surveillance. StandIn was built knowing that history.
These are hard limits baked into the system, not promises in a policy document.
$ denied
Your keystrokes are yours
StandIn does not count keystrokes, track active hours, record mouse movement, or know whether you're at your desk. None of this data exists.
$ denied
Your DMs are invisible
Your DMs are invisible. Your private channels are invisible. If you didn't publish it in a wrap, it doesn't exist inside StandIn.
$ denied
Your mood isn't data
StandIn cannot assess whether you're stressed, annoyed, or disengaged. It only answers from what you explicitly wrote.
$ denied
Your wraps aren't your manager's scorecard
There is no leaderboard, no manager dashboard, no productivity score. Publishing a wrap is a courtesy to your team, not a metric.
$ allowed
Your wrap is your statement. Not their evidence.
What you write in a wrap is on the record — that's the point. But nothing else about your behavior, your patterns, or your activity is recorded. The declared record protects you. The rest of your work is invisible.
These are system constraints, not promises. There is no admin toggle, no escalation path, no override. These capabilities simply don't exist in the product.
Read the security model04What you get
What you actually get.
A real offline. Not an anxious one.
i
Permission to close the laptop
When your wrap is published, you've done your job. You're not abandoning your team — you're handing off properly.
ii
Freedom from late pings
Your representative handles questions while you're offline. Questions get answered. You don't get pinged.
iii
Protection from availability pressure
StandIn gives you a structural answer to "why weren't you online?" — your wrap was published. Context was available.
iv
Accountable without being available
Your work is visible through what you publish. You're responsible for your wrap, not for being online.
v
Your declared decisions stay on the record
When you declare an approved decision in a wrap — a scope change, a deployment approval, a technical direction — it's timestamped and on the record. If someone reverses it later, the record exists. You're not defending a memory. You're pointing to a declaration.
05Your representative
Your Personal Representative
A Representative is the published side of you. When a teammate asks what you did, where PR #482 stands, or whether you approved the schema change — your Representative answers from your wraps, citing the exact line it read from.
Your Representative only knows what you published. It can't read your DMs, infer your mood, or guess what you meant. When it answers, it cites your wrap. When it can't answer, it says so. That refusal is what makes the rest of the answers trustworthy.
How Representatives workLeave a wrap. Log off. Work continues.
See how the wrap-to-representative flow works in practice.