Workflows · Day-start rundown

Start the day knowing what changed overnight

The rundown reads the systems you’d otherwise open one by one and lands before the day starts: what changed, what’s blocked, what’s waiting on a decision, and what it couldn’t see. You decide what to do about any of it.

Get a free written assessment

The day starts with a scavenger hunt

An owner or operations lead opens the inbox, the CRM, the support queue, the project tracker, the order system, and yesterday’s notes to work out what changed. Most of that scan finds normal work. The value is in the few exceptions and decisions buried across those systems.

This fits leaders in professional services, logistics and distribution, B2B services, ecommerce, SaaS, and media production who keep scanning the same sources. It needs a short list of the decisions you actually make and stable read access. It isn’t a company summary or a place to dump every metric you have.

We run this one ourselves. Inside our own media and creative agency it reads what happened overnight, pulls the day’s tasks and meetings, summarizes client calls, and flags the news breaking in the space, into one rundown before the day starts. See the agency workflows.

It earns attention by leaving normal work out

Trigger

The window opens

An agreed schedule, or a manual request, starts the run.

Validation

Check source freshness

Connections, timestamps, required fields, and whether every expected source answered.

Route or draft

Draft the rundown

Changes, decisions, blocked work, and exceptions get grouped, each with a link back to its source.

Human approval

Read and decide

You read it and choose the action, the owner, or the follow-up. Nothing acts on your behalf.

System update

Record decisions

The notes and actions you approve go back to the tracker or source system.

Exception

Name the blind spots

Stale sources, conflicting records, and missing context get named instead of guessed at.

What it reads, what lands, and what you still decide

Those three answers are the whole workflow. The third one is short on purpose.

What it reads overnightSmallest set that answers your questions
The queues

The shared inbox, the support desk, and the order or fulfillment system: what came in, what’s unanswered, what breached a rule your team set.

The records

CRM and pipeline changes, the project or job tracker, and the calendar for today’s commitments.

The machinery

The scheduled jobs and integrations themselves, so a run that failed at 2am is in the rundown instead of being discovered on Thursday.

Access

Read access, scoped to the sources we name. Message bodies only where you tell us they’re in scope, and only for the threads the rules select.

What lands in the rundownIn this order
Exceptions first

What broke a rule, missed a date, or sits outside its normal range, with the record it came from.

Waiting on you

The decisions that can’t move without you, named as decisions rather than as status.

Blocked and by whom

Work that stopped, who it’s sitting with, and how long it has been there.

What moved

The changes worth knowing, kept short. Normal work that behaved normally stays out.

What it couldn’t see

Every source that was stale, empty, or unreachable, named. A quiet rundown and a broken connection look identical otherwise, and that’s the failure mode that actually costs you.

You decide the priorities, owners, commitments, and follow-up. The rundown ranks nothing by importance, commits to nothing, and answers nobody. It reads the systems and puts the few items that need a person in one place, in a fixed order, so you’re deciding at the start of the day instead of hunting. Priority, meaning, owners, and any change to a system stay with you and your team.

What stays yoursYour judgment
Priority

You decide which exceptions matter and which changes need nothing at all.

Meaning

A person works out why something moved and whether the source tells the whole story.

Action

Your team assigns owners, makes the commitments, and approves any system change.

What we need from youClient inputs
Questions

The decisions the rundown should help with, and the noise it should leave out.

Sources

Read access or exports from the smallest set of systems that answers those questions.

Examples

Past summaries, the exceptions you missed, the false alarms you stopped trusting, and one person on your side who can approve the rules.

It has to improve a review you already do

We haven’t published a measured client result for this workflow. A real one needs a baseline of the scanning work, the exceptions missed or caught late, the false alarms, and the decisions it supported, then the same measures once the rundown is in use.

What would count as proofObserved over repeated reviews
Effort

People, sources, and hands-on minutes spent assembling and reading the daily picture.

Signal

Useful exceptions found, exceptions missed, false alarms, and source gaps.

Control

The decisions, edits, and ignored items, recorded with the source context that produced them.

An illustrative scenario, not a client result

These numbers are assumptions. They are not a client result and not a promise about when anything lands.

Assumptions

5 people each spend 20 minutes scanning operating systems, on 20 workdays a month. A defined rundown could remove 12 minutes of scanning per person and leave the reading and the decisions alone.

Arithmetic

5 × 20 minutes × 20 days = 2,000 minutes, or 33.3 current hours. 5 × 12 minutes × 20 days = 1,200 minutes, or 20 hours of modeled monthly capacity.

Meaning

This values scanning time and nothing else. It doesn’t claim fewer missed exceptions, and a rundown people stop opening is worth zero. What it’s worth depends on source coverage, the false-alarm rate, what the tools cost to run, and whether it leads to action.

How this gets bought, scoped, and priced is on the services and pricing page. List the systems you open to start the day in the free written assessment, with the decisions you make from them, and we’ll reply by email with the smallest version worth building.

List the systems you open to start the day.

The smallest rundown that surfaces decisions, without turning into another dashboard.

Get a free written assessment