Map schedule eligibility to project readiness evidence.
Field operations / Scheduling and dispatch
Solar crew scheduling and dispatch workflow
Make the dispatch decision explainable before a crew is committed to a site that is missing prerequisites.
Record
01Crew
02Crew skill
03Assignment
04Field visit
Current reviewReview ready and blocked jobs
Configured during assessment- 01Review ready and blocked jobsCurrent decision
- 02Match job constraints to available resourcesNext controlled handoff
- 03Confirm customer and crew windowNext controlled handoff
- 04Publish the assignment and work packNext controlled handoff
Why this workflow breaks
A valid solar schedule depends on permit status, materials, customer availability, duration, travel, crew skills, electrical licensing, and vehicle capacity. Calendar space alone cannot prove a job is ready to dispatch.
Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.
Workflow sequence
Keep the handoff visible from first review to accepted outcome.
- 01Review ready and blocked jobs
- 02Match job constraints to available resources
- 03Confirm customer and crew window
- 04Publish the assignment and work pack
- 05Review changes and dispatch exceptions
What to configure
Specific controls, qualified by implementation.
Configure crew skill, license, vehicle, duration, travel, and customer constraints.
Record assignment changes, confirmations, and documented overrides.
Expose unresolved blockers beside candidate jobs during dispatch review.
Assessment output
A shared definition of the records, owners, and acceptance checks.
Records in scope
- Crew
- Crew skill
- Assignment
- Field visit
- Vehicle assignment
Roles in the decision
- Dispatcher
- Field operations manager
- Crew lead
Checks before rollout
- Define the source of crew availability and eligibility.
- Agree on readiness blockers and override rights.
- Test weather, cancellation, reassignment, and partial-day scenarios.
Questions to settle
Questions to settle before configuring scheduling and dispatch.
What should a dispatcher see before scheduling?+
The view may include readiness blockers, location, duration, customer window, crew skills, license needs, vehicle, equipment, and material status.
Can a manager override a blocker?+
A documented override can be configured for approved roles, with the missing evidence, reason, and affected owner kept visible.
How are schedule changes communicated?+
The implementation can map who needs an internal or customer-safe update after each type of assignment change.
Next step