.NET Domain-Driven Design with C#: Problem – Design – Solution

Chapter 9. Construction Change Directives

In the last two chapters, I covered Proposal Requests and Change Orders, and in this Chapter I will be showing you the last of the Change Order–related concepts, the Construction Change Directive.

The Problem

Sometimes a Change Order will be approved and signed off on by the Architect and the Owner, but not by the Contractor. The Contractor may not agree with the change in work, contract price, contract time, or both. This type of Change Order will be signed by the Owner and Architect but not by the Contractor. When this happens, the Contractor is obligated to go ahead with the work, with the price and time adjustments to be determined later by the Architect, utilizing standard industry guidelines.

The means to capture this type of change is the Construction Change Directive. At any time that the contractor later agrees to its terms or mutual agreement is obtained by adjustment of its terms, it is then turned into a Change Order. In the event that the contractor finds it impossible to accept the Architect's determination of changed cost and time, the Contractor's only other alternative at that point is mediation and arbitration.

Like RFIs, Proposal Requests, and Change Orders, each Construction Change Directive should also be serially numbered by Project.

The Design

In the SmartCA domain, a Change Order is one of the most important concepts for the entire application, and it also contains several important business concepts that must be closely ...