Output Method vs. Input Method for Revenue Recognition Over Time

Under ASC 606, when a company satisfies a performance obligation over time (rather than at a point in time), it must measure how much of the promised good or service has been delivered. The output method measures progress based on the amount of value transferred to the customer (e.g., units delivered, milestones achieved, hours worked). The input method measures progress based on the effort or resources consumed to date (e.g., costs incurred, labor hours spent). Both are valid; the choice depends on which metric best reflects the underlying economic substance of the contract.

The ASC 606 recognition test

ASC 606 requires three conditions for revenue recognition over time:

1. The customer receives and consumes the benefit as the company performs (e.g., a tailored service is consumed immediately).
2. The company’s performance creates an asset the customer controls (e.g., a partially completed custom asset).
3. The company has the right to payment for performance to date (e.g., a right to progress payments).

Once the company qualifies to recognize revenue over time, it must choose between output and input methods—a choice that directly affects the timing and pattern of reported revenue.

The output method: measuring value delivered

The output method recognizes revenue as the company delivers tangible results the customer can observe or measure:

Examples of output metrics:

• Units delivered or installed (per item, per percentage of total units).
• Milestones achieved (design phase 100%, build phase 75%, testing 30%).
• Hours of service delivered (contract promises 1000 hours; 250 delivered = 25% progress).
• Physical progress (in construction, the weight of steel erected, footage of wall installed).
• Customer acceptance or inspection passes.

Calculation:

Revenue to recognize = (Output completed to date / Total output) × Total contract price

Illustration: A software integration firm is hired to integrate three third-party systems into a client’s platform, earning $300,000 total. The contract allows the client to use and benefit from each integration immediately upon completion.

• System A integration: 40% complete; Value: $120,000 (40% × $300,000).
• System B integration: 0% complete; Value: $0.
• System C integration: 0% complete; Value: $0.
• Revenue to recognize in period: $120,000.

Output is straightforward here because the output (completed integrations) is observable and contractually agreed.

The input method: measuring effort and cost

The input method recognizes revenue in proportion to costs or effort incurred. It is appropriate when inputs correlate reliably to the customer’s satisfaction or when output is less observable:

Examples of input metrics:

• Actual costs incurred divided by budgeted total costs.
• Labor hours worked divided by estimated total labor hours.
• Machine hours operated divided by total estimated operating hours.
• Physical effort (weight of materials, cost of materials consumed).

Calculation:

Revenue to recognize = (Inputs to date / Total estimated inputs) × Total contract price

Illustration: A consulting firm signs a one-year engagement for strategic advisory at $200,000, billing time and materials. The consulting is ongoing and not tied to specific milestones. The engagement is expected to consume 2000 labor hours.

• By month 3, 450 labor hours have been worked.
• Progress: 450 ÷ 2000 = 22.5%.
• Revenue to recognize: 22.5% × $200,000 = $45,000.

The input method works here because the consultant’s time is the primary value; progress cannot be easily tied to external milestones.

Choosing between the two: practical guidance

Favor output method if:

• The contract specifies quantifiable deliverables or milestones (units, phases, stages).
• The customer can directly measure and observe progress (construction, installation, delivery).
• Output units are contractually defined and easily traceable.
• Delays in payment are unlikely to correlate with progress measurement errors.

Favor input method if:

• Progress is best measured by resources consumed (labor, materials).
• Output is continuous and not easily segmented into discrete units (consulting, ongoing maintenance).
• The contract is cost-plus or time-and-materials; inputs directly drive billing.
• Service quality or customer satisfaction is the primary measure, not discrete deliverables.
• Historical data supports a strong correlation between inputs and progress.

Volatility and estimation risk

Both methods carry estimation risk:

Output method volatility: If the company initially estimates total output at 1000 units but later discovers the true final count is 1200, it must reestimate and adjust prior-period revenue. A large revision signals to investors that the company over- or under-estimated progress, damaging credibility.

Input method volatility: If the company initially estimates 2000 total labor hours but the work is 60% complete at 1500 hours, it must reestimate remaining effort. If actual efficiency improves (fewer hours than expected), revenue is pulled forward; if efficiency declines, revenue is pushed backward. This can mask operational performance.

Blended and hybrid approaches

Some contracts use hybrid methods:

• Milestone + input: A software development contract pays $50,000 upon code completion and $50,000 upon acceptance testing. The first $50,000 is output-based (binary milestone); the second uses input methods (% of test cases passed).
• Multiple performance obligations: A construction contract recognizes revenue for the structure (output: % complete by square footage) and for ongoing warranty service (input: years elapsed).

In each case, the company must clearly map the contract’s terms to the appropriate method per performance obligation.

Common pitfalls

Overstating inputs as output: If a contract is truly time-and-materials (input-based), the company cannot switch to output-based recognition just because it has paid for labor hours. The economic substance of the contract determines the method, not convenience.

Revising estimates too liberally: Small revisions to total output or inputs are normal; large, frequent revisions suggest weak contract understanding and invite auditor scrutiny.

Mixing methods across similar contracts: If two contracts are economically similar, the company must use the same method. Inconsistency is a red flag for revenue manipulation.

Ignoring performance obligations: Some contracts contain multiple performance obligations. Each must be recognized separately using the method that best reflects its economics. Bundling dissimilar obligations masks the pattern of revenue.

Disclosures required

Under ASC 606, the company must disclose:

• Which method(s) it uses for each significant contract type.
• Why that method was chosen.
• How it measures progress (units, labor hours, costs, milestones).
• Significant estimates and revisions made during the period.
• Any judgment applied in determining which obligations are satisfied over time versus at a point in time.

Clear disclosure helps investors and auditors understand the basis for reported revenue and assess the risk of future revisions.

See also