A 12-minute morning scan of your workspace

A workspace morning scan checklist is how you prove the morning pass actually saw the parts of the company that matter before you trust the ranked day. In Chief of Staff, every morning Nautis scans your whole workspace (tasks, pipeline, runway, meetings, approvals, invoices, wellbeing signals, and more), ranks what matters most, and presents it as one prioritized list with a one-sentence headline. The product does the scan. Your checklist is the coverage check: each domain shows a proof signal, or you fix the input before you rearrange the calendar. This is operating guidance. It is not medical or legal advice.

One list beats seven tabs only if coverage is real

A workspace morning scan checklist fails when you open Chief of Staff, skim the headline, and still keep Slack, bank, and calendar as secret sources of truth. The point of the scan is one prioritized list. That list is only as complete as the modules it can see.

Illustrative miss (composite only): Palisade's briefing looked calm while an overdue invoice sat unlogged and a wellbeing signal was never connected. The founder followed the quiet list into deep work. Cash and health debt waited until Friday. A coverage check would have caught both before trust.

Run the checklist in twelve minutes. If a row fails, fix or flag it. Do not pretend the rank is omniscient.

Coverage checklist table

Use this table every weekday. Proof beats memory.

Workspace morning scan checklist discipline is boring on purpose. Seven domains, same order, every day.

Timed twelve-minute pass

Minute 0-1: open Chief of Staff. Read the one-sentence headline. Do not open email yet.

Minute 1-4: walk rows 1-3 (tasks, pipeline, runway). For each fail, write one fix owner in a Note line. Do not solve the whole company.

Minute 4-7: rows 4-5 (meetings, approvals). Confirm Today matches the calendar. Open Approval Center if At a glance shows pending approvals.

Minute 7-10: rows 6-7 (invoices, wellbeing). Glance Finance for Overdue. If wellbeing is not configured, mark N/A once so you stop pretending it was scanned.

Minute 10-12: accept or reject trust in the ranked list for the day. If two or more rows failed, your first job is input repair, not creative work.

Illustrative Palisade pass (composite only): rows 1-5 pass; row 6 fails (Overdue invoice not in workspace); row 7 N/A. Founder logs the invoice, Refresh after the workspace changes, then starts the day. The workspace morning scan checklist made the rank honest.

A new briefing is generated automatically every morning at 7:00 am in your organization's timezone. Click Refresh any time to regenerate it with the latest data. Refresh after you fix a failed row. Anxious Refresh with no new inputs does not improve coverage.

Protect the twelve-minute box on the calendar like a meeting with a customer. Sliding it after inbox returns the old archaeology habit the scan was meant to end.

What counts as proof, not theater

Tasks proof: a due date and owner in the system the scan reads, not a sticky on your monitor.

Pipeline proof: stage and next step the CRM or pipeline module holds.

Runway proof: last Startup Health check-in or an explicit cash number you update on a cadence, with the change since last check-in visible in At a glance when present.

Meetings proof: calendar-backed Today items.

Approvals proof: you know the pending count; Owners and Admins clear background agent requests they own.

Invoices proof: Finance Invoices shows Sent, Overdue, or Paid states you trust.

Wellbeing proof: the signal the scan can see, or a dated N/A. N/A is honest. Fake green is not.

Workspace morning scan checklist entries that only say "looked fine" teach nothing next week. Write fail or pass with a noun.

At a glance on the left rail can show runway with the change since your last check-in, pending approvals, and Today's mix across priorities, blockers, pipeline, and calendar. Use it as a coverage hint for rows 3-5, not as a reason to skip the table.

Illustrative five-day coverage log

Illustrative Palisade week (composite only):

Monday: fail invoices; pass others. Fix then Refresh. Tuesday: all pass. Trust the list. Wednesday: fail pipeline (next step blank on top deal); fail approvals (three pending). Clear Approvals first. Thursday: fail tasks (hiring blocker only in WhatsApp). Move to Task Board. Friday: all pass; wellbeing N/A. Short day.

They did not redesign Autonomy mid-week. They did not rebuild section theory. They ran coverage. By Friday the ranked list matched the company.

If the same row fails three days, assign a standing owner outside the morning pass. The checklist surfaces holes. It is not the remediation project.

Illustrative standup line (composite only): "Scan coverage 6/7; invoices fail; Jaya owns Finance sync by noon." One line beats a meeting about vibes. Workspace morning scan checklist culture is pass/fail nouns, not mood.

When work lives outside the system

Most coverage fails are human copies of the truth, not Chief of Staff defects.

Illustrative copies (composite only): pipeline updated in a personal sheet; invoices created as PDF email only; tasks living in a founder brain dump; approvals left unread because chat felt faster. The scan cannot rank what the workspace never held.

When a row fails, ask where the system of record is before you ask why the AI is wrong. Workspace morning scan checklist language stays about inputs. Save ranking judgment for after coverage passes.

If wellbeing is unavailable on your plan or not enabled, keep the N/A line dated. Do not invent a green score. Honesty about missing signals is part of coverage.

Travel mornings: run the rows on mobile if needed, still in order. Shrinking to just Approvals on travel trains omission. Shorten proof glances; keep all seven domains.

New hires: pair on the checklist for three days. The ranked list feels magical until someone shows a failed invoices row. Teaching coverage prevents cargo-cult trust in the headline card.

Weekly: count fails by domain. The loudest column gets a remediation owner with a due date. Do not add an eighth domain for vanity metrics. Seven matches the scan's named domains.

Workspace morning scan checklist stays off the action path

This pass is coverage, not judgment theater and not an audio ritual. After rows pass, use your normal briefing actions on items. The checklist stops when you know whether the scan saw the seven domains.

Do not expand the morning into a second full inbox review. Slack can wait until the rows close. A workspace morning scan checklist protects attention by front-loading omission risk.

Anyone with read permission for Chief of Staff can view briefings. Update permission is needed to act on briefing items. Only organization Owners and Admins can approve or reject requests from background agents and change Agent Autonomy settings. Coverage still matters for every reader: a quiet list with blind domains misleads the whole org.

If you use a Dashboard Today's briefing card, still open the full Briefing for the coverage pass. Condensed cards are entry points. Coverage needs the domains behind the headline.

Stop the pass at twelve minutes even if curiosity pulls you into Commodore chat. Digging is allowed after trust is scored.

Install the same week

Day 1: print or pin the coverage table. Day 2: run it once with a timer; log fails. Day 3: fix the loudest failed row's source module. Day 4: run again after 7:00 generation; Refresh only after real fixes. Day 5: share pass/fail counts with a co-founder; pick owners for repeat fails.

End of week: archive the five-day log into a monthly Note. Patterns in row fails are operating debt. Paying that debt raises the quality of every future prioritized list without writing a new ranking theory.

Shared orgs: the briefing lead for the day runs coverage and posts pass/fail in a one-line standup. Dual silent scans with no shared fails leave the same blind spot twice.

For burn and runway labels when row 3 fails often, see How to calculate startup burn rate and runway. For the Chief of Staff map, see What is an AI chief of staff. For ask-before-acting when Approvals pile up behind row 5, see AI that asks before acting.

A workspace morning scan checklist is finished when a teammate can run the seven domains cold in twelve minutes and say whether the prioritized list earned trust. The scan ranks. Coverage decides if the rank deserves your morning.