Construction Back-Office: The Complete 2026 Guide for Mid-Market Contractors

Why mid-market construction is the hardest back-office Mid-market construction firms operate the most operationally complex back-office in the mid-market, and the complexity is structural rather than circumstantial. A manufacturing firm of comparable revenue runs one production line, or a handful of them, within four walls, with a single ERP that captures the entire operation and a finance team whose accounting work maps tidily to the operational reality. A professional-services firm runs dozens of concurrent engagements, but each engagement is largely a labor-cost-plus-pass-through model that resolves into time-and-materials billing or fixed-fee revenue recognition without much structural complexity. A construction firm of fifty million to five hundred million in revenue, by contrast, is running ten to seventy concurrent jobs at any given moment, each with its own contract type, its own cost-code structure, its own change-order trail, its own retainage timing, its own bonding implications, its own percentage-of-completion math, and its own field-versus-office handoff complications. The back-office is not running one business; it is running one business per active job, and the consolidation is the closing exercise that produces the financial statements. The complexity layers begin with percentage-of-completion accounting, which the construction industry has used as the principal revenue-recognition method for the better part of a century and which ASC 606 retained for the overwhelming majority of construction contracts. Under percentage-of-completion, revenue is recognized as the firm's performance progresses against the contract, with progress most commonly measured by costs incurred to date divided by total estimated costs at completion. The mechanics are straightforward in principle; the application is the constant exercise that drives the back-office calendar. Every active job requires a current estimate at completion, the denominator in the percentage calculation, and the estimate must be refreshed whenever the job's economics change materially. A stale estimate at completion distorts the percentage independently of the costs incurred, which means it distorts the earned revenue, which means it distorts the WIP schedule, which means it distorts every downstream report the controller produces. The firms whose back-office runs cleanly have a discipline around project-manager estimate refresh that they enforce monthly at minimum; the firms whose back-office produces audit findings have project managers who refresh the estimate when prompted and not before. The second complexity layer is change order chaos, and the chaos is the operating reality of construction rather than a deviation from it. Owners issue change directives that the firm executes before the change order is fully approved; firms execute claim work that they believe is owed under the contract but for which approval is pending; subcontractors submit change-order pricing on the basis of field conditions that turn out to differ from the assumptions; and the change-order log on any active job of meaningful size is a living document that the project manager, the controller, and the project executive read together with different mental models. The accounting treatment of approved, pending, and disputed change orders has direct effects on the earned revenue, the WIP, and the cash position. The firms that document change orders well, contemporaneously, in writing, with the supporting cost-impact and schedule-impact analysis, protect themselves against disputes and produce the documentation the auditor will request at year-end. The firms that document change orders poorly accumulate a backlog of pending items that the controller treats conservatively in the books and that the project executive treats optimistically in the forecast, and the gap between the two views surfaces unpleasantly when the dispute or the audit arrives. The third layer is the field-versus-office gap that every construction firm contends with at every scale. The work happens in the field, the cost is incurred when material is delivered to the job site, when labor punches into the time-tracking system, when the equipment hour meter ticks over, when the subcontractor's crew shows up, and the accounting happens in the office, downstream of the field events that the back-office may not learn about for days or weeks. The field-versus-office gap shows up everywhere: daily logs that aren't completed for a week and then are completed from memory; time entries that are submitted at the end of a pay period and that aggregate the hours without the cost-code detail; photos that document the work but that aren't tagged or filed in a way that lets the project manager retrieve them when a dispute arrives; delivery tickets that pile up in the trailer until someone takes them back to the office for entry. The data-hygiene baseline that a back-office requires, and that any AI pilot depends on, lives in the field, and the field is where it most commonly degrades. The fourth layer is retainage, the contractual practice under which the owner withholds a percentage (typically five to ten percent) of each progress payment until substantial completion, with the retained amount released after punch-list completion, final lien releases, and any required closeout documentation. Retainage ages on the firm's balance sheet for months past the work itself, creating an accounts-receivable balance that doesn't behave like a normal receivable: it isn't past due in the conventional sense, it isn't reasonably expected to be collected on standard terms, and it doesn't fit the aging-bucket discipline that the controller uses for ordinary receivables. The firm needs a separate aging discipline for retainage, a separate set of follow-up workflows for stale retainage on closed jobs, and a clear view of which retainage balances are at risk and which are simply waiting on the closeout cycle. The fifth layer is AIA billing, the industry-standard progress-billing format embodied in the AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) documents that owners and architects expect to see on most commercial construction projects. AIA billing requires the firm to produce, every billing cycle, a schedule-of-values continuation sheet that breaks the contract down by line item, shows the work completed to date, the work completed this period, the materials stored, the retainage withheld, and the amount due. The schedule of values must tie to the firm's cost-code structure, must support the percentage-of-completion calculation, and must be defensible to the architect's review. Firms that bill AIA-format on most of their work develop a billing discipline that runs adjacent to the GL close; firms that try to run AIA billing as an afterthought to the standard AR cycle find the architect rejecting the applications and the cash flow suffering as a result. These five layers, percentage-of-completion accounting, change-order chaos, the field-versus-office gap, retainage, and AIA billing, compound rather than add. A firm with a clean cost-code structure but poor change-order documentation has a percentage-of-completion calculation that is mathematically defensible and economically wrong. A firm with disciplined estimate refresh but a weak retainage practice carries a balance sheet that overstates current-cycle collectibility. A firm with strong AIA billing but a degraded field-to-office handoff bills accurately for work whose cost basis the back-office doesn't fully understand. The mid-market construction back-office's job is to operate all five disciplines concurrently and consistently across every active job, and the firms that scale past one hundred million in revenue without restructuring the back-office every two years are the firms that build the disciplines deliberately rather than letting them emerge. The cost code structure that decides everything The cost-code structure is the load-bearing decision in the construction back-office, and most mid-market firms underestimate how far the decision reaches. A cost-code structure is the hierarchical chart of accounts the firm uses to classify direct construction costs, labor, materials, subcontractors, equipment, and other direct costs, at the job-cost level, with the structure typically running from a high-level division (a division-of-work category such as concrete, masonry, or mechanical) down through a phase or major work item, down through a specific cost code, and in some firms down further to a sub-cost-code or activity level. The cost-code structure is what the estimator uses to build the bid, what the project manager uses to track the job's performance against the estimate, what the controller uses to charge actual costs through the AP and payroll systems, what the percentage-of-completion calculation uses for the cost-to-cost ratio, and what the WIP schedule rolls up into for the bonding-side reporting. A cost-code structure that is consistent across all of these uses produces a back-office that operates as a single coherent system; a cost-code structure that is fragmented across uses produces a back-office in which every report requires a reconciliation between the version of the structure the source system uses and the version of the structure the receiving report expects. The first discipline is firm-wide standardization. Many mid-market construction firms have allowed their cost-code structures to evolve job-by-job, the estimator builds a structure that fits the specific project's scope, the project manager modifies the structure as the job progresses, and the resulting structure is unique to that job and incomparable to any other. The result is that the firm cannot answer basic operational questions across the portfolio: what is the firm's labor productivity in concrete formwork across all active jobs, what is the firm's typical cost overrun in mechanical rough-in, what is the average cost per square foot for tilt-up wall construction. The firms that standardize the cost-code structure at the firm level, with a master cost-code catalog that all jobs use, with project-specific extensions only at the lowest levels, preserve the ability to learn from one job to the next and to roll up portfolio-level metrics. The firms that don't standardize learn from each job in isolation, repeat the same mistakes across jobs, and discover the cost of the fragmentation when they try to build an AI pilot that depends on cross-job cost data. The second discipline is the mapping from the cost-code structure to the ERP. The ERP, Sage 300 CRE, Foundation Software, Viewpoint Spectrum, Viewpoint Vista, CMiC, Acumatica Construction Edition, or one of the comparable platforms, is where the actual costs accumulate. AP invoices are coded to a job and a cost code at entry; payroll allocations distribute labor cost to jobs and cost codes through the timekeeping system; equipment costs flow through the equipment ledger to the job and cost code; subcontractor costs follow through the subcontract module. The cost-code structure in the ERP must match the cost-code structure the estimator uses and the structure the project manager tracks, because a mismatch means the actual costs land in a code the estimate didn't anticipate, or the estimate references a code that the ERP doesn't recognize, and the variance reports require manual reconciliation to make sense. The firms that get this right define the cost-code structure once, in a single source of truth, and propagate it to the estimating system and the ERP through a controlled change process; the firms that get this wrong let the estimator, the project manager, and the controller each maintain their own version, and the back-office bears the reconciliation cost on every job. The third discipline is the mapping from the cost-code structure to the construction-management platform, which for most mid-market commercial firms means Procore and for the Autodesk-aligned firms means Autodesk Construction Cloud. The construction-management platform is where the project-execution workflow runs, RFIs, submittals, change orders, daily logs, drawings, punch lists, and the platform's cost-management modules also track committed costs and forecasted final costs by cost code. The platform's cost-code list must align with the ERP's cost-code list, because the change-order amounts that the project manager logs in Procore eventually flow to the ERP as cost commitments and revenue adjustments, and a misalignment means the integration either requires manual mapping at the transaction level or simply doesn't work. We treat the project-management to ERP integration discipline in detail elsewhere; the cost-code alignment is the prerequisite that makes the integration possible at all. The industry-standard reference for the cost-code structure is the CSI MasterFormat, maintained by the Construction Specifications Institute, which provides a hierarchical classification of construction work by division (currently fifty divisions, from general requirements through electrical, communications, integrated automation, and the more recently added utility-and-infrastructure divisions). MasterFormat is the default basis for the cost-code structure in most commercial construction estimating systems and is the structure most architects and owners expect to see referenced in the schedule of values. The AIA's contract documents, the American Institute of Architects maintains the industry-standard A-series owner-contractor agreements, B-series owner-architect agreements, and the G-series project-management forms including the G702/G703, assume an underlying cost-code structure that maps to MasterFormat for the schedule-of-values continuation sheet. A firm that adopts a cost-code structure that diverges materially from MasterFormat takes on the cost of translating between its internal structure and the structure the owner and architect expect to see in the AIA paperwork. The common cost-code mistakes are predictable and avoidable. Over-granularity is the first: a structure with so many cost codes that the estimator, the project manager, and the AP clerk all struggle to code consistently, and the resulting cost data is fragmented across so many codes that meaningful aggregation requires a separate roll-up step. Under-granularity is the second: a structure with too few cost codes for the project manager to track performance against the estimate, with the result that the variance report shows the job as on-budget overall while masking significant cost overruns in specific work areas that an appropriately granular structure would have flagged. Inconsistent application is the third: a structure that exists on paper but that different project managers, estimators, and AP clerks apply differently, with the result that the cost data is comparable in name only. Estimate-versus-actuals misalignment is the fourth: a structure in which the codes the estimator uses to build the bid don't match the codes the project manager and AP clerk use to track actuals, with the result that the variance reports compare incomparable categories. The remedies are the same in each case: firm-wide standardization, an explicit catalog with definitions, training for everyone who touches the structure, and a controlled change process that prevents the structure from drifting unintentionally. Change orders, RFIs, and the documentation that survives a dispute Change orders are the operational reality of construction, and the documentation discipline around them is the difference between a firm that gets paid for the work it does and a firm that performs work for which the documentation cannot support collection. A change order, in its formal sense, is a written modification to the contract that adjusts the scope, the price, the schedule, or any combination of the three. The formal change order, typically executed on an AIA G701 Change Order form or an equivalent owner-specific contract-modification document, is the end state of a workflow that begins much earlier, with a change directive from the owner or a change-condition observation from the firm, that moves through pricing and schedule analysis, that surfaces in RFIs and field instructions, and that the firm executes (often before the formal change order is signed) on the basis of the owner's verbal authorization, written email, or operational necessity. The discipline that protects the firm is the discipline that documents the entire workflow contemporaneously, in writing, in a form that another party, an arbitrator, a litigation expert, an auditor, a surety underwriter, could read months or years later and reconstruct what happened and why. The change-order workflow in a disciplined mid-market firm follows a consistent pattern. The change condition is identified, by the owner's directive, by the firm's observation of a differing site condition, by an RFI response that changes the scope, or by a design change communicated by the architect. The condition is logged in the project-management platform, Procore, Autodesk Construction Cloud, or comparable, with a unique identifier, the date, the source, and the initial scope description. The firm prepares a pricing analysis that breaks the change-order amount down into labor, materials, subcontractor costs, equipment, and any indirect or markup components, with the cost-code categorization tied to the firm's standard structure. The pricing analysis is submitted to the owner for approval, typically via an AIA G701 Change Order Request or an owner-specific change-order proposal form. The owner reviews, negotiates if necessary, and either approves the change order in writing or rejects it (or, more commonly, leaves it pending while requesting additional information or while internal approvals work through the owner's organization). The approved change order is logged as a contract modification in both the project-management platform and the ERP, with the change-order amount added to the contract value and the revised contract amount feeding through to the percentage-of-completion calculation and the WIP schedule. The complications in this workflow are constant. Owners frequently direct the firm to proceed with the changed work on the basis of a verbal authorization or a field directive, with the formal change order to follow later. The firm faces an operational choice: refuse to proceed until the change order is formally executed (which causes schedule impact and damages the customer relationship), or proceed on the verbal authorization with the documentation discipline that protects the firm if the formal change order is delayed or disputed. The disciplined firms proceed with a clear documentation protocol: the field directive is captured in writing the same day, typically by an email to the owner's representative confirming the verbal direction and the firm's intent to proceed, with the cost-impact and schedule-impact analysis appended. The protocol gives the firm a contemporaneous record that the owner cannot later deny, and it gives the auditor a basis for treating the resulting work as a documented change rather than an unauthorized cost. RFIs (Requests for Information) are the other half of the documentation discipline, and they sit upstream of many change orders. An RFI is a formal written request from the firm to the architect or owner asking for clarification of the contract documents, resolution of a conflict between drawings and specifications, or guidance on a field condition that the documents don't address. The RFI response, issued by the architect or owner, becomes part of the contract documentation and frequently becomes the basis for a subsequent change order if the response changes the scope. The disciplined firms run their RFI process through the project-management platform, with each RFI assigned a unique identifier, a clear question, an expected response date, the actual response date, the response content, and any follow-on actions including change-order generation if the response changes the scope. The discipline matters not only for the immediate project execution but for the dispute documentation: a firm that can produce a complete RFI log showing what was asked, when it was asked, what was answered, and when it was answered has a defensible record of the contract administration; a firm whose RFI log is incomplete or whose responses are scattered across email threads has a documentation gap that an opposing party can exploit. Daily logs are the field-side documentation discipline that supports both change-order claims and dispute defense. A daily log records the work performed on the job site each day: the crews present, the weather conditions, the deliveries received, the equipment on site, the work activities completed by area and cost code, the visitors and inspections, the safety incidents, and any noteworthy events including owner directives, unforeseen conditions, and work delays. The daily log is the contemporaneous record of what happened on the job, and it is the primary documentation that supports change-order claims for unforeseen conditions, weather delays, owner-caused delays, and other circumstances where the firm needs to prove what occurred on a specific date. The mid-market firms that maintain disciplined daily logs, typically through the project-management platform's mobile app, with the superintendent completing the log at the end of each day rather than retrospectively at the end of a week, have the documentation foundation for change-order recovery; the firms that treat daily logs as a compliance afterthought have a gap that surfaces every time a dispute requires contemporaneous documentation that doesn't exist. The contemporaneous documentation principle runs through all of this. The principle is that documentation created in the ordinary course of business at the time the events occurred is far more credible, to an arbitrator, a judge, a surety underwriter, an auditor, or an opposing party in negotiation, than documentation created retrospectively in preparation for a dispute. Contemporaneous documentation reflects what actually happened; retrospective documentation reflects what the party preparing it wishes had happened. The disciplined construction firm builds its documentation practices around the contemporaneous principle: daily logs completed daily, RFIs logged when they're issued and responses logged when they're received, change orders priced and submitted promptly after the changed condition is identified, field directives captured in writing the same day, and the entire documentation trail living in systems that timestamp the entries and preserve the audit history. Lien notices are the legal documentation discipline that protects the firm's payment rights, and the discipline varies materially by state. Most US states require firms providing labor or materials to a construction project to file or serve a preliminary lien notice (also called a notice to owner or a notice of furnishing) within a specified number of days from when the firm first provides labor or materials to the project. The notice preserves the firm's right to file a mechanic's lien against the project property if the firm is not paid, and the notice deadlines are strict, a missed notice deadline can extinguish the lien right regardless of how strong the firm's payment claim is on the merits. The mid-market construction firms operating across multiple states maintain a lien-compliance workflow that tracks the notice requirements for each state, generates the required notices on a calendar basis, and serves the notices through the appropriate channel for each jurisdiction. The discipline is unglamorous and the cost of failure is direct: a firm that misses lien-notice deadlines on a project where the owner becomes insolvent has converted secured payment claims into unsecured general-creditor claims, with the predictable recovery implications. The change-order, RFI, daily-log, and lien-notice disciplines are interdependent, and we treat the change-order management documentation in greater operational detail in a dedicated guide. The disciplines together comprise the documentation foundation that survives a dispute and that the ASC 606 contract-modification analysis depends on, and the firms whose back-office runs cleanly invest in the disciplines deliberately rather than treating them as a project-level afterthought. Construction software selection: Procore vs Autodesk Construction Cloud vs Sage vs Foundation Construction software selection for the mid-market is the back-office decision that compounds longest, and the selection is decided on dimensions that the demo rarely surfaces. The selection question is not "which platform is best", every credible platform in the mid-market category has reference customers who love it and reference customers who regret it. The selection question is which combination of platforms fits the firm's contract types, scale, geographic footprint, back-office maturity, and integration tolerance, and which set of multi-year implementation pain points the firm is willing to absorb. We treat the head-to-head selection matrix in a dedicated guide; this section frames the category boundaries, the principal vendors in each, and the integration discipline that decides whether the platforms work together or separately. The construction-software landscape for the mid-market splits into three categories, and the selection sequence matters. The first category is project management and operations, the platform that runs the field-execution workflow including drawings, RFIs, submittals, change orders, daily logs, photo documentation, punch lists, and the project-team coordination that lives between the field office and the project manager's desk. The second category is financial accounting and job costing, the platform that runs the GL, AP, AR, payroll, job costing, equipment costing, WIP, and the financial reporting that produces the audited financial statements and the WIP schedule. The third category is the integrated suite, a single vendor offering both categories under one platform, typically with tradeoffs against the best-in-class point solutions in each category but with the integration advantage that the platforms share a common data model. Most mid-market firms operate a two-platform stack, a project-management platform plus a financial-accounting platform, connected by integration, because the best-in-class point solutions in each category have outpaced the integrated suites for most firm profiles. Procore is the dominant project-management platform in the mid-market commercial construction segment, with a customer base that spans general contractors, specialty contractors, and self-perform firms. Procore's strengths are the breadth of its module set (RFIs, submittals, drawings, change orders, daily logs, observations, punch lists, photos, schedule integration, cost management, bid management, and an increasingly extensive set of preconstruction and analytics modules), the maturity of its mobile app for field use, the breadth of its API and integration ecosystem, and the network effect of being the platform that owners and architects are most likely to expect on a project. Procore's tradeoffs are the cost (Procore's pricing for mid-market firms ranges roughly from forty thousand to one hundred fifty thousand dollars annually at the lower end of the mid-market and significantly higher at the upper end, with the pricing model tied to construction volume rather than user count, which produces unfavorable economics for firms with high revenue per user), the depth of its accounting integration (which depends heavily on the ERP partner and the implementation discipline), and the implementation complexity for firms transitioning from a fragmented set of point solutions. Autodesk Construction Cloud is the principal competitor to Procore in the mid-market commercial segment and is the natural fit for firms whose design-side workflow already runs on Autodesk Revit, AutoCAD, or BIM 360. Autodesk Construction Cloud combines BIM 360 (the firm's earlier construction-collaboration platform), PlanGrid (acquired in 2018 and integrated as the field-management module), and the subsequently developed Autodesk Build, Autodesk Takeoff, Autodesk Cost, and the related modules into a unified platform. Autodesk's strengths are the deep integration with the Autodesk design-side tooling (which matters for design-build firms and for general contractors who do their own preconstruction modeling), the platform's BIM-coordination capabilities, and the increasingly competitive feature set in the construction-execution modules. Autodesk's tradeoffs are the relative immaturity of some construction-execution modules compared to Procore (the modules are catching up rapidly but the implementation experience can surface gaps), the integration story with the financial-accounting platforms (which depends heavily on the specific ERP and the integration partner), and the platform's pricing complexity (Autodesk's per-user and per-project pricing components can produce surprising total-cost calculations for firms with large project portfolios and lean user counts). Sage 300 CRE (formerly Timberline) and Foundation Software are the principal financial-accounting and job-costing platforms in the mid-market, with each having a specific fit profile. Sage 300 CRE is the long-standing market leader in mid-market commercial construction accounting, with deep functionality for job costing, equipment costing, payroll, AP, AR, GL, and the WIP and financial reporting that the controller depends on. Sage 300 CRE's tradeoffs are the user-experience showing its age (the platform's heritage as a Windows-desktop application is still visible in the modern incarnation, and the mobile and web experiences lag the best-in-class alternatives), the implementation complexity (Sage 300 CRE implementations frequently take six to twelve months and require specialized consultants who command premium rates), and the integration story with the project-management platforms (Procore-to-Sage and Autodesk-to-Sage integrations exist and work, with the depth of the integration depending on the version of Sage and the implementation partner). Foundation Software is the principal alternative in the same financial-accounting category, with a particular strength in payroll for construction firms operating in multi-state union environments, and with a customer base that skews toward specialty contractors and smaller general contractors compared to Sage's broader mid-market base. We treat the Sage-versus-Foundation-versus-Viewpoint comparison in detail in the dedicated selection-matrix guide; the short version is that the financial-accounting platform should be selected on the basis of the firm's specific payroll and job-costing complexity, the implementation partner's quality, and the integration to the project-management platform the firm has selected or will select. Viewpoint Spectrum and Viewpoint Vista are the principal alternatives in the integrated-suite category for larger mid-market firms, with both platforms now operating under the Trimble Construction One umbrella. Spectrum is the web-native, cloud-hosted option, and Vista is the longer-tenured on-premise or hosted option that scales to the upper end of the mid-market and into the lower end of the enterprise segment. CMiC is the principal alternative in the integrated-suite category for firms whose preference is a single vendor for both project management and financial accounting, with a customer base concentrated in the upper mid-market and lower enterprise segments. Acumatica Construction Edition is the newer entrant in the cloud-native integrated category, with a model that integrates with Procore for project management while providing the financial-accounting layer, and with growing traction in the mid-market for firms whose preference is a cloud-native financial platform. The selection across the three categories is decided by the integration discipline more than by the individual platform features. A mid-market firm running Procore for project management and Sage 300 CRE for financial accounting has two excellent platforms whose integration depends entirely on the implementation discipline, the cost-code alignment, the change-order data-flow design, the cost-commitment synchronization, and the WIP-data reconciliation process that ties the two platforms together. The same firm running Autodesk Construction Cloud and Foundation Software has the same integration discipline to design and execute. The firms whose two-platform stack runs cleanly are the firms that treated the integration as a first-class implementation workstream, with explicit ownership, clear data-flow definitions, and ongoing maintenance discipline; the firms whose two-platform stack runs poorly are the firms that treated the integration as an afterthought to the platform implementations, with the predictable result that the two systems carry inconsistent views of the same job. We treat the project-controls integration discipline as a dedicated topic; the discipline is what makes the two-platform stack actually function as the unified back-office the firm purchased. The AI capability gap across the construction-software vendors is the dimension on which the platforms are most actively differentiating in 2026, and the gap matters most for firms planning the next phase of digital transformation. Procore has invested heavily in its analytics and AI capabilities, with the Procore Copilot product and the broader Procore Analytics suite providing predictive-completion estimates, change-order-recovery analysis, and risk-flagging across the project portfolio. Autodesk has invested comparably in the Autodesk Construction IQ and the AI features embedded across the platform's modules, with a particular strength in BIM-coordination AI and predictive risk on design-side issues. Sage and Foundation have been slower to develop platform-native AI capabilities, with the AI story for firms on those platforms running primarily through third-party tools that integrate with the financial-accounting data. The platform-selection question for firms planning AI adoption is which platform's AI roadmap aligns with the firm's planned use cases and which platform's data architecture supports the integration of third-party AI tooling where the platform's native AI lags. Job cost accounting under ASC 606 Job cost accounting under ASC 606 is where the construction back-office's operational discipline meets the auditor's testing methodology, and the firms whose application of the standard survives audit cleanly are the firms that built the documentation infrastructure deliberately. ASC 606, issued by the Financial Accounting Standards Board (FASB) in 2014 and effective for nonpublic mid-market construction firms in fiscal years beginning after December 15, 2018, replaced the construction-specific revenue-recognition guidance that had governed percentage-of-completion accounting since the early 1980s. The headline impact at adoption was modest for most construction firms, because the cost-to-cost input method remained the predominant measure of progress on over-time performance obligations, and the financial-statement effects were correspondingly limited. The more consequential change was the restructuring of the supporting documentation the auditor expects to see, and the auditor's testing has evolved over the years since adoption to probe the documentation in ways the prior standard did not. We treat the ASC 606 application to construction contracts in dedicated detail in a separate guide; this section frames the percentage-of-completion-versus-completed-contract decision, the revenue-recognition timing implications, and the audit-ready accounting infrastructure that the standard now expects. The percentage-of-completion versus completed-contract decision under ASC 606 is mediated through the over-time-versus-point-in-time distinction in the standard. ASC 606 recognizes revenue over time when one of three criteria is met: the customer simultaneously receives and consumes the benefits of the firm's performance, the firm's performance creates or enhances an asset that the customer controls as the asset is created or enhanced, or the firm's performance does not create an asset with alternative use to the firm and the firm has an enforceable right to payment for performance completed to date. For most construction contracts, the second or third criterion is satisfied, the firm's performance creates real property that attaches to land owned by the customer, or the firm's performance creates a specific asset that has no alternative use and the contract provides an enforceable right to payment for work completed, and the over-time conclusion drives percentage-of-completion treatment. The completed-contract method, which defers all revenue recognition until the contract is substantially complete, is rarely appropriate under ASC 606 for typical commercial construction contracts and is generally limited to specific situations where none of the over-time criteria can be supported. The firm's policy memo must address the over-time-versus-point-in-time analysis contract by contract or by contract type, with the supporting analysis documented in a form the auditor can read. The revenue-recognition timing under percentage-of-completion is driven by the cost-to-cost input-method math: percentage of completion equals costs incurred to date divided by total estimated costs at completion, and earned revenue equals the percentage multiplied by the transaction price. The mechanics are straightforward; the discipline that produces clean revenue recognition is the discipline that maintains accurate inputs to the calculation. The numerator, costs incurred to date, is fed by the job-cost ledger and depends on the AP, payroll, equipment-cost, and subcontractor-cost workflows running cleanly and posting in the right period. The denominator, total estimated costs at completion, is fed by the project manager's estimate-at-completion refresh and depends on the project manager actually updating the estimate when the job's economics change rather than letting the estimate go stale until prompted by the controller. The transaction price is fed by the original contract value plus approved change orders plus the firm's estimate of variable-consideration components including unapproved change orders, claims, liquidated damages, and performance bonuses, with each variable component subject to the "probable, no significant reversal" constraint that ASC 606 imposes. The audit-ready accounting infrastructure that ASC 606 expects begins with the contract-level analytical workpaper, which most construction firms either do not maintain or maintain in a generic-template form that the auditor reads with skepticism. The workpaper for a material contract walks through the five-step model, identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, recognize revenue as the obligations are satisfied, for the specific contract, identifies the performance obligations (typically one for an integrated construction project, occasionally more for contracts with distinct equipment-supply or design components), justifies the input method (typically cost-to-cost, with the justification reflecting the contract's specifics), treats the variable-consideration components with the supporting estimates and the "probable, no significant reversal" analysis, and addresses any contract modifications under the ASC 606 modification mechanics (separate contract, termination-and-new-contract, or continuation with prospective or cumulative-catch-up accounting). The workpaper is the document the auditor reads before they read the math, and a workpaper that does not exist or is generic-template-grade produces the audit findings that show up in the management letter year after year. The variable-consideration treatment is the source of most ASC 606 audit findings in construction, and the discipline is straightforward but consistently underweighted. Approved change orders are included in the transaction price as of the approval date, with the approval evidenced by the AIA G701 or equivalent contract modification. Unapproved change orders and claims are included in the transaction price only to the extent that the firm has documented evidence that approval is highly likely and the amount is reasonably estimable, with the "probable, no significant reversal" constraint applied conservatively. Liquidated damages are estimated as negative variable consideration when the schedule risk warrants the estimate, with the supporting schedule analysis documented. Performance bonuses are estimated as positive variable consideration when the bonus criteria are likely to be met. The recurring audit finding we identify in construction firms is the recognition of claim revenue at full claimed value before any documented basis for collection, the firm has performed disputed work, has filed or intends to file a claim, has booked the claimed revenue in full, and has no contemporaneous documentation that the owner has acknowledged the work, agreed to the pricing methodology, or otherwise indicated approval. The conservative practice, and the practice that survives audit cleanly, is to recognize claim revenue only when documentation criteria are met and to use a probability-weighted percentage rather than the full claimed value until approval is documented. The uninstalled-materials treatment is the second predictable audit-finding area. Materials procured for a job but not yet installed have been paid for, are sitting in costs incurred to date, and would inflate the percentage of completion if treated mechanically as cost-to-cost inputs. ASC 606 requires that uninstalled materials be excluded from the cost-to-cost calculation when they do not represent progress on the performance obligation, with the firm recognizing revenue equal to the cost of the materials with zero margin (the "zero-margin" treatment) and the gross-margin recognition deferred until the materials are installed. The policy memo must address how the firm identifies uninstalled materials, when the exclusion is applied, and how the zero-margin recognition is documented. Firms that ignore the uninstalled-materials treatment routinely overstate percentage of completion in the early periods of jobs with significant material procurement, and the resulting over-recognition surfaces as an audit adjustment when the auditor tests the WIP at year-end. The contract-modification mechanics under ASC 606 distinguish between modifications treated as separate contracts (when the modification adds distinct goods or services at standalone selling price), modifications treated as terminations of the existing contract and creation of a new contract (when the remaining goods or services are distinct from those transferred before the modification), and modifications treated as continuations with prospective or cumulative-catch-up accounting (when the modification is not a separate contract and the remaining goods or services are not distinct). Most construction-contract modifications, including the typical change order on a single-performance-obligation contract, are treated as continuations with cumulative-catch-up accounting, where the change-order amount is added to the transaction price and the percentage-of-completion calculation is adjusted with a catch-up entry for the change in earned revenue. The policy memo addresses the firm's modification-classification framework and applies it consistently across the contract portfolio. WIP schedules, bonding, and surety relationships The WIP schedule is the single most important report the mid-market construction back-office produces, and the firms whose back-office runs cleanly treat the WIP as a first-class operational artifact rather than a month-end compliance exercise. A WIP (work-in-progress) schedule is the project-by-project summary of every active contract that the firm is performing, showing for each contract the original contract value, the approved change orders, the revised contract value, the costs incurred to date, the total estimated costs at completion, the percentage of completion, the earned revenue, the billings to date, the over- or under-billings, the gross profit earned to date, and a set of derived metrics that the controller, the CFO, the surety underwriter, and the bonding agent each read with their own questions in mind. The WIP is the report that ties the job-cost ledger to the financial statements, that supports the percentage-of-completion revenue recognition the auditor will test, and that the surety underwriter relies on to assess the firm's bonding capacity at every renewal cycle. We treat the WIP schedule discipline in detail in a dedicated guide; this section frames the WIP's role in the back-office calendar, the bonding-capacity implications, and the surety-underwriter expectations that decide the firm's bonding-line economics. The WIP schedule discipline runs on a monthly cycle for most mid-market firms, with the WIP produced as part of the month-end close and reviewed by the controller, the CFO, and the project executives before it is finalized. The discipline begins with the project-manager estimate-refresh: every active contract requires a current estimate at completion, and the estimate must be reviewed and updated by the project manager each month rather than carried forward from the prior period. The estimate-refresh is the discipline that maintains the accuracy of the percentage-of-completion math, because the denominator moves with the project's evolution and a stale denominator distorts the percentage independently of the costs incurred. The controller reviews the refreshed estimates with the project managers, challenges estimates that move materially without explanation, and ensures that the estimate changes reflect the project's actual evolution rather than the project manager's wishful thinking about how the job will end. The reviewed estimates feed the WIP calculation, and the WIP feeds the financial statements and the surety reporting. The over-and-under-billing analysis is the WIP's most operationally significant output. A contract is over-billed when the firm has billed more than it has earned (billings exceed earned revenue, producing a liability on the balance sheet typically labeled "billings in excess of costs and estimated earnings on uncompleted contracts"), and a contract is under-billed when the firm has earned more than it has billed (earned revenue exceeds billings, producing an asset typically labeled "costs and estimated earnings in excess of billings on uncompleted contracts"). The over-and-under-billing positions reveal the cash-flow rhythm of the contract portfolio and the firm's billing discipline. A firm that is consistently over-billed across the portfolio is collecting cash ahead of earnings, which is favorable for working capital but creates exposure if the percentage-of-completion math is overstated and the over-billing is masking margin erosion that will surface later. A firm that is consistently under-billed is financing the customer's project with the firm's own working capital, which strains the credit line and surfaces in the cash-flow forecast. The disciplined firms read the over-and-under-billing positions contract by contract and use the analysis to drive both billing discipline (catching up under-billings through aggressive billing) and revenue-recognition scrutiny (probing over-billings for percentage-of-completion overstatement). The bonding capacity that the surety underwriter extends to the firm is decided largely on the basis of the WIP and the firm's overall financial profile, with the WIP carrying particular weight because it shows the surety the firm's current exposure to the contract portfolio and the firm's discipline in managing the portfolio. A surety underwriter at most major construction-surety carriers, Travelers Construction Services, Liberty Mutual Surety, Zurich Surety, CNA Surety, and the comparable carriers in the mid-market segment, reviews the firm's audited financial statements, the in-house WIP at each renewal, and the firm's contract backlog to set the single-project bonding limit and the aggregate bonding limit that the firm can access. The single-project limit constrains the largest individual contract the firm can bid; the aggregate limit constrains the total bonded backlog the firm can carry. The bonding capacity scales roughly with the firm's working capital, equity, and the surety's assessment of the firm's contract-management discipline, with the discipline assessment heavily informed by the WIP's quality and the consistency of the firm's WIP across periods. A firm whose WIP shows clean percentage-of-completion math, controlled over-and-under-billing positions, accurate estimate-refresh discipline, and a contract portfolio diversified across customer concentration and contract type receives bonding capacity at favorable multiples of working capital; a firm whose WIP shows ragged math, large or volatile over-billings, stale estimates, or concentrated customer exposure receives bonding capacity at compressed multiples and at less favorable rates. The surety underwriter expectations are predictable, and the firms that build the back-office to meet them gain access to bonding lines that materially expand the firm's project-bidding range. The underwriter expects an in-house WIP produced monthly, prepared on a basis consistent with the audited financials, reviewed by the controller and the CFO before submission to the underwriter at quarterly or semi-annual intervals. The underwriter expects the WIP to roll forward consistently from period to period, with material changes in earned-revenue, estimated-costs-at-completion, or over-and-under-billing positions explained in the cover memo that accompanies the WIP submission. The underwriter expects the firm's audited financial statements to be prepared on a basis that supports the in-house WIP without significant reconciling items, with the percentage-of-completion mechanics applied consistently between the in-house and audited views. The underwriter expects the firm to maintain a contract-backlog summary that shows the bonded and unbonded backlog by project, by customer, and by contract type, with the backlog reconciliation to the WIP straightforward. The firms that submit underwriter packages that meet these expectations as a matter of course earn the underwriter's trust and the corresponding bonding capacity; the firms that submit packages requiring multiple follow-up cycles and reconciliation work surface the underwriter's concerns about management discipline and earn correspondingly conservative bonding terms. For mid-market construction firms whose bonding requirements exceed the capacity individual sureties extend, the SBA Surety Bond Guarantee Program provides a federal guarantee that participating surety carriers can use to extend bonding to firms that would otherwise be capacity-constrained. The SBA program is principally relevant for smaller mid-market firms (under roughly twenty million in revenue for most contracts) and for firms entering federal contracting where the bonding requirements scale with the contract value. The program is a useful supplement to the firm's commercial-surety relationships, with the application discipline running on similar documentation expectations to the commercial surety underwriting. The relationship with the firm's bonding agent, typically an independent insurance broker specializing in construction surety, is the operational layer that connects the firm's back-office discipline to the underwriter's bonding decisions. The bonding agent reads the WIP and the underwriter packages on the firm's behalf, advocates for the firm's bonding capacity with the underwriter, and provides the firm with the early-warning signal when the firm's financial profile or the contract portfolio is moving toward bonding-capacity constraint. The firms whose bonding agent relationships work are the firms that share the WIP and the back-office discipline transparently with the agent and that act on the agent's feedback before the underwriter's renewal raises the same issues. The trade association the bonding agents most commonly belong to is the National Association of Surety Bond Producers, and the construction-industry counterparts at the Associated General Contractors provide additional industry-side context on bonding-market conditions and the surety-relationship best practices. AI in construction, the 80% failure pattern More than eighty percent of construction AI pilots never reach production, and the failure pattern is consistent across the firms we evaluate. The AI is rarely the bottleneck. The construction-AI vendor's models are competent at the tasks they are designed for, change-order risk prediction, schedule-slip detection, takeoff acceleration, photo-tagging, document classification, RFP automation. The vendor's demo is genuinely impressive on the curated data the vendor uses to demonstrate the product. The pilot fails in the firm's environment because the firm's data is fragmented across spreadsheets, email threads, project-management platforms, ERPs, field apps, scanned PDFs in cloud storage, and project managers' personal notes, and the AI cannot perform the task on data the AI cannot reliably access in a form the AI can understand. We treat the construction-AI pilot failure pattern and the data-hygiene baseline in dedicated operational detail; this section frames why the failures are predictable, what the successful pilots share, and what mid-market construction firms should evaluate before committing to the next AI investment. The data-fragmentation problem in mid-market construction is structural, and the structure is what makes the AI hard. A typical mid-market construction firm's project data lives in seven to ten distinct systems on an active project: the project-management platform (Procore, Autodesk Construction Cloud, or comparable) holding the RFIs, submittals, drawings, change orders, daily logs, and photos; the financial-accounting platform (Sage, Foundation, Viewpoint, or comparable) holding the job-cost ledger, the AP and AR data, the payroll data, and the WIP calculations; the scheduling platform (Primavera P6, Microsoft Project, or comparable) holding the schedule logic and the float analysis; the estimating platform (Sage Estimating, On-Screen Takeoff, BlueBeam, or comparable) holding the bid data and the cost-estimate breakdowns; the document-management platform (BIM 360 Docs, SharePoint, Egnyte, or comparable) holding the contract documents, drawings, specifications, and submitted document packages; the email system holding the contemporaneous communication that documents the project execution; the project managers' personal spreadsheets and notes holding the operational tracking that hasn't been migrated to the platform; and the field crews' mobile apps holding the daily logs, time entries, and photo uploads that may or may not have synchronized to the platform. Each of the systems is internally consistent, more or less. The data is fragmented across the systems, with the same project entity carrying inconsistent identifiers across platforms, the same cost code carrying inconsistent definitions, the same change order represented differently in the project-management and financial systems, and the same daily-log entry potentially appearing in the platform, in a separate spreadsheet, in an email summary, and in a manager's personal notes. The AI pilot that depends on cross-system data, and most operationally meaningful AI use cases do, fails because the AI cannot reliably reconcile the system-to-system inconsistencies, and the human effort required to reconcile them on every prediction defeats the AI's value proposition. The successful pilot pattern is the inverse of the failure pattern. The firms whose AI pilots reach production share a set of preconditions that the firms whose pilots fail typically lack. First, they have a firm-wide cost-code standardization that propagates consistently across the estimating system, the project-management platform, and the financial-accounting platform, so that the AI working on any one system's data is working with categories that match the other systems. Second, they have a change-order workflow that runs through the project-management platform with the documentation discipline that produces complete and contemporaneous records, so that the AI evaluating change-order risk or recovery has a clean dataset to learn from. Third, they have a daily-log discipline that produces complete, timely, structured field-side documentation in the project-management platform, so that the AI analyzing field productivity or schedule risk has source data that reflects what actually happened on the job. Fourth, they have a document-control discipline that keeps contract documents, RFIs, submittals, and drawings in the platform's document repositories with consistent naming and metadata, so that the AI looking up contract clauses or specification requirements can find the relevant documents reliably. Fifth, they have an ERP-integration discipline that synchronizes job-cost data, change-order data, and contract data between the project-management and financial-accounting platforms on a defined cadence, so that the AI working on cost-prediction or revenue-recognition tasks has consistent data across the two principal data sources. The evaluation framework for construction AI investments follows from the precondition analysis. Before committing to an AI pilot, the firm should evaluate the data-source assumption, what data the AI requires to perform the task, where the data currently lives in the firm's systems, what the data-quality state is in each source system, and what the integration or aggregation work is to bring the data into a form the AI can consume reliably. The firm should evaluate the scope assumption, what specific decisions or workflows the AI is intended to support, what the current decision quality is, what the AI is plausibly capable of contributing, and what the operational integration is between the AI's output and the firm's existing workflow. The firm should evaluate the vendor's reference customers honestly, not the curated demo customers but the firms that have used the vendor in production for at least twelve months, with attention to the integration burden the firm carried, the implementation timeline, the ongoing maintenance, and the actual decision-quality improvement. The construction-AI vendors most active in the mid-market in 2026, including the AI capabilities embedded in Procore, Autodesk Construction Cloud, and the specialized vendors in change-order analysis, schedule risk, takeoff automation, and field-safety analysis, are competent at the tasks they target. The pilots succeed in the firms that have built the data-hygiene baseline first; the pilots fail in the firms that hope the AI will resolve the data fragmentation rather than depend on it being resolved. The order matters, and the firms that invert it, buying the AI first and discovering the data problem in the implementation, spend the AI investment on the data-cleanup work the AI was supposed to make unnecessary. Field/office handoff: the data hygiene baseline The field-office handoff is the operational seam where the construction back-office's data hygiene is most commonly broken, and the discipline that maintains the seam cleanly is the foundation that everything downstream depends on. The work happens in the field; the accounting and the project administration happen in the office; and the data that bridges the two is generated by superintendents, foremen, and field crews whose primary job is to build the project, not to maintain the back-office's source data. The firms whose handoff runs cleanly have built the field-side discipline into the daily work, with mobile tools and workflow expectations that produce the documentation as a side effect of the work rather than as an additional administrative burden; the firms whose handoff runs poorly rely on retrospective documentation and the office staff's reconciliation work to fill in the gaps. The daily logs are the principal field-side documentation artifact, and the discipline is straightforward: the superintendent or foreman completes the log at the end of each day, in the project-management platform's mobile app, with the crew presence, the weather, the deliveries, the equipment, the work activities by area and cost code, the visitors and inspections, the safety incidents, and any noteworthy events. The discipline matters because the daily log is the contemporaneous record that supports change-order claims for unforeseen conditions, weather delays, and owner-caused delays, and it is the primary documentation that the firm relies on in any subsequent dispute. The disciplined firms enforce the same-day completion expectation as a non-negotiable element of the superintendent's job; the firms that allow daily logs to be completed retrospectively at the end of a week find that the retrospective logs are thin, incomplete, and unreliable as dispute documentation. The document control discipline is the office-side counterpart, and it lives in the project-management platform's document repository and the related document-management workflow. Contract documents, drawings, specifications, RFIs, submittals, change orders, and the meeting minutes and correspondence that document the project's administration must be stored in the platform's document repository with consistent naming conventions, version control, and metadata that allows retrieval months or years later when a dispute or an audit requires it. The discipline is mostly habit, the project administrator or project manager who uploads documents promptly, names them consistently, and tags them appropriately produces a document trail the firm can rely on. The discipline most commonly degrades when the project-administrator role is under-resourced or when the project manager treats document control as a low-priority task relative to field-execution concerns. The firms whose document control runs cleanly invest in the project-administrator role explicitly and hold the role to a documentation standard that the back-office can rely on. The photo documentation discipline is the visual counterpart to the daily log, and the mid-market platforms have made it operationally trivial: the superintendent or foreman takes photos throughout the day using the project-management platform's mobile app, with the photos automatically tagged with the project, date, location (often by GPS), and the photographer's name. The disciplined firms add the additional metadata that makes the photos useful for retrieval, the area of work, the cost code, the trade, the specific activity, through tag taxonomies that the platform supports. The undisciplined firms accumulate thousands of untagged photos that are technically in the system but practically unretrievable when needed for a specific claim or dispute. The time tracking discipline is the labor-cost source data that feeds the job-cost ledger, and the field-to-office transmission of labor hours is the discipline that decides whether the job-cost ledger is accurate. The disciplined firms use mobile timekeeping tools that capture the hours by job, by cost code, and by labor classification, with the entry happening daily at the worker level or through the foreman's daily review, and the data synchronizing to the payroll and job-cost systems with minimal manual intervention. The undisciplined firms rely on paper timesheets that get submitted at the end of the pay period, with the hours aggregated to the job but not to the cost-code level, and with the cost-code allocation happening in the office on the basis of someone's guess about what work was performed. The cost-code-level allocation accuracy in the job-cost ledger depends entirely on the field-side time-tracking discipline; the firms that get this wrong have job-cost data that is accurate at the job level and noise at the cost-code level, with the predictable downstream effects on percentage-of-completion accuracy and the back-office's ability to learn from one job to the next. The equipment tracking discipline is the analogous source data for equipment costs, and it depends on the field-side discipline of capturing equipment hours, fuel consumption, and equipment-to-job allocations. The platforms support equipment-tracking modules that automate the data capture when the field crews use them, with the equipment-cost data flowing through to the equipment-cost ledger and the job-cost allocations. The discipline is the same in shape as the time-tracking discipline and the same in consequence: the firms that maintain it have equipment-cost data that supports accurate job costing, and the firms that don't carry equipment cost as a poorly-allocated overhead that masks the true job-by-job economics. The data-hygiene baseline that the back-office requires, and that the AI pilot depends on, is the cumulative result of these field-side disciplines maintained consistently across every active job. The firms whose baseline is solid have built the disciplines into the field organization's daily work and have invested in the project-administrator and superintendent roles that enforce the disciplines; the firms whose baseline is degraded have allowed the field organization to treat the back-office's data needs as someone else's problem, with the resulting data fragmentation that defeats AI pilots and degrades every report the back-office produces. Frequently asked questions What is construction back office? Construction back office refers to the administrative, financial, and project-controls functions that support the field-execution side of a construction firm. The back office includes the accounting, AP, AR, payroll, job costing, equipment costing, WIP and financial reporting, contract administration, change-order processing, billing, retainage management, surety and bonding administration, lien-compliance workflows, document control, and the project-controls disciplines that connect the field execution to the financial accounting. In mid-market construction firms, the back office typically employs ten to fifty people depending on revenue scale and operational complexity, with the back-office headcount-to-revenue ratio varying meaningfully across firm types (general contractors typically run leaner back-office ratios than self-perform contractors with heavy field-labor and equipment-cost-tracking needs). What's the best construction software for mid-market? There is no single best construction software for mid-market firms, and the firms that ask the question that way typically end up with selections they regret. The selection question splits into three categories, project management and operations, financial accounting and job costing, and integrated suites, and the best platform in each category depends on the firm's contract types, scale, geographic footprint, back-office maturity, and integration tolerance. The most common mid-market commercial construction stack in 2026 is Procore for project management plus Sage 300 CRE or Foundation Software for financial accounting, with the integration between the two platforms decided by the implementation discipline. The Autodesk Construction Cloud alternative is increasingly competitive for Procore in the project-management category, particularly for design-build firms and firms already invested in Autodesk's design-side tooling. We treat the head-to-head selection matrix in dedicated detail. Procore vs Autodesk, which to pick? Procore and Autodesk Construction Cloud are the two principal project-management platforms for mid-market commercial construction in 2026, and the selection between them is decided by a small number of dimensions. Procore typically wins for general contractors with diverse subcontractor portfolios, for firms that value the platform's network effect with owners and architects, and for firms whose preconstruction workflow doesn't depend heavily on the Autodesk design-side tooling. Autodesk Construction Cloud typically wins for design-build firms, for firms whose preconstruction and BIM-coordination workflow already runs on Autodesk Revit and BIM 360, and for firms that value the design-to-construction continuity that the Autodesk stack provides. Both platforms are competent across the construction-execution feature set; the selection should be made on the basis of the firm's specific operating profile, the integration story with the firm's financial-accounting platform, and the implementation partner's quality. How do change orders work in construction accounting? Change orders are written modifications to a construction contract that adjust the scope, the price, the schedule, or any combination. In construction accounting under ASC 606, approved change orders are added to the contract's transaction price as of the approval date, with the percentage-of-completion calculation adjusted to reflect the revised contract value. Unapproved change orders and claims are included in the transaction price only to the extent that the firm has documented evidence that approval is highly likely and the amount is reasonably estimable, with the "probable, no significant reversal" constraint that ASC 606 imposes on variable-consideration recognition. The accounting treatment is downstream of the change-order workflow's documentation discipline, change orders that are documented contemporaneously through the project-management platform with the supporting cost and schedule analysis produce recognition that survives audit; change orders that are documented poorly produce audit findings on the variable-consideration treatment. What's percentage-of-completion accounting? Percentage-of-completion is the principal revenue-recognition method used in construction for long-duration contracts, under which revenue is recognized as the firm's performance progresses against the contract rather than waiting for the contract to be completed. Under ASC 606, percentage-of-completion accounting applies when the firm's performance obligation is satisfied over time, which is the case for most construction contracts because the firm's performance creates real property that attaches to land the customer owns, or because the firm's performance creates a specific asset with no alternative use and the contract provides an enforceable right to payment for work completed. The progress measurement is most commonly the cost-to-cost input method: percentage of completion equals costs incurred to date divided by total estimated costs at completion, and earned revenue equals the percentage multiplied by the transaction price. What is a WIP schedule? A WIP (work-in-progress) schedule is the project-by-project summary of every active construction contract the firm is performing, showing for each contract the contract value, the costs incurred to date, the total estimated costs at completion, the percentage of completion, the earned revenue, the billings to date, the over- or under-billing position, and the gross profit earned. The WIP is the report that ties the job-cost ledger to the financial statements, supports the percentage-of-completion revenue recognition the auditor tests, and provides the surety underwriter with the principal view of the firm's contract-portfolio exposure and management discipline. The mid-market construction firms whose back-office runs cleanly produce the WIP monthly as part of the close cycle, with the controller and the CFO reviewing the schedule before it is finalized. Why do construction AI pilots fail? More than eighty percent of construction AI pilots fail to reach production, and the failure pattern is consistent: data fragmentation across spreadsheets, email, scheduling tools, ERPs, project-management platforms, and field apps prevents the AI from accessing the data it needs in a form it can reliably use. The AI itself is rarely the bottleneck; the firm's data hygiene is. The successful pilots share a set of preconditions, firm-wide cost-code standardization, change-order workflow discipline, daily-log completeness, document-control hygiene, and ERP-integration synchronization, that the failed pilots typically lack. Firms planning AI investments should evaluate the data-hygiene baseline first and the AI capability second. How much does Procore cost? Procore's pricing for mid-market construction firms is tied to the firm's annual construction volume rather than to user count, with the pricing model producing an annual cost typically ranging from roughly forty thousand to one hundred fifty thousand dollars at the lower end of the mid-market and significantly higher at the upper end. The exact pricing depends on the modules selected (the base platform plus the optional modules including Procore Analytics, Procore Capital, Procore Pay, and the specialty modules), the firm's volume tier, the contract length, and the discount the firm negotiates. Procore's pricing model is unfavorable for firms with high revenue per user, because the pricing scales with volume rather than with the number of people using the platform; firms with low revenue per user (typically heavy self-perform contractors with large field organizations) get more favorable economics from the model. Total cost of ownership includes the platform license plus implementation services (typically thirty to one hundred fifty thousand dollars for mid-market implementations), integration costs to the financial-accounting platform, and ongoing administration and training. What is AIA billing? AIA billing is the industry-standard progress-billing format embodied in the AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) documents maintained by the American Institute of Architects. AIA billing requires the firm to produce, each billing cycle, a schedule-of-values continuation sheet that breaks the contract down by line item, shows the work completed to date and this period, the materials stored, the retainage withheld, and the amount due, with the application submitted to the architect for review and certification before the owner releases payment. Most commercial construction contracts require AIA-format billing, and the firms that bill AIA-format on most of their work integrate the billing discipline with the GL close to produce applications that pass the architect's review on the first cycle rather than requiring rework. What is retainage? Retainage is the contractual practice under which the owner withholds a percentage of each progress payment, typically five to ten percent, until substantial completion of the contract, with the retained amount released after the completion of the punch list, final lien releases, and any required closeout documentation. Retainage creates a receivable balance on the firm's balance sheet that ages differently from ordinary receivables, with retainage balances aging months past the work itself, and the firm's back-office requires a separate aging discipline for retainage to manage the closeout cycle and to surface stale retainage balances that require active collection effort. Where to go deeper The disciplines this guide covers are operationally interconnected, and the dedicated guides linked throughout treat each discipline in the depth that the mid-market construction back-office requires. The Procore-versus-Sage-versus-Foundation selection matrix treats the construction-software selection question in head-to-head detail, with the implementation-pain-point analysis the demo doesn't surface. The ASC 606 percentage-of-completion guide treats the revenue-recognition standard's application to construction contracts and the audit-side testing that determines whether the firm's documentation is defensible. The job-cost discipline and project-controls guide treats the integration between project management and financial accounting and the controls infrastructure that makes the two-platform stack actually function. The change-order management documentation guide treats the workflow and documentation discipline that produces change-order recognition that survives audit and dispute documentation that survives litigation. The WIP schedules and bonding-agent guide treats the WIP discipline and the surety-relationship management that decides the firm's bonding capacity. The construction-AI pilots and data hygiene guide treats the AI-readiness assessment and the data-hygiene baseline that decides whether AI pilots reach production. The adjacent back-office disciplines that mid-market construction firms share with other mid-market industries are treated in the broader Securem field-guide library. The thirteen-week cash-flow operational rhythm is the cash-management cadence that construction firms with significant working-capital cycles depend on. The mid-market ten-day close reference calendar is the close-cycle discipline that supports the monthly WIP and the financial-reporting cadence the back-office runs on. The intercompany close-cycle bottleneck guide is relevant for multi-entity construction firms with separate corporate entities for distinct business units or joint ventures. The account-reconciliation hygiene evidence-pack guide is the controls discipline that supports clean audits and the surety underwriter's confidence. The accrual-discipline mid-market mistakes guide treats the accrual practices that affect job-cost accuracy at month-end. The ASC 842 lease-accounting implementation guide is relevant for construction firms with significant equipment leases, real-estate leases, or right-of-use assets that the standard now requires on the balance sheet. The board-reporting-decisions-not-status guide treats the executive reporting discipline that connects the back-office's operational reporting to the board's governance role. The finance-transformation-needs-systems-integrator guide is relevant for firms planning a back-office systems transformation that exceeds the scope of in-house implementation. The five-layer AI compliance-stack guide is the compliance and governance framework for firms scaling AI adoption across the back-office and project-execution workflows. The firms whose back-office runs at the standard the mid-market construction segment now requires built the disciplines deliberately over a multi-year horizon, with the cost-code structure, the change-order workflow, the WIP discipline, the ASC 606 application, the field-office handoff, and the data-hygiene baseline each addressed as a first-class operational investment rather than as a project-level afterthought. The firms whose back-office lags treat the same disciplines as compliance overhead and pay for the gap in audit findings, bonding-capacity compression, failed AI pilots, and the constant rework that an under-disciplined back-office generates. The Securem twenty-one-day diagnostic is the engagement format we use to assess where a mid-market construction firm sits across these disciplines and where the highest-leverage investments are for the firm's specific operating profile.