01
The reversal problem
Engineering ships based on a decision that was made over Slack and never written down. Monday morning a PM asks 'wait, did we actually agree to that?' — and nobody can prove the original call was made, by whom, or when.
For EMs, CTOs & VPs
Lead with context, not control.
StandIn gives you a structured, cited record of what your distributed team decided, shipped, and got stuck on — without monitoring anyone or adding a meeting to their calendar.
See how it works01What breaks without it
02
The visibility trap
You can see who's typing. You can't see what's actually moving. So you check presence indicators and convince yourself that green dots mean progress — while the real signal is buried in PR queues you never open.
03
Meeting bloat
The status meeting exists because the status doesn't exist anywhere else. Add another sync. Add another async update request. The calendar fills. The clarity doesn't.
04
Silent burnout
Your Amsterdam lead is answering Slack at 23:00 because San Francisco won't stop asking. You never told them to — but you never gave them permission to stop, either. By the time the signal reaches you, they're already drafting a resignation.
05
Trust erosion
Each tool you add that watches people harder is a vote that you don't trust them. Engineers notice. The best ones leave first. You're left with the people who don't mind being watched.
02Who this isn't for
This tool is not for every leader
StandIn is built for leaders who want to understand work progress, not monitor people. If you're looking for activity tracking, keystroke logs, or productivity scoring, StandIn will actively block those queries — by architecture, not policy. It's designed to make surveillance use impossible, not just discouraged. If that's the use case, a different tool serves it better. If you want visibility into decisions and blockers without burning your team's trust, read on.
Diagnose your team's handoff problem
03How it helps
From checking up to checking the record.
See blockers and progress. Don't check whether people are online.
Project-level clarity
Instead of asking 'Is Sarah working?', you ask 'Where does Project Atlas stand?' StandIn pulls together individual wraps into a coherent project view.
> query: status of q3 launch?
> standin: design approved (amsterdam). engineering blocked on api keys (sf). ops investigating.
i · work, not worker
See the work, not the worker.
StandIn shifts the focus from presence to progress. Instead of wondering if someone is at their desk, you can ask whether the blocker got cleared. This is how you manage output without micromanaging people.
ii · normal hours
Everyone keeps normal hours.
Amsterdam logs off at 18:00 knowing the record is left. San Francisco wakes up and gets unblocked from the wrap, not from a ping. The shift where someone is 'always available' becomes the shift where nobody has to be.
Normal working hours for everyone
Amsterdam closes at 18:00. San Francisco opens at 09:00. The handoff happened in writing, not in a calendar invite. Nobody got pinged after dinner. Work still moved.
04The record
When a decision was made, you can prove it
When a decision is written into a wrap — a release approval, a scope change, a technical direction — it becomes a timestamped record. If someone challenges it later, the evidence is there. StandIn doesn't prevent reversals. It makes them visible.
#standin · query
query: was the api migration approved before friday's handoff?
standin: yes. sarah's 17:00 wrap on march 14 notes: ‘api migration approved for q2 deployment. owner: sarah. successor for approvals: dave.’
source: wrap #847, 17:00 gmt.
source: wrap #847, 17:00 gmt.
"That's not a status update. That's evidence."
05The boundaries
What a leader sees, and what a leader can't.
Two columns. A hard wall between them. The wall is enforced by the code, not by a policy document.
$ What leaders can see
Progress and blockers
Status of tickets, PRs, roadmap items — drawn from what the team published in wraps, not inferred from activity.
Declared decisions
Every scope change, release approval, and direction call that was published — with the author, timestamp, and the wrap it came from.
Coverage and gaps
Which threads are current, which have gone quiet, and where ownership has drifted. Gaps show up as 'no state declared' — not as red flags next to a name.
$ What leaders can never see
Individual activity
Keystrokes, active hours, mouse movement, login times, 'last seen' — none of this is collected. It cannot be queried because it does not exist.
Private conversations
DMs, private channels, group chats. If it wasn't explicitly published in a wrap, it is invisible to StandIn and to you.
Work ranking
Who publishes most. Who's 'most productive.' Who's quiet. StandIn refuses to produce leaderboards across individuals — the query returns nothing.
06Why limits
Why limits build trust
i
People control their own narrative
StandIn only reports what users explicitly publish. They own what's on the record — and that ownership is why they publish in the first place.
ii
It stays in its lane
StandIn is a guest in your Slack. It reads the channels it was invited to, nothing else. It doesn't walk into private spaces or act outside the grant it was given.
iii
Silence stays neutral
Not publishing today is a valid state. The tool doesn't penalize it, flag it to a manager, or surface it on any dashboard that ranks humans.
07Team & project views
Roll-ups without a roll-call.
Your leads review their team's draft, add decisions and risks, and publish. You read the roll-up and know where every project stands — without scheduling a single meeting.
Team aggregation
Individual wraps feed a team-level summary your lead reviews and publishes. You see the team's week as a coherent picture, not a pile of fragments you have to reassemble.
Project health
For each cross-team initiative, see which threads have recent wraps, which have gone quiet, and where decisions are still pending — with the owner's name attached.
Coverage visibility
Who's on, who's off, what's covered, what isn't. Not a presence dashboard — a handoff view, so you know whether a project has someone awake when something breaks.
08Governance
A governance record, generated as a side effect.
StandIn produces a permanent, verifiable record of every decision, authority resolution, and handoff — sourced from what your engineers actually wrote, exportable for auditors and acquirers. You don't have to build it. It accumulates.
See the decision and handoff record →09Representatives
Team Representatives
Team Representatives are how you get answers about distributed work without pulling anyone into a Zoom. Every answer is sourced to a named engineer and a timestamp. No one gets interrupted. No one schedules a status meeting just so you can ask three questions.
A Representative never paraphrases. It quotes. If the question can't be answered from published wraps, it says so — and names the person who'd need to answer. You get the same answer you'd get from a status meeting, without taking the hour.
How Representatives work