Short answer: to schedule many rooftop solar installs at once, give every job the same stage list, only book a crew date once a job's approvals and materials are in, plan crew capacity one week at a time, and review the whole pipeline every week. The crew is rarely the bottleneck. Approvals, deliveries and paperwork are.
Why is solar scheduling getting harder?
Volumes are rising fast in several markets at once. In India, the PM Surya Ghar rooftop scheme reached about 16,328 installs a day in July 2026, up from 5,038 a day in October 2025, with 29,469 active installers (pv magazine, 5 Aug 2026). Australia installed 180,878 rooftop systems in the first half of 2026, 35% more than a year earlier (Clean Energy Council, Jan–Jun 2026 report).
Field service already struggles with plans. A Salesforce survey of 6,500 service professionals in 40 countries found 47% of appointments don't go as scheduled (Salesforce, Jan 2026). In ServiceTrade's 2026 survey of 800+ technicians, 44% named inefficient scheduling as a top frustration (ServiceTrade).
What makes many solar jobs different from one?
A single install is a chain of steps. We covered that chain in our solar installation timeline guide. With 20 or 50 jobs, the problem changes:
- Jobs sit at different stages at the same time.
- Most waiting happens outside your team: utility or network approvals, permits, inspections and deliveries.
- Crews are booked days ahead, so a job that isn't ready wastes a crew day.
The names of the approval steps vary by market. In India it is usually the DISCOM's net-metering approval, in Australia the network operator's connection approval, in the US the permit and permission to operate, and in Dubai the DEWA Shams Dubai approval. The scheduling logic is the same everywhere.
How do you schedule many solar installs at once?
- Use one stage list for every job. For example: survey, design, approval, materials, install, inspection, grid connection, handover. The same stages make every job comparable at a glance.
- Add a "ready to install" milestone. A job only reaches it when approval is in hand and materials are confirmed. Give crews dates only for jobs that have passed it.
- Plan crew capacity weekly. Count the crew-days you have next week, fill them from ready jobs only, and keep a spare slot per crew for weather or rework. Our weather delays guide explains how to size that buffer.
- Group jobs by area and stage. Nearby installs on the same day cut travel time.
- Put office tasks on the same plan. Approval follow-ups, subsidy paperwork and customer calls are tasks with owners and dates, not reminders in a chat.
- Review the pipeline every week. Spend 20 minutes on three questions: which jobs moved a stage, which are stuck, and who will unblock each one.
| Stage | Common blocker | Who owns it |
|---|---|---|
| Survey and design | Customer sign-off | Sales or designer |
| Approval | Utility or permit queue | Office coordinator |
| Materials | Late delivery | Purchasing |
| Install | Crew or weather | Site lead |
| Inspection and grid connection | Slot availability | Office coordinator |
For panels and inverters with long delivery times, set order-by dates as in our long-lead items guide.
What mistakes break a solar schedule?
- Booking the crew before approval. It creates cancelled days and annoyed customers.
- One big spreadsheet with no stages. You can't see which jobs are stuck or why.
- Crews working from old chat messages. The plan and the field drift apart within days.
- Copying generic durations. Approval times differ by utility and city. Track your own average time per stage and plan with that.
- No buffer. A fully booked week has no room for rain, a failed inspection or a sick installer.
A schedule won't speed up a utility queue. What it does is show you early which jobs are waiting, so crews go where work is ready.
Where Zace fits
Zace is a project and task tracker for field service jobs, including solar, and the office tasks around them. You can lay each job out as a Gantt chart, mark milestones such as approval, install complete and handover, link tasks that depend on each other, and assign work with a priority. The same scheduler works on the web, Android and iOS, so the office and the crew see one plan. Zace isn't a dispatch or route-planning tool, and it doesn't connect to utility or subsidy portals. If you want a blank starting point, try the free Gantt chart templates.
Frequently asked questions
How many solar installs can one crew do in a week?
It depends on system size, roof type and travel. Track completed installs per crew for a month, then plan with that number minus one buffer slot.
Should each solar job be its own project?
For larger commercial jobs, yes. For small home systems, many installers keep a pipeline plan where each job is a row with the same stages.
What is the most common cause of solar install delays?
Waiting on outside steps, such as approvals, inspections, grid connection and deliveries, usually takes more calendar time than the install itself. That is why the "ready to install" milestone matters.
How often should I update the schedule?
Update a job the day it changes stage, and review the full pipeline once a week. A schedule that is a week old is worse than a short checklist.