Learn how Notice 89-15 guides whether related long-term construction contracts should be aggregated into one contract or severed into separate contracts. Understand how this affects revenue and cost recognition, and when interdependent work is treated as a single project. This clarity helps ensure accounting results reflect the economic reality of project management and financing in construction.

Multiple Choice

Which guidance item is included in Notice 89-15?

The key idea tested is how long-term construction contracts are treated for accounting purposes when there are multiple contracts involved. Notice 89-15 lays out guidance on whether contracts should be aggregated into a single long-term contract or severed and treated as separate contracts. This matters because the method of revenue and cost recognition (such as percentage-of-completion versus other methods) can change depending on whether you view related work as one project or as independent contracts. Why the chosen item fits best: Notice 89-15 explicitly addresses aggregation and severance of contracts. It provides criteria for when multiple contracts should be combined to form one contract for accounting purposes (e.g., when they are interdependent or performed as part of a single project with shared resources) and when they should be treated separately (e.g., when they are distinct, with independent performance and profits). This guidance directly matches the concept being tested. Context to aid understanding: In practice, a builder or contractor might have several related jobs with common management, financing, or interdependent work. Seeing them as one contract can affect when and how much revenue and costs are recognized in each period. If they’re truly independent, they’re separated so each contract’s income is reported separately. Notice 89-15 formalizes these distinctions so accounting results reflect the economic reality of how the contracts are managed and completed. The other topics mentioned are not the focus of this notice—the guidance isn’t about determining or changing accounting methods in general, nor about small home and residential contracts specifically.

When you’re juggling multiple construction jobs, the way you group work can change how you recognize revenue and costs. It’s not just a numbers game—it's about capturing the economic reality of how projects are run, who’s financing them, and how the work pieces fit together. For financial professionals in the construction world, this nuance lives in the guidance found in Notice 89-15. At first glance, the topic might sound dusty, but get a closer look and you’ll see it’s all about the rhythm of projects—whether a cluster of related contracts is treated as one big long-term effort or as several distinct undertakings.

Let’s start with the core question that often comes up: when do you treat multiple, related contracts as a single, aggregated contract, and when do you keep them separate? The answer isn’t a simple yes or no; it’s about criteria, interdependencies, and how the work is managed. Notice 89-15 provides a framework for deciding whether related contracts should be aggregated or severed for accounting purposes. This matters because the accounting method you apply—and the timing of recognizing revenue and costs—depends on how you classify the contracts as one project or multiple projects.

Aggressive near-term revenue recognition, or a more cautious spreading of income and costs? Those decisions hinge on contract grouping. If the related contracts are interdependent and performed as part of a single project with shared resources, it often makes sense to view them as one long-term contract. That perspective can shape the schedule of revenue recognition, potentially aligning it with the overall project progress. On the flip side, if the contracts are distinct—for instance, when they have independent performance, separate management, and profits—treating them as separate contracts may more accurately reflect the economics. Notice 89-15 lays out the criteria for making this distinction so that accounting results tell the true story of the business activity.

Now, you might wonder: what counts as interdependence or independence in practice? The guidance doesn’t rely on a single magic criterion. Instead, it looks at several factors that together signal whether contracts belong in one bundle or stand alone. Interdependence can include shared management structures, common financing arrangements, overlapping resources, or a plan that ties the contracts together into a unified project. If the jobs share a single schedule, common milestones, or a unified cash flow forecast, that’s a clue they’re interwoven. On the other hand, contracts that are clearly separate—distinct locations, separate crews, separate budgets, and independent profit centers—strongly suggest severance.

Here’s a practical way to picture it. Imagine a general contractor who has a large commercial project with multiple related scopes: foundation, building shell, interior fit-out, and parking structure. If these pieces are tightly coordinated, with shared procurement, a single project manager, and a single budgeting system, it’s natural to view them as parts of one contract. Revenue and costs would then be recognized in a manner that tracks progress on the overall project, rather than in neat, isolated chunks. The financial statements would mirror the project’s progression as a whole, acknowledging how changes in one area influence the rest.

Contrast that with a portfolio of smaller, loosely connected jobs—say, a building renovation, a separate site’s facade work, and an adjacent landscaping contract—where each job is managed independently, funded separately, and executed by different teams. In such cases, severing them into separate contracts can present a clearer picture of performance for each endeavor. The timing of revenue recognition, cost accruals, and even the risk exposure would align more closely with the distinct operational realities of each contract.

Notice 89-15 doesn’t merely give a one-size-fits-all rule. It gives a lens—how to evaluate the relationship among contracts and decide on aggregation or severance. The decision should reflect how the contracts are managed and completed in the real world, not just what the numbers look like on a spreadsheet. That alignment between economic reality and accounting treatment helps prevent mismatches that can distort financial results and mislead stakeholders.

Let me explain with a simple analogy. Think of a symphony orchestra. Each instrument group has its own rhythm and melody, yet they often come together to form a single, cohesive performance. If the conductor treats the whole concert as one piece, the timing of entrances, the release of musical phrases, and the interpretation of the overall mood all hang together. But if certain sections are clearly performing separate pieces—perhaps a string quartet that plays a standalone piece during the same concert—the conductor might emphasize their individual identities. Notice 89-15 is like a score that helps you decide whether to treat related contracts as one grand concerto or as a collection of individual tunes. The goal is honesty in the music of numbers—so the financial reporting resonates with how work actually unfolds.

A few practical implications often surface in discussions among construction finance teams. First, the choice affects the method of revenue and cost recognition. Under a single long-term contract view, you might lean toward a percentage-of-completion approach for recognizing revenue as work progresses. This method smooths earnings over the life of the project and can better reflect ongoing performance. If contracts are treated separately, you might see revenue recognized on a different schedule for each contract, potentially leading to more variability in reported earnings. That isn’t about chasing a particular figure; it’s about giving a true picture of the company’s activities month after month.

Second, the decision influences how you handle budgeting and cash flow forecasting. When multiple contracts are aggregated, the budget may be built around a master schedule, with shared resources and interdependencies driving the plan. Delays in one segment could ripple through the rest, so project controls become critical. You’ll want robust earned value management, resource leveling, and contingency planning to keep the aggregated picture accurate. If contracts are severed, budgeting can be more granular at the contract level, allowing for sharper visibility into the performance of each line item and project. The trade-off is the need for more meticulous tracking and cross-contract coordination.

Third, the aggregation decision can affect risk assessment. Grouping contracts can concentrate risk exposure if a single issue—say, a delay in supply of a key material—affects multiple scopes of work. But it can also spread risk in a way that makes sense if the contracts share the same risk profile and mitigation strategies. Severed contracts, meanwhile, can isolate risk to individual projects, which can be a hedge against one problem dragging down the entire portfolio. It’s a balance between interconnectedness and modular flexibility.

In real-world practice, what helps is a disciplined, evidence-based approach to evaluating contracts. Start with a thorough description of each contract: scope, performance obligations, schedules, financing arrangements, and management responsibilities. Then map out the relationships: are there shared resources, common milestones, or interdependent tasks? Do the contracts share a single project manager or a shared procurement pipeline? Are the costs and revenues reported to a central control point or kept separate for each contract? These questions aren’t just academic; they translate into how you present financial results and how you plan for the future.

It’s worth noting what Notice 89-15 does not do. It doesn’t require you to juggle contracts into a single long-term status whenever possible. It provides criteria to guide the decision, but it ultimately depends on the practical arrangement of the work and how it’s managed. In other words, the guidance respects the realities of construction management—the way teams coordinate, how supply chains behave, and how cash flows into and out of projects. The aim is to ensure that accounting faithfully reflects these realities, not just a theoretical construct.

If you’re thinking about the broader landscape of construction accounting, you’ll see how this discussion fits with other principles. For example, when contracts are aggregated, you often need careful cost-to-cost tracking to maintain a reliable measure of progress. This involves keeping a close eye on quantities completed, costs incurred, and revisions to the project scope. It’s about transparency—giving stakeholders a true sense of how the project is performing against its plan. And when contracts are severed, you’re leaning into the discipline of reconciling multiple independent streams of work, each with its own narrative of risk, performance, and profitability.

For students and professionals in the field, this topic is a reminder that numbers don’t exist in a vacuum. They echo the way work gets done on the ground: the teams, the schedules, the funding, and the decisions that shape the project’s life cycle. Notice 89-15 serves as a compass, helping you navigate the gray areas where contracts blur into one another or stand apart as separate efforts. It’s not about clever accounting tricks; it’s about integrity in reporting—ensuring your financial statements tell a story that aligns with the business reality.

A natural takeaway is to cultivate a habit of documenting the rationale behind aggregation or severance decisions. When teams can point to clear criteria—interdependence, shared resources, unified management—and show how those criteria are applied, you’re less likely to encounter disputes or reinterpretations later on. This is especially important in the construction world, where projects can span years and involve a web of subcontractors, suppliers, and financing arrangements. Clear, well-supported decisions help everyone sleep a little easier at night.

Let’s bring this back to the everyday work life of builders, financiers, and project managers. In practical terms, you’re looking for that moment when the work shifts from “a bunch of related tasks” to “one coherent effort.” It’s the moment when you can say, with confidence, that the contracts belong together because they share a common plan, a unified budget, and a single rhythm of execution. Or you acknowledge that while the jobs live under one umbrella, they’re distinct enough to stand on their own, with separate control points and performance metrics. The nuance matters because it shapes the financial heartbeat of the project.

If you’re curious about applying this concept in your organization, start by revisiting your contract portfolio with a fresh pair of eyes. Gather the key data: scope definitions, milestones, shared resources, financing structures, and management arrangements. Then run a few "what-if" scenarios. What happens to revenue timing if we treat these as one contract versus separate contracts? How would the cash flow outlook shift if we lump them together? What if a major risk materializes—how does the aggregation or severance choice amplify or dampen that impact? These questions aren’t just academic exercises; they’re practical probes that help you understand the economic geometry of your projects.

In closing, Notice 89-15 isn’t about piling on more rules; it’s about clarifying how we depict a construction program in financial statements. The choice to aggregate or sever contracts should reflect the lived reality of how work is organized, financed, and executed. It’s a balancing act between cohesion and independence, between a single grand project narrative and a collection of independent performance stories. When done thoughtfully, it yields reporting that’s not only compliant but also genuinely informative—helping stakeholders see the project’s life as it truly unfolds.

If you’re ever in doubt, remember the guiding question: do these related contracts behave like a single, integrated effort, or do they function as separate, independent undertakings? The answer isn’t just about where the revenue sits today; it’s about the story your numbers tell about how the project is built, financed, and brought to life. And that narrative matters—because, at the end of the day, numbers are most meaningful when they mirror reality with clarity and honesty.