Appendix H — Software and Tools Directory

How to use this appendix

This directory is organized by the problem the tool solves, not by the company that sells it. That is deliberate. Vendors reorganize, acquire each other, rename products, and move into each other's categories constantly — several products named here have changed corporate parents in the last decade — but the problems have been stable for thirty years. Learn the problem and you can evaluate whatever is being sold to you this year.

Three honest statements before the list.

One: you usually do not get to choose. Tool selection is driven far more by what the owner requires, what your company already runs, and what your subcontractors will actually use than by any feature comparison. An owner who runs its capital program on one platform will require your submittals in it. A company with fifteen years of cost history in one accounting system is not switching because you read an article. A drywall subcontractor with nine people in the office will not adopt your platform for its daily reports unless the subcontract requires it and the bid priced it. Evaluate for capability and adoption, not for brand.

Two — and this is the sentence to carry out of this appendix:

A platform does not create discipline. It makes the absence of discipline visible faster.

An RFI log in a platform is not better than an RFI log in a spreadsheet if nobody assigns a ball-in-court and nobody chases the aging report. What the platform gives you is that the aging report generates itself and cannot be quietly not-produced. That is worth a great deal. It is not the same thing as document control, and a contractor who buys a platform believing it is document control has bought an expensive way to be disorganized in public.

Three: there are no prices, version numbers, licence terms, or feature lists in this appendix. They change every year, they depend on your volume and how hard you negotiate, and a number printed in a book would be wrong before the book was read. Get three quotes and use your own numbers. Where you need illustrative cost shapes, Chapter 39 carries them, clearly labelled as illustrative.

H.1 The map: how the categories connect

Most of the value in a construction technology stack is not inside any one tool. It is in the handoffs between them, and the handoffs are where projects lose data, lose money, and lose an afternoon every week to somebody retyping something.

   DESIGN MODEL  ──────────► BIM / VDC  ──────────► FIELD LAYOUT
   (architect,               (federate,             (robotic total station,
    engineers)                clash, LOD)            layout robot)
        │                        │  │
        │                        │  └──────────────► PREFAB / FABRICATION
        ▼                        ▼
   ESTIMATING & TAKEOFF ──► SCHEDULING (CPM) ──► 4D SEQUENCE
        │                        │
        │  budget                │  activities, durations, updates
        ▼                        ▼
   COST ACCOUNTING / ERP ◄── PM PLATFORM ◄──── FIELD: daily reports,
   (job cost, WIP, payroll)     (submittals,          photos, quantities,
        │                        RFIs, drawings,      safety observations
        │                        punch, docs)              ▲
        ▼                            ▲                     │
   PAY APPS, WIP, SURETY             └── REALITY CAPTURE ──┘
                                          TELEMATICS
                                     ┌─────────────────────┐
                                     │  SPREADSHEET        │  ← still where most
                                     │  (every gap above)  │     analysis happens
                                     └─────────────────────┘

Read that table as a shopping list of integration questions. When a vendor says "it integrates," the useful follow-up is "which of these seven handoffs, in which direction, and does it push data or does somebody export a CSV?"

H.2 Scheduling

What the category does. Builds a network of activities with durations and logic, calculates early and late dates, identifies the critical path and float, tracks progress against a baseline, and produces the updates that become the evidentiary record in a delay claim. See Chapter 14 and Chapter 29.

What distinguishes enterprise CPM from a task tracker. This is the distinction that costs people money. An enterprise CPM engine performs a real forward and backward pass, exposes and preserves calculation settings (retained logic versus progress override, calendar handling, constraint treatment), stores layered baselines, keeps an auditable history of updates, and handles resources and multi-project portfolios. A task tracker stores tasks with dates and dependencies and shows them as bars. Both produce a Gantt chart. Only one of them produces a defensible time impact analysis. If your contract requires forensic-grade updates and your tool cannot tell you why the critical path moved between update 14 and update 15, you do not have a scheduling tool.

What to look for. Whether the contract specifies a package by name — many institutional and public contracts do. Whether the calculation options are visible and documented (two people can open the same file and see different critical paths if the settings differ). Whether updates are stored as separate, non-destructive snapshots. Whether it will export in a format your owner's scheduling consultant can read. Whether the field will ever open it — usually no, which is why the next paragraph exists.

How it connects. Durations come out of the estimate's man-hours; progress comes from the field through the PM platform or a look-ahead process; the schedule drives the 4D sequence in the model and the procurement back-schedule in Chapter 16.

Named honestly. Primavera P6 (Oracle) is the enterprise standard on large, public, and institutional work and is frequently specified by name. Microsoft Project is ubiquitous and adequate up to a few hundred activities, with defaults that are genuinely dangerous for construction. Asta Powerproject and Phoenix Project Manager are established CPM alternatives. Deltek Acumen Fuse is used for schedule quality and risk analysis rather than for building the schedule. Cloud and lean planning tools such as Touchplan and vPlanner support pull planning, constraint logs, and percent-plan-complete tracking — the Last Planner System workflow in Chapter 27 — and they are a complement to a CPM, not a replacement for one. For 4D, Synchro (Bentley) and Navisworks (Autodesk) link schedule activities to model objects.

⚠️ The warning that belongs on every scheduling splash screen: the software calculates; it does not think. It will not tell you that a duration is optimistic, that a relationship is a preference dressed as a physical fact, or that the crew you assumed is working on another job.

H.3 Estimating and takeoff

What the category does. Three related jobs that people blur together: measuring quantities off drawings or a model, assembling those quantities into priced items using crews, productivity, and unit costs, and summarizing into a bid with markups, bonds, insurance, and escalation. See Chapter 12 and Chapter 13.

What to look for. For takeoff: calibrated scale that cannot drift, count tools with pattern matching, markups that live visibly on the sheet, automatic re-extension when an assumption changes, and — the single highest-value capability in the category — revision comparison, overlaying two issues of the same sheet and highlighting what changed. For assembly estimating: whether the cost database is yours or somebody else's, whether crews and productivity rates are editable, and whether the output structure maps to your cost codes. For model-based extraction: whether the tool reports the level of development behind a quantity, because quantities pulled from a model that does not support them are precisely wrong, which is far more dangerous than roughly wrong.

How it connects. Takeoff feeds the estimate; the estimate becomes the budget in the cost system and the man-hour basis for schedule durations; the model feeds extraction; published cost data calibrates unit costs you have no history for.

Named honestly. Bluebeam Revu is the common on-screen measurement and markup tool. On-Screen Takeoff (ConstructConnect) is a long-established dedicated takeoff package; PlanSwift and STACK are comparable products. Assemble (Autodesk) and similar tools do model-based quantity extraction, and most modeling platforms will produce element schedules directly. Assembly and unit-price estimating packages include Sage Estimating, and on heavy civil and self-perform work HCSS HeavyBid and B2W Estimate are widely used; trade-specific packages exist for electrical and mechanical. For cost data, RSMeans (published by Gordian) is the most widely used published database in North America, with location adjustment factors, and ENR publishes cost and material indices used for escalation. Treat any published unit cost as a starting point requiring local adjustment — your own completed-project database beats anyone's book.

What none of it changes. Software does not know whether the item is on the sheet, what your assumptions are, where the scope boundary between two packages falls, or whether the units are right. Digital takeoff makes you faster at measuring the drawing you are looking at.

H.4 Project management platforms

What the category does. One place for the project record: drawings and specs (current set, on a device, in the field), submittals, RFIs, daily reports, photographs, punch lists, meeting minutes, correspondence, and increasingly financials. This is the category that has quietly, completely won — which is why nobody talks about it anymore. It is plumbing now.

What to look for. Whether subcontractors can be given access at a cost and a complexity they will actually accept — this is the single biggest determinant of whether a rollout works. Whether the field gets something back from what it enters, or is typing for the office's benefit (that is the "displaced burden," and it is why foremen stop entering quantities in week five). Whether ball-in-court and aging reports are automatic. Whether photos carry a location and a date, because the location tag is what makes them findable, and findable is the whole value. Whether offline access works, and what your written answer is to "what do we do when it is down for a day." Whether data export is genuinely available — you will want the project record in five years, when a claim surfaces and the subscription has lapsed.

How it connects. It is the hub. It takes drawings from document control, feeds progress to the schedule, feeds quantities and hours to cost, and holds the contemporaneous record the claims process in Chapter 33 will live or die on.

Named honestly. Procore and Autodesk Construction Cloud are the two most widely encountered general-contractor platforms; Fieldwire and the category of tools that grew out of the original PlanGrid model serve the field-first end; Newforma is long-established in document and correspondence control; Oracle Aconex is common on large international and infrastructure work; and owner-side program management platforms such as e-Builder and Kahua are what an institutional owner may require you to submit into. Trimble Viewpoint and CMiC bring project management and accounting into one system. Many contractors also run internally built systems, and some of them are excellent.

I am not going to rank these, price them, or tell you which to buy. It depends on your size, your existing systems, your subcontractors, and what your people will actually use — and the market moves.

H.5 BIM and VDC

What the category does. Four distinct jobs, and confusing them is the most common source of disappointment. Authoring creates the model. Federating combines models from many authors into one coordinated whole. Analysis runs clash detection, rule checking, and validation. Exchange moves data between all of the above. See Chapter 35.

What to look for. Whether the tool respects level of development — a model built for spatial coordination says nothing reliable about stud gauge or whether a wall runs to deck. Whether clash results can be grouped, prioritized, and assigned, because a raw clash report of fourteen thousand intersections is noise, not information. Whether a shared origin and coordinate system can be enforced across every author. Whether the tool can read and write IFC — Industry Foundation Classes, the vendor-neutral open format published by buildingSMART for exchanging model data — which is your insurance against being locked into one vendor for the life of a building.

COBie deserves its own sentence, described by function because that is what matters: it is a standardized, spreadsheet-shaped way of handing over asset data — what equipment was installed, where it is, who made it, what its warranty is — so the owner's maintenance system can consume it without somebody retyping four thousand rows. COBie is a data-handover concept and format, not a product, and if your contract requires it, find out at the BIM execution plan stage who populates each field and when, not at closeout.

How it connects. Model → quantity extraction (estimating), → 4D (scheduling), → layout coordinates (field layout), → fabrication (prefab), → asset data (closeout and the owner's facility system).

Named honestly. Authoring: Revit (Autodesk), ArchiCAD (Graphisoft), Tekla Structures (Trimble), and the Bentley modeling family, which is dominant on infrastructure. Federation and clash: Navisworks (Autodesk), Solibri (Nemetschek) for rule-based model checking, Trimble Connect, and Revizto for issue coordination. Open exchange: IFC. Handover: COBie.

H.6 Reality capture

What the category does. Measures what is actually there, as built, instead of what the drawings say should be there. Four techniques with genuinely different accuracy and cost profiles:

What to look for. Who does the registration and processing, which is the part nobody budgets, and who does scan-to-BIM modeling, which is the part that actually costs money. Whether deviation analysis — comparing the point cloud to the model — is supported, because that comparison is where the value is. Whether a named person reviews the output; a scanning program with nobody reading the deviation map is a very expensive archive.

Drones carry a regulatory layer nothing else here does. Operator certification, aircraft registration, airspace authorization, operational limits, and insurance requirements vary by country and have changed repeatedly. Do not take a rule number from any book, including this one — and note that hospitals often have helipads, which makes airspace a live preconstruction issue on exactly the kind of project this book is about. Chapter 39 §39.3.3 lists the requirements by function so you can go find the current version of each.

How it connects. Point clouds feed the model (existing conditions, deviation checks); 360 capture feeds the PM platform's photo record; drone surfaces feed earthwork quantities and the schedule's progress narrative.

Named honestly. Scanning hardware from Leica Geosystems, FARO, and Trimble; processing and registration in Autodesk ReCap, Leica Cyclone, FARO Scene, and Trimble RealWorks. Walkthrough capture from OpenSpace, StructionSite, HoloBuilder, and Matterport. Drone hardware from DJI and Skydio; aerial data processing in DroneDeploy, Propeller, and Pix4D.

H.7 Field layout

What the category does. Puts model coordinates on the deck. Instead of a two-person crew pulling tape from a control line, an instrument takes points directly from the coordinated model and one person marks where it tells them: wall layout, sleeves, hangers, anchors, penetrations, equipment pads.

What to look for. Whether the instrument's field software will read your model format without a conversion step somebody has to remember. Whether control can be re-established quickly after the instrument is bumped or moved, because that is the daily reality. Whether the point file for tomorrow's deck can be produced by the same person who will use it. And — the one that decides everything — whether somebody owns the daily model-to-field handoff by name.

How it connects. Straight out of the coordinated model, and straight into the trades' installation. The value is not speed. It is that the marks agree with the model, so the hangers the mechanical sub installs land where coordination said they would.

Named honestly. Robotic total stations from Trimble, Leica Geosystems, and Topcon, with their field layout software. Automated layout robots that print full wall layout on a slab include Dusty Robotics and HP SitePrint. Machine control on earthmoving equipment — positioning plus a design surface guiding the blade or bucket — is the same idea applied to grading, and it is arguably the most successful automation in the industry.

🏗️ From the field. Kestrel bought a layout instrument and it barely got used for five months. Not because it did not work — because the layout crew reported to the superintendent, the model was owned by VDC, and nobody owned the daily handoff of the layout file. The crew needed tomorrow's file by end of day today; there was no standing time, no named person, no deadline. So they pulled tape, because tape is always available. The fix cost nothing: one named person, a standing weekly deadline, and two lines on the coordination meeting agenda. The technology was never the problem.

H.8 Cost accounting and ERP

What the category does. The system of record for money. Job cost by cost code (committed, actual, forecast), accounts payable and receivable, subcontract and purchase order management, payroll including certified payroll, general ledger, and the work-in-progress schedule your surety and your bank read. See Chapter 28 and Chapter 34.

What to look for. Whether the cost code structure maps to how work is actually organized in the field — if it does not, every field entry is a guess and the foreman knows it, and no platform fixes that. Whether the system produces cost-to-complete, not just cost-to-date, because cost-to-date tells you nothing about whether you are making money. Whether the WIP schedule is generated from the ledger or assembled by hand in a spreadsheet each quarter (a WIP schedule that does not foot is a WIP schedule somebody edited by hand, and that is a finding all by itself). Whether certified payroll for prevailing-wage work is produced natively or requires a separate compliance product. Whether an owner audit under an open-book GMP could actually be supported out of it — see Appendix G, Clause 25.

How it connects. Budget in from the estimate; commitments in from buyout; actuals in from payroll, invoices, and field quantities; pay applications and the WIP out. It is the least glamorous integration in the stack and the one that most reliably eats an accountant's month.

Named honestly. Construction-specific accounting and ERP systems in common use include Sage (the Sage 300 Construction and Real Estate and Sage Intacct Construction families), Trimble Viewpoint, CMiC, Foundation Software, Deltek ComputerEase, and Acumatica's construction edition; several project management platforms now include financial modules that overlap this territory. Subcontractor payment and lien-waiver workflow products such as Textura (Oracle) and GCPay sit between the GC and its subcontractors. Certified-payroll and labor-compliance products such as LCPtracker are common on public work, and many agencies mandate their own submission portal regardless of what you use internally.

H.9 Safety

What the category does. Three jobs. Observation and inspection — structured walks producing findings with a location, a responsible party, a due date, and a photograph. Job hazard analysis — building, issuing, and acknowledging the JHA for a task before it starts. Incident tracking — recording near misses, first aids, recordables, and lost time, with the investigation attached. See Chapter 24.

What to look for. Whether observations can be logged in under a minute on a phone with gloves on and a poor signal, because anything slower does not happen. Whether the system tracks leading indicators — observations made, JHAs reviewed, corrections closed within the day — and not only the lagging incident count, since a tool that only counts injuries measures the thing you are trying to prevent after it happens. Whether near misses are as easy to record as inspections, and whether recording one can ever feel punitive; the scaffold near-miss in this book found three failures, and the third was schedule pressure that nobody wanted to write down. Whether subcontractors can log observations too, on a multi-employer site where the general contractor is very often the controlling employer.

How it connects. Observations belong in the same project record as the daily report; corrections belong in the same look-ahead as the constraint log; incident data belongs with your insurance and prequalification records.

Named honestly. General inspection and observation apps such as SafetyCulture; construction-specific site safety and compliance platforms such as HammerTech; the safety modules inside Procore and Autodesk Construction Cloud; and enterprise EHS systems such as Intelex and Origami Risk for incident, claims, and regulatory tracking at company level.

H.10 Document and drawing markup

What the category does. Opens, marks up, compares, and distributes drawings and specifications — and, more importantly, solves the current-set problem.

The problem it solves, stated plainly. The contract documents have an order of precedence, drawings are revised by addenda and bulletins, and building from a superseded sheet is one of the most expensive routine mistakes in construction. A crew that installs eleven hundred linear feet of partition off a superseded plan has done a week's work that must be undone. When the current set lives on a device that syncs, and the superseded sheet is visibly marked as superseded, that failure mode substantially goes away. That is not a productivity improvement measured in percentages. It is the elimination of a specific, recurring, catastrophic error.

What to look for. Revision comparison — overlaying two issues of a sheet and highlighting the differences — which is the highest-value capability in this category and the one that finds the change nobody told you about. Whether markups are layered and attributable, so an RFI markup by the architect and a field note by your superintendent do not merge into one anonymous scribble. Whether hyperlinked sheet navigation survives export. Whether a set can be published so that old sheets are visibly retired rather than merely replaced.

How it connects. Into the PM platform as the published current set; into estimating as the takeoff surface; into the RFI and submittal record as the marked-up exhibit.

Named honestly. Bluebeam Revu is the dominant markup and comparison tool in North American construction; Adobe Acrobat handles general PDF work; the drawing modules inside Procore and Autodesk Construction Cloud manage set publication and current-set control; Revizto coordinates issues across models and sheets.

H.11 Equipment telematics

What the category does. Modern machines report themselves: engine hours, idle time, fuel burn, location, fault codes, and service intervals. Most equipment built in the last decade has the capability whether or not you use it, and most rental houses will give you access. See Chapter 21.

Why this one works when so much else does not. It removes work rather than adding it — nobody types anything, the machine reports — the data feeds decisions that already exist, and the party that owns the machine is the party that captures the benefit. That alignment, not the elegance of the technology, is why telematics succeeded.

What to look for. Whether you can see a mixed fleet in one place, since a real fleet is four brands plus rentals, and each manufacturer has its own system. Whether the data can be pulled into your own systems through a standard interface — the industry association AEMP developed a telematics data standard for exactly this purpose, since carried into an international standard for worksite data exchange, and asking a vendor whether it supports standardized telematics export is a fair and revealing question. Whether rental machines are included. Whether idle time as a percentage of engine hours is reported, because that is the single most actionable number in the category.

How it connects. Engine hours verify rental invoices and standby claims; actual fuel burn replaces the spec-sheet figure in your equipment budget; utilization across the fleet answers whether you should have rented the fifth excavator or moved the third one; fault codes convert a breakdown that idles a crew of four into scheduled maintenance.

Named honestly. Manufacturer systems including Caterpillar Product Link / VisionLink, John Deere JDLink, Komatsu Komtrax, and Volvo CareTrack, plus third-party mixed-fleet aggregators and the telematics offerings bundled with rental accounts.

H.12 Spreadsheets — treated seriously

I am putting spreadsheets in the same directory as everything above, at the same level of seriousness, because the majority of construction analysis still happens in one. Bid summaries, cash-flow curves, buyout logs, scope comparison sheets, WIP schedules, earned value calculations, quantity reconciliations, change order pricing, cost-to-complete forecasts. Not because contractors are backward. Because the spreadsheet is the only tool in the stack that will hold a shape nobody anticipated, on a Tuesday, in forty minutes.

That flexibility is exactly what makes it dangerous. A purpose-built system will not let you type a number into a cell that used to contain a formula. A spreadsheet will, silently, and it will keep showing you a total that looks completely reasonable.

Spreadsheet discipline

Six rules. They cost about ten minutes each and they are the cheapest risk management in this book.

Why this is not fussiness

More money has been lost on bid day to a spreadsheet error than to a bad unit price. A transposed digit that turns $1,850,000 into $1,580,000 is a $270,000 mistake that no amount of estimating skill will catch, because the number looks fine. On a hard-bid job with a 3% margin, $270,000 is the entire profit on a $9,000,000 contract — and you are contractually bound to build the work at the number you submitted.

The industry has a long history of firms taking losses they could not absorb on bids that contained an arithmetic error rather than a judgment error. Relief is narrow: most U.S. jurisdictions allow withdrawal before award only where the error is clerical or mathematical rather than a judgment call, is material, was noticed promptly in writing, can be proven from contemporaneous documents, and leaves the owner unprejudiced — and the requirements, deadlines, and remedies vary substantially by state and agency. The bid-day controls in Chapter 13 — including reading the final number back digit by digit, out loud, with two people — exist because the alternative is a doctrine you have to hire a lawyer to invoke.

Named honestly. Microsoft Excel is the industry default by an enormous margin; Google Sheets and LibreOffice Calc are real alternatives, and shared-editing behaviour differs between them in ways that matter when four people touch a bid summary on the same afternoon. Power BI and comparable tools are where spreadsheet output goes when it needs to become a recurring report rather than a one-time analysis — and the same discipline applies, because a dashboard built on an unaudited spreadsheet is a faster way to distribute a wrong number.

H.13 Evaluating a tool

Use the framework from Chapter 39. It is five gate questions and four scores, and it takes about an hour per proposal.

The five gates. Any one of them unanswered is a stop, not a discount.

The four scores, 1 to 5 each:

D is a gate, not a score. If you cannot name the person and the decision, kill it regardless of the total. A 17 out of 20 with a D of 1 is a dashboard with good manners.

Who pays versus who benefits is the specifically construction problem, and it is where most technology business cases quietly fall apart. It is the same question as Theme 1 — who owns this risk? — asked about a purchase order instead of a contract clause. Laser scanning: you pay, and the owner gets a free as-built, so charge for the as-built deliverable. Subcontractor platform licences: you pay, the subs get current drawings, so put the obligation in the subcontract and price it in the bid. Machine control: the party that buys it operates it and keeps the production gain — perfectly aligned, which is exactly why it succeeded.

And pilot properly. One scope, one project, one named owner, a fixed window, a pre-registered success criterion in numbers written before the pilot starts, a cost cap, and a kill criterion. An experiment without a pre-registered success criterion is a demonstration, and demonstrations always succeed. That is what is wrong with them.

H.14 What to actually do

If you are a project engineer or a young project manager reading this to decide what to learn, here is the honest ranking.

1. Become genuinely good at spreadsheets — not formulas, discipline. It is the only tool on this list you will use on every job for your entire career, in every company, whatever they buy.
2. Learn to read a CPM schedule properly, whichever package your company runs. The engine matters less than knowing what retained logic does and why the critical path moved.
3. Learn one PM platform well enough to set one up, not just to use one. Setting one up teaches you what document control actually is.
4. Learn enough about models to ask the level-of-development question without being told to.

And carry the two sentences that govern this whole appendix. Tool choice is mostly decided by what the owner, your company, and your subcontractors already use — so evaluate for capability and adoption, not for brand. And a platform does not create discipline; it makes the absence of discipline visible faster — so if the underlying process is broken, buying software will not fix it. It will simply publish it.

Related reading: Chapter 12 (digital takeoff) · Chapter 14 (scheduling software) · Chapter 25 (document control) · Chapter 28 (cost codes and reporting) · Chapter 35 (BIM, LOD, and the execution plan) · Chapter 39 (the adoption framework and the four failure modes) · Appendix C (cost and productivity data) · Appendix D (the forms these tools replace, and the logic behind them).