Posts for subcontractors.
Subcontractors are the most under-served seat in construction technology — and the seat where the operating-system gap costs the most office labor. These posts cover the workflows that matter most to a commercial sub: the ITB inbox, pay applications, retention rollforward, lien waivers, field operations, and what changes when the GC across the table is also on the same platform.
Subcontractors are the most under-served seat in construction technology.
Most construction platforms are GC-first. They give subs a free portal to log into and call it done — while the sub's own business runs on duct tape and four GC portals. Here's why that gap exists, what it costs the sub side of every commercial project, and what we're doing about it.
AIA G702 and G703 for subcontractors: a working guide.
The AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) are the standard pay-application forms used on most commercial construction projects in the United States. This is a working guide for subcontractors: what the forms are, what every line means, how to fill them in without errors, the common mistakes that delay payment, and how AOS automates the entire flow.
Construction retention rollforward by GC: a working guide for sub accounting.
Retention is the single largest line on most subcontractor balance sheets that nobody can produce a clean report on. The dollars are owed, the GCs know they're owed, and yet at closeout the numbers don't match and the negotiation almost always favors the side with better records. This is a working guide for sub accountants on how to roll retention forward cleanly — what to track, where it gets lost today, the state-by-state release triggers most subs miss, and how AOS handles the whole thing on one record.
A field-tech adoption playbook for self-perform specialty trades.
Every construction technology survey for the last ten years has named field-tech adoption as the single biggest unsolved problem in the industry. Self-perform specialty trades — concrete, steel, drywall, MEP, glazing — have it worst. The foreman writes on a steno pad, the office buys software the foreman doesn't use, and the executive wonders why the ROI never materializes. This is a playbook for self-perform subs on how to actually get field tech adopted, what fails consistently, and how to design rollouts that survive contact with the jobsite.
Construction change orders: four patterns and how to manage them without margin erosion.
Change orders are the second-most-disputed line on every commercial construction project, after retention. The dollar volume in change orders on a typical mid-sized project runs 5-15% of contract value, and the management of them — pricing, approval routing, schedule impact, aging, payment — is where margin gets made or lost on both the sub side and the GC side. This is a working guide to the four common change-order patterns, how each one should be priced and routed, the aging problem that quietly erodes margin, and how AOS handles the whole flow.
Prevailing wage and certified payroll for mid-market commercial subs: a 2026 working guide.
Prevailing-wage compliance is one of the highest-stakes administrative obligations in commercial construction. Mis-classify a worker, under-pay a fringe rate, or file a non-conforming certified payroll and your firm can face debarment from public-works projects, penalty assessments, and back-wage liability that ripples across every project on the same contract. This is a 2026 working guide for mid-market commercial subs on Davis-Bacon and state little-DB statutes, WH-347 certified payroll mechanics, fringe-benefit accounting, and the compliance pitfalls that catch firms most often.
The ITB process for commercial subcontractors: from bid invitation to award without losing days to GC portal chaos.
The Invitation-to-Bid (ITB) is where commercial subs win or lose the year. Get the bid quantification right, respond on time, catch every addendum, and you build the backlog that keeps the firm running. Miss a deadline, misinterpret a scope, or lose a bid document in the GC-portal proliferation and you've burned a week of estimator time for nothing. This is a working guide to the ITB process for mid-market commercial subs — the chaos of GC portal proliferation, how to triage incoming ITBs, the addendum-tracking problem, bid-day mechanics, and how AOS unifies the ITB inbox.
Construction COI compliance: how subs maintain coverage and how GCs actually verify it.
Certificate of Insurance compliance is one of the most labor-intensive recurring administrative tasks in commercial construction. Subs maintain four to six active policies, file COIs to every GC client on every active project, and chase renewals continuously. GCs verify dozens of COIs across hundreds of active sub-project relationships and have to track expirations against every project they're on. The cost of getting this wrong — whether you're the sub whose policy lapses mid-project or the GC who paid an uninsured sub — ranges from "annoying" to "company-ending." This is a working guide for both sides on how COI compliance actually works, the recurring mistakes, and how AOS handles the lifecycle.
Construction cost coding and chart-of-accounts decisions for mid-market firms.
Cost coding is the most consequential foundational decision in a commercial construction firm's accounting setup, and it's the decision most often made by accident — inherited from the predecessor controller's 2014 setup, copied from the GC down the street, or matched to the estimator's spreadsheet templates from a prior firm. This is a working guide for mid-market commercial subs and GCs on how cost coding should be designed, why cost-code drift across systems is the root cause of pay-app reconciliation pain, and how to think about restructuring without breaking the historical record.
Construction submittal management: from log entry to install approval without version drift.
Submittals are the workflow that determines whether the product installed on your project actually matches what the architect specified. Get them right and the install proceeds cleanly. Get them wrong — missing approvals, version drift between the approved submittal and the installed product, or install-without-approval — and you're rebuilding a wall on your own dime, or arguing at closeout about whether the substituted product meets the spec. This is a working guide to the submittal lifecycle for mid-market commercial subs and GCs: the submittal vs RFI workflow distinction, the architect's SLAs, the recurring failure modes, and how AOS handles the cross-tenant flow.
Construction RFI management: from field question to architect response without inbox limbo.
The RFI — Request for Information — is the workflow that determines whether questions raised in the field get clean answers in time to keep work moving, or whether they pile up in email inboxes until the schedule slips. RFI cycle time and resolution rate are two of the most consequential metrics on every commercial project, and most of the time they're not measured because nobody owns the log. This is a working guide for mid-market subs and GCs on RFI management.
Construction punch list management: from substantial completion to certificate of occupancy.
The punch list is the workflow that determines whether your project actually closes out cleanly — or sits in punch limbo for months while the GC and subs argue about who owns which incomplete item. The list itself isn't complicated. The management of it, across the sub-GC-owner-architect chain, is where projects either ship on time or grind to a halt three weeks before substantial completion. This is a working guide on construction punch list management.
Subcontractor prequalification for general contractors: a working framework.
Subcontractor prequalification is the GC's first line of defense against project risk — bonding capacity, insurance coverage, safety record, financial stability, references, and operational capacity all checked before the sub bids, not after they've been awarded. Done well, it filters out the firms most likely to default mid-project, deliver substandard work, or generate liability exposure. Done as a paperwork ritual, it produces a binder full of stale forms and zero actual screening.
Construction safety management and EMR: a working guide for mid-market commercial subs.
Safety management is the workflow that determines whether your firm can keep winning commercial work, what your workers' comp insurance costs, and (most fundamentally) whether the people on your jobsites go home in the same condition they arrived. EMR — the Experience Modification Rate — is the single number every GC will check during prequal, every insurance underwriter will base your rate on, and every owner will use to filter eligible bidders on certain projects. This is a working guide for mid-market commercial subs on how safety actually has to work.
Construction project scheduling: CPM, baseline, and the working schedule.
The project schedule is the document that determines whether your project hits substantial completion on time — or slips by weeks while the GC and subs argue about whose delay caused which milestone to miss. CPM scheduling, baseline vs working schedule, weekly look-aheads, delay attribution, and concurrent delay analysis are the workflows that separate projects that ship on time from projects that ship at all. This is a working guide for mid-market subs and GCs on how project scheduling actually has to work.
Construction warranty management: from substantial completion through the warranty period.
The construction warranty period starts the day after substantial completion and runs for one year on most commercial projects — longer for specific systems (roofing, glazing, mechanical equipment, foundation work). Whether that warranty period goes smoothly for the GC or sub depends almost entirely on how well warranty obligations were documented at closeout and how the warranty-claim workflow is structured. This is a working guide on construction warranty management.
Introducing AOS — one operating system for every seat in AEC.
Construction has run on a patchwork of tools none of which were built for it. AOS is one operating system, one record, and one bill — for general contractors, owners and developers, subcontractors, architecture firms, and residential builders.