On January 4, 2026, I sat across from a federal contracting evaluation team and heard something that rewired how I think about national infrastructure delivery.
They explained the scoring logic for a multi-year preventive maintenance contract covering VA facilities across an entire VISN. Technical capability? Scored. Past performance? Scored. Management approach? Scored.
Then they said it: Geography factor.
I wasn't ready for that.
The Shock of Geography
I had spent months building a system that could connect every technician to every task. Schedule them. Track completion. Capture reportables. Submit documentation the moment outcomes were verified. I had designed a coordination engine that could theoretically manage preventive maintenance across 171 VA medical centers from a single operational hub.
And the evaluation team was telling me that none of that mattered if we couldn't prove physical presence in the region.
Not remote monitoring. Not digital coordination. Not even a subcontractor network with national reach. They wanted to know: Do you have people — right now — within driving distance of these facilities?
That's the moment geography became a constraint in my vocabulary.
Why Geography Is Different
Every other constraint in this series describes a system-level bottleneck — knowledge, coordination, trust, talent, technology. These are organizational challenges. You can engineer solutions. You can build platforms. You can change how people work.
Geography doesn't work like that.
Geography is physical. It's the distance between your nearest qualified technician and the facility that needs service on Tuesday morning. It's the travel radius that determines whether a four-hour response time is achievable or a contractual liability. It's the difference between 'we can mobilize' and 'we're already there.'
In federal preventive maintenance — especially across VA, DoD, and GSA facilities — geography isn't a nice-to-have. It's an evaluation criterion. Contracting officers score it. Evaluation boards weight it. And firms that can't demonstrate regional coverage don't make the competitive range, regardless of how sophisticated their technology or coordination systems are.
The Federal PM Reality
Federal preventive maintenance contracts are not construction projects. They're not one-time mobilizations with a defined start and end. They are recurring, distributed, multi-year obligations that require consistent physical presence across a geographic footprint.
Consider what a typical VA VISN PM contract requires:
- Monthly inspections at 8–15 facilities spread across 2–4 states
- Quarterly maintenance on critical MEP systems (HVAC, electrical, plumbing, fire protection)
- Emergency response within defined SLA windows — often 4 hours for critical systems
- Seasonal work (winterization, summer cooling prep) that must happen within narrow weather windows
- Documentation and reporting that proves not just completion, but the right person completed it at the right facility at the right time
You can't do this from a headquarters 600 miles away. You can't do it by flying crews in. The economics don't work. The response times don't work. And critically — the evaluation team knows it.
What I Thought Would Work
Before January 4th, I believed our coordination system was the answer. And in many ways, it still is — but not as a substitute for physical presence. As a complement to it.
Here's what I had built:
- Task assignment engine: Connect every PM task to a qualified technician based on trade, certification, and availability
- Scheduling system: Optimize routes and timing across facilities to minimize travel and maximize coverage
- Reportable capture: Real-time documentation of completed work — photos, readings, checklists — submitted immediately upon completion
- Payment trigger: Once all reportables meet expected outcomes, submit for payment release
The logic was sound. Connect person to task. Schedule the work. Capture the evidence. Submit for payment. A clean, digital loop.
But the evaluation team wasn't asking whether I could coordinate the work. They were asking whether I had the geographic infrastructure to perform it.
The Coalition Answer
This is where the coalition model stopped being a strategic concept and became an operational necessity.
If geography is the constraint, the solution isn't hiring. You can't hire your way to national coverage — not as a small business, not in specialty trades, not in the current labor market. The solution is regional coalition formation.
Here's what that means in practice:
Regional Partners, Not National Subcontractors. Instead of one subcontractor with claimed national reach, you build relationships with firms that are already embedded in their regions. Firms whose technicians live within the service radius. Firms that already have relationships with local facility managers. Firms that don't need to mobilize — they're already there.
Shared Coordination Infrastructure. The coalition doesn't just share work — it shares the coordination layer. The same task assignment engine, the same reportable capture system, the same documentation standards. This is what Groundline provides: a single operational memory that spans the coalition, so every partner is working from the same playbook without needing the same office.
Geographic Qualification as a Feature. When you can demonstrate to an evaluation team that you have SDVOSB-qualified, trade-certified technicians within 50 miles of every facility in the VISN — not on paper, but with names, certifications, and past performance — geography stops being a constraint and becomes a competitive advantage.
The Math of Coverage
Let me make this concrete. A single VISN might cover facilities across three states. To maintain 4-hour emergency response capability across that footprint, you need:
- Minimum 3–5 regional hubs with qualified technicians in each trade discipline
- Local supervision at each hub — someone who knows the facilities, knows the staff, knows the quirks of each building
- Parts and materials staging within reasonable distance of each facility cluster
- Backup capacity for when primary technicians are unavailable (vacation, illness, other commitments)
A single firm trying to self-perform this is either massive (and therefore not a small business) or stretched thin (and therefore unreliable). The coalition model solves this by making each regional partner responsible for their zone — with shared standards, shared documentation, and shared accountability.
Why This Matters Beyond Federal Work
The geography constraint doesn't disappear in commercial construction. It manifests differently.
In data center construction, the constraint is proximity to skilled labor pools. You can't build a facility in rural Virginia if the nearest qualified MEP workforce is in Baltimore — not unless you're prepared to pay for housing, travel, and retention premiums that destroy your margins.
In healthcare facility maintenance, the constraint is response time. Equipment failures in operating rooms or imaging suites don't wait for a crew to drive three hours. The contractor who wins that work is the one who's already local.
In mission-critical environments, the constraint is continuity. The technician who serviced the UPS system last quarter needs to be the same one who services it this quarter — because they remember the anomaly they flagged, the workaround they documented, the conversation they had with the facility engineer.
Geography is a memory problem as much as a logistics problem. The knowledge of a facility lives in the people who work in it. When those people are far away, the knowledge is far away too.
Building the Geographic Layer
After January 4th, we restructured our approach to federal PM pursuits around three principles:
1. Map Before You Bid. Before responding to any solicitation, map the geographic footprint against our coalition's actual coverage. Where do we have partners? Where are the gaps? Can we close those gaps before proposal submission — or is this a pursuit we should pass on?
2. Qualify Locally. Every coalition partner in a region must be independently qualified — not just technically, but administratively. SAM registration, trade certifications, insurance, bonding. The evaluation team isn't just scoring whether you have people nearby. They're scoring whether those people are contract-ready.
3. Connect the Memory. The coordination system doesn't replace geographic presence — it connects it. When a technician in VISN 6 completes a PM task, that documentation flows into the same operational memory as the technician in VISN 8. Patterns emerge. Standards propagate. The coalition gets smarter with every service call, regardless of where it happens.
The Lesson
I built a system to coordinate work across distances. The federal evaluation process taught me that coordination without presence is theory. Presence without coordination is chaos. The answer is both.
Geography as a constraint is humbling because you can't engineer around it. You can't build an app that makes someone closer to a building. But you can build a coalition that ensures someone qualified is always close — and that what they learn becomes part of the system's permanent memory.
That's the first constraint. Not because it's the hardest to understand — it's the most obvious. But because obvious constraints are the easiest to ignore. And in federal contracting, ignoring geography means you never make the competitive range.
---
This is the first article in our Theory of Constraints series, exploring how physical distance and regional coverage create structural bottlenecks in distributed infrastructure work — and why coalition formation is the only scalable answer.