One of the most expensive problems in security integration doesn’t start with a bad install, a blown budget, or a missed deadline.
It starts with a site walk.
A missed detail. A photo with no context. A handwritten note nobody can decipher two weeks later.
That’s it. That’s the whole origin story. No dramatic failure, no obvious red flag, no moment where anyone could point and say, “There, that’s where it went wrong.” Just a small gap in information, captured in a format that wasn’t built to survive the trip from the field to the office.
I’ve sat with that idea for a while now, because the more conversations I have with integrators, the more I realize how much money moves through that gap without anyone noticing it’s there. Nobody budgets for it. Nobody puts it on a P&L line item called “things we missed during the site walk.” But it’s there, and it’s real, and it’s bigger than most people think.
And from there, it turns into:
- Rework
- Change orders
- Extra truck rolls
- Project delays
- Margin erosion
I didn’t expect to be writing about site walks this much. But here we are, because it turns out this is the thing that’s actually resonating.
The Conversation I Keep Having
A lot of my conversations lately start the same way:
“I saw one of your posts on LinkedIn.”
So, I ask what resonated. And it’s almost always around these exact issues: the gap between what happens in the field and what makes it back to the people who need it.
Sometimes it’s a sales leader who’s tired of hearing “we didn’t know about that” from engineering three weeks into a project. Sometimes it’s an operations person who’s had it with change orders that shouldn’t have needed to exist in the first place. Sometimes it’s someone on the technical side who’s just plain worn down by being handed a folder of blurry phone photos and a scrawled note that says something like “conduit run — see Dave,” when Dave left the company eight months ago and nobody thought to ask him before he did.
Different roles, different day-to-day frustrations, but the same root cause every single time. The information captured in the field never made it to the people who needed it, in a form they could actually use.
What’s interesting to me is who this is happening to. This isn’t a “small integrators who haven’t figured it out yet” problem. Some of the largest, most sophisticated system integrators in this industry (companies with real process discipline, formal training programs, established QA steps) are still running site walks on paper, pen, phone photos, spreadsheets, and tribal knowledge. Smart people, strong processes on paper, and still capturing critical project information in a format that doesn’t travel well past the person who collected it.
That’s the part that surprised me most when I started paying close attention. I expected this to be a maturity problem, something that got solved as companies scaled and formalized their operations. It’s not. Scale doesn’t fix it. If anything, scale makes it worse, because more site walks means more chances for a detail to get dropped somewhere between the parking lot and the proposal.
I’ll admit my view here is shaped by where I sit. Part of my day-to-day at System Surveyor is talking to integrators about this workflow, so I hear the site walk described from every angle, including the AE’s side, engineering’s side, and the install crew’s side. That vantage point is probably why this specific gap jumped out at me in the first place. It’s not abstract to me; it’s the thing I hear about, in some form, almost every week.
The Site Walk Isn't the Problem
Here’s the thing I want to be really clear about: the problem isn’t that the site walk gets done. It gets done. Someone shows up, walks the site, takes notes, snaps some photos, talks to the client.
The problem is what happens after it.
Sales hands it off to engineering. Engineering finds gaps. Operations has questions nobody can answer because the person who walked the site is three projects removed from this conversation by now. The project gets installed anyway, because it has to. Something was missed. Now someone has to go fix it.
And every single time that loop runs, margin gets chipped away. Quietly. Not in a way that shows up on a single invoice, but in a way that shows up when you zoom out.
One project might absorb the cost of a missed detail without anyone blinking. But across hundreds of projects a year? That’s not a one-off. That’s a profitability problem, and it’s happening at scale whether or not anyone’s tracking it that way.
A Scenario That Probably Sounds Familiar
Let me walk through how this actually plays out, because I think it’s easier to see the cost when you follow one detail through the whole lifecycle of a project.
An AE goes out to do a site walk for a new access control install. It’s a big facility, multiple entry points, a mix of old infrastructure and new construction. They’re moving fast; they’ve got two more site walks that day so they take some photos on their phone, jot a few notes, and mentally flag a couple of things they’ll “remember to mention later.”
One of those things is a door that has a non-standard frame. It’s going to need a different mounting bracket than the standard spec. Small detail. Easy to remember in the moment.
A couple of days later, that same AE hands off the file to engineering. The photos are on their phone, unsorted, mixed in with a hundred other things. The notes are on a legal pad somewhere on their desk, or maybe they typed a quick summary into an email, but the mounting bracket detail didn’t make the cut, because it genuinely slipped their mind. It happens. They’re human, and they were juggling five projects that week.
Engineering builds the proposal and the install plan based on standard hardware, because that’s what the information in front of them supports. Nobody flags the door.
The install crew shows up. They find the door. They don’t have the right bracket. Now there’s a decision to make: order the part and delay the install, or have someone drive back to the shop and hope it’s in stock. Either way, that’s a truck roll, a schedule slip, and a labor cost that wasn’t in the original estimate.
Multiply that one door by every project where a similar detail didn’t make it from the field to the file. That’s the leak. It’s not one catastrophic failure — it’s a hundred small ones, each one small enough to shrug off, each one still coming out of margin.
What Digitizing Actually Fixes
This is the part that I think gets missed in the conversation. When people hear “digitize the site walk,” they think it’s about convenience. Going paperless. A nicer-looking form.
That’s not really what it’s about.
Digitizing the site walk is about replacing the downstream problems that paper, disconnected photos, and tribal knowledge create. When I talk to integrators who’ve moved their site walks into a platform like System Surveyor, where the photos, notes, and measurements are tied directly to a location on a digital floor plan instead of floating around loose, the conversation usually shifts pretty quickly from “this is nice to have” to “I don’t know how we did this any other way.” It’s about:
- Less rework, because the information captured in the field actually makes it to engineering intact. Not summarized, not filtered through someone’s memory two weeks later intact, the way it was originally documented, tied to the exact location and asset it belongs to.
- Fewer unnecessary change orders, because scope was documented accurately the first time. A change order isn’t inherently a bad thing, sometimes the client changes their mind, sometimes conditions genuinely change. But a change order that exists because a detail was missed during the original site walk is pure cost. It’s not billable in any way that feels fair, and it’s the kind of thing that quietly damages trust with the client too.
- Better handoffs between sales, engineering, and operations, because everyone’s working from the same source instead of a game of telephone. Nobody’s translating someone else’s notes. Nobody is asking “wait, what did they mean by this?” three weeks after the walk happened.
- More accurate scopes, because the details aren’t living in someone’s memory, a stack of unsorted photos, or a notebook that gets lost in a truck somewhere. The scope reflects what’s actually at the site, not what someone remembered about the site.
And ultimately, it’s about protecting the margin you worked hard to win in the first place. You already fought for that deal. You already priced it competitively enough to win it. Don’t let it get eaten alive by a communication gap that happened before the project even started.
Who Feels This the Most
If I had to break down where this shows up by role, it would look something like this:
- Sales/Account Executives feel it as credibility. When engineering keeps coming back with questions the AE can’t answer, or when a project they sold turns into a headache for the ops team, that reflects on them even when the root cause was a documentation gap, not a sales gap.
- Engineering feels it as friction and guesswork. They’re often building proposals and install plans off information that’s incomplete, and they know it’s incomplete, but they don’t always know what’s missing until it’s too late to ask.
- Operations and project management feel it as schedule risk. Every unresolved detail from the site walk is a landmine that might go off mid-install, and when it does, it’s their job to absorb the fallout. Reschedule the crew, source the part, explain the delay to the client.
- Install teams and technicians feel it the most literally. They’re the ones standing at a door with the wrong bracket or looking for a conduit run that was never actually documented, trying to solve a problem in the field that should have been solved weeks earlier at a desk.
- Leadership feels it last and feels it as a number: a margin percentage that’s a little lower than it should be, spread across every project, without a clean explanation of why.
Everyone’s absorbing the cost of the same root problem. They’re just absorbing it in different currencies, such as time, stress, trust, or dollars.
So, Where Is It Actually Getting Lost?
I ask this question a lot, and I’ll ask it here too: for system integrators reading this, where do you see the most profitability getting lost between the site walk and project completion?
Is it the handoff from sales to engineering? Is it change orders that shouldn’t have been necessary? Is it the truck roll back to a site because a detail wasn’t captured the first time? Or is it something earlier and quieter than all of that? A scope that was never quite right to begin with, because the person walking the site didn’t have the tools to capture it accurately in the moment?
I don’t think there’s one universal answer. Every integrator I talk to points to a slightly different stage in the process. But the pattern underneath is almost always the same: information that existed at one point in time, captured by one person, in one format, that didn’t survive the trip to everyone else who needed it.
That’s really what this whole conversation comes down to for me. Not paper versus digital as some kind of philosophical debate, but a simple operational question, “Is the information you’re capturing in the field actually usable by the people who need it next?” If the answer is “mostly, but not always,” then that gap is where your margin is going.
I’d genuinely like to know where you’re feeling it because in my experience, once you can identify exactly where it’s leaking, it gets a lot easier to fix. If you’re curious what it looks like to close that gap, it’s genuinely a big part of why I like the work I do at System Surveyor. I’d be happy to show you sometime, no pressure either way.
FAQs
When a detail is missed during the site walk, engineering scopes and prices the project without it. The gap usually isn’t discovered until the install crew is on site, at which point fixing it requires additional parts, labor or time that wasn’t in the original estimate. Some change orders are legitimate, such as when a client changes their requirements. But a change order caused by a missed detail is pure cost, and it can damage client trust as well.
Beyond the direct cost of fuel and vehicle time, an unplanned truck roll pulls a technician away from billable work, can push back the install schedule, and often requires rescheduling other jobs. When the trip happens because a part or detail wasn’t captured during the original site survey, all of that cost comes straight out of the project’s margin.
No. Some of the largest and most process-driven integrators in the industry still run site walks on paper, phone photos, spreadsheets and tribal knowledge. Scale tends to make the problem worse, not better, because more site walks mean more opportunities for details to get lost between the field and the office.
Everyone involved in the project feels it, just in different ways. Sales loses credibility when engineering comes back with unanswered questions. Engineering works with incomplete information. Operations teams absorb the schedule risk. Install teams deal with the problem in the field. Leadership eventually sees it as lower-than-expected margins across the business.
Digitizing the site walk isn’t just about going paperless. It keeps field information intact as it moves from sales to engineering to operations. When photos, notes and measurements are tied to a specific location on a digital floor plan, nothing depends on someone’s memory or an unsorted camera roll. Everyone works from the same source, scopes are more accurate, and fewer details get missed before installation.
Ask a simple question: is the information captured in the field actually usable by the people who need it next? If engineering regularly has to follow up with the person who walked the site, if install crews find surprises on site, or if change orders keep coming up for things that “should have been caught,” your site survey process is likely where margin is leaking.
Start by identifying where information is getting lost in your process. Look at your recent change orders and return trips and trace each one back to its root cause. If many trace back to the site walk, standardizing how field information is captured and shared, ideally in one central, location-based platform, is the most direct way to close the gap.
Shelby Chatigny is an Account Executive at System Surveyor, the leading digital platform for physical security site surveys and system design. With 5+ years of experience across the physical security industry, she brings a unique perspective from both the manufacturer and integrator sides. Shelby works closely with customers to modernize site walks, streamline digital design and help teams deliver more accurate, collaborative, and efficient security projects. She enjoys building relationships in the industry and supporting professionals who want to elevate their workflows and scale their business with better tools and clearer communication. Shelby lives in the mountains of North Carolina where she enjoys hiking, reading, writing poetry, playing with her two dogs and spending time with family and friends.