Daily Command Center

The daily command center is the first place a builder should check each morning. It combines live jobs, approvals, schedule risk, revenue, procurement blockers, selection blockers, payment context, and Agent Board tasks into one operating view.

DispatchIQ is the default builder portal landing page. Use it to orient the day before opening individual department screens.

When to use it

Use DispatchIQ when you need to answer:

• Which jobs, approvals, or payments need attention right now?
• What should a project manager, scheduler, or owner review first?
• Are procurement blockers, selections, or schedule risks creating downstream problems?
• Which AI-agent tasks are waiting for human confirmation?

Daily workflow

1. Open DispatchIQ from the left navigation or the builder portal home route.
2. Read the top operating summary first. This gives the current day’s high-level pulse.
3. Review the suggested prompts such as approvals, weather risk, PO blockers, selections, or payment status.
4. Ask DispatchIQ a specific operational question. Good questions include "Which jobs are behind schedule?", "What approvals are waiting?", or "Which procurement blockers affect this week?"
5. Open the linked workflow when DispatchIQ points to a specific task. Do not clear a risk from the chat alone when the underlying job, PO, approval, or payment still needs action.
6. Use the floating DispatchIQ assistant from deeper screens when you need context without leaving the workflow.

How to ask useful questions

Ask for an action-oriented answer:

• "Show me delayed jobs and the next owner for each one."
• "Summarize payment approvals that need review."
• "Which PO delivery risks could affect the build calendar this week?"
• "What should I handle before the next phase handoff?"

Avoid vague questions like "How are things?" unless you want a broad summary.

Related screens

Portal area	Use it for
DispatchIQ	Daily operating triage and AI-assisted routing.
Agent Board	Live agent tasks, approvals, transcripts, and work requiring confirmation.
Alerts	Central list of operational alerts and exceptions.
Jobs	Job-level follow-up after DispatchIQ identifies a project risk.
Procurement	PO blockers and vendor/material readiness.
Financials	Revenue, AR/AP, payment, and margin context.

Good operating habits

• Start with the command center before opening department pages.
• Treat DispatchIQ as a triage layer, not the system of record for every item.
• Follow links into the owning workflow before approving or dismissing important work.
• Ask for owner, due date, and blocker whenever the answer is too general.
• Keep approvals explicit. Actions that affect money, schedule, homeowners, or vendors should be reviewed before they are confirmed.