How to rank blockers and pipeline in a briefing

Founder briefing blockers pipeline ranking is the morning order of work inside the daily Founder Briefing: clear what is blocked and what needs approval before you drown in pipeline busywork. The Chief of Staff help (checked 31 Oct 2026) describes the briefing as what changed, what is blocked, and what needs you today. Nautis scans the workspace, ranks what matters most, and presents one prioritized list with a one-sentence headline. Items are grouped in priority order into Priorities, Blockers, Approvals, Pipeline, Today (meetings and calendar), and Runway. Each item shows a severity pill, Critical or Attention. This post follows that help page. It does not invent a custom scoring formula beyond what the docs state.

Founder briefing blockers pipeline: read the sections in order

Open Chief of Staff, Briefing view (also reachable from the Dashboard Today's briefing card via View). The headline card summarizes the day; Listen plays a spoken version. Work the list top-down. Blockers and Approvals sit above Pipeline in the documented section order. That order is the product's ranking frame for your morning, not a suggestion to clear every lead email first.

The left rail At a glance panel shows runway (with change since last check-in), pending approvals, and Today's mix across priorities, blockers, pipeline, and calendar. Use At a glance to see whether Approvals or Blockers dominate before you click into Pipeline.

Critical versus Attention before you touch Pipeline

Every item shows a severity pill: Critical or Attention. Clear Critical items first, then Attention, before chat or pipeline busywork takes the morning. Click an item to open its source module. Do not mark pipeline Attention items done while a Critical blocker still sits above them unless you have a written reason.

Severity pills are labels on items, not a separate workflow. The ranking still lives in section order plus those pills. If two Critical items compete, use Do it or Ask Commodore on the one with an executable action, and Mark done only when the underlying issue is actually handled.

Act without confusing Do it for approval

Quick actions on items:

• Do it appears when there is an executable action (help example: Send reminder on an overdue invoice). A lookup runs right away. A change creates a card in Chief of Staff chat and in the Approval Center; the item shows Card ready in chat; nothing runs until the card is approved unless Agent Autonomy lets that action Run without asking. A draft, such as an email, always opens a card you can edit first.
• Ask Commodore hands the item to built-in chat with full context.
• Mark done clears the item and teaches the engine it mattered.
• Snooze until tomorrow hides it until the next briefing.
• Dismiss hides it and keeps it from resurfacing for two weeks.

Done, snooze, and dismiss tune what future briefings prioritize. Update permission is required to act on briefing items. The briefing is per-organization; your done/snooze/dismiss updates it for everyone.

Do it does not approve anything. Approvals for agent changes still finish in the Approval Center or on the chat card. Keep that distinct from "clearing" a Pipeline row.

Shape tomorrow with Priorities, not with hope

Owners and Admins open Settings, Priorities. What matters most right now holds six sliders that shape tomorrow's briefing: Revenue at risk, Runway and burn, Deals and fundraising, Team health, Marketing and brand, and Everything else. Set each from Lower to Top of mind and Save. Help confirms priorities saved apply to tomorrow's briefing. Weights also learn from done/snooze/dismiss. If Pipeline keeps drowning Blockers in your mornings, raise Deals and fundraising only when that is truly top of mind, and raise Runway and burn or Revenue at risk when cash or revenue risk should outrank lead noise.

When the briefing is generated, and when to Refresh

A new briefing generates automatically every morning at 7:00 am in the organization's timezone and is cached for the day unless you hit Refresh. Refresh regenerates with latest data. Generation usually finishes well under a minute; if it fails, Try again leaves data untouched. Briefing generation uses a very small amount of AI credits for the headline; if credits run out, items still appear with a plain fallback headline. Voice playback and chat use their own credits.

Owners and admins can get a morning briefing ready notification (and email controlled by the weekly-digest email preference) when anything notable appears. You're all caught up means nothing urgent surfaced across the company right now; new priorities, blockers, and approvals appear as they come up.

Sources behind Blockers and Pipeline

Help lists briefing inputs from across the workspace: task boards, leads pipeline, today's meetings, runway from Startup Health, pending agent approvals, overdue invoices, burnout check-ins, fundraising signals, meeting action items, decision reviews, and more. Sources with no data are skipped. Blockers often trace to tasks, approvals, invoices, or fundraising stalls. Pipeline items trace to leads pipeline movement. Click through to the source module instead of debating the card in the abstract.

Full Chief of Staff setup and views: Chief of Staff. The daily habit companion is how to run a daily founder briefing. For Pending agent cards specifically, the Approval Center path is the same help page's Approvals view.

An illustrative Monday pass (not a customer story)

The walkthrough below is an illustrative example only. It is not a real company briefing, measured time saved, or customer quote. Section names and actions match the help page.

At 7:10 am local, the founder opens Briefing. At a glance shows two pending approvals and a runway flat versus last check-in. Priorities lists one Critical cash item. Blockers lists a Critical overdue invoice reminder and an Attention task dependency. Approvals lists two Pending agent cards. Pipeline lists four Attention lead follow-ups.

They clear the Critical priority note, open the invoice item, tap Do it for Send reminder (draft card opens; they edit and approve). They open Approvals, Approve one Internal update, Reject one External email. They Mark done the blocker task after unblocking in the task board. Only then do they work two Pipeline Attention items and Snooze the other two until tomorrow. They skip Chat until Ask Commodore is needed on one remaining Attention blocker that lacks a Do it action. They do not Dismiss Critical items to clean the list. Tomorrow's briefing will reflect done/snooze choices; they leave Priorities sliders unchanged until Friday review.

Dashboard card and Listen without skipping the list

The Dashboard Today's briefing card shows the headline, runway, a needs approval chip, and the top four items. Use View to open the full Briefing page before you act. Chevron collapses the card; refresh regenerates; X hides it with a Show bar remaining; preferences are per browser. The needs approval chip is a reminder to open Approvals, not a reason to ignore Blockers above Pipeline on the full page.

Listen on the headline card plays a spoken summary. Use it while you pull up the list, then still click Critical Blockers and Approvals items. Spoken overview is not a substitute for Mark done after real work in the source module.

Shared briefing, shared done actions

Anyone with read permission for Chief of Staff can view briefings. Two people see the same briefing because it is the company's day, not a personal to-do list. When you Mark done, Snooze, or Dismiss, you change the list for everyone. Agree with cofounders who owns the morning pass on Critical Blockers so two people do not Dismiss each other's items. Update permission is required to act; without it you can read but not clear.

Past briefings stay under the Briefing view, including Weekly digest entries generated Monday mornings. Use the weekly digest for last week / week ahead context; use the daily pass for founder briefing blockers pipeline order. Evening debrief (5:00 pm local) is off by default; ask a workspace admin to enable it if you want end-of-day closure. It does not replace the 7:00 am section order.

Keep Pipeline in its place

Pipeline is a section, not the whole morning. Founder briefing blockers pipeline discipline means Blockers and Approvals get Critical attention first, Pipeline gets a bounded pass next, and Today/Runway get a glance so meetings and cash are not surprises. Chat is for Ask Commodore digs after the list is triaged, not instead of reading the ranked sections. Weekly digest (Monday morning last week / week ahead) lives under past briefings for a wider reset; it does not replace the daily Blockers-before-Pipeline pass.