6 Field Conditions That Need Three-Part Evidence

A field team can return a precise distance, a sharp photograph, and a detailed note and still leave design unable to use any of them. The distance has no labelled endpoints. The photograph cannot be matched to the object. The note says “tight area” without identifying what is tight or which work it affects.

The problem is not a shortage of media. It is a broken relationship among three different kinds of evidence. A measurement describes geometry. A photograph establishes identity and visible context. A written note preserves circumstances, method, limits, and first-hand observations that a number or image cannot prove. Some field conditions need those three parts linked as one record.

This guide identifies six such conditions. It is not another complete solar site survey checklist, and it does not replace the broader site-survey evidence-package guide. It owns a narrower decision: when one medium would invite a receiving team to guess, what should the assessor measure, photograph, write, and route?

Why do some field conditions need all three evidence types?

Some solar field conditions need measurements, photos, and notes because the next decision depends on geometry, identity, and context together. The measurement answers “how much,” the photograph answers “which object and where,” and the note answers “how observed, under what limits, and what remains unresolved.” None should silently stand in for another.

Think of the three parts as a joined evidence record, not three files in unrelated folders. The measurement should name endpoints that appear in the photograph. The photograph caption should use the same building, plane, obstruction, panel, or route identifier as the note. The note should state the source, observation time, method, access limit, and decision question.

That relationship is more useful than simply collecting more. Twenty close-up images of a rooftop unit may show fasteners, labels, and surface wear while never showing which roof plane contains the unit. A single context image plus an identifying close-up, labelled dimensions, and a bounded observation can be easier to act on.

The receiving team must also know what the record does not settle. A surveyor may accurately measure a stained roof area and document visible surface variation. That does not diagnose a leak, identify a cause, estimate remaining roof life, or establish structural adequacy. A clear electrical label does not prove available capacity or approve an interconnection. An access photograph does not create a safety plan.

This boundary matters because field observations sit upstream of several decisions. Roof geometry may affect modeling and placement. Object relationships may affect layout, service access, and installation planning. Electrical records may affect a qualified electrical review. Logistics may affect scheduling and site coordination. If the evidence package blurs observation and conclusion, every downstream artifact can inherit the same ambiguity.

The U.S. Department of Energy identifies roof age, tree cover, size, shape, and slope as relevant considerations in a homeowner solar decision. Its photovoltaic system design overview also explains that modules are only one part of a complete PV system, alongside mounting, inverter, and other technologies. These categories justify connected observations. They do not determine the suitability, design, or approval of a particular site.

Use a three-part bundle when all of the following are true:

• A physical relationship influences the next project decision.
• A later reader needs to identify the exact objects or areas involved.
• Observation circumstances, access limits, reported information, or uncertainty could change how the evidence is interpreted.

If one condition is absent, the survey brief may legitimately request fewer media. The rule is not “three items for everything.” The rule is “never force one medium to answer a question it cannot support.”

Which six field conditions need measurements, photos, and notes?

Use a three-part evidence bundle for six recurring conditions: irregular roof geometry; obstructions and service relationships; visible roof deterioration, repairs, or changed conditions; electrical equipment and proposed route relationships; accessible attic, framing, or other concealed-condition viewpoints; and staging, lifting, access, shutdown, or operational constraints. Each bundle needs a named recipient and return rule.

1. Roof edges, plane transitions, and irregular geometry

Irregular geometry needs more than an outline. Hips, valleys, dormers, parapets, stepped roof sections, additions, curved edges, hidden eaves, and elevation changes create relationships that can look obvious in a photograph while remaining impossible to scale. A dimension list can be equally misleading when nobody can tell which line belongs to which roof object.

Measure the endpoints that control the next decision. That may include an edge length, ridge-to-eave distance, plane transition, elevation difference, parapet height, or the spacing among fixed reference points. Record units, method, and whether the value was directly observed, derived by the approved field method, taken from a supplied drawing, or estimated. Never mix those statuses in one unlabeled column.

Photograph the whole roof section before taking close-ups. Give each plane and transition a stable identifier, then show the measurement endpoints in a marked image or a linked sketch. Include enough surrounding context to distinguish similar dormers, repeated bays, or adjacent buildings. If vegetation, equipment, glare, weather, or access hides an edge, photograph the obstruction to observation rather than pretending the missing line was seen.

The note should state which surfaces were accessible, which edges were visible, what blocked the view, and which geometry remains inferred. It should also name the intended use. A dimension accepted for preliminary roof modeling is not automatically accepted for attachment details, structural work, construction, or another purpose.

Return the bundle when an endpoint cannot be identified, two dimensions do not reconcile under the team’s method, a required surface was inaccessible, or current observations conflict with remote imagery or drawings. The roof-model or survey lead receives the geometry record. Roof, structural, code, and construction conclusions go to reviewers authorized for those questions.

2. Obstructions, equipment, clearances, and access relationships

An obstruction is not just a footprint. Rooftop units, vents, drains, hatches, skylights, chimneys, antennas, parapets, piping, walkways, and fall-protection components can have access, service, drainage, shade, safety, or operating relationships that a layout reviewer must not infer from a cropped image.

Measure the object footprint only when the brief requires it, then capture distances to named roof edges, adjacent objects, pathways, or other stable references relevant to the open question. Height may matter for geometry or shading, but only use the requested and authorized method. A distance is not a code clearance unless the current project criteria and responsible reviewer say so.

Take one identifying photograph that locates the object on the roof and one context view that shows neighboring objects and likely approach directions. Add a readable label close-up where the label is within scope and can be captured without unsafe or unauthorized access. Photographs should show what exists, not imply that the proposed design around it is acceptable.

Write what the object appeared to be, whether it was operating, what access was permitted, what could not be seen, and whether a site representative provided information about service or maintenance. Attribute reported statements: “facility representative reported quarterly service access” is different from a first-hand observation. Do not decide a required service zone from that statement alone.

Shading deserves a separate link in the record. Sandia’s PV Performance Modeling Collaborative describes plane-of-array irradiance through solar position, array orientation, irradiance components, ground reflection, and shading-related inputs. A field object record can inform modeling, but a photograph alone does not quantify its energy effect.

Return or escalate when the object identity is uncertain, its base or full height is hidden, the measured reference cannot be found in the image, operational access is disputed, or a treatment depends on local, manufacturer, safety, or discipline-specific criteria. Route geometry to design, service questions to the appropriate equipment or facility owner, and technical requirements to qualified reviewers.

3. Visible roof deterioration, repairs, ponding, or changed conditions

Visible discoloration, patches, open seams, damaged-looking areas, accumulated water, repairs, temporary coverings, and differences from earlier imagery should be recorded precisely and described cautiously. They are observations that may change the project route. They are not diagnoses.

Measure the visible extent only if it can be done within the approved field plan. Name the boundaries and reference points. If the area is irregular, use multiple dimensions or a marked sketch rather than one number that suggests false precision. Do not probe, lift, open, sample, or disturb roof materials unless the assigned work, authorization, training, and safe procedure explicitly permit it.

Photograph the area in context, then capture the visible detail. Show nearby drains, penetrations, seams, edges, equipment, or previous repair boundaries when relevant. Preserve the date and recent weather context if known because a photograph of water after rain and a photograph of staining during dry conditions are different observations.

The written note should avoid causal labels. “Visible standing water in the marked area at 10:20 after rain reported earlier that morning” is bounded. “Drainage failure” is a conclusion the observation may not support. Record odors, sounds, softness, movement, or customer statements only as observations or attributed reports and only when gathered within the approved scope.

DOE’s homeowner solar guide identifies roof age among factors to consider and notes that roof size, shape, slope, and tree cover can matter. That guidance supports asking the question. It does not let a field assessor determine roof condition, remaining life, waterproofing, attachment suitability, load capacity, or solar suitability from visible evidence.

Stop or return the affected field task if the area cannot be approached under the site plan, if the requested measurement would disturb material, or if conditions have changed enough to invalidate the brief. Send the three-part record to the project owner and the qualified roof or structural route as appropriate. Keep the related layout zone preliminary until the responsible decision is recorded.

4. Electrical service, labels, enclosures, and proposed routes

Electrical evidence often fails because close-ups and routing photos become separated. A readable equipment label can identify marked information while hiding where the enclosure sits. A wide wall image can show relationships while making every label illegible. A route length without endpoints leaves the designer guessing whether the path crossed a doorway, roof edge, occupied space, or inaccessible area.

Measure only the physical relationships requested by the survey brief and permitted by the electrical-safety plan. Examples may include enclosure location relative to stable building references, accessible route segments, or available wall area. A field dimension does not establish conductor sizing, equipment rating, electrical capacity, code compliance, utility acceptance, or permission to use a route.

Photograph the overall equipment area first. Then capture enclosure identification and labels that can be read without opening, removing, or crossing an unauthorized boundary. Include the proposed route context, direction changes, penetrations, obstructions, access restrictions, and endpoints. If the surveyor cannot safely or legally access something, the correct evidence is a restriction note and context image from the permitted position.

The note must identify what was energized or believed energized only according to the approved process, what remained closed, who provided access, and which information came from a site contact. Record illegible, damaged, missing, or conflicting labels without guessing the value. Route every technical interpretation to the qualified electrical reviewer.

OSHA’s solar hazard overview identifies arc flash, electric shock, falls, and thermal burns among serious hazards solar workers may face, and links electrical, fall, lockout/tagout, crane, heat, and personal protective equipment topics. This U.S. source supports treating access and electrical observations as safety-sensitive. It does not create a site-specific work plan or compliance conclusion.

Return the package when required identifiers are unreadable, enclosures cannot be photographed from the authorized position, route endpoints are ambiguous, the field condition differs from the supplied one-line or plan, or the request exceeds the surveyor’s scope. The electrical design or engineering owner decides the next technical step; the surveyor preserves the observable facts.

5. Accessible attic, framing, and other concealed-condition viewpoints

Attics, ceiling spaces, framing views, equipment rooms, and other concealed-condition access points require disciplined evidence because a narrow view can be mistaken for the whole structure. The field record should show what could be observed from the authorized position and make the missing coverage unmistakable.

Measure only the features named in the brief, using the approved method and access plan. Possible observations include spacing between visible members, visible member depth at an accessible edge, a reference distance from an access opening, or the location of a visible obstruction. Do not infer hidden continuity, material properties, connection capacity, load path, structural adequacy, or the condition of unobserved areas.

Take an orientation photograph at the access point before close-ups. Show the direction of view and connect each close-up to a wider image or simple sketch. Include a scale reference only where the field procedure allows it and where it will not be mistaken for a calibrated measurement. Darkness, insulation, finishes, stored material, restricted movement, and inaccessible bays belong in the visual record.

The note should say where the observer stood, how far the visible area extended, whether framing was partly concealed, and which members could not be identified. If a customer or building representative describes hidden construction, retain the statement as customer-provided information. It is not equivalent to first-hand observation or an accepted record drawing.

The field assessor should never widen access, move material, enter a restricted space, or improvise around a hazard merely to complete a media checklist. OSHA’s recommended safety and health practices include management leadership, worker participation, hazard identification, hazard prevention and control, education, program evaluation, and coordination. The responsible employer and site process must determine safe work, not this article.

Return the record if the viewpoint cannot be tied to a roof area, visibility is too limited for the requested observation, dimensions cannot be connected to visible members, access conditions differ from the plan, or a structural conclusion is being requested from a field observation. Send the bundle to the structural or project reviewer within that person’s remit.

6. Staging, ladder or crane access, pathways, shutdowns, and operations

Installation logistics involve relationships across the site: where people and equipment may enter, where materials might be staged, what areas remain occupied, what operations cannot be interrupted, and what physical constraints require specialist planning. A single parking-lot photograph rarely carries those relationships.

Measure only the dimensions requested for preliminary planning, such as a gate opening, clear corridor, building reference distance, or available area bounded by identifiable objects. Do not convert those values into a lift plan, fall-protection plan, traffic-control plan, fire-access decision, load rating, or assurance that equipment can be staged safely.

Photograph each proposed access area from both approach and destination where possible. Show gates, overhead objects, grades, curbs, landscaping, occupied routes, surface changes, locked areas, roof access points, and neighboring operations. Aerial or roof-level context may help connect locations, but it does not erase ground-level visibility gaps.

Notes carry the operating context: access hours, delivery restrictions, occupant movement, customer-reported shutdown limits, security procedures, planned events, weather restrictions, and areas excluded by the site representative. Attribute each rule to its source and record whether it was observed, supplied, provisional, or still needs confirmation.

OSHA’s solar overview includes crane and hoist safety among its hazard topics. That is enough to show why a site assessor should preserve access and lifting observations for responsible planning. It is not enough to choose equipment, approve a lift, establish safe distances, or authorize work. Those decisions belong in the employer’s and qualified parties’ project-specific processes.

Return or escalate when the measured path does not match the photographed route, access depends on moving an unknown obstruction, the site contact cannot confirm a reported restriction, or the proposed method requires a safety, engineering, property, authority, or equipment-owner decision. Send logistics evidence to project operations, then route specialist questions to their owners.

Before this field record enters a solar design workflow, the reviewer should be able to trace each measurement, photograph, and note to the same condition and see the limits on its intended use.

How should a team capture and hand off a three-part record?

Build the record around one field condition and one downstream decision. Assign a stable condition ID, define the question before the visit, capture measurements with labelled endpoints, take identifying and contextual photos, write observation and limitation notes, reconcile the three parts, route exceptions, and release only the uses the accepted evidence actually supports.

Use this sequence for each condition:

1. Name the decision. Write the exact question the evidence must help answer, the intended project stage, the receiving owner, and the decisions it will not settle.
2. Assign a stable condition ID. Use the same ID on the field form, photographs, sketches, measurements, returned questions, model objects, and review record.
3. Define the requested measurement. Name the units, endpoints, preferred method, acceptable alternative, and action if the measurement cannot be taken.
4. Define the required views. Request an orientation image, object-identification image, context image, close-up, or route sequence as the question requires. Do not rely on an unbounded request for “lots of photos.”
5. Capture the observation note. Record observer, time, location, method, first-hand observation, supplied information, access or visibility limit, and unresolved question.
6. Reconcile at the site when safe and practical. Confirm that endpoints appear in the relevant image, identifiers match, units are present, and the note points to the correct object. This is a completeness check, not a technical approval.
7. Return exceptions explicitly. If the field team could not capture an item, state why, what evidence exists, whether conditions changed, which output is affected, and who must decide the next action.
8. Review for intended use. The receiving owner accepts, rejects, or restricts the evidence for a named use and routes technical conclusions to qualified people or authorities.
9. Connect the accepted successor. Update the roof model, layout, route record, open-item log, or planning document that consumed the evidence, and retain the earlier revision’s status.
10. Close with a return trigger. State what future conflict, site change, missing area, revised scope, or reviewer decision would reopen the condition.

The solar site-survey process guide owns the visit’s broader sequence. This process begins at the condition record and ends when a receiver knows what the linked media support. The field-change communication guide applies when an observation changes work already released or planned.

Copy-ready three-part field capture record

1. Project, property, building, and survey date:
2. Condition ID and condition category:
3. Downstream decision and intended evidence use:
4. Receiving owner and escalation owner:
5. Measurement requested, units, endpoints, and approved method:
6. Measurement returned, method used, and confidence or limit:
7. Orientation photo IDs:
8. Object-identification and close-up photo IDs:
9. Context or route photo IDs:
10. First-hand written observation:
11. Customer, facility, or third-party information with named source:
12. Access, visibility, weather, timing, or equipment limits:
13. Difference from remote imagery, drawing, model, or earlier revision:
14. Conclusion explicitly outside the surveyor’s scope:
15. Missing evidence and reason:
16. Interim restriction on layout, model, route, release, or schedule:
17. Recipient disposition, permitted use, and date:
18. Required technical or external review:
19. Affected successor records and revisions:
20. Closure condition and trigger for reopening:

The record is intentionally explicit about refusal and limitation. “Not captured because the enclosure remained closed under the electrical-safety plan” is useful evidence. A blank cell is not. The former tells the receiver to change the question, source, or authorized route. The latter encourages guesswork.

What makes a three-part field record ready to use?

A three-part field record is ready when the condition and decision are named; units and endpoints are visible; photos establish identity and context; notes separate observations, reported information, and limits; all parts share stable IDs; missing evidence has an owner; qualified conclusions remain outside the survey; and the receiving owner records a permitted use or return decision.

Use a return matrix rather than a vague “complete” status:

Illustrative example, not a customer case

Suppose a preliminary layout shows a lower roof beside a rooftop unit, but the remote source does not reveal the unit’s service side. The survey brief creates condition OBS-04 and asks whether the visible unit and roof-edge relationship can support preliminary layout review. It does not ask the assessor to establish a code clearance.

The field return includes two dimensions with endpoints marked on image OBS-04-P03: unit base to the east roof edge and unit base to the nearest fixed penetration. Image OBS-04-P01 locates the unit on the building. Image OBS-04-P02 shows the label from an authorized position. A short route sequence shows the apparent approach from the hatch.

The note says the south panel was openable only by facility personnel and remained closed; the facility representative reported that service normally approaches from the south; piping obscured part of the base; and no service-clearance conclusion was made. The surveyor flags the brief’s requested full-height dimension as not captured because the upper endpoint could not be observed under the approved method.

Design can now locate the observed object and reserve an affected zone. The equipment or facility owner can confirm service information. The appropriate technical reviewer can decide what treatment is required. Nothing in the bundle claims compliance or final placement. Its value lies in preventing a dimension or photograph from being stretched into that conclusion.

Before accepting a package, ask a skeptical reader to find:

• One condition ID carried across every measurement, image, note, and receiving record.
• A photograph that proves which object or area each dimension describes.
• Labelled endpoints, units, and method for every decision-relevant measurement.
• An observation note that says what the assessor actually saw.
• A separate label for customer-provided or third-party information.
• A clear statement of access, visibility, weather, timing, and method limits.
• The decision the evidence supports now and the decisions it does not support.
• A named return owner for missing, conflicting, unsafe, or out-of-scope evidence.
• A downstream revision or open-item record connected to the accepted bundle.
• A trigger that reopens review if the site, scope, source, or controlling decision changes.

SurgePV can support connected 3D roof modeling, array layout, shading analysis, energy-yield modeling, electrical workflow records, materials, and proposals. Those functions depend on source data, assumptions, equipment models, configuration, and review. Software does not turn field media into proof of safe access, roof condition, structural adequacy, electrical capacity, code compliance, utility acceptance, or construction approval.

Frequently Asked Questions

Solar assessors usually ask whether every observation needs all three media, whether a photo can supply scale, what belongs in notes, who owns an incomplete return, and whether software can validate the site. The consistent answer is to match evidence to a named decision, preserve limits, and route conclusions to the responsible reviewer.

Does every site-survey item need a measurement, photo, and note?

No. Use all three when geometry, identity, and context must remain connected for the next decision. A clearly identified equipment label may need photographs and a note but no field dimension. The survey brief should define the minimum evidence for each question, and the surveyor should record why a requested item could not be captured.

Can a photograph replace a solar site-survey measurement?

A photograph can show an object and its surroundings, but it does not automatically establish a reliable dimension or scale. If size, distance, elevation, or route length matters, return the requested measurement with its endpoints and method. Keep the photograph as identity and context evidence, not as silent proof of an unrecorded dimension.

What should a solar surveyor write in field notes?

Write what was observed, where and when it was observed, how a measurement was taken, what limited the view or access, and which question remains open. Distinguish first-hand observations from customer-provided information. Do not turn discoloration, a label, a sound, or a restricted area into a technical conclusion outside the assigned role.

Who reviews incomplete three-part field evidence?

The owner of the next affected decision should review completeness, then route technical questions to the competent discipline. A design lead may check geometry, while qualified roof, structural, electrical, safety, code, utility, or construction reviewers decide matters within their remit. The return record should name both the immediate recipient and any escalation owner.

Can solar design software validate site conditions?

No. Software can organize project inputs and support modeling, layout, analysis, electrical workflow, materials, and proposal work. It does not visit the site, verify a measurement, diagnose roof condition, establish safe access, interpret every local requirement, or grant engineering, utility, permitting, or construction approval. Responsible reviewers must accept evidence for its intended use.