Talk to us about your solar installation management project.
Tell us your project volume, the jurisdictions you operate in, and the specific workflow that is breaking down. We'll tell you what we'd build and how long it would take.
Installation team juggling permit applications, equipment delivery windows, and crew schedules across separate tools with no unified project status view?
Site survey results stored in photos and PDFs that the design team can't access without the sales rep forwarding them?
Solar installation companies managing 20 or more concurrent projects hit the limit of what spreadsheets and shared drives can track. Permit status, equipment delivery windows, and crew schedules are spread across separate tools. Nobody has a single view of which projects are on track and which are blocked.
We build custom installation management software for solar companies that connects every phase of the project -- from signed contract through site survey, permit submission, equipment delivery, installation, and energisation. The project status is always current, and the right people see it without having to ask.
Project pipeline from contract to energisation with milestone tracking
Crew scheduling and dispatch tied to permit and equipment status
Site survey and design document management
Permit and inspection milestone tracking with jurisdiction-specific workflows
RaftLabs builds custom solar installation management software covering project pipeline from signed contract to energisation, crew scheduling tied to permit and equipment status, site survey and design document management, permit and inspection milestone tracking with jurisdiction-specific workflows, equipment and material tracking, and customer communication. Projects typically deliver in 10-14 weeks at a fixed cost.
Generic project management tools track tasks and due dates. They don't know that a crew cannot be scheduled until the permit is approved and the equipment is confirmed delivered. They don't know that a site survey photo set needs to be accessible to the design engineer, the permit coordinator, and the customer in different formats. They don't know that an inspection failure in one jurisdiction requires a different correction workflow than a failure in another.
Solar installation management software needs to understand those dependencies. When a permit clears, the system should flag the project as ready for crew scheduling. When equipment delivery is confirmed, it should check whether the permit is also in place. When a milestone slips, it should recalculate the energisation date and alert the customer automatically. Those workflows are built, not configured.
Full project lifecycle from signed contract to energisation, with every milestone tracked in a single pipeline view. The workflow stages that the pipeline models are: site survey scheduled, site survey complete, permit submitted, permit approved, equipment ordered, equipment delivered, installation scheduled, installation complete, utility inspection passed, interconnection application submitted, and PTO (Permission to Operate) received. Each project card shows the current milestone, the number of days the project has been in that status, and the next action required to advance it. Operations managers see all projects at once with filter controls for status, assigned crew, jurisdiction, and target energisation date.
Overdue milestones are flagged automatically using configurable thresholds per stage -- a permit that has been in review for more than the jurisdiction's typical approval window triggers a follow-up flag without anyone checking the spreadsheet. Stage duration analytics highlight which pipeline phases are consuming more time than expected across the portfolio, so the operations team can identify systemic bottlenecks rather than managing exceptions one by one. When a milestone slips, the system recalculates the projected energisation date and updates the customer-facing timeline automatically.
Crew scheduling tied to project readiness -- a project does not appear as schedulable in the dispatch queue until its AHJ permit is approved and equipment delivery is confirmed. This dependency check is enforced by the system, not by a coordinator manually cross-referencing two spreadsheets. Crew availability calendar showing each installer's assigned projects, days off, and certification status. Skill-based assignment routing enforces NABCEP certified installer requirements where applicable, and electrical licence requirements are checked against the project's jurisdiction before a crew lead is proposed for a job.
Job dispatch pushes the site address, access notes, equipment manifest, and permit approval documentation to the crew lead's mobile app before the morning start. Multi-crew coordination is supported for larger commercial installations where the mounting crew, electricians, and commissioning technician work on different days -- each sub-crew sees only their assigned scope in the dispatch view. Schedule conflict detection alerts the operations team when a crew lead is double-booked across two projects or when a certification required for a specific job type is missing or expired. Daily crew manifest report gives the operations team a single-page view of all crews scheduled that day, which projects they are on, and what equipment is assigned to each vehicle.
Site survey captured on a structured mobile form that covers roof type, pitch, material, orientation, shading analysis, electrical panel make and capacity, main breaker rating, meter location, utility interconnection point, and photo documentation of each relevant area. Survey data submitted from the field and immediately visible to the design engineer and permit coordinator without any file transfer step. Photo sets are stored against the project record and tagged by survey area so the designer can navigate directly to the panel photo or roof orientation shots without scrolling through a general photo dump.
Design documents -- CAD layout files, single-line electrical diagrams, structural engineering stamps, and load calculations -- are stored against the project record with version control so the current approved revision is always identifiable. Document package assembly for AHJ permit submission works by selecting the required documents for the jurisdiction, generating a combined PDF in the required format, and logging the submission date and method. Correction requests from the AHJ are attached to the permit record with the required revision noted and assigned for rework. Customer-facing documents -- executed contract, proposal, permit approval confirmation, and PTO letter -- are stored in the customer portal separately from the internal engineering documentation.
Permit workflow configured per AHJ (Authority Having Jurisdiction) -- each jurisdiction in your operating territory has its own required steps, document checklist, submission method (online portal, mail, or in-person counter), and typical approval timeline. Many AHJ portals now accept electronic submissions; the system tracks the portal submission reference number and expected review window. Permit submission date is logged, the expected approval date is calculated from the jurisdiction's configured average review time, and the permit coordinator receives an alert if the approval window passes without a response.
Approval, correction request, or rejection is recorded with the AHJ's notes attached and the required corrective action assigned to the appropriate team member. Interconnection applications for NEM (Net Energy Metering) or NEM-V tariff programmes are tracked separately from the building permit, with utility-specific application forms and interconnection timelines maintained per utility. The distinction matters because a passed building inspection does not mean the utility interconnection is approved -- both must be complete before the crew can commission the system and the customer can receive PTO. Inspection scheduling with the utility or building department is recorded against the project with the assigned technician. Inspection result -- pass, conditional pass, or failed with correction required -- is logged with photo evidence attached, and the correction workflow assigns the required rework before the re-inspection is scheduled.
Equipment order placed at contract execution, with the purchase order linked to the project record. The order covers the full system bill of materials: PV modules (manufacturer, model, wattage, quantity), inverter (string or microinverter, model, serial range), racking and mounting system, balance-of-system (BOS) components including conduit, combiner, and disconnects, and any battery storage components. Expected delivery date is tracked against the installation schedule so the crew dispatch dependency check reflects actual delivery status rather than estimated delivery. Inventory managed per warehouse or yard so the operations team can see which projects' equipment is on-hand, in-transit, or awaiting ordering.
Delivery confirmed by the warehouse team with the actual arrival date recorded against the project record. Equipment shortfall -- fewer panels delivered than ordered, substituted inverter model -- is logged against the project with the impact on the installation schedule assessed and communicated. Panel, inverter, and racking serial numbers are recorded at installation for manufacturer warranty registration and utility interconnection documentation. Some utilities require serial numbers on the interconnection application; the system generates the required report directly from the project record. Material consumption per project feeds job costing so the operations team sees actual material cost against estimated cost across the project portfolio, with QuickBooks or Xero integration for project accounting.
Automated customer notifications triggered at each project milestone: site survey scheduled, permit submitted to the AHJ, permit approved, installation date confirmed, installation complete pending inspection, utility inspection passed, interconnection application submitted, and PTO received. Notification content is configured per milestone by the company, with the customer's name, project address, expected dates, and any action required from the customer populated automatically from the project record. Notifications sent by SMS, email, or both depending on the customer's stated preference.
Customer status portal shows the current milestone and the next step in plain language -- no permit application numbers or interconnection acronyms that mean nothing to the customer. A visual progress bar shows where the customer sits in the installation journey. Two-way communication is logged against the project record so questions asked through the portal, and responses from the installation team, are stored in a single place rather than spread across individual email inboxes. Post-installation, the customer receives the PTO date, a monitoring app setup guide, and instructions for claiming applicable tax credits. The communication record is available to the customer service team and the installation crew so every person who touches the account has context before responding to a customer contact.
Frequently asked questions
Solar installation has milestone dependencies that generic tools don't model. You cannot schedule a crew without a permit approval from the AHJ and confirmed equipment delivery from the warehouse. You cannot submit for utility interconnection without a passed electrical inspection. You cannot close a project and release the final payment draw without a signed completion certificate and a confirmed PTO date. Generic project management tools track tasks and due dates, but they don't enforce those dependencies or recalculate downstream dates when an upstream milestone slips.
Solar installation software also needs to understand permit workflows by jurisdiction -- a simple permit-by-affidavit in one municipality and a multi-stage review requiring stamped structural engineering in another require different checklists and different expected timelines. It needs to handle multi-document package assembly for AHJ permit submissions, store site survey photo sets in a structured format the design engineer can navigate without the sales rep forwarding attachments, and track NEM or NEM-V interconnection applications separately from the building permit because the two processes run on different timelines with different responsible parties. A generic task tool cannot encode any of that context. Those workflows are built, not configured.
Permit requirements for residential solar vary considerably. Some jurisdictions accept a simple online permit-by-affidavit submission with minimal documentation and approve within a few days. Others require stamped structural engineering calculations, a load letter from the utility, a separate electrical permit application, and multiple site inspections across the build and commissioning stages. The AHJ portal submission method also differs -- some accept direct electronic file upload, others require in-person counter submission or a third-party permit service.
We map the specific workflow for each jurisdiction you operate in during the scoping phase -- required documents, AHJ portal submission process, expected approval timeline, inspection stages and the required intervals between them, and correction workflows. Those configurations are built into the system so the permit coordinator sees the correct checklist, document requirements, and expected timeline for each project's jurisdiction rather than applying a generic process. When you expand into a new jurisdiction or market, the workflow for that AHJ is added to the system configuration without a code change to the application. Jurisdictions with unusually long review windows or active permit backlogs can have adjusted expected timelines set independently so the operations team receives follow-up alerts calibrated to that AHJ's actual pace.
Certification requirements are stored against each installer's profile -- electrical licence type and the state it covers, roofing certification, NABCEP PV Installation Professional or Associate status, manufacturer-specific commissioning training for inverter brands you install, and OSHA-10 or OSHA-30 safety certifications. Job requirements can specify any combination of these -- an AC disconnect and commissioning job may require a licensed electrician plus the inverter manufacturer's commissioning certification; a roof-mount and racking job may require roofing certification and NABCEP associate status.
When a job is being assigned, the scheduling tool filters the available crew list to installers who meet all required certifications for that job type. If the crew lead or specialist required for the job is not available on the requested installation date, the scheduler flags the conflict and surfaces the next available date when a qualified crew member is free, or identifies an alternative qualified crew member. Certification expiry dates are tracked against each installer profile. The system flags upcoming renewals before the expiry date -- a NABCEP certification or electrical licence approaching expiry appears on the installer's profile and in the operations team's alert queue before it affects job assignment eligibility, not after the certification has already lapsed.
A focused platform covering the project pipeline, permit tracking, crew scheduling, and customer status notifications typically runs $30,000--$40,000. A full platform adding site survey management, design document storage, equipment tracking, a customer portal, and two-way customer communication typically runs $50,000--$80,000. Projects with multiple jurisdictions, large crew rosters, or integration with an existing CRM or ERP are scoped individually. We price at fixed cost agreed before development starts. Projects deliver in 10-14 weeks depending on scope.
What clients say
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.

All of the sprints were completed on schedule and on budget. We highly recommend RaftLabs!
01 / 02
Tell us your project volume, the jurisdictions you operate in, and the specific workflow that is breaking down. We'll tell you what we'd build and how long it would take.