When Solar Sales Spike: Forecast Admin Capacity Before the Queue Grows

A strong sales week can create a difficult operations week later. New customers need intake checks, existing jobs need documents, and completed installations arrive for review while the same administrator is answering status enquiries.

Counting signed contracts will not tell you whether the team can absorb that work. A useful capacity forecast asks which tasks will arrive, when they will arrive and whose time they require. It should reveal a decision early enough to change the plan.

The method below is an original planning example for a solar business. All figures are hypothetical, not industry benchmarks or Nexus client results. Replace them with observations from your own operation.

Forecast work at each stage

Start with the stages in your solar administration workflow. List the work expected to enter each stage during the planning period, rather than assuming every new sale reaches every stage in the same week.

Use known bookings and current job records where available. For less certain arrivals, record the assumption and prepare a lower and higher scenario. A forecast of 40 new intakes might coexist with 30 evidence packs from earlier installations. Those are different cohorts.

Separate hands-on work from elapsed waiting. Ten minutes preparing a document request and three days waiting for a reply are different measures. Waiting affects job progress; it does not consume three full days of administrative labour. The follow-up and eventual review still require time.

Keep administrative preparation separate from professional assessment. The Clean Energy Regulator requires the relevant documents to be completed and signed before STCs are created. A busy queue does not remove that prerequisite. Read CER's certificate creation guidance.

Measure handling time without turning it into a quota

Sample comparable tasks over a defined period. Record time spent actively completing the task, its complexity and whether it returned for correction. Avoid using the quickest example as the standard for everybody.

Keep routine cases and exceptions separate when their effort differs substantially. Preparing a pack with every source present is not equivalent to resolving conflicting equipment records. A useful estimate includes the ordinary variation your team encounters.

Record rework explicitly. You can include typical correction effort within a task estimate or show it as a separate forecast line. Do not count the same effort twice. Document which approach the planner uses.

Discuss the estimates with the people doing the work. If measurement creates pressure to skip checks or hide interruptions, the resulting forecast will be less reliable.

Work through a busy-week example

For each task, multiply the expected number of handling events by the estimated active minutes, then divide by 60. The following hypothetical week has 40 new intakes, with other work arriving from jobs already in progress.

The rows count tasks, not unique installations. One job can require more than one type of work. The correction estimate here is additional to the preparation estimate.

Suppose the assigned administrators have 24 hours available for these activities after their other commitments. The forecast shows a six-hour gap. Adding a person with six free hours will help only if that person can perform the affected tasks and the necessary systems and instructions are ready.

Test a busier case as well. If evidence-pack preparation rises from 30 to 42 packs at the same assumed handling time, it adds five hours. The total becomes 35 hours, creating an eleven-hour gap against the same capacity. This simple comparison makes the sales-to-operations discussion more concrete.

Put reviewer capacity beside admin capacity

A separate review queue can remain overloaded even after administrative preparation improves. Forecast the responsible reviewer's actual available time and the work likely to be ready for that review.

For illustration, 30 internal file reviews at an assumed 12 minutes each require six hours. If the assigned reviewer has four hours allocated, that stage has its own two-hour gap. These figures are planning assumptions; they do not prescribe how long a technical review should take.

SAA assigns system-design responsibilities to the system designer, including site-specific design and equipment suitability. Moving preparation to offshore support does not transfer those responsibilities. SAA Technical Requirements, section 3.3.

Name the people qualified and authorised for each review. An untrained substitute should not be treated as interchangeable capacity simply because their calendar has space.

Choose the intervention at the constrained stage

Use the forecast to select a specific response. If the gap is routine intake work, a trained VA may be able to check fields, organise records and flag exceptions. If it is unresolved design questions, the next action belongs with the relevant professional.

Other responses include fixing a recurring missing-information problem, reserving review sessions or rescheduling work with the appropriate owner. Confirm changes to customer commitments through the responsible team; the planner itself is not authority to promise a new installation date.

Include training and handover time when adding support. A person starting this week may initially need more review from the existing team. Our solar VA onboarding guide provides a structure for that transition.

Identify the backlog tasks selected for the week and keep the unselected remainder visible. Otherwise a plan can appear balanced because old work disappeared from the calculation. Review age, due dates and consequences with the operational owner when setting priorities.

Compare the forecast with what actually happened

At the end of the period, compare arrivals, active handling time, available hours and completed work with the forecast. Record why they differed: an unexpected absence, more complex jobs, incomplete inputs or a change in timing.

Use that evidence to improve the next forecast. A consistent underestimate of correction time calls for better assumptions and an investigation of the cause. It does not automatically mean the people doing the corrections are underperforming.

Keep the planner small enough to maintain. A weekly table, a named owner and a short list of decisions can be sufficient. Talk to Nexus about solar administration support to identify a defined task queue and the training it needs before the next sales spike arrives.