Missed-Obstruction Checklist for Rooftop Solar Designs

The obstruction most likely to disrupt a rooftop solar layout is not necessarily the largest object on the roof. It is the small feature that looked like a stain in imagery, the drain hidden near a low point, the planned vent mentioned in a facilities email, or the neighboring tree that was outside the survey frame.

A useful checklist does more than name objects. It forces the team to ask what evidence was available, when it was captured, what remains invisible, and which project output depends on the answer. That turns “check the roof” into a controlled design task.

This guide is for preliminary and detailed rooftop solar workflows. It does not set code clearances, safe-work methods, structural conclusions, fire-access rules, equipment servicing space, or installation instructions. Those decisions require current project evidence and the responsible qualified parties. OSHA publishes solar workplace safety resources for relevant United States work, while local requirements and employer procedures still control the individual job.

Define obstruction by decision effect

An obstruction is not limited to something that physically occupies module space. Include any feature that changes usable area, shade, roof access, drainage, equipment service, attachment planning, conductor routing, edge treatment, emergency access, maintenance, customer scope, or the confidence of the current model.

That definition catches objects that a visual-only checklist misses. A roof drain may occupy little area but influence where equipment and access can go. A parapet may sit outside the array yet affect shade or edge geometry. A planned rooftop unit may not exist during survey but still reserve space. A fragile or restricted zone may look empty while being unavailable.

Give every finding one or more effect tags: layout, shade, access, drainage, structure, attachment, electrical route, service, safety review, scope, or future condition. The tags direct the item to the right reviewer and show which outputs need revision if the condition changes.

Build the evidence stack before drawing

No single source sees the whole roof. Assemble an evidence stack proportionate to the release being prepared:

1. Current project identity and intended design release.
2. Available aerial or satellite imagery with capture information where known.
3. Roof plans, architectural records, equipment schedules, or facility documents supplied for the project.
4. Previous photographs or inspection material with date and location.
5. Customer or facility statements, labeled as statements rather than observations.
6. Site survey evidence gathered under the project’s access and safety procedures.
7. Information about planned roof, mechanical, tenant, or building work.
8. The open-condition register and named verification owners.

Compare sources instead of merging them silently. If a roof plan shows three vents and current imagery appears to show four, record the conflict. If a customer says an old unit was removed, keep that statement separate until suitable evidence supports the design decision.

The U.S. Department of Energy describes assessment and design as distinct parts of the broader process of going solar. The exact workflow varies, but the separation is useful: early information can support a preliminary conversation without being treated as final site verification.

Checklist group 1: roof openings and penetrations

Start with features that break or pass through the roof surface. Depending on the building, these may include vents, pipes, flues, drains, scuppers, skylights, hatches, curbs, ducts, conduits, antennas, anchors, and small service penetrations.

For each feature, record a stable label, roof plane or zone, approximate position, evidence source, observation date, visibility, and whether dimensions are measured, documented, estimated, or unknown. Capture a wide image for context and a closer image when the project procedure allows it. A close image without orientation can be impossible to place later.

Do not decide treatment from the object’s informal name. Two features both called “vent” may have different functions, servicing needs, heat or exhaust implications, manufacturer requirements, and responsible reviewers. The checklist should route the question rather than guess.

Review clusters carefully. Several small penetrations can create an irregular unusable zone that is easy to miss when each point is marked independently. Verify the space between features and any access relationship the project requires.

Checklist group 2: mechanical and service equipment

Rooftop units, fans, cooling equipment, tanks, communications equipment, exhausts, and other building systems affect more than their footprints. Doors open. Panels need service. Components may be replaced. Air or exhaust may travel. Contractors need routes that a tight array can obstruct.

Record equipment outline, visible service sides, access route, known operating or replacement plans, curbs, nearby penetrations, and any project document that controls the treatment. Do not infer a servicing clearance from imagery or from another project. Obtain the relevant equipment information and route it to the responsible designer, facility representative, contractor, or engineer.

Ask whether the equipment is active, abandoned, planned for removal, or scheduled for replacement. Each answer needs evidence and timing. An “abandoned” unit that remains on the roof is still a physical obstruction until an authorized project plan says how and when it changes.

On commercial roofs, facilities and solar schedules can move independently. Add a trigger that reopens layout review if rooftop equipment scope changes after the solar survey.

Checklist group 3: drainage and roof function

Empty-looking roof area may serve drainage. Record drains, scuppers, gutters, valleys, crickets, low areas identified by the responsible roof information, and visible water-management features. Preserve access for inspection or maintenance as required by the project’s controlling documents and reviewers.

Do not infer drainage performance from one dry-day photograph. The field record can show where a drain was observed and whether access was available. Roof performance conclusions belong with the appropriate qualified party and current evidence.

Placing objects near drainage paths can affect more than module layout. Mounting, ballast where applicable, cable routing, walk paths, and temporary construction materials may matter. The checklist should send the drainage context into installation planning, not leave it as a designer’s private note.

The National Institute of Standards and Technology publishes building-material research resources that illustrate the breadth of building-performance questions. A general research source cannot assess an individual roof, so keep project findings and professional review at the center of the decision.

Checklist group 4: edges, parapets, steps, and roof geometry

Roof edges and changes in elevation can be hard to read in overhead imagery. Parapets may cast shade, conceal lower features, or complicate dimensions. Steps between roof levels can appear as lines without revealing height. Overhangs, canopies, dormers, ridges, hips, valleys, and curved surfaces each need the geometry required by the design stage.

Record which geometry is directly supported and which is inferred. A preliminary model can carry an estimated parapet height when the purpose allows it, but the estimate should be labeled and assigned a verification trigger before a dependent release.

Edge treatment also intersects with fall protection, fire access, construction means, and local rules. Do not place universal offsets in a global checklist. Record the controlling jurisdiction, code or requirement identified by the responsible reviewer, and the version or date used.

Use the solar design confidence-level guide to distinguish what a model can support at each evidence stage. Confidence labels are valuable only when the team defines their evidence and release meaning.

Checklist group 5: shade-producing objects near the roof

An obstruction does not need to sit on the roof. Trees, poles, adjacent buildings, roof screens, taller building sections, architectural features, and nearby infrastructure may affect shade at different times.

Record object identity, position relative to the array area, height evidence, capture date, season, and whether future change is known. For vegetation, distinguish current observed condition from possible growth or pruning. Do not predict a future tree state without a documented basis and appropriate review.

The PVWatts Calculator is a public tool from the National Laboratory of the Rockies (NLR, formerly the National Renewable Energy Laboratory/NREL) for preliminary photovoltaic energy estimates. Its outputs depend on inputs and assumptions, and it does not verify the exact obstruction geometry of a project site. Use site-specific shading analysis and evidence at the level required by the decision.

Keep shade findings connected to customer communication. If an object materially affects a modeled scenario, the proposal should explain the scenario and its evidence rather than presenting one production figure without context.

Checklist group 6: access, pathways, and reserved zones

Some empty areas are intentionally empty. Roof hatches, ladders, service paths, equipment replacement routes, emergency access, maintenance zones, tenant rights, roof-warranty conditions, or future construction may reserve space.

Ask who controls each reservation and which document defines it. A salesperson’s sketch, a facilities request, an authority rule, a safety plan, and an equipment manual do not carry the same authority. Preserve the origin and route conflicts to the responsible decision-maker.

Record vertical as well as horizontal access. An array that looks clear from above may interfere with opening a hatch, moving equipment, reaching a panel, or crossing a level change. Field and installation reviewers often notice these relationships faster than a remote designer, so give them a defined review point.

The checklist should include “no array planned here and why.” Without that note, an excluded zone can look like unused capacity during a later value-engineering pass.

Checklist group 7: small and low-contrast features

Small features create disproportionate surprises because they vanish at common image scales. Thin pipes, low vents, anchors, cable trays, roof patches, lightning-protection components, seams, drains, sensors, and low curbs can blend with texture or shadow.

Review imagery at more than one scale and with more than one orientation where available. Compare roof plans and field photos. During survey, use a systematic sweep by roof zone rather than photographing only obvious equipment. Keep image resolution and visibility limitations in the record.

Do not “clean up” a model by deleting uncertain marks. Create an unresolved-feature marker with an owner and release effect. A visible question is safer than a smooth model that silently assumes open space.

Checklist group 8: temporary and planned conditions

Construction materials, temporary equipment, snow where relevant, maintenance activity, seasonal vegetation, or a pending roof project can make current evidence misleading. Planned additions matter even when the roof is clear on survey day.

Record what exists now, what is temporary, who provided the plan, expected timing if documented, and what event triggers a recheck. Avoid turning a proposed schedule into a fact. “Facility manager states unit removal is planned” remains a statement until the project receives the evidence required for its next decision.

Temporary obstruction can also hide permanent features. If a zone was not visible, mark it unobserved. Do not infer that nothing lies beneath stored material or snow.

Classify every obstruction by confidence and effect

A long object list becomes manageable when each row carries a decision state.

Use confidence categories defined by the organization. “Confirmed” should name the evidence adequate for that purpose. A feature can be confirmed to exist while its dimensions or required treatment remain unresolved.

What evidence should an obstruction record contain?

An obstruction record should identify the project and roof zone, stable feature label, evidence source, observation date, visibility, location, dimension status, confidence, effect tags, responsible reviewer, required verification, release impact, affected outputs, and next review event. It should distinguish observed, documented, estimated, reported, conflicting, and unknown information so a marked object never appears more certain than the available evidence supports.

Use one row per feature or unresolved area, then link multiple observations to that row. A vent visible in imagery, a roof plan, and a survey photograph does not need three unrelated findings. It needs one feature identity with three sources whose dates, positions, and descriptions can be compared. Keep conflicting sources visible until a responsible reviewer accepts the basis for the current release.

Copy-ready obstruction record:

1. Project, building, roof plane or zone, and current design revision:
2. Stable feature identifier and plain-language description:
3. Observation source, observer or provider, capture date, and retrieval date:
4. Wide-context image, detailed image, plan reference, or statement reference:
5. Position, orientation, visibility, and areas not observed:
6. Existence status: observed, documented, reported, inferred, conflicting, or unknown:
7. Dimension status: measured, documented, estimated, or unknown:
8. Effect tags: layout, shade, drainage, access, service, attachment, electrical route, structure, safety review, scope, or future condition:
9. Current treatment and the evidence supporting it:
10. Decision owner, qualified reviewer, and escalation route:
11. Required verification, due event, and release effect:
12. Dependent layout, model, material, electrical, proposal, work-order, and field records:
13. Change history, closure evidence, and next review trigger:

Avoid a single confidence score that blends different questions. The team can be confident that an object exists while lacking dimensions, function, or required treatment. It can have a measured position while not knowing whether equipment remains active. Separate existence, geometry, function, and decision status so one strong field does not make the whole row look settled.

Use a treatment matrix to route the finding:

The record should point to evidence, not embed a private conclusion in a colored roof marker. A red polygon could mean shade, exclusion, unknown geometry, or a reviewer hold. Use a stable label and defined status that survives grayscale printing, exports, language changes, and a new person opening the project later.

Review the negative space

Most obstruction checks focus on marked objects. Add a deliberate review of apparently empty array area. Ask why the team believes each large open zone is usable. Which evidence shows the surface, access, roof function, shade context, and reserved uses? What could be hidden by capture angle, image date, or missing access?

This reverse review is especially useful after automatic or rapid layout work. Dense module placement can make an uncertain roof look settled. Hide the modules, inspect the base evidence, and then restore the design. The sequence makes subtle features easier to see.

Have a second reviewer examine the negative space without being told where the first reviewer found objects. Independent attention is more valuable than two people confirming the same annotations together.

How should reviewers search for obstructions that imagery misses?

A reviewer should search beyond visible objects by comparing imagery, plans, facility records, survey photographs, customer statements, planned work, and the apparently empty areas selected for modules. Hide the layout, inspect every roof zone systematically, mark unobserved or conflicting areas, and ask which roof function, access need, nearby object, or future condition could make the negative space unavailable or unsafe.

Begin with source limits. Record image age where known, viewing angle, resolution, shadow, roof texture, vegetation season, cropped boundaries, and any roof area hidden by parapets or equipment. A crisp image can still be stale. A current image can still hide a low feature. The review should not confuse visual quality with evidence completeness.

Sweep the roof in a fixed pattern. Divide it into named planes or zones and review each against the obstruction groups: openings, mechanical equipment, drainage, geometry, nearby shade sources, access or reserved areas, small features, and temporary or planned conditions. Mark “reviewed with no feature identified” separately from “not visible” or “not reviewed.” Silence should never carry all three meanings.

Then reverse the view:

1. Hide modules, shade colors, and other design overlays.
2. Display the cleanest available base source and its date.
3. Outline each large area the layout treats as open.
4. Ask what evidence supports roof surface, geometry, drainage function, access, service use, and planned conditions in that area.
5. Compare plans and facility records for objects or reserved uses that do not appear in imagery.
6. Compare survey photos from more than one orientation where available.
7. Mark cropped, shadowed, blocked, low-contrast, or inaccessible areas as visibility gaps.
8. Restore the design and test whether any module, route, attachment, or equipment decision depends on an unresolved zone.
9. Give the unannotated sources and open-area outlines to a second reviewer for an independent pass.

Ask different roles different questions. A facility representative may know about planned equipment or roof work. A roof professional may identify drainage or warranty concerns. An installer may notice access and sequence constraints. A designer may identify model dependencies. Engineering, safety, code, authority, and equipment decisions remain with the responsible qualified parties. The checklist collects questions; it does not replace their judgment.

Illustrative workflow example, not a customer result: A remote reviewer sees a clean rectangular area and an automated layout fills it. During negative-space review, an older facility plan shows a roof opening while survey photos do not cover that zone. The team marks the area unobserved, assigns verification, and prevents the dependent detailed release from treating the rectangle as confirmed open roof.

Review adjacent and off-roof conditions as well. Taller roof sections, nearby buildings, trees, poles, and planned construction can affect sunlight or access without appearing inside the array boundary. Record their position, source, date, and unresolved dimensions. Do not translate presence directly into energy loss without the project-specific model and review.

Use the roof-constraint communication guide when a finding affects the customer conversation. The explanation should state what the team observed, what remains uncertain, which output may change, and who will resolve it. A blank area removed without explanation can look like an arbitrary design reversal.

Connect obstruction review to every downstream output

When an obstruction changes, the impact can spread. The layout may change module quantity or grouping. Shading and energy models may need another run. Materials, electrical records, installation instructions, commercial scope, price, and proposal graphics may need revision. The customer may need an explanation.

Create a dependency list before release. For each obstruction effect tag, name downstream outputs that require review. Do not assume that saving a roof model updates every exported or externally authored record.

The solar design source-of-truth guide explains how to choose one controlled project basis. Use that basis to regenerate or reconcile outputs, then record the revision relationship.

Use a three-pass obstruction review

One long checklist invites fatigue. Split the work by purpose.

Keep the reviewer’s view uncluttered during each pass. Discovery works best against source imagery and records before module placement dominates the screen. Classification needs the finding register beside the project evidence. Release review needs the controlled design plus every downstream output. Switching views on purpose reduces the temptation to treat a polished model as evidence that every roof condition was considered.

Record the duration and scope only as internal process data when useful. Do not publish a claim that the three-pass method is faster or more accurate without retained comparative evidence. Its immediate value is simpler: the team can see which kind of judgment each pass is meant to make, and a reviewer can identify where an unresolved item should return.

Pass one: discovery

Review every evidence source and mark possible features without deciding detailed treatment. Capture conflicts and invisible zones. The goal is to avoid premature deletion.

Pass two: classification

Name each feature, confidence, dimension status, effect tags, owner, and required evidence. Route technical questions. Merge duplicate observations that clearly describe the same object while preserving provenance.

Pass three: release

Compare the active design with the obstruction register. Confirm that unresolved conditions are visible in the release, required reviews are complete, downstream outputs agree, and verification triggers have owners. A different reviewer should run this pass when resources allow.

Handle a late discovery without blame

When a new obstruction appears, contain the project first. Identify what work or decision is affected. Confirm the active revision. Capture suitable evidence under site procedures. Notify the authorized reviewer and prevent superseded instructions from spreading.

Then trace the mechanism. Was the object absent from older imagery? Hidden by another feature? Missed during survey? Added after survey? Present in a plan that never reached design? Removed from the model during cleanup? Each mechanism calls for a different improvement.

Update all dependent outputs and record the customer or commercial effect where relevant. Do not change only the roof plan and leave the proposal, materials, work order, or financial scenario behind.

What should happen when an obstruction appears after design release?

When a late obstruction appears, pause the affected decision or work, preserve the active revision, collect suitable evidence under site procedures, identify the authorized reviewer, and map every dependent layout, shading model, energy result, material output, electrical record, proposal, work order, and release. Issue controlled revisions, withdraw superseded instructions, explain material customer effects, and record the discovery mechanism before resuming.

Containment comes before cause analysis. Identify the location, work or decision exposed, active package, installed condition, and immediate protection required by the organization’s procedure. Do not erase the object from the story by editing the model first. Preserve what the project team and crew were using when the discovery occurred.

Open a late-obstruction change record with these fields:

1. Project, roof zone, active revision, release status, and reporter:
2. Feature identity, discovery source, date, location, visibility, and evidence:
3. Affected work, decision, installed condition, and immediate containment:
4. Previous obstruction record or reason no record existed:
5. Responsible designer and other qualified review routes:
6. Layout, shade, energy, material, electrical, commercial, proposal, procurement, and field dependencies:
7. Customer, schedule, contract, utility, authority, safety, or other review required where applicable:
8. Accepted treatment, evidence basis, owner, and decision date:
9. Revised documents, package identifier, withdrawal steps, and recipient confirmation:
10. Resume condition, field verification, customer explanation, and closure evidence:
11. Discovery mechanism and preventive process change:

Trace the mechanism without collapsing it into “missed during survey.” The feature may have been added later, hidden by temporary material, absent from stale imagery, present in an unshared plan, photographed without location context, removed during model cleanup, or visible but classified incorrectly. Each cause suggests a different control. More training will not fix a file that never reached the designer.

Map dependency before recalculation. An obstruction that changes placement may change quantities and electrical relationships. A shade-producing object may change the modeled energy basis. A reserved access zone may alter scope without affecting shade. Do not rerun every output automatically or update only the easiest one. Have each owner assess the outputs connected to the accepted effect tags.

Explain material changes without blame or false certainty. Tell the customer which new evidence appeared, which prior assumption or source it replaced, which documents or scenarios changed, what remains under review, and which version now controls. Avoid implying that one corrected layout resolves engineering, utility, authority, commercial, or installation questions outside that revision.

Resume only from a controlled release. A verbal answer may protect the site temporarily, but the project history needs the authorized decision, updated outputs, distribution record, and superseded-package treatment. Confirm that printed, downloaded, subcontractor, CRM, proposal, and work-order copies no longer direct people to the old state.

Software supports the checklist; evidence controls the release

SurgePV supports 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Those capabilities can help a team carry an obstruction decision through connected work.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility. A model cannot reveal a feature that its evidence never captured.

The checklist therefore belongs on both sides of software use. Screen evidence before modeling, and compare the completed model with the evidence register before release.

Make uncertainty visible while it can still be managed

The SurgePV shadow-analysis page provides current first-party context for the modeled shading workflow discussed above.

The purpose of an obstruction checklist is not to declare that a roof has no surprises. It is to show what the team looked for, which sources it used, what remains uncertain, and what decision happens next.

Cover roof penetrations, mechanical equipment, drainage, geometry, nearby shade objects, access zones, small features, and future conditions. Review empty areas with the same suspicion as marked objects. Give each finding a confidence, owner, trigger, and downstream impact.

That record will not make every early layout final. It will keep preliminary knowledge from dressing up as final evidence.

Frequently Asked Questions

What counts as an obstruction in a rooftop solar design?

An obstruction is any existing, temporary, or planned feature that affects usable area, shading, access, drainage, attachment, routing, maintenance, safety review, or another project decision. Examples include vents, skylights, equipment, parapets, roof drains, hatches, trees, adjacent structures, walkways, and areas reserved for future work.

Can satellite imagery find every rooftop obstruction?

No. Imagery can support early screening, but visibility depends on capture date, angle, resolution, shadows, roof material, and changes since capture. Small, low-contrast, hidden, temporary, or newly installed features may be absent or ambiguous, so project scope determines what field verification and other evidence are required.

When should obstruction verification occur?

Use staged verification. Screen available records before layout, collect suitable site evidence before the release that requires it, and recheck material conditions before affected field work. The exact timing depends on project scope, access, jurisdiction, responsible reviewers, and whether a change would invalidate current design or commercial outputs.

Who decides how much clearance an obstruction needs?

The responsible designer and other qualified parties determine treatment from the selected equipment, manufacturer instructions, safe access needs, project requirements, applicable codes, local authority rules, and engineering or contractor review. A generic checklist can identify the decision, but it should not invent a universal clearance for every feature and jurisdiction.

What should happen when an obstruction is discovered late?

Pause the affected decision, identify the active project revision, document the feature and evidence, and route it to the authorized reviewer. Then update every affected layout, model, material output, electrical record, proposal, work order, and release. Keep the prior version visibly superseded rather than editing one isolated document.