M&E subcontractor software: what you actually need in 2026

Most construction software is built for main contractors. It's expensive. It's complicated. It assumes you've got a full-time IT person and a head office with reliable Wi-Fi.

If you're an M&E subcontractor running two or three jobs with 15 to 40 lads on each, that's not your world. Your world is site cabins, 4G signal, and a QS who does three other jobs as well.

The M&E subcontractor problem

You're caught between two pressures. The main contractor wants digital records, programme updates, and compliance paperwork. Your lads on site want to install kit and go home.

So you end up bodging it. WhatsApp for photos. Excel for trackers. Paper diaries that sit in a drawer until someone needs them for a dispute. None of it talks to each other. None of it is searchable.

When a payment dispute lands, you spend three days pulling evidence from five different places. Half the photos have no dates. The diaries have gaps. Your QS is reconstructing timelines from memory. You've been there. I've been there.

What M&E subcontractors actually need

You don't need a platform with 200 features. You need five or six things that work properly on a building site.

• Site diary that your engineers will actually use. Three taps. Photo first. GPS-stamped.
• Progress tracking tied to your activity schedule. Not the main contractor's programme. Yours.
• Payment application support. Cumulative records that match your valuation.
• Early warning and compensation event tracking. With timestamps and notification dates you can prove.
• Document storage that's searchable. Not a shared drive with 400 folders nobody maintains.

That's the list. Everything else is nice to have.

What main contractor software gets wrong

Main contractor platforms like Asite, Viewpoint, or Fieldwire are built around their workflow, not yours. They want you to upload data into their system so they can manage you. That's fine for them. It's a problem for you.

You don't own that data. When the job finishes, your access gets switched off. If a dispute comes up two years later, you're asking the main contractor for access to your own records. Good luck with that.

The other problem is cost. Most main contractor software charges per user. You've got 30 people on site. At ten or fifteen quid per user per month, that's real money. So you buy three licences and only your PM and QS use it. The engineers on the tools never log in. The records don't get made.

The data you need to protect yourself

M&E subcontractors lose money in disputes because they can't prove what happened and when. Not because they did bad work. Because the records weren't there.

You need three types of data, captured at the time the work happens:

1. Daily site records. What was installed, where, by whom, with photos. Every day. No gaps.
2. Notification records. Every early warning, every compensation event, every payment notice. With the date it was sent and the date it was received.
3. Correspondence trail. Every RFI, every instruction, every site direction. Logged with a timestamp you can prove.

If you've got those three things in one searchable system, you can build an adjudication case in hours, not weeks. If you don't, you're relying on your QS's memory and a box of paper.

What to look for in M&E software

Forget the sales demo. They all look good in a demo. Ask these questions instead:

• Does it work offline? Your lads are in risers and ceiling voids with no signal. If the app needs constant internet, they won't use it.
• Is pricing per project or per user? Per user kills adoption. You need unlimited users at a flat rate.
• Can you export everything? PDF reports, CSV data, photo archives. If you can't get your data out, it's not your data.
• Does it understand NEC4? Most generic construction apps don't know what a compensation event is. You need software built around the contract you actually work under.
• Can your least tech-savvy engineer use it? Put it in front of him. Give him ten minutes. If he can't log a record, the app has failed.

Trial it on a real project for 30 days. Not a sandbox. A real job with real lads and a real programme. That's the only test that matters.