Most dashboards are built to show how the business performed. That is useful, but it is not the first thing an operator needs in the morning. First you need to know what needs a decision, what is stuck, what is moving, and where the system created new output.
A daily operating dashboard is an exceptions surface. It does not try to show everything. It shows the small set of things that should interrupt you: overdue work, waiting approvals, quiet leads, stalled drafts, active clients, open deals, client reviews, renewal risks, and recent movement.
When this exists, the question changes from "Where do I look?" to "What do I handle first?" That is the entire point.
If a number does not change what you do today, it does not belong at the top of this dashboard. Put performance numbers lower on the page or save them for a weekly metrics view.
Coordination Zero OS has a version of this dashboard, but you are not copying the app. You are copying the operating logic: attention first, movement second, output third, details last.
Cards for exceptions, blockers, and decisions. These are the numbers that should make you click into work.
These card names are examples, not a fixed recipe. A membership business might swap in member churn risk, renewals due, onboarding stuck, cancellation requests, or community questions unanswered. An agency might care more about client approvals and review cycles. The pattern is the same: show the open loops that need a human.
A compact cross-system summary. Not every record. Just the stage of each major part of the business.
A light outcome row: published assets, hours saved, leads captured, revenue won, member renewals, or completed deliverables. This is how a founder can see what the team is pushing out without micromanaging every task. It also gives you a clean monthly review trail so next month's goals are based on actual system output, not memory.
Start with anything overdue, waiting, blocked, quiet, or stale. A good daily dashboard makes neglect visible.
For daily use, stage counts usually matter more than performance. Show where work sits in the system.
Charts and recent activity are useful, but they should not push the day-start decisions out of view.
Before you build anything visual, inventory the tables or lists your dashboard can read. In your system those might be tasks, content, deals, clients, campaigns, leads, invoices, projects, members, renewals, or approvals.
For each source, you need two things: the status or stage values, and the date that tells you when something became stale. Without those two pieces, the dashboard has to guess. Guessing is how "nothing needs attention" becomes a lie.
Performance metrics need cleaner definitions than daily exceptions. Do not block this build because you have not solved attribution, channel analytics, or revenue reporting yet.
Build the source tables first, then come back to this dashboard. The dashboard is not where work lives. It is where work gets surfaced. Start with the hub that matches the thing you need to track: Content Studio for content records, Sales Hub for leads and deals, Client Center for client approvals and reviews, Marketing Hub for campaigns, and Task Tracker for deadlines and follow-ups.
Fields needed: status, deadline, owner, and workspace or business. Counts feed past due and due today.
Fields needed: content type, status, updated date, scheduled date, published date, and approval status. Counts feed drafts, approvals, scheduled work, recent activity, and published output.
Fields needed: stage, value, last activity date, close date, and outcome. Counts feed open deals, stalled deals, leads, and revenue won.
Fields needed: client status, last touchpoint, open requests, approval status, review date, and response owner. Counts feed active clients, quiet clients, client approvals outstanding, follow-ups overdue, and reviews overdue.
Fields needed: campaign status, launch date, owner, and current stage. Counts feed active campaigns and launches coming in the next seven days.
Fields needed: member status, renewal date, churn risk, cancellation request date, onboarding stage, and last engagement date. Counts feed renewals due, churn risk, stuck onboarding, and member follow-ups.
Use these prompts with the AI tool you are building with. Paste in whatever schema, table list, screenshots, exports, or field names you already have. If you do not have tables yet, use the first prompt to decide which ones to build before you design the dashboard.
You are helping me design a daily operating dashboard for my own business OS.
This dashboard is not a metrics report. It should show:
1. What needs my attention today
2. What is moving across the business
3. What the system produced recently
Here are the tables, lists, or tools my business currently uses:
[PASTE TABLES, DATABASES, SPREADSHEETS, OR TOOL LIST. IF I DO NOT HAVE TABLES YET, SAY "I AM STARTING FROM SCRATCH."]
For each source, identify:
- Which fields matter for a daily operating dashboard
- Which status or stage values need to be counted
- Which date fields tell us something is stale, overdue, scheduled, published, closed, or recently updated
- Which fields are missing and should be added
- If I am missing the source entirely, what table or list I should build first
Return the answer as a table with columns:
Source, Daily Use, Build This First?, Fields Needed, Stale/Overdue Date, Status Values, Missing Fields, Dashboard Zone.You are helping me define the top row of my daily operating dashboard.
The top row should only include things that change what I do today. It should not include vanity metrics, channel analytics, impressions, subscribers, or performance reporting.
Here is my data inventory:
[PASTE THE OUTPUT FROM PROMPT 01]
Recommend 5 to 8 attention cards.
For each card, give me:
- Card name
- Plain-English definition
- Source table or list
- Filter logic
- Threshold for when it should appear urgent
- What action I should take when I click it
Prioritize overdue work, waiting approvals, client approvals outstanding, follow-ups overdue, client reviews overdue, quiet leads, stalled drafts, stalled deals, upcoming deadlines, and membership-specific risks like renewals due, churn risk, onboarding stuck, or cancellation requests.You are writing a build spec for a daily operating dashboard in my business OS.
Use this dashboard structure:
- Zone 1: What needs me today
- Zone 2: What is moving
- Zone 3: What it produced
- Details: charts or recent activity below the fold
Here is my approved card and source logic:
[PASTE YOUR FINAL CARD LIST AND DATA INVENTORY]
Write a builder-ready spec that includes:
1. Page purpose
2. Dashboard zones
3. Cards and labels
4. Data source for each number
5. Empty states
6. Error states
7. Mobile layout
8. What is out of scope for this page
Make the spec tool-agnostic. Do not assume a specific app. I may build this in Airtable, Notion, Sheets, Supabase, or a custom web app.You open the page and know the day in under a minute. You can see the problem areas without clicking around. Every card has a next action. The dashboard earns its place because it saves attention, not because it looks official.
Click each item as you confirm it. The goal is a dashboard you trust enough to open before email.
The top row only includes things that change what you do today
Every card has a clear source table or list
Stale, overdue, stalled, and waiting are defined in plain English
Performance metrics are not crowding out the daily operating view
Empty states and loading errors are visible, not silently treated as zero
The dashboard works on a phone well enough for a quick morning scan