How project-centric companies authorize, budget, execute, and integrate pre-contract work without destroying their cost baseline, margin visibility, or revenue recognition integrity.
Every project-centric company has felt the squeeze: the customer needs work to start now, but the contract isn't signed yet. Sometimes you get a Limited Notice to Proceed. Sometimes you just get a verbal commitment and a prayer. Either way, work happens before the money is officially on paper. The financial, operational, and accounting implications are real. This paper walks through the end-to-end lifecycle of pre-contract work execution: how to authorize it, how to budget it, how to run it, and how to fold it into the executed contract without creating a margin-destroying accounting mess. Whether the pre-contract spend eventually becomes billable or gets absorbed as cost of performance, you need a clean plan from day one.
Pre-contract work execution is a reality across every project-centric industry. If your company recognizes revenue over time against contracts or project agreements, this paper applies to you.
The specifics vary by industry and contract type, but the core challenge is universal: you're spending money before the contract that funds that spend is finalized. The accounting treatment, governance framework, and integration mechanics follow the same playbook.
Pre-contract work falls into two distinct categories. They share a common problem, but carry different risk profiles, authorization levels, and financial treatment.
Work performed by the contractor at their own financial risk, typically before contract award, with no formal customer authorization. The contractor bears 100% of the cost exposure. It's a strategic bet: you start early to hold schedule, protect the customer relationship, or maintain competitive position, knowing the spend may never be recoverable.
A written authorization from the customer directing the contractor to begin a defined scope of work prior to full contract execution. The LNTP establishes a cost ceiling, a scope boundary, and a customer obligation to reimburse allowable costs incurred within those limits. It carries contractual weight.
| Dimension | At-Risk Work | LNTP |
|---|---|---|
| Authorization | Internal management decision | Written customer authorization |
| Cost Exposure | 100% contractor risk | Customer-funded up to ceiling |
| Scope | Contractor-defined; discretionary | Customer-defined; bounded |
| Cost Ceiling | Internal budget only | Not-to-exceed (NTE) amount specified |
| Contractual Standing | No enforceable right to recover | Binding; creates a reimbursement obligation |
| Revenue Recognition | No revenue until contract executed | Revenue recognizable against LNTP performance |
| Typical Duration | Weeks to months | 30–120 days (usually specified) |
At-risk work that never converts to a contract is a direct hit to your P&L. Every dollar of at-risk spend should be tracked with the same rigor as contracted work. The audit trail matters whether you recover the cost or not. Sloppy tracking creates problems in both directions: it makes recovery harder if the contract lands, and makes the write-off harder to defend if it doesn't.
Starting work before a contract is signed isn't just a financial decision. It's a governance decision. The authorization framework must be airtight. If things go sideways, the paper trail is the only thing between your CFO and a very bad quarter.
Regardless of whether the work is at-risk or LNTP, you need a formal internal approval process. It is the single most important control in the pre-contract lifecycle.
When an LNTP is received, the Contracts or Legal team must validate several additional elements before work begins:
Scope alignment: Does the LNTP scope match the proposal scope, or is it a subset? Any delta must be documented and priced.
NTE ceiling adequacy: Is the authorized ceiling sufficient to cover the planned burn rate for the LNTP period? If not, the PM must re-scope or request a ceiling increase.
Terms flow-down: Do the LNTP terms reference the anticipated contract terms (liability, IP rights, insurance, warranties)? Gaps here create exposure at contract execution.
Period of performance: Is the LNTP duration realistic given the expected contract execution timeline? Build in buffer.
The budgeting approach for pre-contract work often gets treated as temporary, with lightweight tracking that creates problems downstream. When the contract executes, Finance is left reconciling two cost baselines into one coherent EAC. The better approach is to structure the budget and cost accumulation correctly from day one so that integration is a clean handoff, not a reconstruction project.
Pre-contract work must be tracked in a project structure that mirrors the anticipated contract WBS. Two reasons this matters: (1) clean integration at contract execution, and (2) audit readiness if the costs become billable or are reviewed by external auditors.
The X.PRE structure allows all pre-contract costs to be accumulated in dedicated project elements that can later be either (a) reclassified into the contract project structure at execution, or (b) closed out and absorbed as period cost or allocated to cost of goods sold.
The budget baseline is the NTE ceiling from the LNTP instrument. The PM manages to this ceiling with the same rigor as a fully executed contract. Cost and schedule tracking must be formal, even if full earned value management is not required.
ASC 606 NTE Controls
The budget is internally authorized via the WAD. It represents the maximum exposure the company is willing to absorb if the contract never materializes. This is effectively a pre-contract investment decision and should be governed with the same rigor as any capital allocation.
WAD Controls Internal Budget
Even for at-risk work, set up budgets by cost element: direct labor by skill mix, subcontractor, materials, travel, and other direct costs. If this work becomes billable, you'll need cost element detail to support invoicing and audit. If it doesn't become billable, you'll need it for accurate project post-mortem and overhead allocation.
Once authorized, pre-contract work must be executed with the the same cost discipline as a signed contract. More, actually. The margin for error is thinner and the consequences of overrun are less forgiving.
Integration at contract execution is where the upfront discipline pays off. Without a planned transition path, Finance ends up reconciling two separate cost baselines into a single EAC after the fact. The integration approach should be defined before pre-contract work begins, not figured out after the contract is signed.
Reconcile all costs accumulated on the pre-contract project elements. Validate every charge against the WAD scope. Remove or reclassify any costs outside the authorized scope. Produce a clean incurred cost summary by cost element and project element.
Map each pre-contract project element to its corresponding contract WBS element. This is a one-to-one or many-to-one mapping. Never one-to-many. Every pre-contract dollar must land in exactly one contract element. Traceability matters more than convenience.
The contract's cost baseline must reflect the pre-contract actuals as "burned" budget. Earned value for completed pre-contract work is established at contract execution. Remaining budget is allocated to forward work. If pre-contract costs exceed the value allocated to that scope, you're already in a negative margin position. Surface it immediately.
Pre-contract activities become completed milestones in the project schedule. Successor activities and dependencies update. Critical path recalculated. Any schedule risk created during the pre-contract phase gets surfaced in the project risk register.
In the ERP: pre-contract project elements are closed to new charges, actual costs are settled or reallocated to contract project elements via transactional postings, and the contract project is activated with full budget load. Cost element detail, commitment items, and billing plan assignments transfer cleanly. If the WBS was structured correctly upfront, these postings are straightforward. If not, you're looking at manual journal entries and reconciliation work.
The cleanest approach is to create the pre-contract project as a child element of the anticipated contract project in the WBS hierarchy from day one. At contract execution, the pre-contract elements are statistically closed and their accumulated costs settled upward or laterally into the contract WBS. This preserves the audit trail, maintains general ledger integrity, and avoids manual journal entries to move costs between unrelated cost objects.
When the contract executes (or doesn't), the at-risk costs face one of three outcomes. The financial treatment is different for each, and the accounting must be determined before the books close for the period in which the contract executes.
Best case. During contract negotiations, the contractor successfully argues that the pre-contract work was performed at the customer's direction (implicit or explicit) and should be included in the contract value. The pre-contract costs reclassify from the pre-contract WBS to the contract WBS. Revenue is recognized under ASC 606 as part of the overall performance obligation. The EAC reflects these costs as incurred with corresponding budget allocation.
More common. The customer won't pay for the at-risk work separately, but the contract executes. The contractor absorbs the at-risk costs as part of their cost of performance:
Under ASC 606, the at-risk costs become part of the total estimated cost at completion. They reduce the margin on the contract but are recognized proportionally as the performance obligation is satisfied over time (cost-to-cost input method). These costs were incurred before the contract, but they contribute to satisfying the performance obligation and therefore must be included in the EAC used for percentage-of-completion calculations.
Worst case. No contract, no recovery. The at-risk costs are expensed in the period as business development, pre-contract, or bid and proposal expense. It's a direct P&L hit. If the company allocates these costs to an overhead pool, it increases the overhead rate, which flows to all active projects. Double hit: direct cost lost, and indirect rates go up.
The decision to capitalize at-risk costs as WIP (versus expensing immediately) requires a probability assessment that must be documented. Auditors will scrutinize the basis for concluding that contract execution was "probable." Contemporaneous documentation of the probability assessment is essential. That means documenting the competitive landscape, customer communications, and deal status. Retroactive justification does not pass muster.
LNTP integration is mechanically simpler because the costs are already customer-authorized and the accounting treatment is established from day one. But "simpler" doesn't mean "automatic."
Revenue recognition for pre-contract work intersects with ASC 606 in ways that require careful judgment. The core question: when does a performance obligation exist, and how do pre-contract costs relate to it?
An LNTP creates a performance obligation from the date of issuance. Revenue is recognized over time using the cost-to-cost input method, where progress is measured by costs incurred relative to total estimated costs for the LNTP scope. At contract execution, the LNTP performance obligation merges into the broader contract performance obligation, and the cumulative catch-up adjustment (if any) is recorded.
At-risk work creates no performance obligation until the contract executes. No revenue is recognized during the at-risk period. Costs are capitalized as WIP if recovery is probable (i.e., the contract is expected to execute), or expensed immediately if recovery is not probable.
| Outcome | Revenue Impact | Cost Treatment | Margin Impact |
|---|---|---|---|
| Costs become billable | Included in transaction price; recognized over time via cost-to-cost | Reclassified to contract WBS; part of EAC | Neutral (if priced at cost + margin) |
| Costs absorbed (non-billable) | No incremental revenue; total transaction price unchanged | Added to EAC; increases total cost at completion | Negative: margin compression |
| No contract executed | No revenue recognized | Expensed as period cost | Direct P&L hit; potential overhead rate increase |
Your ERP must support the full lifecycle: pre-contract cost accumulation, segregation, integration, and ongoing contract execution. Here's what matters in practice.
| Phase | Configuration Requirement | ERP Module |
|---|---|---|
| Pre-Contract Setup | Dedicated project/WBS with pre-contract status flag; budget profile with NTE controls; separate cost centers if indirect at-risk | Project System Controlling |
| Cost Accumulation | Time entry integration; commitment management for POs and subcontracts; real-time cost reporting against WAD budget | Time Mgmt Procurement |
| LNTP Billing | Milestone or cost-reimbursable billing configuration; billing plan tied to LNTP NTE; rate application | Billing Rev Acctg |
| Contract Integration | Settlement rules from pre-contract to contract WBS; cost reclassification entries; budget reprogramming | Project System Finance |
| Post-Execution | Full project controls structure; revenue recognition events; cost baseline with pre-contract actuals incorporated | Project System Rev Acctg |
Pre-contract work is inherently risky. The companies who do it well share common disciplines.
Pre-contract work isn't going away. Customer timelines will continue to outpace procurement cycles, and contractors will continue to start work before the ink is dry. That's the reality of project-centric business.
The question isn't whether you'll do at-risk or LNTP work. It's whether you'll do it with the financial discipline, governance rigor, and system architecture to protect your company when the contract executes, and when it doesn't.
Set up the controls. Build the WBS right. Track the costs like they matter. Because they do.
Revelation Technologies (RevTech) is an SAP consulting firm specializing in project-centric industries including Aerospace & Defense, Government Contracting, Construction, Engineering, and Professional Services. We help companies design and implement the ERP architectures, financial controls, and project management frameworks that make complex project execution, including pre-contract work, operationally clean and audit-ready. Learn more at revtech.consulting.