Decide whether to write, meet, or wait

You lose a day when a question arrives without an owner. They answer with a question. You reply after their night. Someone then books a call to rebuild the message that should have been sent first.

A write-first request is complete enough to answer without a follow-up. A response window says when a reply is fair. A meeting happens only when voices in the same hour are cheaper than another written round.

Information someone can read later is a written update or a doc comment. If they cannot open the artifact, fix the permission. A meeting will not grant access.

A choice between two options names A, B, your recommendation, and the UTC time the default applies if comments stay quiet. Meet only when that written round still ties the choice. "Thoughts?" is the brief you skipped.

One owner can unblock you when the note includes the verify step. Share a screen only when another screenshot would cost more than the overlap you have.

Three regions move the artifact overnight and decide inside the thickest pairwise window. A three-way call is for a conflict the relay could not close. The overlap rules are in timezone collaboration without chaos.

Status belongs in the end-of-day note, not in a call that reads the ticket aloud. Use the buckets in end-of-day status update. How those lines scan is in how to write async status people actually read.

Sensitive feedback is a scheduled 1:1 inside overlap. A public thread is the wrong room.

If the writing shows that nobody knows the next move, fix the action before you reserve time. Thirty minutes will not invent a missing owner.

Name the path out loud. Status goes to the ticket, a decision to the doc, a how-to to the runbook, a blocker to the named channel, an incident to the page. "Just ping me" is what people say when those paths are missing. Replacing the habit is in when "just ping me" replaces a system. A live hour that survives this sort still has to earn its slot: fewer and better remote meetings and when a remote team needs a meeting.

Publish response windows before chat habits form

"Always available" feels kind for about a week. Then a 02:00 ping expects a reply and an apology. Publish the window. A reply outside it can be a favor. It must not become the job. If a new hire cannot point at the sentence, you do not have a window.

During the agreed overlap, chat is fair and a same-day reply is the aim. Instant is a different product. Production instant-reply is the on-call rotation, paid and named.

Outside overlap, the message has to already be complete, and the reply waits for the next overlap. Overnight silence means the window is working. A midnight nudge "in case you are up" means it is not.

Urgent is one named channel, or the contract phone, for production that is down. A vague ask is not urgent because the sender feels stuck. If everything is urgent, read available all day is a bad system. Write who may use the path: on-call may page, a Thursday demo may not, a client uses the contract number and no other.

Put the UTC range where week one will find it. Re-post it when the roster changes and on the week the clocks move. Misses from that week are in DST mistakes remote teams make. Wording is in response expectations that respect time zones. Map hours before you publish a range you cannot keep: timezone collaboration without chaos.

Example. Assumptions: six engineers, Berlin and New York, paid on-call with a named rotation, everyone else off call. P1 gets a reply within one hour inside overlap, or on the page path if it fires outside. P2 gets a reply on the next workday in the requester's zone. Everything else is a written request with a UTC deadline. "Can you look today" is not a P2.

Example. Assumptions: you are a freelancer, the statement of work names email, chat is not included, weekends are off unless paid on-call says otherwise. You check email at 11:00 and 16:00 local, those clocks are in the kickoff note, and a message at 18:30 waits. Production down uses the contract phone.

Example. Assumptions: product and design share one doc, Thursday overlap is about two hours, legal is not in the thread. Comments are due at 17:00 UTC Tuesday. You book 25 minutes on Thursday only if two options are still tied. Otherwise you record the recommendation and ship the default. A skipped comment is not a tie.

"End of day" is three instants. Write the UTC hour. "Tomorrow morning" is a different time for every reader.

Hold the send until six fields are real

Do not send while a field is empty. Your delay is cheaper than a night of questions in the other zone.

The outcome is one sentence. "Checkout" is a topic. "Choose the provider for PAY-200" is an outcome. ASAP is not a deadline. If you cannot name a UTC hour, you do not yet know whether this is a decision. If the link needs secret history, put that history on the ticket first. "Any ideas" asks them to start their day on your thinking. With no options yet, ask for one experiment and a time box.

"Looks good" is not a verify step. A command, a click path, or a comment on a named ticket is. If you cannot describe the check, you will disagree later about whether the work happened. The owner if the thread stays silent is you, executing a default you will really carry out. A bluff teaches people to wait for a meeting. "We will figure it out" is not a default. If another team must act, name them.

Copy the six-field request template

Decide whether to write, meet, or wait You lose a day when a question arrives without an owner. They answer with a question. You reply after their night. Someone then books a call to rebuild the message that should have been sent first. A write-first request is complete enough to answer without a follow-up. A response window says when a reply is fair. A meeting happens only when voices in the same hour are cheaper than another written round. Information someone can read later is a written update or a doc comment. If they cannot open the artifact, fix the permission. A meeting will not grant access. A choice between two options names A, B, your recommendation, and the UTC time the default applies if comments stay quiet. Meet only when that written round still ties the choice. "Thoughts?" is the brief you skipped. One owner can unblock you when the note includes the verify step. Share a screen only when another screenshot would cost more than the overlap you have. Three regions move the artifact overnight and decide inside the thickest pairwise window. A three-way call is for a conflict the relay could not close. The overlap rules are in timezone collaboration without chaos. Status belongs in the end-of-day note, not in a call that reads the ticket aloud. Use the buckets in end-of-day status update. How those lines scan is in how to write async status people actually read. Sensitive feedback is a scheduled 1:1 inside overlap. A public thread is the wrong room. If the writing shows that nobody knows the next move, fix the action before you reserve time. Thirty minutes will not invent a missing owner. Name the path out loud. Status goes to the ticket, a decision to the doc, a how-to to the runbook, a blocker to the named channel, an incident to the page. "Just ping me" is what people say when those paths are missing. Replacing the habit is in when "just ping me" replaces a system. A live hour that survives this sort still has to earn its slot: fewer and better remote meetings and when a remote team needs a meeting. Publish response windows before chat habits form "Always available" feels kind for about a week. Then a 02:00 ping expects a reply and an apology. Publish the window. A reply outside it can be a favor. It must not become the job. If a new hire cannot point at the sentence, you do not have a window. During the agreed overlap, chat is fair and a same-day reply is the aim. Instant is a different product. Production instant-reply is the on-call rotation, paid and named. Outside overlap, the message has to already be complete, and the reply waits for the next overlap. Overnight silence means the window is working. A midnight nudge "in case you are up" means it is not. Urgent is one named channel, or the contract phone, for production that is down. A vague ask is not urgent because the sender feels stuck. If everything is urgent, read available all day is a bad system. Write who may use the path: on-call may page, a Thursday demo may not, a client uses the contract number and no other. Put the UTC range where week one will find it. Re-post it when the roster changes and on the week the clocks move. Misses from that week are in DST mistakes remote teams make. Wording is in response expectations that respect time zones. Map hours before you publish a range you cannot keep: timezone collaboration without chaos. Example. Assumptions: six engineers, Berlin and New York, paid on-call with a named rotation, everyone else off call. P1 gets a reply within one hour inside overlap, or on the page path if it fires outside. P2 gets a reply on the next workday in the requester's zone. Everything else is a written request with a UTC deadline. "Can you look today" is not a P2. Example. Assumptions: you are a freelancer, the statement of work names email, chat is not included, weekends are off unless paid on-call says otherwise. You check email at 11:00 and 16:00 local, those clocks are in the kickoff note, and a message at 18:30 waits. Production down uses the contract phone. Example. Assumptions: product and design share one doc, Thursday overlap is about two hours, legal is not in the thread. Comments are due at 17:00 UTC Tuesday. You book 25 minutes on Thursday only if two options are still tied. Otherwise you record the recommendation and ship the default. A skipped comment is not a tie. "End of day" is three instants. Write the UTC hour. "Tomorrow morning" is a different time for every reader. Hold the send until six fields are real Do not send while a field is empty. Your delay is cheaper than a night of questions in the other zone. The outcome is one sentence. "Checkout" is a topic. "Choose the provider for PAY-200" is an outcome. ASAP is not a deadline. If you cannot name a UTC hour, you do not yet know whether this is a decision. If the link needs secret history, put that history on the ticket first. "Any ideas" asks them to start their day on your thinking. With no options yet, ask for one experiment and a time box. "Looks good" is not a verify step. A command, a click path, or a comment on a named ticket is. If you cannot describe the check, you will disagree later about whether the work happened. The owner if the thread stays silent is you, executing a default you will really carry out. A bluff teaches people to wait for a meeting. "We will figure it out" is not a default. If another team must act, name them. Copy the six-field request template

Need: [one sentence outcome]
By: [deadline in UTC]
Context: [link to the ticket, doc, or pull request]
Options / recommendation: [A, B, and which you recommend, or "action only, no decision"]
How I'll verify: [the check that proves done]
If no reply by the deadline: [the default you will actually execute]

Paste the block and change the nouns.

Example. Assumptions: the choice is between two named checkout providers, the cost table and risk notes already live on the ticket, legal has not flagged either provider, and you will ship if the thread stays quiet.

This ask creates the five pings:

Thoughts on checkout? ASAP thanks.

This one can sit overnight:

Need: Choose checkout provider A (Stripe) or B (Adyen) for PAY-200
By: Thursday 16:00 UTC
Context: PAY-200 (cost table and risk notes are on the ticket)
Options / recommendation: A has lower fees. B has stronger EU SCA defaults. I recommend A.
How I'll verify: A decision comment on PAY-200 and the ticket owner updated
If no reply by the deadline: Ship with A. Revisit only if legal flags an SCA gap.

When the deadline passes with no reply, the default applies. Silence is not a veto and it is not extra time. Send one bump. Repeat the six fields, set a new UTC cutoff, and restate the default.

Bumping PAY-200. Same recommendation: ship provider A. New cutoff is Friday 16:00 UTC. If there is no comment by then, I will ship A and record it on the ticket.

A second bump with no new cutoff is a meeting request you have not earned. If one written round still ties two options you will defend, book a short live slot and take it from the meeting budget in fewer and better remote meetings. Do not grow a standing series from one stuck thread.

Keep the record small: context, options, the choice, the owner, the date, and when you will revisit. A light pattern is in document team decisions without bureaucracy.

One default must not auto-apply. If carrying it out would spend money you cannot reverse, ship a migration, or take a legal position nobody has seen, write this instead: "do not ship, and book the next overlap slot." A surprise hold teaches people to ignore the next default.

Put the decision where the next reader can find it

A complete note in a place nobody searches is still lost. You will explain it again, live.

Status lives on the ticket, or in one named channel. Cancel the standup that reads the ticket. A lead skims the Blocked filter.

Decisions live in a doc with a comment deadline. If you use chat, one topic, the ticket link in the first message, and a closing summary. When you inherit a long thread, read the latest summary, then the decision, then open questions. Read history only when those two disagree.

After you answer a new question once, add it to the runbook and reply with the link. A blocker with no named owner is yours until the ticket names one. "Waiting on someone" does not say who, or what done looks like. Social time can be live when the invite says social. An unlabeled morning call trains people to decline the decisions too.

Choose a status note, one bump, or twenty minutes

Stuck work has three moves. A fourth channel splits one ask across partial readers.

You still own tomorrow. Write Done, Open, Blocked, and Next in one place. Elsewhere, link it. Buckets: end-of-day status update. The test in how to write async status people actually read is whether someone offline can name your next physical move.

The deadline on a complete ask already passed. One bump, same six fields, new UTC cutoff, default restated. "Any update?" gets you "looking," which is not a decision.

The options are still tied after one honest round. Book twenty minutes, required people only, choice written before you leave. No exit line means you are not ready. Cut the choice in half and return to the brief. Do not promote the slot into a series.

Ownership crosses a night. Handoff fields: state, proof, next move, blockers, what not to redo. If they must ping you to start, fix proof or next before logout. Method: leave work someone else can continue.

One cadence: end of day for the squad, a midweek client note with one decision ask, Friday done plus Monday's first move. Two homes for the same news means Monday is reconciliation.

Example. Assumptions: you own the work through Friday, another zone may read it in their morning, nothing is on fire, the pull request is the record. Name the pull request, the check you ran, the step left, and your first move. Do not ask anyone to keep an eye on it. Name an action and a UTC time, or say you still own the ticket.

Publish the norm and redirect the unstructured ping

The norm is a page. Paste this and replace the brackets. If a line is false, change it before you publish. A norm you ignore trains people to skip the next one.

Write first. Meet only when one written round still ties a real choice.
Status: Done / Open / Blocked / Next in [location]
Overlap hours: [UTC range] on weekdays
Outside overlap: complete written request, reply next overlap
Urgent: [channel] for production down only
Decisions: doc, UTC deadline, default if silent
Handoff when ownership crosses a night: State, Proof, Next, Blockers, Do not redo

Walk a new hire through it for thirty minutes on a live ticket. Fill the six fields together. A fake ticket hides the hard part: finding the link and a default you will execute. Say what overlap is not. It is not instant reply, and it is not a reason to put status in the only hours two cities share.

Use verbs and UTC dates. "I don't love it" is not a critique. Name the alternative and the deadline.

Redirect a ticketless direct message where others can see it:

Logged on TICKET-88 with options A and B. Reply there by Thursday 16:00 UTC. I will not track this in DMs.

Do not also answer in the direct message. A fast ticket reply is fine. A private answer buys a permanent exception.

Three weeks if "just ping me" is the habit. Week one, publish the paths. Week two, leads redirect in public with the link. Week three, a question asked three times gets a doc section before Friday. Watch repeat questions, and whether a new hire can file a complete request alone. Do not watch who is fastest in chat. Answer complete requests before the deadline. Redirect fragments even when you know the answer.

Fix one weekly number before Friday

Pick one count. Fix it before Friday.

Example. Assumptions: six people, Berlin and New York, two to three shared daytime hours, tickets are the record, no daily standup. Monday outcomes go on the epic. Tuesday comments are due at 17:00 UTC. Wednesday is a 20-minute slot only if comments still tie. Thursday pairing is only for a bug that failed a written reproduce. Friday is the rollup and Monday's first move. Social time is optional and labeled.

Example. Assumptions: one freelancer, one client, email is the contract channel, your zone is Central European Time, weekends are off. Send this, including on a week you happen to be free at 18:00:

I check email at 11:00 and 16:00 CET on workdays. Production down: call the number in the statement of work. Everything else gets a same-day reply inside those two checks.

Always-on is a different product. Price it or decline it. A launch-week exception needs an end date in the same sentence. When it ends, restate the two checks.

Count four things. No owner or no UTC date: add the default, or the brief is not ready. Pings outside overlap: re-post the hours and redirect once in public. Meetings with no pre-read: cancel, or require the link a day ahead. Budget and exit lines are in fewer and better remote meetings. A repeated question with no doc: write the section and reply with the link only.

If the windows are the mess, recompute them in timezone collaboration without chaos. Write first, with an ask, an owner, and a UTC deadline. Meet when one written round still ties a choice you will defend. Publish the overlap so sleep is not scored as a slow reply.