An EPC finishes a build. The real status of that work doesn’t land in a project system. It lands in an email, or a phone call, or a text to whoever happens to be the point of contact that week. The program might have a dashboard, a tracker, a dozen fields meant to capture exactly this. None of it matters if the person who did the work was never inside any of it to begin with.
EPCs, attachers, and landowners sit outside every system a program runs, not by accident, but because they were never going to be inside it in the first place.
Why they’re outside, structurally
An EPC runs its own project tools across every client it works for and has no reason to adopt a new one for a single program. An attacher negotiating a pole or tower agreement operates under its own process, on its own timeline, often with its own legal and engineering teams in the loop. A landowner isn’t running any system at all. They’re a person, or a family, with a lease and a phone number.
None of these parties is failing to coordinate. They’re coordinating fine, on their own terms, for their own purposes. The gap isn’t a willingness problem. It’s that the program’s systems stop exactly at the boundary of the organization that built them, and these three groups all sit past that boundary by definition.
Email becomes the system by default
When there’s no shared system that crosses that boundary, something still has to carry status back and forth, and it’s almost always whatever’s easiest in the moment: an email thread, a call, a text. That’s not a failure of process. It’s the only option left once the formal systems don’t reach that far.
The problem isn’t that email exists. It’s that it becomes the actual system of record for some of the most consequential status in the program, real ground-truth on whether a build is done, a wayleave is signed, or a landowner has agreed to terms, and none of that is searchable, auditable, or visible to anyone who wasn’t copied on the thread.
The cost lands on whoever’s holding the program together
This is the same gap the program manager usually ends up absorbing, because someone has to turn scattered messages into a program-level answer. Except here, the information isn’t even sitting in a system the program manager can query. It’s sitting in an inbox, possibly several different inboxes, belonging to whoever happened to be on the thread when the update came through. Finding out whether an EPC is actually done, or whether a landowner has actually agreed, means tracking down the right message rather than checking a record.
Multiply that across every EPC, attacher, and landowner on a program at once, and the real status of the entire external side of the work exists nowhere a program can see it in one place. Decisions get made on whatever was last confirmed verbally, which is rarely current and never complete.
Why forcing them into the program’s system doesn’t work
The instinct is to solve this by getting contractors and landowners to use the same system everyone internal uses. That rarely sticks. An EPC working a dozen clients isn’t going to run a dozen different project tools. A landowner isn’t going to learn a construction management platform to confirm a signature. Asking external parties to adopt internal infrastructure is asking them to absorb a cost that isn’t theirs to carry, and it gets resisted or ignored for exactly that reason.
What closes the gap
What actually works is a layer built for exactly this boundary: lightweight enough for an EPC, an attacher, or a landowner to update without adopting a new system, but structured enough that what they confirm becomes part of the program’s actual record instead of a message in someone’s inbox. The goal isn’t getting external parties to work like internal ones. It’s capturing their input in a form the program can actually use.
Where we come in
This is what Sitenna’s Management Cloud is built to bridge: a way to capture status from EPCs, attachers, and landowners directly into the program’s record, without asking any of them to adopt tools that were never built for them. Real status stops living in an inbox and starts living somewhere the whole program can see it.
If you’d like your program’s external status to be as visible as everything happening inside it, get in touch today.
About Sitenna
Sitenna is the intelligent operations platform built to eliminate blind spots across modern infrastructure. By centralizing fragmented asset data and automating workflows from site acquisition through execution and management, Sitenna delivers the real-time visibility and control needed to keep projects on track. With Sitenna, infrastructure teams move faster, collaborate smarter, and scale confidently – turning complexity into clarity at every stage.
Contact us at sales@sitenna.com