Field management software

Most of the information on a construction project is not in the model. It is in requests for information, submittals, daily reports, inspection checklists, photos, meeting minutes, punch lists, change events and payment applications. For decades these lived in binders, email threads and spreadsheets. Cloud-based field management platforms now put them in one place, accessible from a phone or tablet on site and from the office. This lesson covers what these platforms do, how the main workflows run, how to measure them and how to roll them out so the field actually uses them. It deliberately avoids comparing products: the major platforms offer similar core functions, and the choice usually depends on integration, cost and the firm's existing systems.

What field management platforms do

A field management platform is a project database with forms, workflows and permissions. Each record type (an RFI, a submittal, an inspection) has fields, a status, an assignee and a history. Users create and update records from the field, attach photos and mark up drawings; the platform routes records to the right people, sends reminders and keeps an audit trail. Most platforms also hold the current drawing set and specifications, synchronized for offline use, so a foreman can open the latest sheet without searching.

Requests for information

An RFI is a formal question from the contractor to the design team when the contract documents are unclear, conflicting or incomplete. CON-120 described what makes a good RFI. A digital RFI workflow adds structure: each RFI has a number, a subject, a question, a suggested solution, references to drawings and specifications, attachments, a due date, a ball-in-court party and a record of the answer and its distribution. Linking RFIs to drawing locations means that anyone opening the sheet sees a pin where an RFI applies.

Contracts often set a response time for RFIs, such as five or ten working days, and the platform's due dates should reflect it. RFI metrics tell the project manager whether questions are being answered fast enough to keep work moving. The following script computes turnaround statistics from simulated RFI data.

import random, statistics

random.seed(42)
rfis = []
for n in range(1, 121):
    discipline = random.choice(["Arch", "Struct", "Mech", "Elec"])
    base = {"Arch": 6, "Struct": 5, "Mech": 9, "Elec": 7}[discipline]
    days = max(1, round(random.gauss(base, 3)))      # working days to answer
    rfis.append((n, discipline, days))

all_days = [d for _, _, d in rfis]
print(f"RFIs: {len(rfis)}  mean {statistics.mean(all_days):.1f} d  median {statistics.median(all_days)} d")
late = sum(d > 7 for d in all_days)
print(f"Answered after the 7-day contract time: {late} ({late / len(rfis):.0%})")
for disc in ["Arch", "Struct", "Mech", "Elec"]:
    d = [x for _, k, x in rfis if k == disc]
    print(f"{disc:6s} n={len(d):3d} mean={statistics.mean(d):4.1f} max={max(d):2d}")

RFIs: 120  mean 6.2 d  median 6.0 d
Answered after the 7-day contract time: 39 (32%)
Arch   n= 35 mean= 5.7 max=12
Struct n= 41 mean= 4.4 max=10
Mech   n= 21 mean= 9.6 max=15
Elec   n= 23 mean= 6.9 max=12

Reports like this show where the bottleneck is. Here the mechanical engineer is slowest on average, which may justify a conversation about staffing or about sending fewer, better-written RFIs. Averages hide outliers, so the oldest open RFIs should also be reviewed individually at each project meeting.

Submittals

Submittals (shop drawings, product data, samples, mock-ups and test reports) show how the contractor and trades intend to meet the design. A submittal register lists every required submittal, usually extracted from the specifications, with its specification section, responsible trade, required review time and the date it is needed on site. Working backward from the need date, the register sets the date each submittal must be submitted, which links submittals to procurement and the schedule.

Digital submittal workflows route packages to reviewers in sequence or in parallel, track the ball in court, record review stamps (such as reviewed, reviewed as noted, revise and resubmit, rejected) and link approved submittals to the procurement log and to the model elements they represent. Approved product data later become part of the handover package.

Daily logs and site records

The daily log is the project's diary: weather, workforce by trade, equipment on site, work performed, deliveries, inspections, visitors, safety observations, delays and instructions received. Digital logs are faster to complete, can pull weather automatically, can be compared across days and are easy to search when a dispute arises months later. Photos attached to the log, with time stamps and locations, are powerful evidence of conditions and progress.

Daily logs only help if they are complete and objective. A log that says "good day, work progressing" is useless in a claim. A log that records "Electrical crew of 6 stood down 10:00–13:30 waiting for ceiling grid to be released in zone C; foreman notified GC superintendent at 10:05" is valuable. Training superintendents and foremen in what to record is as important as the software.

Records also matter for payment and liens. State prompt-payment statutes and mechanics' lien laws set timelines and notice requirements that vary widely from state to state, and federal projects are governed by the Prompt Payment Act and Miller Act. Accurate, time-stamped records of work in place and of notices given help contractors get paid and defend their position.

Inspections, quality and safety

Inspection and test plans become digital checklists: before a slab pour, the foreman confirms formwork, reinforcing, embeds, sleeves and cover, attaches photos and gets the engineer's sign-off; before ceilings close, each trade confirms its above-ceiling work and inspection. Deficiencies found are logged with a location pin, photo, responsible trade and due date. Quality metrics such as first-time pass rate and open deficiencies by trade show where problems are recurring.

Safety modules handle hazard assessments, toolbox talks, observations, near misses and incident reports. HSE courses cover the content of these programs; the digital point is that forms are completed on site, routed automatically and analyzed for trends, and that workers can report hazards quickly from a phone. Lesson 9 shows how safety data feed dashboards.

Punch lists and closeout

Near completion, the architect, owner and contractor walk the building and record deficiencies on a punch list (also called a deficiency list). Digital punch lists pin each item to a location on a drawing, attach photos, assign the responsible trade and track closure with before-and-after photos. Because each trade sees only its own items on a phone, items get closed faster. Closeout also includes collecting warranties, operation and maintenance manuals, as-built information, attic stock and training records, which the platform can track as a checklist.

Asset data for handover (Lesson 3) are best captured as equipment is installed and commissioned rather than at the end. A field engineer scanning a QR code or barcode on a newly installed pump can record its serial number, installation date and photo of the nameplate in seconds, linked to the model element. By substantial completion, the asset register is largely complete.

Integration and data flow

Field platforms create the most value when they connect to other systems. Common integrations include the accounting system (commitments, change orders and payment applications), the scheduling tool (activities linked to inspections and RFIs), the document platform or CDE (drawings and models), and the owner's systems at handover. Without integration, staff re-type data, and the systems drift apart. Before selecting a platform, a contractor should map which data flow where, and test the integrations on a pilot project.

Data ownership and export also matter. The contract should state that project records belong to the parties who need them and can be exported in usable formats at the end of the project; a platform subscription that ends with the project should not take the record with it. Lesson 11 returns to these questions.

Rolling out a field platform

Field adoption follows the principles in Lesson 1. Start with a few modules that solve real pain, such as drawings, RFIs and daily logs; make them mandatory and retire the old process; train in short, practical sessions on site; give foremen devices that work with gloves, in sunlight and offline; and review usage weekly. Trades must be included: if subcontractors cannot access the platform, they will keep using email, and the record will be split.