90 seconds, then it's on.

One short brief at the end of your day. Sourced answers for everyone who needs them while you're off.

01 · The brief

Your brief is mostly written before you start.

StandIn drafts it from the work that already happened in your tools. You fix what's off, add the one thing only you know, and hit publish. Ninety seconds.

Sarah's brief90s
What shipped today
Auth API refactor complete. PR #402 pushed and ready for review.
What's blocked
Ticket #482: waiting on Ops for a configuration credential before merge.
Who owns the next action
Dave Chen: review PR #402 and approve when Ops resolves #482.
Back online
Tomorrow 09:00 JST
Once published, your team can ask about this. You won't be pinged.Publish · 90 seconds
02 · The switch

When you're off, your StandIn is on.

It answers in your words, from your brief and your work history, with a source under every answer. The moment you're back, it steps back.

When you're off, your StandIn is on.Sarah publishes her brief in Tokyo at 5pm.
03 · Honesty

It never guesses.

When the answer isn't in your work, it says so and points to the person who does. That's why your teammates can trust what it says, and why you can stand behind it.

A
Alex · Amsterdam

@standin What did Sarah think of the vendor proposal?

SStanding in for Sarah

That isn't in Sarah's work. Priya reviewed the proposal; ask her.

I only answer from what was published in briefs and connected tools.
04 · A worked example

Sarah is asleep. Nobody waited.

Sarah's StandIn answers from her brief, timestamped, with her name:

A
Alex · Amsterdam · 10:00

Alex in Amsterdam asks at 10am his time: "Is the auth API ready to merge?"

SStanding in for Sarah17:00 JST

Yes, PR #482 is ready. Merge it if the JWT config has landed.

Source: Sarah's brief · Tokyo, 17:00 JST

Sarah is asleep. Nobody waited.

No one needs to ping her overnight.

See it answer for yourself.