IT for Construction: Sites That Move, Connectivity That Doesn't Exist Yet

Construction has an IT problem shaped unlike any office business. The work happens at locations with no infrastructure, those locations exist for months and then disappear, and the people on them need current drawings and the ability to record what they are doing — frequently with no usable signal.

Office IT practices do not transfer. These are the patterns that hold up.

Site connectivity

A new site starts with nothing. What is practical, roughly in order of how often it is the right answer:

Cellular routers with external antennas. Deployable same-day, no installation lead time, and an external antenna on a mast makes a substantial difference to a marginal signal. The default starting point for most sites.

Multi-carrier failover. Site coverage varies by carrier in ways that are hard to predict. A router accepting two SIMs from different carriers is far more reliable than betting on one.

Satellite where terrestrial coverage genuinely does not exist. Low-earth-orbit services have made this viable for remote sites in a way it was not a few years ago.

Fixed line only for long-duration projects where the lead time is tolerable. On a nine-month project, a circuit taking twelve weeks is not useful.

Specify the kit as a standard site pack: router, antenna, switch, access point, UPS, all in a rugged case, pre-configured and ready to deploy. A site should be an unpacking exercise, not a design exercise.

Design for no connectivity

Even with the above, there will be no signal in the basement, in the lift shaft, in the plant room and on the far side of the structure. Any application the site team relies on must work offline and sync later.

This is the single most important selection criterion for field software, and it is routinely overlooked in favour of features. An inspection app that requires connectivity will be used on paper and typed up in the evening — which is where data is lost and timesheets become fiction.

Check specifically: does it work with no signal, does it queue reliably, and what happens when two people edited the same record offline?

Devices that survive the environment

Standard laptops and tablets do not last on a construction site. What works:

• Rugged or semi-rugged tablets for site use, with screens readable in sunlight and usable with gloves
• Screen protectors and cases as standard, not optional
• Spares on site. A broken device stops a person working, and a courier takes a day
• Charging infrastructure in the site office — vehicle chargers and power banks for people in the field

Budget for shorter device life than in an office. It is a cost of the environment, not a failure of procurement.

Drawings and version control

The highest-consequence IT risk in construction is someone building from a superseded drawing.

The requirements:

• One source of truth, with clear version indication
• Superseded versions visibly marked, not just removed
• Offline access to the current set, which conflicts with the first point and must be handled by the application through sync and a clear "last updated" indication
• Change notification that reaches people in the field, not just an email to the office

This is a document management problem with safety and cost consequences, and it deserves more attention than the hardware.

Photographs and records

Site photography has become a primary record: progress, defects, conditions at a point in time, evidence for variations and disputes.

That means:

• Automatic sync from devices to central storage, so records are not held on one person's phone
• Organised by project and date, automatically — manual filing does not happen
• Retained for the limitation period applicable to construction disputes in your jurisdiction, which is typically years after completion
• Backed up, because this is evidence

A dispute three years after handover is won or lost on records. Storage is cheap relative to that.

Subcontractors

A large proportion of people on site do not work for you, and they need some access to your systems — drawings, induction, permits, timesheets.

• Separate access from your staff identity, with its own lifecycle
• Time-limited to the engagement, with an actual expiry
• Scoped to the project, not the whole estate
• A defined offboarding when a subcontract ends — including collecting devices and revoking access

Subcontractor access that outlives the engagement is one of the most common findings in a construction business access review.

The site office

Each site office needs enough to function and nothing worth stealing:

• no local servers, no local data
• everything cloud-based and accessible from anywhere
• printing for drawings, which is still required
• a phone solution that works on the available connection, with cellular fallback
• physical security for equipment, which on a site is a real consideration

Decommissioning a site

The step that is always rushed, because the project is finishing and everyone has moved on:

• recover equipment, and check it back into the standard site pack
• confirm all data has synced before devices are wiped
• revoke site-specific access and subcontractor accounts
• cancel the connectivity service — recurring charges for closed sites are common and quietly expensive
• archive project records to their retention location

A checklist for this, applied every time, prevents both the lingering costs and the lost records.

The organising idea

Treat sites as deployable units: a standard pack, a standard configuration, a standard setup procedure, a standard decommission. The variation between projects is in the construction, not in the IT.

The businesses that struggle are the ones where each site is improvised by whoever is available — which means every site is slightly different, nothing is documented, and the knowledge leaves with the project team.