Daily DispatchIQ Triage

Use this workflow at the start of the day, before an operations meeting, or any time the team needs to decide what matters most. The userbase for this guide is the owner, operations lead, PM, or office manager who has to turn scattered portal signals into a short list of real actions.

Workflow outcome

At the end of this workflow, the team should know which items need action today, who owns each action, which source screen must be updated, and which issues are only informational.

DispatchIQ is the daily command center. It should be used to route attention, not to replace source-record review.

Step 1: Open DispatchIQ before opening individual records

Start in DispatchIQ because it summarizes the operating picture across jobs, schedule, procurement, selections, payments, customers, and agents.

Read the page in this order:

1. Jobs that need attention.
2. Approvals waiting on a human.
3. Schedule or phase risk.
4. Procurement and material blockers.
5. Customer or homeowner communication risk.
6. Payment or financial status.
7. AI-agent tasks that need review.

The goal is not to clear every card. The goal is to decide what deserves action now.

Step 2: Classify each item

Put each item into one of four categories:

Category	Meaning	Next move
Act now	Work is blocked or a deadline is near.	Open the source workflow and update the record.
Assign owner	The item is real but needs a person, not immediate completion.	Assign the responsible team member and due date.
Watch	The risk is visible but not yet blocking.	Keep it on the radar and review again later.
Informational	The card is useful context only.	Do not create unnecessary work.

This keeps DispatchIQ from becoming a noise dashboard.

Step 3: Open the source workflow before making decisions

Use DispatchIQ as the triage layer, then move to the system of record.

Common routes:

• Job or contract issue -> Create and Set Up a New Job or the job detail page.
• Subcontractor assignment -> Schedule Subcontractors.
• Material issue -> Procure Materials and Track POs.
• Payment issue -> Financial and Payment Approvals.
• Customer issue -> Customer Issue to Service/Warranty.
• Agent-prepared action -> Review and Approve Agent Work.

Step 4: Decide the action owner

Every active item should have an owner.

Use practical ownership:

Issue	Typical owner
Schedule move	PM or operations manager.
Subcontractor confirmation	PM, scheduler, or subcontractor coordinator.
Purchase order or delivery	Procurement or office manager.
Payment approval	Finance or owner.
Homeowner escalation	Customer service or PM.
Labor correction	Field supervisor or payroll owner.
Agent approval	Human owner of the affected workflow.

If no one owns the item, it is not actually being managed.

Step 5: Update the source record

After deciding what to do, update the underlying screen:

1. Change the job, calendar item, PO, ticket, payment, or callback status.
2. Add a note if context would otherwise be lost.
3. Hold, reject, or approve work with a reason.
4. Assign a due date when the item needs follow-up.
5. Return to DispatchIQ only after the source record is accurate.

Step 6: End with a short operations list

Before leaving the triage meeting, write the operating list:

• What must be done today.
• Who owns it.
• Which workflow it belongs to.
• What would make it complete.
• What can wait.

Related screens

Portal area	Use it for
DispatchIQ	Daily attention routing and operating triage.
Jobs	Project source of truth after job risk appears.
CascadeIQ / Build Calendar	Schedule risk and phase movement.
Procurement / PO Lifecycle	Material readiness and vendor follow-up.
Financials / Payments	Payment or approval issues.
Agent Board	Agent-prepared work that needs review.