Map office and field work around one project record.
Map scheduling, crew, work-order, field-evidence, issue, material, labor, quality, and closeout context around the installation workflow your team runs today.
Currently onboarding a first group of early-access installers.
One project context. Clear office and field ownership.
Installation work needs explicit readiness, assignment, evidence, issue, cost-handoff, and acceptance records across office and field roles.
Define the permit, design, material, crew, site, and document conditions required before work is assigned.
Map milestone, form, photo, issue, quality, and change records with role-appropriate access and review.
Identify how labor, material, subcontractor, and exception context should move from field work into project and accounting review.
Define assignment around readiness, availability, and responsibility
Review the conditions that make a job and crew ready, who may assign work, which conflicts matter, and how schedule exceptions are approved.
See how it comparesMap the work order, field evidence, and cost handoff together
Define assigned scope, documents, materials, labor context, milestones, issues, changes, quality evidence, and the records required for acceptance.
Compare operations toolingGive each field update an owner and review path
Assess how milestones, photos, forms, issues, changes, and quality evidence should be captured, reviewed, and related to the project record.
12 rails set · 4 photos attached
Roof string 1 of 3
Added 2 optimizers — sent for approval
Installation workflow decisions to settle before configuration.
Installation workflow rollout
Carry each office-and-field requirement into the right phase.
Assessment, configuration, validation, and operation each answer a different part of readiness, assignment, field evidence, issue handling, and closeout.
| Capability | Assess | Configure | Validate | Operate |
|---|---|---|---|---|
| Readiness and assignment rules | Included | Included | Included | Included |
| Field role and permission model | Included | Included | Included | Included |
| Milestone and quality evidence | Included | Included | Included | Included |
| Issue and change approval | Included | Included | Included | Included |
| Material, labor, and cost handoff | Included | Partial | Included | Partial |
Included means the topic is a primary focus in that phase. Partial means it may be revisited as the rollout develops.
Common questions
Install operations — answered directly.
Does Solar1 replace field service tools like Scoop Solar?
Replacement depends on the field tool, records, mobile requirements, and financial handoffs your team needs to preserve. The assessment may identify replacement, integration, or a staged boundary rather than assuming full consolidation.
Can field crews use Solar1 on a phone without an office login?
Mobile field access, assigned-work views, evidence capture, issue reporting, and permission boundaries are assessment areas. Exact device and field behavior is confirmed and validated before rollout.
How does Solar1 handle change orders in the field?
The assessment maps who can raise a change, required scope and evidence, approval authority, work-order effect, cost context, customer or contract impact, and the record needed to close the change.
Does Solar1 work offline when there is no signal on a job site?
Offline operation is not presented as a generally available capability. Connectivity, device, caching, conflict, and synchronization requirements should be documented during assessment and verified before a remote team relies on them.
Assess the office-and-field operating record.
Bring the schedules, assignments, work orders, devices, evidence, issues, and closeout process your team uses today.