Manage a solar installation job by keeping the customer requirement, site information, approved scope and delivery responsibilities connected. The office should know which decision or prerequisite comes next, and the attending team should receive the current work brief. At closeout, the record should explain the work completed, the relevant handover and anything still outstanding.
This article concerns the operating record around the installation. It is not an electrical design, testing or certification guide. Technical assessment and any required authorisations belong with the appropriately qualified people and relevant current requirements. WorkOrderPro can organise service information; it does not issue a certificate of compliance or make a system technically compliant by marking a job complete.
Begin with the customer's actual requirement
Capture what the customer wants the project to address in their own words, then route the requirement for appropriate technical assessment. A request for backup during interruptions, a change to existing equipment and an investigation into a system problem can lead to different work. Do not treat every enquiry as the same standard installation.
Record the site and relevant decision contacts. The person discussing the project may differ from the person controlling access, accepting the proposal or handling payment. The office needs to understand those responsibilities before arranging visits and sending customer documents.
Keep initial expectations separate from assessed scope. A customer description helps the team understand the need, but it does not establish that a particular configuration is suitable. The job record should show what was requested and what the responsible technical person subsequently proposed, without presenting an unreviewed promise as a confirmed design outcome.
Prepare the site-assessment appointment
A useful assessment brief identifies the customer, actual location, access arrangement and reported requirement. Include relevant known equipment or previous work where available. A technician attending for the first time should understand the purpose of the visit without relying on a private sales conversation.
Confirm what information the responsible assessor needs before attendance. The office can help collect existing documents or arrange the appropriate contact, but should not invent technical answers to complete a form. Unknown information should remain visible so the assessor knows what needs establishing.
After the assessment, the next person needs a usable outcome. The record should explain whether the team is ready to prepare a proposal, needs further information or must arrange another qualified review. A note that merely says “site seen” gives the office little basis for progressing the project responsibly.
Keep observations distinct from the proposed solution
Record the relevant site observations and the technical person's proposed scope as separate parts of the account. This helps later readers understand which facts were established and which decisions were made from them. A photograph or customer statement should not silently become a definitive technical conclusion.
Use clear references for the intended equipment and work area. If the customer has several buildings or existing systems, identify which one the proposal concerns. Ambiguous location information can affect procurement, attendance and later service history even when the quoted amount is correct.
Where an unresolved condition affects the proposal, give it an owner and next action. Do not hide uncertainty inside a general description that makes the project look ready when it is not. A clear assessment handover is valuable because many later decisions depend on the accuracy of that starting record.
Build a quotation the team can use after approval
The proposal should identify the current scope, relevant service and equipment lines, quantities and important boundaries. The customer needs to understand the decision, and the attending team later needs to recognise the work that was accepted. A polished total without a usable scope is an incomplete handover.
If options are presented, explain meaningful differences in the work. Suitability remains with the responsible qualified person. Do not imply that a customer choosing a package automatically validates its technical design or resolves every site requirement.
WorkOrderPro's quote-review workflow supports valid public approval links and relevant option selection. Demonstrate the complete proposal, customer view and recorded decision. Message delivery through a configured channel is a separate outcome from creating the review link, so verify the path your business intends to use.
Turn approval into a readiness review
An accepted proposal is an important commercial step, but the installation still needs a practical plan. Review the attending people, relevant equipment, access and any prerequisite identified by the responsible team. Do not automatically convert approval into a customer promise that all work can start immediately.
Use a readiness review that fits the project. The office should identify what is confirmed, what remains pending and who owns each unresolved item. A job can be visible on the schedule while still lacking a required input. Make that condition explicit before the crew travels.
| Project stage | Record the team needs | Next responsibility |
|---|---|---|
| Enquiry | Customer requirement and correct site | Arrange appropriate assessment |
| Assessment | Findings and unresolved information | Prepare reviewed scope or further input |
| Proposal | Current work and commercial lines | Obtain the relevant decision |
| Approval | Identifiable accepted scope | Review installation readiness |
| Attendance | Current brief and assigned people | Record work and relevant findings |
| Closeout | Outcome and handover status | Resolve outstanding actions and review documents |
Coordinate the crew with clear roles
A solar-related project may involve more than one person and more than one visit. Record the actual assignment through the supported work-order process and identify the person coordinating the attendance. The team should understand who owns the customer communication and the office handover.
Give supporting crew members the information relevant to their part of the work. A primary assignment alone does not explain every contribution. If a person changes or joins later, update the working arrangement and communicate the current brief rather than assuming everyone saw the original discussion.
WorkOrderPro's dispatch workflow supports reviewing the day and relevant allocations. Use it alongside qualified decisions about who may perform the work. A software assignment does not establish competence or authorisation; it records the operating arrangement your business has reviewed.
Keep equipment identification readable
Record identifying details for customer equipment where they are known and relevant. WorkOrderPro's equipment registry includes site, type, make, model, serial number, installation date and warranty expiry. These fields help distinguish the actual item across later visits.
Check source information carefully. Similar units can have different identities, and an unreadable label should not be replaced with a guessed serial number. Unknown dates should remain unknown until a reliable source is available. A completed-looking record is less useful than an honest one if later staff rely on incorrect details.
Keep equipment history associated with the relevant service work. A future technician should be able to identify the item and understand earlier interventions. The registry supports that information handover; it is not a live monitoring connection or proof that the equipment's warranty covers every subsequent issue.
Separate project equipment from technician-held parts
The equipment installed or maintained for the customer and the consumable parts held by a technician are different records. The equipment identity supports the customer's service history. Van stock concerns quantities held and movements such as replenishment or deduction.
WorkOrderPro's van-stock workflow is technician-based. Demonstrate how your team records relevant part use and how the office reviews replenishment. Do not assume that a van-stock increase automatically transfers stock from a separate warehouse or creates a purchasing transaction.
For project preparation, join the information deliberately. The current proposal describes the accepted scope, the procurement or issue process explains what is available, and the job brief explains the planned attendance. A record in one area should not be treated as proof that every physical item has reached the site.
Use photographs to explain the work sequence
Relevant images can help the office understand the visible site context and work performed. Choose views that answer a practical question, such as identifying the area, explaining a finding or showing a comparable completion state. Avoid collecting a large gallery without clear association or notes.
WorkOrderPro's photo workflow supports job stages and short notes. Review the correct job reference and the purpose of each image. Customer sharing is separate, with uploads defaulting to not customer visible in the photo workflow. Demonstrate the intended sharing path rather than assuming every image appears automatically in a portal.
A photograph does not replace technical testing or certification. It can show a visible condition, while the relevant qualified record establishes other parts of the work. Keep those roles clear so the office does not present a set of installation pictures as proof that every technical requirement has been satisfied.
Record scope changes before losing the context
Site work may reveal a condition requiring another decision. Record the finding, the proposed change and the person responsible for review. Distinguish a change to the accepted scope from a clarification of work already included. The office needs that context before preparing another proposal or revising the plan.
Use the appropriate approval process for a material commercial change. A technician noting additional effort does not by itself establish that the customer accepted another charge. The saved proposal and decision should remain clear enough for the final invoice reviewer to follow.
Communicate the changed scope to the attending team and update the relevant preparation. A revised customer document is not useful if the crew continues working from an earlier brief. Treat the change as a handover across the people affected, not only an edit to one field.
Make commissioning and handover responsibilities explicit
The job process should identify who is responsible for the relevant technical completion activities and who collects the resulting records for the customer handover. This article does not prescribe the tests, settings or certificate requirements for a particular installation. Those must be determined and performed through the appropriate qualified process.
Use the work order to make the status of that handover understandable. The office should distinguish a document expected from a responsible person, a document received for review and information actually handed to the customer. Do not mark every item complete simply because installation attendance has ended.
WorkOrderPro does not issue an electrical certificate of compliance by completing a job card. Keep any required certificate or approval within its proper process and reference the resulting information appropriately. The product's role is to support a clear operating record around the work, not to confer technical authority.
Prepare a customer handover the recipient can follow
A useful handover explains the completed scope, relevant equipment identity, the support route and any outstanding next step. The customer should know whom to contact with a service question without searching the original quotation thread. Technical instructions should come from the appropriate qualified source and equipment documentation.
Choose the recipient and format deliberately. The person managing the property may need the service information while an accounts contact handles the invoice. Review what each person should receive and avoid sending unrelated internal material simply because it is attached to the job.
| Handover area | What to establish | What not to assume |
|---|---|---|
| Completed scope | Clear description of the work performed | Attendance alone means every task is finished |
| Equipment identity | Correct site and identifying details | Similar appearance proves the same item |
| Technical records | Responsible source and reviewed status | Job software issues a certificate |
| Customer information | Appropriate instructions and contact route | Every recipient needs every internal record |
| Commercial closeout | Accepted scope and reviewed amounts | Completed work equals collected cash |
| Follow-up | Named owner and next action | A note automatically creates every future visit |
Keep completion, invoicing and payment distinct
Physical work, office review and customer payment are different stages. The completion account should explain what was performed and what remains. The invoice reviewer then uses the accepted commercial arrangement and relevant changes to prepare the customer document.
Do not interpret a completed-work value as cash received or project profit. WorkOrderPro's operational reporting uses defined work-order measures; the business still needs the appropriate cost and payment records for financial questions. A project can be technically complete while the office has further commercial work to do.
If the customer raises a question, locate the full record rather than relying on one image or status. The quote, decision, work notes and relevant handover information should support a factual explanation. No software workflow guarantees that every disagreement disappears, but a coherent record helps the people involved discuss the same facts.
Plan later service around the actual arrangement
If the customer has an agreed repeat-service arrangement, record its scope and responsibilities clearly. WorkOrderPro's maintenance-contract workflow can generate preventive work from a recurring setup. Generation is not the same as a confirmed appointment or completed maintenance.
Choose the interval through the relevant agreement and qualified planning. Do not assume that registering equipment enables sensor monitoring, fault prediction or automatic runtime-based maintenance. Those capabilities require their own demonstrated integration and operating response.
For a return visit, prepare the technician with the relevant previous history. Explain what has already happened and what the new attendance should address. A useful service record helps continuity across people and time rather than relying on the original installation team to remember every detail.
Trial a complete solar-service handover
Use a representative project with an assessment, a customer decision and a multi-person attendance. Follow it through the office and field workflow, including a changed scope or missing prerequisite. Ask each role to complete its step from the saved record.
Inspect the final handover as someone who did not attend. Can the reviewer identify the accepted scope, equipment, completed work and outstanding action? Are technical-record responsibilities clear without implying that the application created the certificate? These are practical acceptance questions for the operating process.
Review current pricing for the required feature set and full team. WorkOrderPro staff billing includes active administrators, dispatchers and field users, excluding disabled accounts. Start a trial with the handovers your business needs to manage, then judge the product by the clarity of those records and responsibilities.
Frequently asked questions
Is this an electrical installation or design guide?
No. It covers job information and operating handovers. Technical design, testing and required authorisations must follow the relevant qualified process and current requirements for the actual installation.
Does WorkOrderPro issue certificates of compliance?
No. Completing a work order does not issue a CoC or establish technical compliance. Keep certification with the authorised process and use the job record to make responsibilities and received information understandable.
Does an approved quote mean the crew can attend immediately?
Not necessarily. Review people, equipment, access and outstanding prerequisites. Approval records the commercial decision; dispatch still needs a practical readiness check and current appointment arrangement.
Can we keep identifying details for installed equipment?
The equipment registry supports site, type, make, model, serial number and relevant dates where known. Verify the source and preserve uncertainty rather than inventing missing identification information.
Do job photographs prove that the installation passed every technical check?
No. They support visible context and the work narrative. Appropriate testing and technical records are separate responsibilities, and a photo gallery should not be presented as a substitute for them.
Is van stock the same as project procurement?
No. Van stock records technician-held quantities and movements. Demonstrate any separate warehouse, purchasing or project-issue process your operation requires instead of assuming one action completes all of them.
Does equipment registration enable automatic performance monitoring?
No monitoring connection should be assumed from a registry entry. Sensor data, fault alerts and runtime-based decisions need their own demonstrated integration and qualified operating process.
What should the software trial prove?
It should show a clear request, reviewed scope, usable crew brief and coherent customer handover. Include a realistic exception and verify that another colleague can continue the work from the saved information.