A commercial solar project often begins with a simple question: how many panels fit on the roof? That question matters, but it comes after several decisions that shape the project more directly. A building’s busiest hours, electrical loads, roof plans, and backup-power needs all affect what a useful system looks like. Mapping those details first can help a property team ask better questions and avoid designing around assumptions that turn out to be wrong.
Start with the building’s operating calendar. A warehouse that runs equipment through the afternoon has a different energy profile from an office that empties at five. Reviewing utility bills alongside schedules, equipment records, and planned expansions gives an installer a clearer picture of how the site uses power. When comparing proposals, ask a local solar company to explain how the proposed system relates to those operating patterns, not only how much electricity it may produce over a year.
This approach also gives facilities, finance, and operations teams a shared starting point. Instead of debating panel counts in isolation, they can weigh system design against practical priorities: predictable energy costs, available roof space, equipment resilience, or room for future growth. Those priorities may point to different choices, so recording them early helps keep the project grounded.
Read the building before reading the proposal
Utility bills offer a useful baseline, but they do not explain every change in demand. A new refrigeration unit, a second shift, or an electric vehicle fleet can alter a site’s load. Facilities staff usually know when these changes happened and what may come next. Their notes can help distinguish a typical month from an unusual one.
Look at interval data if the utility provides it. Daily and hourly patterns can reveal when demand rises, how long it stays high, and whether the building uses substantial power after sunset. Solar generation varies with daylight, so the timing of consumption affects how much on-site production the business can use directly. A proposal should describe its assumptions about operating hours and future loads in plain terms.
Put roof work and solar work on one calendar
A roof can appear ready for panels while still having a replacement or repair date on the maintenance schedule. Installing solar shortly before major roof work may lead to removal and reinstallation expenses. The same conflict can arise with HVAC upgrades, structural repairs, or plans to add rooftop equipment.
Facilities managers can reduce surprises by reviewing capital plans before requesting final system designs. Ask the roofing contractor and solar installer to coordinate on roof condition, warranty requirements, attachment methods, and access routes. If roof work is due soon, the team can compare sequencing options instead of treating the schedule as a problem discovered after procurement.
Separate energy savings from resilience goals
Grid-connected solar panels typically stop supplying power during an outage unless the system includes equipment designed to operate safely without the grid. Businesses that need backup power should identify which loads matter most and how long they must run. A server room, security system, or refrigeration circuit may warrant a different backup plan from general lighting throughout the building.
That conversation can include batteries, generators, load controls, or a combination of technologies. Each option has different costs, operating requirements, and limits. A useful design brief names the circuits or operations the business wants to protect, then asks the project team to explain how the proposed equipment would perform in an outage. This prevents a broad phrase like “backup power” from hiding a mismatch between expectations and system capability.
Give the project team a clear brief
A concise brief helps installers prepare proposals that can be compared on common terms. It need not dictate a solution. Instead, it should describe the building, the business’s priorities, and known constraints. Include information such as:
- Recent utility bills and interval data, when available
- Typical operating hours, seasonal schedules, and planned shifts
- Known equipment additions or expansions that may change electricity use
- Roof age, maintenance plans, and any scheduled replacement work
- Critical loads and the business’s expectations during a grid outage
- Procurement timing, budget boundaries, and the people who will review proposals
With this information in hand, ask each bidder to state its assumptions, list any site inspections or studies still needed, and explain which project goals the design addresses. Compare projected production and cost alongside maintenance responsibilities, equipment access, and the effect of future building work. A proposal that clearly identifies uncertainty gives the team a better basis for decisions than one that hides it behind a single polished estimate.
Make the first meeting count
The first project meeting works best when the right people attend. Facilities staff can explain roof conditions and operating patterns. Finance can clarify how the company evaluates long-term investments. Operations can identify equipment that cannot tolerate interruptions. Bringing those perspectives together early helps the design respond to the actual building rather than a generic profile.
Commercial solar is a long-lived building decision, so the planning process should account for more than the first year’s electricity bill. When a team documents how the property works, what may change, and what it needs during an outage, it can evaluate proposals with sharper questions. The result is a more practical conversation about system size, schedule, cost, and the role solar should play in the site’s energy plan.