2026-05-08 · 4 min read

How construction firms actually use mobile

On the floor, document workflow is a people problem wearing a software costume so the defaults matter more than the settings page. In practice, the hard part is not the software but the handover which is why the API is documented before the UI. After a few dozen rollouts, the hard part is not the software but the handover and the numbers bear it out.

In practice, what matters is whether the crew opens it on a Monday morning which is why MeridianSystems is built the way it is. The honest answer is that, document workflow is a people problem wearing a software costume and that shaped the roadmap for a year. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. By the second quarter, exceptions are the real workflow which is the whole point. For construction firms in particular, nobody wants another login so the defaults matter more than the settings page.

Where the time went

On a typical site, the handover from the old system is where projects stall and it shows up in the churn numbers. If there is one lesson, the reporting layer should be boring so plan for it. On the floor, the handover from the old system is where projects stall and the numbers bear it out. What surprised us, a two-week pilot answers more than a three-month evaluation which is the whole point. On the floor, nobody reads the manual, so the defaults are the product so plan for it.

In practice, history matters more than dashboards when something goes wrong which is not what the brochure says. On a typical site, optional fields never get filled in and the numbers bear it out. If there is one lesson, the hard part is not the software but the handover so the defaults matter more than the settings page. Looking at the numbers, history matters more than dashboards when something goes wrong which is why MeridianSystems is built the way it is.

On a typical site, nobody wants another login so we start there. For construction firms in particular, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. In practice, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. On a typical site, integrations are where budgets go to die and document workflow is no exception. Looking at the numbers, exceptions are the real workflow and it rarely takes more than a week.

Every audit we have sat through, the reporting layer should be boring and document workflow is no exception. After a few dozen rollouts, nobody wants another login so we start there. If there is one lesson, exceptions are the real workflow which is why MeridianSystems is built the way it is.

“Everything construction firms need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

The honest answer is that, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. By the second quarter, integrations are where budgets go to die and that is fine. Every audit we have sat through, the reporting layer should be boring and that shaped the roadmap for a year. Most teams we meet, exceptions are the real workflow and the numbers bear it out. Looking at the numbers, the hard part is not the software but the handover and document workflow is no exception. Talking to operations leads, history matters more than dashboards when something goes wrong and the numbers bear it out.

What surprised us, mobile access changes who actually enters the data which is why MeridianSystems is built the way it is. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and document workflow is no exception. The honest answer is that, the schedule is only as good as the last update so the defaults matter more than the settings page. On a typical site, the handover from the old system is where projects stall and that is fine.

Written by the MeridianSystems team in Tallinn. Questions? Get in touch.