BlogHow-to

How to set up a morning brief you actually read

Inbox, calendar, orders, and portals patrolled before you sit down. Set up a two-minute morning brief, sorted worst first, with copyable asks.

The first hour of most workdays is a patrol: inbox, calendar, the order queue, the tracker, a portal or two, all visited mostly to confirm that nothing changed overnight. The patrol has to happen. It does not have to be you.

The exceptions are real, after all. Somewhere in those tabs is the shipment that stalled, the payment that bounced, the reply that finally landed. The problem is the ratio: sixty minutes of checking to find the four minutes that matter. Worse, the patrol fails on the mornings it matters most: the busy morning you skip it is the morning the stalled shipment gets a second day older.

Why dashboards don't get read

Dashboards show everything all the time, which is a polite way of showing nothing. What a morning needs is a brief: written, short, sorted worst first, and opinionated about what needs a human today. A good brief also admits what it could not check, which is the difference between a report and a rumor.

The two-minute rule is a useful forcing function. If the brief takes longer than two minutes to read, it is carrying inventory instead of exceptions, and the fix is a tighter threshold, not a faster reader.

What belongs in a morning brief?

Three things. Exceptions: whatever crossed a threshold overnight. Movement: the items you were waiting on that finally moved, or quietly resolved themselves. Open loops: who owes you what, and for how long. Links on all of it, so acting takes one click instead of a search. Anything that needs a decision gets a line of context, enough to decide without re-investigating.

Start with the everything sweep. It reads across your inbox, sheets, and portals and comes back with one list of open loops, stalled items first.

Do a status sweep of everything we're waiting on. Go through [sources, e.g. the inbox, the Waiting On tab, and the open items doc] and check each item at its source: has the reply landed, the status changed, the document arrived? Mark each item moved, stalled, or resolved, and note who owes the next step. Update the tab and brief me, stalled items first. Tell me the total count and flag anything you couldn't check.
Use caseCheck everything we're waiting on and brief meSweep the inbox, sheets, and portals for everything we're waiting on and where it stands.View →

If your mornings revolve around orders, make the brief operational. This one patrols the store, the carrier tracking pages, and the vendor portals before you are fully awake, and returns the short list of orders that need a human.

Every morning, check open orders across Shopify and the carrier tracking pages [carriers, e.g. FedEx and UPS], plus the vendor portals for inbound POs. Flag what needs attention: shipments stalled more than [threshold, e.g. 2 days], orders unfulfilled past our ship promise, inbound POs that slipped. Update the ops tracker and write me a short brief, worst first, with links. Tell me the counts and anything you couldn't check.
Use caseCheck the carriers and vendor portals and brief meCheck the carriers and vendor portals for orders that need attention, and brief me.View →

Weekly briefs suit work that moves weekly. Here is the property version, Monday morning, worst first; swap in whatever your week orbits. The ordering matters more here than anywhere, because Monday attention is the scarcest kind.

Every Monday, pull two things from AppFolio for [portfolio, e.g. all three buildings]: the delinquency report and the open work orders. For delinquencies: who, how much, how many days, and whether a payment plan exists. For work orders: anything open past [SLA, e.g. 7 days], anything marked urgent, and vendors who haven't responded. Update the ops sheet and brief me worst first. Flag anything that looks like a data error rather than a real problem.
Use caseBrief me Monday on delinquencies and open work ordersPull delinquencies and open maintenance from AppFolio and brief me, worst first.View →

Keeping it honest

Brief asks are read-and-report by design: nothing changes except the tracker you named, and nothing outward ever goes without you. Every brief ends with what could not be checked, so silence never masquerades as good news. Open the session any morning and watch the patrol run if you want to audit your own coverage.

How is this different from notifications?

Notifications interrupt; a brief waits. Notifications arrive one at a time with no ranking; a brief is sorted worst first by something that read all of it. And notifications only cover the apps that thought to ping you, while a brief patrols the places that never ping: the portal, the tracker, the aging sheet. You already triage all day. The morning brief is the one place where the triage was done before you arrived, which is also why briefs age well: thresholds tune, and the brief gets sharper the longer it runs.

The schedule is the point

A brief you have to request is just a report; a brief that arrives on its own is infrastructure. Set the patrol to Routine · daily 7am and the portfolio version to Routine · Mondays 8am, then tune. Tighten thresholds until the brief stays under two minutes; loosen them if it starts missing things you cared about. Tuning takes a sentence. Briefs land before the day starts on purpose: that is when a ranked list of exceptions is a plan rather than an interruption.

See also: Routines that run themselves for how schedules work, and How to automate email follow-ups that wait for your OK for what to do with the open loops the brief surfaces.

The patrol was never the job; the exceptions were. Read two minutes of worst-first instead of walking the tabs yourself. Get early access on macOS or Windows; when access opens, make the morning brief your first routine.

Related