An installation count tells you how many jobs reached one milestone. It does not tell you how many customer files are waiting for a document, how often a handover returns for correction or how much time your team spends reopening the same record.
A useful solar operations dashboard makes that hidden workload visible. It builds on a clear solar administration workflow. It helps a manager decide where to intervene, what to clarify and which repeatable tasks could move to trained administrative support.
The six measures below are an original management framework. They are not regulatory benchmarks or claimed Nexus client results. Start with consistent definitions and compare your own operation over time.
Set up the underlying job record first
Each job needs a unique reference, current stage, stage-entry date, named owner, next action, due date and blocker. Link those fields to the underlying records so a reviewer can verify what happened.
Keep distinct milestones separate. “Installed,” “documents reviewed,” “claim submitted” and “customer follow-up complete” mean different things. The CER requires relevant documents to be completed and signed before STCs are created, so an installation date alone cannot demonstrate submission readiness. CER: creating small-scale technology certificates.
Agree whether time measures use calendar or business days. Define how cancellations, reopened jobs and missing dates are treated. Write these rules beside the dashboard so changes in the numbers do not merely reflect changes in recording habits.
1. Jobs awaiting evidence
Count open jobs that cannot progress because a required record is missing or unresolved. Count the job once in the headline total, even if several documents are outstanding. Keep the individual missing items in a supporting list.
Group blockers by the next responsible party: customer, sales, installer, designer, administration or another clearly defined owner. This shows which handoff needs attention without assuming every delay belongs to the administrator maintaining the tracker.
The useful management question is: “Which missing items can we resolve today?” Review recurring blockers as a process issue. If the same record is missing in many jobs, change how it is requested or collected upstream.
2. Age in the current stage
Measure the elapsed time since a job entered its present stage. Show the oldest jobs alongside the median, rather than relying only on an average. A single difficult job can move an average substantially; a median alone can hide that difficult job.
Use stage-specific expectations. A customer document request and an external assessment should not automatically share the same target. Record external waiting time visibly instead of concealing it or assigning it to the wrong team.
When a job changes stage, preserve its history. Moving it back and forth should not erase evidence of a long delay. Review the oldest exceptions for a next action, an owner and an escalation date.
3. First-pass completeness
Calculate the share of handover packs that meet your agreed completeness checklist on their first formal review. The denominator is all packs first reviewed in the period; the numerator is those accepted without being returned for missing or inconsistent information.
For illustration only, if 24 of 30 first reviews meet the checklist, first-pass completeness is 80%. That is a calculation example, not a target or an industry benchmark.
Separate administrative completeness from technical approval. A file can contain every requested document while still requiring a designer's decision. Record the top reasons for incomplete packs and use them to improve instructions, templates and training.
4. Repeat administrative touches
Track how many separate handling events a job requires in a defined process. Agree what counts: a document request, a manual correction or a repeat review may be useful events; every mouse click is not.
Use a sample if recording every event would add more administration than it reveals. Look for files reopened because information is scattered across inboxes, ownership is unclear or a status was not updated after a call.
More touches do not automatically mean poor work. A complex exception may need careful attention. Examine why the touches occurred, and distinguish necessary customer support from avoidable repetition before changing the process.
5. Rework caused by preventable errors
Record jobs returned for correction and, where practical, the time required to correct them. Assign a reason such as incorrect data entry, obsolete template, missing source check or unclear instructions.
Keep genuine scope changes separate. A customer requesting additional work after approval is different from an administrator entering the wrong equipment reference. Combining them can make the wrong process look responsible for the workload.
Review causes with the people doing the work. A high rework count might point to inadequate training, ambiguous instructions or a rushed upstream handover. The dashboard should help fix those conditions rather than encourage staff to hide corrections.
6. Internal close-out time
Choose a clear start and finish for the internal process you control. One option is the time from receipt of the agreed minimum records to completion of your internal review. Also show the preceding wait for those records so the earlier backlog remains visible.
Do not label internal completion as network approval, certificate registration or payment. These are separate outcomes with their own dependencies.
Track reopened close-outs. If a file is marked complete and later returns because something was missed, record that event and its cause. Otherwise the dashboard may reward premature closure while the underlying work continues.
Run a short weekly review that ends with decisions
Use the same reporting window each week. Bring the oldest blocked jobs, recurring missing items and common rework causes to a short operational meeting. Select one process improvement and name the person responsible for it.
| Pattern in the dashboard | Useful next investigation |
|---|---|
| Many jobs missing the same record | Check the original request and collection stage |
| Good completeness but long waiting times | Check reviewer capacity and handoff ownership |
| Many touches with little progress | Check scattered communications and unclear decisions |
| Fast close-out followed by reopening | Check the completion definition and review quality |
A trained solar VA can maintain records, prepare exception lists and organise the evidence behind these measures. See our solar VA task guide for a practical division of work. Your operational and technical owners remain responsible for the decisions that move jobs forward.
Nexus provides solar administration training and administrative task outsourcing. Book a consultation to identify the queue you want to improve and the information your team needs to manage it.
