We get some version of the same question on almost every new project: "Is our documentation good enough to work from?"
Usually, yes. Here's what actually helps.
Photos and video
Smartphone photos are the backbone of most remote as-built projects. A few things make them more useful:
- Get close enough to read nameplate text, not just a wide shot of the panel
- Photograph wire labels and terminal numbers where visible
- A short walkthrough video of a room or MCC lineup gives us spatial context stills can't
Redlines and markups
Scanned or photographed redlines work fine even when they're messy. We've worked from decades of accumulated pencil marks on the same print. What matters is that we can read the annotation — if it's illegible in one area, a follow-up photo of just that section solves it.
What doesn't work
The only real blocker is missing information with no way to fill the gap remotely — for example, a device that was removed years ago with no photo record and no one left on staff who remembers what it was. In those cases we flag it plainly rather than guess, and it becomes a line item on the clarification checklist.
Send what you have. We'll tell you within 24 hours if there's a gap.