Illustration of a construction worker in a hard hat and safety vest recoiling from a desk monitor whose screen has become a red-eyed, jagged-toothed face with claws reaching out, a progress bar stalled beneath it

Guides

Your in-house construction software works. Will it scale?

Seven questions for contractors managing RFIs, submittals, and project records in a system they built themselves.

Written by Vinay Nair
on

“We have our own system.”

We hear that from contractors, and we understand why. Someone knew the business, saw a problem, and built a tool around the way the team had already worked. The forms were familiar, and if something needed to change, the team could handle it in-house. At the time, there may have been little reason to invest in a platform built for a much larger company.

Building your own construction project management software is an achievement. The harder part is keeping it reliable as your projects, people, and requirements change.

AI coding tools have also made it much easier to get an application off the ground. But once that application is carrying live RFIs, submittal approvals, and project correspondence, it becomes part of the infrastructure your business depends on.

Before you fund the next round of development, check what is holding the system up today. An in-house system can be a sound choice. The seven questions below show where it usually breaks, and where it does not.

1. Is one person carrying the whole load?

Every contractor understands the risk of having critical project knowledge sitting in one person’s head. The same risk applies to software.

Your system may have been built by a technically minded PM, an estimator who knows Power Apps, or an outside developer who understands your processes. That can work very well until that person is unavailable, and something stops working.

Maybe an RFI stops reaching its reviewer. A permission change locks out a superintendent. An automation fails while the person who built it is tied up with a tender deadline.

Who takes over?

Own your admin accounts. Document the workflows. Keep access to the code. And have a second person who can diagnose a failure when the builder is unavailable. Name one person who owns testing, updates, and recovery.

Buying a platform moves most maintenance to the vendor. It does not move the questions. Ask how support is staffed, how issues escalate, and what happens during an outage. Your team should know who to call before a live job depends on the answer.

2. Does your RFI and submittal software close the loop, or just collect the form?

Creating an RFI form is relatively straightforward. Managing everything that happens after someone submits it takes more structure.

Take a mechanical contractor whose duct run clashes with a structural beam. The RFI needs the right drawing reference, a clear description, supporting photos, and a required response date. The GC coordinates the review, the designer responds, and the relevant trades need to receive the answer.

If the answer changes scope, cost, or sequence, a second round of approvals starts. A design response and commercial approval are not the same thing.

Submittals have similar dependencies. A reviewed equipment submission still needs to reach the supplier and the site team. An approved submittal does not mean the equipment is ordered, shipped, or delivered.

Those handoffs are what a construction system has to manage.

In smrtGC, RFIs, changes, and submittals have owners, due dates, and live status. The Critical Completion Monitor brings overdue items into view across active projects. smrtSUB gives trade contractors their own records and tracking across the projects they are delivering.

A good way to test your current system is to select a revised submittal or an RFI that led to extra work. Can another PM follow the question, response, distribution, and outstanding actions without having to rebuild the story from email?

That is what closing the loop should look like.

3. Does your system work for the field, or only the office?

The office may have a complete process mapped out. The field still has to use it while coordinating crews, checking drawings, receiving deliveries, and keeping the job moving.

If field reporting takes too long, the foreman may send a text instead. If attaching photos is awkward, the photos may stay on someone’s phone. Someone in the office must turn those messages into a formal project record.

The system still gets updated, but only because another person is filling in the gaps.

Off-the-shelf tools have this problem too. In FMI and PlanGrid’s 2018 Construction Disconnected survey of 599 construction leaders, 36% of respondents cited poor fit with existing work processes as a reason technology fell short of expectations, and 25% cited low adoption.

When you evaluate a system, bring field leaders into the process. Ask them to report a real issue using the device they normally carry. See how long it takes, what information gets missed, and whether they need help to complete the process.

We built smrt-E around that handoff. It uses voice capture for daily logs, RFIs, and safety reports, along with photos and offline capture. A field-generated RFI can then go through PM review before being routed to the architect.

The goal is simple: capture useful information while it is still fresh and keep the field and office working from the same record.

4. How much administrative rework sits outside the system?

Contractors spot physical rework fast. Admin rework hides in small tasks spread across the week.

A coordinator copies an approval into the submittal register. A PM searches through email for the latest response. Someone rebuilds the status report before the progress meeting.

No single task looks big. Together they eat hours every week.

In the same 2018 survey, respondents spent an average of 5.5 hours a week looking for project data. That historical finding does not tell you what your company is losing today or how much new software would save. It does show why information handling is worth measuring.

You can start by looking at your own workload. Our True Construction Software Cost Calculator compares subscription costs, administrative time, and switching costs over three years.

Before you use it, track the time your team spends on workarounds for two weeks. Then enter your current subscription costs, your weekly admin hours, and the cost of the alternative.

  • Your current platform: Enter your existing subscription costs and mark the modules your team actually uses. If your internal system has no subscription cost, enter zero.
  • Hidden admin time: Enter the weekly hours your company spends on tasks such as chasing subcontractor documents, re-keying change orders, or typing field reports after hours. Use your blended hourly employment cost and working weeks per year.
  • The alternative: Enter the proposed subscription, migration, integration, and training costs. Then use a conservative estimate for the percentage of administrative time you expect to recover.

For example, if three PMs each spend two hours a week chasing subcontractor documents, that adds up to six hours a week. At a blended cost of US$65 per hour over 50 working weeks, that represents US$19,500 a year in staff time.

Recovering some of that time creates more capacity for the team. It does not automatically mean payroll goes down.

The calculator covers subscriptions and selected administrative tasks. You should still keep a separate allowance for hosting, internal development, maintenance, and technical support on both sides of the comparison, without counting the same costs twice.

Both approaches have ongoing costs. Ask what your company gets back for them.

5. Are your systems connected, or held together by workarounds?

Construction information moves across a lot of boundaries: field to office, contractor to consultant, procurement to delivery, and operations to accounting.

An internal application may handle one part of that process very well while leaving the handoffs to spreadsheets, exports, and someone’s memory.

The same survey found that 22% of respondents cited poor integration with existing technology and software.

For every important connection, make sure you understand what information moves, in which direction, who checks it, and what happens when something fails.

We connect project workflows with Microsoft 365, so email and supporting documents stay with the project record. The wider platform can also be extended through modules for drawings, job costing, crew time, HR, and bidding. That can bring more of the work into one environment, but the implementation still matters.

Your accounting system, for example, may remain the right place for financial information. The important thing is to confirm what the connection actually does. Is it an export or a live integration? Which edition does it support? Who maintains it?

Two systems on the same software list are not necessarily connected. Test the handoff your team actually needs.

6. Who is responsible for security and recovery?

A working screen tells you that an application can perform a task. It tells you much less about permissions, security updates, or recovery.

AI-generated apps share that blind spot: a screen that works tells you nothing about permissions, updates, or recovery. What matters is who is responsible for checking the system before important project information depends on it.

Can a subcontractor see only the jobs and records they should have access to? What happens when an employee leaves? Who tests changes, updates dependencies, and investigates a security issue?

You should ask the same questions of a commercial provider, including SMARTBUILD. Ask for documented responsibilities and evidence of the controls that matter to your business.

7. Will the record hold up at closeout?

A project system still needs to be useful after the immediate task is finished.

A question about an equipment substitution may come up months later. A change may be challenged during pay application review. A back-charge may require a subcontractor to show what happened on site and when.

A useful project record should bring the relevant correspondence, photos, revisions, instructions, and approvals together in one place.

For a GC, that helps with coordination across the owner, consultants, suppliers, and trades. For a subcontractor, it means maintaining an independent record of its work and commercial position alongside the information held in the GC’s system.

That distinction is central to smrtSUB, our construction management software for subcontractors, which keeps RFIs, changes, daily reports, and payment-supporting documentation in the subcontractor’s own project record.

A project record needs to be more than a shared folder. People should be able to identify the current information, understand its status, and retrieve the history behind it.

Backups and exports matter too. Can you restore a project and hand over a usable record, including attachments and revisions?

Closeout is not the time to discover that important information cannot leave the system.

What if your in-house system already has a solid foundation?

Then keep building on what works.

A well-supported internal system with reliable workflows and strong adoption may continue to serve the company well. The gap may be much narrower. Maybe daily reports still come in late, field information is incomplete, or someone spends hours turning voice messages into formal records.

That is where smrt-E may fit without requiring a full platform replacement. It is available as a standalone product, with published connections to smrtGC, smrtSUB, Procore, and Autodesk. If your system is custom-built, we would check compatibility first.

Start with the handoff you want to improve. Look at where the information is captured, who reviews it, and where the final record needs to live.

Build the business case around the work

A system built to scale should help your team manage more work without requiring the same increase in chasing, duplicate entry, and software maintenance. Whether you keep building or buy project management software for construction, hold both options to the same test.

Kaiser Martin Group reports 50% less paperwork, while GEN-PRO reports its PMs managing five projects each, up from three.

Your business case should be based on your own project volume, administrative hours, and support costs. Include the effort required to switch and compare both options against the same real workflows.

At SMARTBUILD, we connect the people managing the job with the information they need to keep it moving, including RFIs, submittals, changes, drawings, field documentation, and the records that support payment.

Bring us one workflow that takes more effort than it should. We will map it with you and show where smrtGC, smrtSUB, or smrt-E would take work off your team. Book a 30-minute workflow review.

See SMARTBUILD on your own project