When a construction workflow system is called "useless", the complaint usually describes a symptom rather than the fault. Site engineers still message progress to the office. Approvals sit with one manager who is travelling. The cost report disagrees with the site sheet. Replacing the software rarely fixes any of this.
This guide works through the problems that appear after go-live. Each one separates likely causes from the fix, then adds a prevention step. Start with the diagnostic sequence before choosing a symptom.
Diagnose before you replace
- Walk the actual workflow. Follow one work order from site instruction to payment, including the paper and chat around the system.
- Find where data first enters. If entry happens at head office from a photo of a paper form, the system is a reporting tool.
- Compare adoption by role. A project manager may love the dashboard while foremen avoid the app. Average usage hides it.
- Test on the device and network used on site. A form that takes two minutes on office Wi-Fi can take ten on a phone with poor signal.
- Check master data. Projects, cost codes, suppliers and item names must match across procurement, stores and accounts.
- Review approval rules and notifications. Find out who approves, what happens when they are unavailable, and whether reminders reach anyone.
- Compare report definitions. Two reports can disagree because they measure different dates, statuses or cost bases, not because data is wrong.
Problem 1: site staff bypass the system
Likely causes. The daily form asks for information the engineer does not have. Login needs a password reset every few weeks. The app needs a connection in a basement or on a remote plot. The supervisor still asks for a WhatsApp summary. The form duplicates a paper register an auditor requires.
Fix. Keep only the fields the business uses daily; the office can fill the rest. Enable offline capture with a visible sync status and prefill project, date, shift and crew. Make the system the only place the supervisor checks progress and stop accepting the WhatsApp duplicate as an official record.
Prevention. Pilot each form with two foremen. Set an adoption measure per site, not per company, and review it in the weekly site meeting. Remove any field never used in a report or decision.
Problem 2: progress data is days out of date
Likely causes. Entry happens at head office from paper sheets. The site team saves a draft and waits for approval, so nothing appears until the manager returns. Reminders go to an unowned group mailbox. Month-end reporting encourages weekly bulk entry.
Fix. Move first entry to the person who sees the work. Set a daily cut-off, lock the previous day, and keep an exception route for late changes. Give the project manager a list of missing sites instead of a reminder to everyone. Add photo evidence only where it settles a dispute.
Prevention. Put completeness on the daily stand-up agenda and publish a weekly ranking by site. Revisit the cut-off after month one; 6 p.m. may not survive a site that finishes at 8 p.m.
Problem 3: approvals stall
Likely causes. One person approves every value band. There is no delegation when the approver is on leave. Thresholds are unclear, so requests go to the wrong person. Notifications arrive by email while the approver works from a phone, and the screen hides supporting documents.
Fix. Define bands by value and type, with a named delegate for each. Add an escalation timer and a visible queue. Allow approval from a phone with the key documents attached. Record the decision and the reason, not just the click.
Prevention. Test the delegation path before leave. Review cycle time monthly and investigate the slowest step. If a band is always escalated, the threshold or the approver is wrong.
Problem 4: drawing revisions conflict
Likely causes. Drawings arrive through chat groups and personal email. File names use dates rather than revision codes. There is no transmittal record showing who received which version. Printed copies remain on site after a revision, and nobody acknowledges receipt.
Fix. Create a controlled document register with a revision code, issue date, status and recipients. Send revisions through a transmittal that requires acknowledgement. Mark superseded copies clearly and collect or stamp the printed copies on site. Link the current drawing to the relevant work order.
Prevention. Adopt the information-management principles in ISO 19650: a common naming convention, a defined exchange process and a single distribution point. Audit a sample of work orders each month against the register.
Problem 5: duplicate entry across site, procurement and accounts
Likely causes. Each department uses its own identifier for the same project or purchase order. A spreadsheet bridges two systems because the integration was never built. The integration exists but has no error queue, so failed records are retyped. Supplier names differ by spelling.
Fix. Agree canonical project, supplier and purchase-order identifiers, then map every system to them. Integrate the highest-volume handoff first, with an idempotency key and a reconciliation report. Publish a weekly list of records that failed to sync and assign an owner.
Prevention. Treat the integration as a service with an owner and a support path. Review unmatched records monthly. Do not let a spreadsheet become the unofficial bridge; build reports from source data.
Problem 6: cost reports do not match the budget
Likely causes. Cost codes are chosen after the expense is incurred. Commitments such as purchase orders and subcontracts are not captured, so the budget looks healthier than it is. Variations are agreed on site but entered weeks later. Labour hours are keyed in bulk and allocated by guesswork.
Fix. Require a cost code at requisition and before a commitment is issued. Record commitments and actuals in the same system, clearly separated. Maintain a variation register with approval status. Set a weekly cut-off for labour and plant hours, and reconcile payroll to the project allocation.
Prevention. Hold a monthly cost review with site, procurement and finance using one set of definitions. Track unallocated costs and the age of unapproved variations; both predict a surprise at project close.
The prevention routine
Once the immediate problems are fixed, review the workflow monthly: where data enters, which steps are duplicated, which reports are trusted and which forms have grown longer than the job they record. Give new site staff a short induction and pair them with an experienced user for the first week. Agree severity definitions with the vendor so a broken approval chain is not treated as a routine question.
Construction workflow tools sit within Business Automation. The pricing page explains how process review, configuration and support are scoped. For reporting discipline, read the guide to business KPI dashboards.
Sources
- ISO 19650-1:2018, Information management using BIM — concepts and principles, accessed 17 November 2026.
- UK BIM Framework, guidance and standards, accessed 17 November 2026.
- FIDIC, international construction contracts, accessed 17 November 2026.
- ISO 9001:2015, Quality management systems — requirements, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.