Every superintendent I know has, at some point, entered the same labor hours into three different systems in one week. Once into the field app, once into a payroll spreadsheet the office demanded, and once into a cost report because the first two didn't talk to each other. That is the problem integration is supposed to solve, and it's why "does it integrate?" has become one of the first questions asked when a company shops for field management software.
But "does it integrate" is the wrong question. Almost everything integrates with almost everything now, at least on the sales slide. The real questions are: which connections actually save you work, how much do they cost to stand up and maintain, and what breaks when the sync fails at 6 a.m. on a Monday. This article walks through the integrations that matter on a real jobsite, in rough order of payback, and where the wheels tend to come off.
Start With the Integration That Kills Double Entry
The highest-value connection is almost always the one that stops somebody from typing the same number twice. On most jobs that's the link between field-captured labor and the office cost and payroll systems.
Here's the failure mode to avoid: your foremen record hours in the field app, and a bookkeeper re-keys them into your accounting package every Friday. Two things go wrong. First, transposition errors — a 40 becomes a 4.0, and a cost code blows its budget on paper. Second, timing — the office is always a week behind the field, so your job-cost reports describe a project that no longer exists. By the time a code shows overrun, the crew has moved on.
A clean accounting integration pushes hours, equipment usage, and cost-code allocations straight from the field into the accounting system. When you evaluate one, don't just confirm it "connects." Ask the specific questions:
- Does it map to your cost codes, or does it force a generic code structure you'll have to translate anyway?
- What happens to a timecard that's already been posted to payroll and then gets corrected? (Reopened periods are where sync tools quietly create duplicates.)
- Is the sync one-way or two-way, and if two-way, which system wins a conflict?
Get those three answered and you've learned more than any feature list will tell you.
Scheduling: Where the Look-Ahead Meets the Master
Most commercial jobs run on two schedules whether anyone admits it or not. There's the CPM master schedule — the Primavera or Microsoft Project file the scheduler updates monthly for the owner — and there's the short-interval plan the field actually works to. The master tells you the milestone dates. The weekly work plan tells your plumber which units he's roughing in Tuesday.
The dream is that these two stay in lockstep automatically. In practice, a full two-way sync between a CPM tool and a look-ahead tool is more trouble than it's worth for most contractors. The two schedules are built at different resolutions and updated on different clocks, and forcing every look-ahead tweak back up into the master creates noise the scheduler doesn't want. What you actually need is a controlled flow: milestone and activity dates roll down from the master into your look-ahead schedule so the field plan stays anchored to contractual dates, and progress rolls back up as clean percent-complete, not as a hundred micro-edits.
This is the honest case for good short-interval scheduling software, LookAheadWall included: it lives in the gap between the master schedule and the crew, letting the field plan the next three to six weeks in real detail — by location, by trade flow — without fighting the CPM tool. The integration you want there is a sane import of the master's dates and an export of progress, not a fragile real-time marriage that breaks every time someone re-baselines.
A practical rule: if an integration requires your CPM scheduler and your field to update on the same cadence, it will fail, because they never do. Design the connection around the fact that the master moves monthly and the look-ahead moves weekly.
Drawings and Documents in the Field
The document integration that pays off isn't glamorous — it's making sure the crew is looking at the current drawing. Superintendents have all lived the nightmare: a wall built to a superseded revision because the printed set in the gang box was two ASIs old. Tearing that out costs more than any software license.
Connecting field management software to your document or drawing management system means the current set is available on the phone or tablet, and — this is the part that matters — old revisions get pulled or clearly flagged when a new one lands. When you assess this, test the revision-control behavior specifically. Load a set, push a revision, and see what the field user sees. If the superseded sheet is still openable without a giant warning, that's a hole.
The RFI and submittal side is the other half. A field-generated RFI that automatically lands in the office document workflow — with the location, the sheet reference, and a photo attached — closes the loop between "the guys have a question in the field" and "somebody's tracking it." Without that link, questions get texted to a PM who forgets, and the crew works around the problem instead of resolving it.
ERP and the Enterprise Data Question
If your company runs a full ERP — Viewpoint, Sage, CMiC, and the like — the field software integration is a bigger, more political project than any of the above. ERP holds the master employee records, the job budgets, the AP, the equipment ledger. Field data feeding into it touches finance, and finance systems don't forgive sloppy imports.
Two honest truths here. First, ERP integrations are almost always deeper and more brittle than the marketplace connectors for smaller tools, precisely because they touch money. Budget real implementation time — mapping cost structures, testing in a sandbox, running parallel for a pay period before you trust it. Second, the quality of an ERP integration depends far more on the specific ERP and version than on the field tool's brochure. "We integrate with Sage" can mean a certified, supported bi-directional connector or a nightly CSV export somebody wrote once. Ask which, and ask who supports it when it breaks.
BIM, Equipment, and Safety: Nice, But Know Why
A few integrations get a lot of marketing air and less field payoff. Judge them on whether they solve a problem you actually have.
BIM / 4D: Linking the schedule to the model so planned work shows up visually is genuinely useful on complex, congested jobs — think a mechanical room where sequencing is a spatial puzzle, or a hospital with brutal above-ceiling coordination. On a straightforward wood-frame multifamily job, it's overhead you don't need. Buy it when the coordination problem is spatial, not just temporal.
Equipment telematics: If you run owned iron, pulling hours and location from fleet telematics into your cost tracking closes a chronic leak — equipment time that never gets charged to the job. If you rent everything, this integration is mostly noise.
Safety systems: The value is in making safety a planning input, not a separate binder. When your toolbox-talk requirements, permit needs, and hazard flags surface inside the weekly plan — this activity needs a hot-work permit, that one needs fall protection — safety stops being an afterthought. The integration that just files incident reports into a corporate database is compliance, not prevention.
APIs, HR, and Communication Tools
An open API is worth more than any single pre-built connector, because it's your escape hatch. When the vendor doesn't offer the integration you need, a documented API means your IT person or a contractor can build it. When you evaluate software, having an API you can actually reach — with real documentation, not a "contact sales" page — is a signal the vendor expects to live in a connected ecosystem.
HR and payroll connections matter mostly for compliance data: certifications, insurance, and — for subs — current COIs. A connection that flags an expired certification before you assign that worker to a task, or a lapsed sub insurance before they're on site, prevents the kind of problem that stops a job cold. Communication integrations (calendar, messaging) are the lowest-stakes of the bunch — pleasant when a schedule change pings the right channel, but nobody chose their field platform over calendar sync.
What Actually Breaks, and How to Buy Around It
Integrations don't fail dramatically. They fail quietly, and someone finds out three weeks later that the numbers stopped flowing. A few hard-won lessons:
- Sync direction and conflict rules matter more than sync speed. Real-time sounds great, but the question that bites you is "when the field and the office both changed the same record, which one wins?" Get that answer in writing before you buy.
- Every integration is a maintenance liability. When a vendor pushes an update, connectors break. Don't connect systems you don't genuinely need, because each one is something else to babysit.
- Phase it. Stand up the double-entry killer first — usually labor to cost. Prove it for a month. Then add the next connection. A big-bang integration launch across five systems on day one is how you end up trusting nothing.
- Watch the mapping, not the connection. Two systems can be "connected" and still be useless if their cost codes, phase codes, or employee IDs don't line up. The unglamorous mapping work is where integrations succeed or fail.
The goal was never a diagram with a dozen tools wired together. The goal is that a foreman records the day's work once, in the field, and it shows up everywhere it needs to — costed, scheduled, documented — without anyone re-typing it. Chase the integrations that get you closer to that, in order of payback, and be honest about the ones that just look good in a demo. Your field team will feel the difference the first Friday nobody has to key the same hours in twice.