Guides / Topic

Remote Ops

The day-to-day running of a team that works apart: who is doing what, what is stuck, when work changes hands and how decisions get made without a meeting.

11 guides. Last updated . What's new

What remote ops covers

Remote ops is the operational layer under a distributed team. It is not the product work itself. It is the status updates, reminders, handoffs and small decisions that let people in different places and hours keep moving without waiting for each other.

Big companies give this to an operations team or a program manager with dedicated software. At a company of five or fifty it usually lands on a founder, an office manager or whoever set up the project tracker, and the tools are the ones already paid for: a Google Sheet, Slack, Notion and a shared calendar.

When it works nobody notices. When it does not, people ask "where are we on this?" in three channels, a reminder goes out twice, a handoff is missed by an hour because of a clock change, and a decision sits open for a week because nobody said when it closes.

Where it usually goes wrong

Status lives in chat
Updates are scattered across threads, so the only way to get the full picture is a meeting. A weekly digest built from the tracker replaces the round of "any updates?" messages.
Blocked work hides in a long list
A tracker with 200 rows does not show the five that are stuck. A filtered view, or a daily post of just the blocked items, puts them in front of the people who can unblock them.
Reminders repeat or never arrive
Simple scripts send the same reminder every time they run. The fix is to record what was sent, which takes a few lines of code and is easy to leave out.
Times are converted by hand
Someone adds or subtracts hours in their head, and twice a year daylight saving makes the answer wrong. Storing times in UTC and converting per person fixes it once.
Decisions have no deadline
An async decision without a closing date becomes a meeting. A log with an explicit "respond by" date tells everyone when the decision closes.

How these guides help

Each guide solves one of these problems inside software you already use, with a formula or a short script rather than a new subscription. You get the answer at the top, a small sample table to try it on, the code to copy, and a list of what it needs: which sheet tabs, which columns, which permissions Google will ask for.

Every guide ends with a check note that says how it was verified. Formulas and templates are checked against their sample data. Scripts are syntax-checked and reviewed against the published API documentation; none of the scripts in this topic has been run in a live account yet, and each note says so, so try them on a copy first.

The 11 guides

Status without the status meeting

Turn the tracker your team already updates into something people read: a weekly digest, a Notion report page, or a short daily list of what is blocked.

Reminders and deadlines

Get due dates out of the tracker and in front of people, once, where they will see them, and ask for the weekly update without chasing anyone.

Time zones and decisions

Handoff times that are right for everyone, and a written way to decide things without getting everyone online.

Questions

Do I need to know how to code?

Not for the formula guides: you paste a formula into a cell. The script guides use Google Apps Script, which opens from Extensions > Apps Script in any Google Sheet. You paste the code, set the values the guide lists, and approve the permissions Google asks for. Reading the code before you run it is a good habit, and the scripts are kept short enough to do that.

Why build this in a spreadsheet instead of a project management app?

Many small teams already track work in a sheet, and a few formulas or a short script can take it a long way before another per-seat subscription is worth it. If you do move later, a tracker with one row per task and clear owner, status and due date columns imports into most project tools.

Will a script send messages as me?

The reminder guide sends email and the Slack guide posts to a channel. The digest guide only creates a Google Doc, the calendar guide writes events to a calendar you choose, and the Notion guide creates a page. Scripts run under the Google account that installs them, and the scheduled ones stop when you delete their trigger. Each guide lists the permissions involved before you start.

Esc