Creating & Managing Jobs

The lifeblood of Proof-OS is the Job Lifecycle State Machine. Unlike legacy CRMs that rely on human data entry to move a project from “In Progress” to “Completed”, Proof uses required-gate validation to progress pipeline stages.

Intake & Dispatch

When a new emergency call rings in, your dispatchers will use the Create Job modal. We stripped away all the bloat so your dispatcher only needs 3 things to trigger an initial routing:

1. Customer Phone Number
2. Property Address
3. Severity Classification (Water, Fire, Mold, Bio)

Clicking Calculate Route will query the Proof AI engine to find the optimal responder.

[!TIP] If the caller only knows their zip code, you can use the Quick Intake mode. It will hold the job in a ‘Pending Location’ state while deploying the initial response protocol.

The 6 Stages of a Job

1. Intake: Call received, preliminary classification.
2. Dispatched: A verified technician is en route. Telemetry tracking engaged.
3. On-Site Assessment: Technician has arrived. Vision AI mapping begins.
4. Mitigation Active: Drying equipment set, demolition happening. Daily psychrometric locks required.
5. Pending AR: Equipment pulled. Re-construction starting. Awaiting final payment pipeline.
6. Closed: Zero balance, warranties active.

Required Documentation Gates

You cannot manually skip stages. For example, to move from Mitigation Active to Pending AR, the system requires:

• 3 consecutive days of acceptable moisture reduction metrics.
• A signed Certificate of Completion from the homeowner.
• Proof Vision AI validation that the affected area matches the billed scope.

This helps you avoid submitting incomplete estimates to a TPA.