Where the handoff actually breaks
In theory the handoff is simple: the field team sends data, the design team draws. In practice it breaks in three places. The first is missing data that the designer discovers days into drawing. The second is unlabeled data, where a number is present but nobody can tell whether it was measured, copied from an old drawing, or guessed. The third is ambiguous data, such as a photograph of a nameplate that is cropped, blurred or taken from an angle that hides the rating.
Each failure produces the same result: a question from the designer to the field team, a pause in drawing, and sometimes a return visit. Anyone who has run an EPC engineering desk knows the cost is not the question but the queue it sits in.
What a plan set needs from the survey
A commercial plan set typically includes a site plan, a roof or array layout, structural information, a single-line electrical diagram, equipment details, conduit routing and the safety and labeling sheets required by the local authority. The survey record should map to those sheets directly.
- Site plan. Property features, building footprint, access routes, utility locations and the position of the equipment.
- Roof layout. Dimensioned roof outline, parapets, penetrations, rooftop units, drains and setbacks for fire pathways.
- Structural information. Framing type, member sizes and spacing, deck type, roof buildup and any drawings gathered.
- Single-line diagram inputs. Service voltage, switchgear and main ratings, bus rating, available fault current, interconnection point and meter details.
- Equipment placement. Proposed inverter and disconnect locations with clearances and the conduit route.
- Labeling and signage inputs. Existing labels, fire access and rapid shutdown device locations.
Label every value
The most useful habit a survey team can adopt is labeling the source of each value. A joist depth read from a stamped designation is a different kind of fact from a joist depth assumed because the ceiling was closed. Both can be acceptable in a design, but the engineer needs to know which they have. A simple three-way label, measured, from drawing, or assumed, removes a huge fraction of handoff questions.
It also protects the people involved. When an engineer seals a design, the basis for each input matters. A record that distinguishes measured facts from assumptions lets the engineer decide what to verify, what to treat conservatively and what to push back on.
Photographs that engineers can use
- Each nameplate photographed straight on, in focus, with the whole plate in frame, plus a wider shot showing where it is.
- Each roof zone photographed from a consistent set of positions, tied to a roof sketch.
- Close-ups of unusual conditions, with an item in the frame for scale.
- A consistent naming scheme so the designer can find photos without asking.
Our note on main switchgear photos and documentation shows what a set of electrical photographs should look like, and the commercial rooftop checklist orders the captures the way a crew works.
Formats and exports
Designers work in CAD and in modeling tools, so the survey record is most useful when it can move into those tools without retyping. Roof dimensions and equipment locations in an exportable format save hours. Our platform supports survey PDF and DXF exports for this reason. A PDF is good for reading and sign-off, while a DXF gives the designer geometry to build on.
One record, not two
The cleanest handoff is no handoff: the survey and the design share a single record. When the design team works from the same data the field team captured, nothing has to be reinterpreted. That is the model behind Solar Survey AI's commercial on-site survey and design and engineering: the survey delivers 48 hours after the visit, and the plan set is sealed by a licensed professional engineer using the framing and switchgear captured on site.
A worked example of an unlabeled value
Consider a structural note that reads "joists 24 inches deep." On its own it looks complete. But the designer cannot tell whether that figure was measured with a tape at an exposed joist, copied from a drawing set that is thirty years old, or assumed because the ceiling was closed. If it was measured, the engineer can use it with confidence. If it came from a drawing, the engineer may ask for verification. If it was assumed, the engineer must treat it conservatively or request a visit.
Now consider the same note written as "joists 24 inches deep, measured at the mechanical room, north bay, photo 31; other bays assumed similar." The same information now carries its own evidence and its own limit. The designer knows what to trust and what to check, and no question has to travel back to the field.
This is a small habit with a large effect. It costs a few extra words at capture time and saves a message thread later, and it scales to every field in the record, from roof dimensions to bus ratings.
A handoff review you can run in ten minutes
Before sending a record to design, someone should run a brief review: does every sheet in the expected plan set have the inputs it needs? Is every value labeled? Are nameplates legible? Are there open questions the field team already knows about? Writing those open questions at the top of the record, instead of hoping the designer finds them, is an easy way to build trust between field and office.
For permitting context, see our permitting and engineering page, which explains how a stamped plan set supports the approval process, and the permit note for the package a permit office expects.