Solar operations features

Follow one solar project record from first inquiry through service.

Explore the records, decisions, and handoffs Solar1 can map with your team during a workflow assessment. Start with the operational problem that is costing the most attention today.

Operating record

  1. 01Customer and siteIdentity, context, evidence
  2. 02Commercial decisionScope, proposal, agreement
  3. 03Delivery controlReadiness, ownership, exceptions
  4. 04Financial contextCost, billing, profitability

Feature map

Start where the workflow breaks.

Each area opens into three focused capability pages with records, roles, implementation checks, and related workflows.
Implementation-led

A feature matters only when the surrounding handoff works.

Every feature is scoped around the records, owners, and decisions it needs to carry across the operating workflow.

  1. 01
    Assess

    Start with the system your team already trusts

    Map the current tools, project records, owners, approval paths, and exceptions before changing how work moves.

  2. 02
    Configure

    Shape Solar1 around real handoffs

    Define stages, fields, permissions, notifications, and role views around the workflow your team actually runs.

  3. 03
    Validate

    Test representative projects before rollout

    Walk through sample jobs, edge cases, acceptance checks, and reporting needs before broader operational use.

  4. 04
    Enable

    Train by role, then expand with control

    Confirm owners, training notes, operating rituals, and review cadence so the team knows what changed and why.

Next step

Choose one workflow to examine first.

Bring the current records, owners, approvals, exceptions, and tools. The assessment turns them into a reviewable rollout boundary.
Book an assessment