Where the waiting is longest.
Across time zones, the waiting is measured in whole nights, and it lands hardest on the office furthest from headquarters. This is where StandIn started.
It starts as a math problem. It ends as a tax.
Amsterdam is nine hours ahead of San Francisco. London is eight. Sydney is already in tomorrow. That's the math. The tax shows up when the overlap window closes and the work doesn't.
Every distributed team pays it in some combination of these three patterns. They compound. They're invisible in any one day, expensive across a quarter.
The 8 PM ping
You check Slack "one last time" because another office is waking up. You answer. Now you're back at work, and you'll do it again tomorrow.
The half-day wait
You ask a question at 2 PM. The only person who knows the answer signed off at 1 PM. You're blocked until they log on. Multiply by three people, a full week.
The artificial urgency
Because delays hurt, everything becomes "urgent." Speed replaces clarity. Noise replaces signal. The team keeps moving and nobody is sure where it's going.
Offices had this solved, for free.
In a physical office, continuity is ambient. You can see who's around. You overhear the decision before it becomes a document. You know when someone leaves because they walk past you. Distributed teams inherit none of it by default.
Ambient presence
You see Sarah leave her desk. You don't send her a message expecting an instant reply. Nobody had to write that rule down.
Overheard decisions
The decision gets made in a hallway conversation. Three people absorb the "why" without anyone typing it up. Remote teams lose that every time.
Explicit handoffs
"Cover me, I'm heading out. The call about the vendor is at 4." One sentence at the door. Distributed work has no door.
Shared working time
Eight hours of overlap was the default, not a negotiation. Cross-continent teams fight to find two.
Remote lost all four, and tried to solve it with more Slack.
The standard fix was more channels, more threads, more "quick syncs," longer docs. All of it produces volume, none of it produces continuity. The work still resets every time a new timezone wakes up.
The next shift logs on and spends the first hour scrolling backwards (the Slack thread, the PR comments, the ticket, the doc) trying to reconstruct where the last shift left things.
Because nobody trusts the reconstruction, the people with the context stay on to explain it. Amsterdam answers pings at 10 PM. San Francisco pre-answers at 7 AM. The day never closes.
Remote workers don't burn out because they lack discipline. They burn out because they're personally compensating for a missing structural handoff. Time and attention are the fuel.
StandIn isn't faster communication. It's the handoff, written down.
A brief is the digital equivalent of "I'm heading out. Here's exactly where things stand, and here's who owns what next." The context stops living in a person. It lives in the record. When you log off, your teammates read the record instead of waking you up.
Publish the brief.
Sarah's brief is auto-drafted from her PRs, her tickets, and the two threads she was in. She reviews it for sixty seconds, adds one handoff note, publishes. Then she's actually off.
Read the rollup.
Alex opens his morning rollup. Sarah's brief is at the top, already summarized against the projects he owns. He knows what shipped, what's blocked, and what she's asking him to pick up. No archaeology.
Is the auth refactor ready to merge?
Yes. Sarah's brief confirms it's complete and PR #482 is ready for review.
Notice what didn't happen. Sarah didn't stay online. Alex didn't wait nine hours. No 8 PM ping. No 7 AM pre-answer. The handoff happened while both of them were asleep.
What changes when the handoff is structural.
The 5 PM hard stop becomes real.
Publishing your brief is the closing ritual. Once it's up, your team has what they need. You can actually log off, without guilt, without the one-more-check spiral.
Mornings start already briefed.
The first thirty minutes aren't spent scrolling Slack and piecing together what happened overnight. You open one rollup and you're caught up on the things that touch your work.
The "just checking in" Slack dries up.
When the answer is already in the record (cited, dated, attributed) nobody needs to ping the human. The interruption budget gets paid back to focused work.
This isn't for everyone. Three honest cases.
StandIn assumes a specific posture about work: written context, asynchronous trust, durable handoffs. If any of the following sound like your team, this will fight you more than help you.
You need real-time response as a metric.
StandIn is built for depth, not speed. If the thing you're measuring is minutes-to-reply, this is going to feel slow on purpose.
Your team won't publish.
The whole system is downstream of people actually publishing briefs. If briefs aren't going to happen four days a week, nothing downstream works.
You want a visibility tool.
StandIn records work, not workers. It won't tell you who was online, how long, or how fast. If that's the brief, you're looking for a different product.
After the brief, your StandIn takes the next shift.
When Sarah publishes at 17:00 in Tokyo, her Personal StandIn goes live. For the rest of her evening, Alex in Amsterdam can ask it questions and get sourced answers drawn from what she actually wrote. He doesn't wait for Tokyo to wake up. She doesn't get pinged at 2 AM.
Her StandIn cites her brief, says "I don't know" when the answer isn't there, and stays on until she publishes again the next day. The timezone handoff stops being a daily negotiation and becomes a quiet, automatic exchange.
How StandIns work →