Notion vs. Slite for a Commercial Solar and Energy EPC

Here, each project manager maintains their own notes on permitting requirements and utility interconnection quirks for the jurisdictions they work in, loosely organized and updated as they go. This works reasonably well for an EPC concentrated in a handful of familiar jurisdictions, where a project manager's accumulated knowledge covers most of what comes up, and the cost of an occasional gap is manageable, especially if the team is small enough that everyone can still ask a colleague directly when something's unclear.

Here, permitting requirements by authority having jurisdiction and interconnection requirements by utility live in a single, maintained reference that every project manager checks rather than relying on personal notes. This costs more to build and keep current, but it prevents the specific failure mode of expanding into a new jurisdiction and discovering requirements the hard way, through a rejected application, that a colleague who's worked there before already knew and simply never wrote down anywhere the rest of the team could find it.

Regardless of which approach you take for permitting, your commissioning checklist, the sequence that confirms a system is installed correctly and performing before handoff, deserves a single, standard structure applied to every project. Build it once, with a place to record actual readings against expected performance, and treat any deviation from the standard sequence as something to note and explain, not silently skip because a crew was behind schedule.

A system you installed years ago needs an O&M call, and the documentation on what was actually installed, panel model, inverter serial numbers, any change orders during construction, lives in a project folder nobody's opened since closeout. Structure this so it's genuinely findable by site address or customer name, not buried in the same folder structure as active project files, since the person fielding that call usually isn't the one who ran the original installation.

If you're working a small set of familiar jurisdictions and utilities, the flexible, project-manager-owned approach is a reasonable place to start, as long as you're deliberately capturing what each PM learns rather than letting it stay personal. The moment you're expanding into new territories, or you've had a permitting delay caused by a requirement someone already knew about but hadn't written down, it's worth the investment in a centralized, published reference instead.

Whichever approach you pick, check that these pieces exist:

• Permitting requirements are organized by authority having jurisdiction and interconnection requirements by utility, so project managers stop relying on personal notes.
• Every project uses one standard commissioning checklist structure, built once and applied the same way each time.
• Records of what was installed, including panel model, inverter serial numbers and change orders, can be found years after project closeout.
• Installer credentials, such as a NABCEP certification or state electrical license, show current status and renewal dates to whoever staffs a crew.
• Field changes to the design are captured as they happen instead of being reconstructed from memory after construction.

Installer certification, whether it's a NABCEP credential or a state electrical license, needs the same treatment as credentialing in any regulated trade: current status visible to whoever's staffing a crew, with renewal dates tracked far enough ahead that a lapsed certification never shows up on a jobsite unnoticed. Keep this next to your crew scheduling reference, not in a separate HR file, so a project manager assigning a crew can confirm certification status in the same place they're already checking availability, and can swap in a currently certified installer without a last-minute scramble.

This becomes more important, not less, as you scale, since a larger crew roster makes it easier for an individual certification lapse to go unnoticed until a customer's inspector or your own utility flags it during interconnection review.

Field conditions on a commercial solar install rarely match the original design exactly, roof structure discovered mid-installation, an electrical panel that needs unplanned upgrades, and these changes need to be captured as they happen, not reconstructed from memory at closeout. Document each field change with what was changed, why, and who approved it, linked to the specific project, so your as-built documentation actually reflects what's on the roof rather than what the original design called for. A crew lead who can log a change from a phone on-site is far more likely to actually do it than one who has to remember to mention it back at the office days later.