Design change control is the formal process of identifying, evaluating, approving, and recording any modification to an approved design before, during, or after construction. Properly implemented, it produces a documented, auditable trail that protects safety, cost, schedule, and regulatory compliance at every stage. Authorities typically draw a hard line between material changes, which require prior approval, and immaterial changes, which may proceed but must still be recorded.
TL;DR:
- Material structural changes must obtain authority approval before work resumes, while immaterial adjustments can be recorded and incorporated later.
- Changes are classified into minor, moderate, and major tiers based on risk, with documentation requirements increasing with the level of impact.
- The five-step workflow includes standardized capture, impact assessment, approval, controlled implementation, and post-implementation review.
- Clear roles and communication protocols prevent unauthorized implementation and ensure every change is properly documented and authorized.
- A risk-based, tiered approach minimizes unnecessary delays and aligns scrutiny with safety and compliance priorities.
Table of Contents
- What design change control covers
- When a change needs authority approval versus when it can just be recorded
- A tiered classification of changes
- Step-by-step change control workflow
- Roles, responsibilities, and stakeholder communication
- Contractual implications and commercial controls
- Risk-based assessment and post-implementation review
- Applied guidance: how Aman implements design change control
- Integrating change control with quality management systems
- Tools and software for managing design change control
- Metrics and KPIs for tracking change control performance
- Common challenges and best practices
- Why disciplined change control matters in regulated design work
- How Aman can help with design change control and authority coordination
- Sources
- FAQ
What design change control covers
Design change control governs any alteration to an approved design after that design has been accepted, whether the alteration originates from a site condition, a client request, a coordination clash, or a regulatory finding. Its purpose is to make sure that no modification bypasses the scrutiny the original design received, while avoiding unnecessary bureaucracy for genuinely trivial adjustments. According to RICS practice guidance, effective change control is a systematic process for identifying, evaluating, approving, and implementing alterations to scope, cost, or timeline, built around standardized submissions and a maintained change register.
Several terms get used interchangeably in practice but carry distinct meanings:
- Design change: any deviation from the approved drawings, specifications, or calculations.
- Variation: a contractually defined instruction to alter the works, usually triggering a price and time adjustment.
- Compensation event: the NEC-specific term for an event entitling the contractor to additional time or money.
- Deviation: a regulatory term, used in statutory submissions, describing a departure from previously approved plans.
Changes surface throughout a project’s life. Pre-contract, they usually reflect design development or value engineering. Post contract, they often arise from buildability issues, site discoveries, or client-driven scope shifts. At handover, late changes tend to concern finishes, commissioning data, or as-built discrepancies that must be reconciled before certification.
When a change needs authority approval versus when it can just be recorded
The distinction between material and immaterial changes determines whether work can continue immediately or must wait for regulatory sign-off. Under Building and Construction Authority guidance, material changes to approved structural plans made during construction require authority approval before the change proceeds, while immaterial changes may continue but must be recorded and incorporated into later submissions. The Building Control Regulations reinforce this split: material deviations require submission of amended plans, and where structural, revised calculations, while immaterial deviations call for record plans and certification by a qualified person or accredited checker.
In practice, the line falls roughly here:
- Material changes: altered load paths, revised foundation design, changes to fire compartmentation, structural member resizing beyond approved tolerances.
- Immaterial changes: minor dimensional adjustments, non-structural partition relocations, finishes substitutions with no load or life-safety effect.
A permit for structural works can be applied for at the same time as, or after, plan approval, but material structural changes still require BCA approval before the change is carried out. That sequencing matters because starting material work ahead of approval exposes the project to stop-work orders and rework.
The qualified person bears the certification burden in both cases. For immaterial deviations, that person signs off on record drawings and confirms no safety impact. For material deviations, the qualified person, often supported by an accredited checker for the relevant structural category, must prepare and submit amended plans before work resumes.
A tiered classification of changes
Not every change deserves the same level of scrutiny, and treating a cosmetic finish swap with the same rigor as a structural resizing wastes time without improving safety. A tiered, risk-based structure, similar in spirit to the graded review approach used in nuclear and aerospace engineering, lets teams match formality to actual risk.
- Minor: no safety, structural, or regulatory impact; limited cost or schedule effect. Action: log in the change register, no formal approval required beyond design-lead sign-off.
- Moderate: some structural, mechanical, or compliance relevance, but within approved tolerances or performance criteria. Action: qualified person review, PE certification where applicable, and record submission.
- Major: safety-critical, structural, fire, or life-safety consequence, or a departure from approved plans beyond tolerance. Action: amended plans, structural calculations where relevant, and formal authority resubmission before implementation.
A practical flow maps each tier to its documentation set: minor changes close with a register entry and internal sign-off; moderate changes close with a PE certificate attached to the record submission; major changes close only once the authority has issued fresh approval and the amended plans are incorporated into the permanent record.
Pro Tip: Set the tier at the point of capture, not after the technical review, so the right level of scrutiny is applied from the outset instead of being retrofitted once work is already underway.
Step-by-step change control workflow
A workable change control process moves through five stages, each with its own documentation and sign-off requirement. Skipping a stage to save time is usually what turns a minor change into a dispute later.
- Capture: the originator completes a standardized change request form recording the trigger, the proposed modification, drawings affected, and an initial tier estimate.
- Impact assessment: the design team reviews technical feasibility, estimates cost and time effect, checks statutory implications, and runs a risk assessment proportionate to the proposed tier.
- Decision: the appropriate approver, determined by tier, either rejects, approves, or escalates the change; approval is recorded with a date, signature, and reference number.
- Implementation: approved changes are issued through controlled documents, revised shop drawings, updated BIM models, or formal site instructions, each carrying a version number tied back to the change reference.
- Verification and closure: the completed change is checked against the approved instruction, as-built records are updated, and the change is closed out in the register with a post-implementation note.
The change request form should capture, at minimum:
- A unique reference number linked to the drawing or specification affected.
- A description of the proposed change and its trigger (site condition, client instruction, design error, coordination clash).
- An initial risk and tier estimate, pending the full impact assessment.
Impact assessment is where most of the technical work happens. It should cover:
- Technical feasibility and compatibility with adjacent systems or structures.
- Cost and time implications, including knock-on effects on other trades.
- Statutory relevance, flagging whether the change crosses into material deviation territory.
Decision gates vary by tier but should always be explicit about who can sign. A design lead might close out a minor change unilaterally; a moderate change typically needs qualified person sign-off; a major change needs both internal technical approval and, where structural or fire-related, external authority clearance before implementation begins. The BCA structural submissions process illustrates how that external clearance step is documented in practice.
Implementation controls matter as much as the decision itself. Every approved change should trigger a new drawing revision, a dated shop drawing where fabrication is involved, and, where temporary works are affected, a specific instruction to the site team rather than a verbal confirmation. Verification closes the loop: quality checks confirm the work matches the approved instruction, as-built records are updated to reflect the final condition, and a short post-implementation review captures whether the change performed as expected or introduced any unforeseen issue.
Roles, responsibilities, and stakeholder communication
Clear ownership prevents the most common failure mode in change control: a change that gets implemented on site before anyone with authority has actually approved it. Each project needs defined roles.
- Qualified person (QP): certifies design compliance and, for structural matters, prepares or endorses amended plans submitted to the authority.
- Project manager: owns the change register, chases impact assessments, and confirms decisions are communicated to all affected parties.
- Contractor: raises change requests arising from site conditions and implements approved changes through controlled documentation.
- Consultant design lead: performs the technical impact assessment and recommends the tier and approval route.
- Accredited checker: independently reviews structural changes falling within categories that require third-party checking.
- Client or owner: approves changes affecting cost, program, or scope beyond the design team’s delegated authority.
Communication protocols should specify timing: a change request raised on site typically needs an initial response within a set number of working days, with the full impact assessment following once the technical review is complete. Submissions to the owner or authority should be packaged as a single coordinated document rather than a scatter of emails, pairing the change request, impact assessment, and recommended tier in one submission. The change register itself becomes the single source of truth, and every entry should close with either a formal written instruction or an acknowledgment confirming no further action is needed.
Contractual implications and commercial controls
How a change is priced and timed depends heavily on which contract suite governs the project. JCT contracts process changes as variations, instructed by the contract administrator and valued against a schedule of rates or by fair valuation. NEC contracts route changes through compensation events, with strict notification windows and a quotation procedure that can bar recovery if deadlines are missed. FIDIC contracts use a variation order mechanism similar to JCT but with its own notice and determination procedure under the engineer’s authority. The terminology differs, but the practical consequence is the same: a change not captured through the correct contractual mechanism risks becoming unrecoverable cost or time.
Estimating cost and time impact accurately at the point of assessment, rather than after the fact, is the single best defense against later disputes. The RICS practice note recommends standardized submission formats and a change register maintained on a monthly cycle, paired with early warning notices under NEC-style contracts to flag cost or time risk as soon as it becomes apparent.
Useful commercial controls include:
- Setting a contractual time limit for submitting change requests after a trigger event occurs.
- Agreeing provisional pricing for urgent changes, with final valuation reconciled later against actual cost.
- Issuing early warning notices the moment a potential change is identified, rather than waiting for full quantification.
Risk-based assessment and post-implementation review
A scaled risk assessment, weighing likelihood against consequence, should accompany every change above the minor tier. Safety-critical items, structural load paths, fire compartmentation, egress routes, deserve the same proportionate rigor regulated industries apply to product lifecycle changes, where quality risk management determines how much scrutiny a change receives relative to its potential impact.
Post-implementation review closes the loop that many change processes skip. It should record whether the change performed as intended, whether cost and time estimates held, and whether any unforeseen interaction emerged with adjacent systems. Metrics worth tracking include approval cycle time, the proportion of changes closed without rework, and the ratio of minor to major changes over a project’s duration.
A subtler risk is cumulative drift: a series of individually minor changes that, taken together, move the built structure meaningfully away from the original design intent. Periodic change audits, reviewing the register as a portfolio rather than item by item, catch that drift before it compounds into a safety or compliance gap.
Pro Tip: Review the change register as a whole every quarter, not just change by change, so a pattern of small deviations gets flagged before it becomes a systemic issue.
Applied guidance: how Aman implements design change control
This tiered process can be applied across structural, facade, and M&E design changes, preparing the documentation each tier requires rather than defaulting to full resubmission for every item.
- Standardized change request forms capturing trigger, drawings affected, and initial tier.
- PE certificates for moderate-tier changes requiring qualified person endorsement.
- Amended plans and structural calculations for major-tier changes requiring authority resubmission.
- A maintained change register tracking status, approver, and closure date for every entry.
Multi-agency coordination, across key authorities, can run through a single point of contact rather than parallel, disconnected submissions, which shortens the back-and-forth that otherwise stalls approvals. 3D BIM and shop drawing production support this by giving reviewers a coordinated, versioned model to assess rather than a stack of disconnected 2D revisions, which speeds the technical review stage that typically consumes the most time in a change submission.
Integrating change control with quality management systems
Design change control works best when it sits inside a broader quality management system rather than operating as a standalone checklist. ISO 9001-aligned firms typically treat the change register as one input into their document control system, so a design revision automatically triggers updates to related procedures, drawings, and inspection records rather than existing in isolation. That integration matters because a change approved in the design office but never reflected in the site quality plan creates exactly the kind of gap that leads to nonconforming work.
A quality management system also gives change control its audit trail. Every approval, certificate, and record plan becomes traceable evidence during an ISO surveillance audit or a regulatory inspection, which matters when an authority later asks for the chain of custody behind a structural modification. The structural engineering checklist approach, where compliance items are verified against a fixed document set, reflects this same principle: change control and quality management share the same underlying logic of defined criteria, documented verification, and traceable sign-off.
Firms running both systems in parallel, rather than integrated, tend to duplicate effort, maintaining a change register in one place and a nonconformance log in another, with no link between them. Tying the two together, so a major-tier design change automatically opens a corresponding quality record, closes that gap and gives both the design team and the quality function the same version of events.
Tools and software for managing design change control
Most mid-size and large projects now manage change control through a mix of document management platforms, BIM coordination tools, and dedicated construction management software, rather than spreadsheets alone, though a well-structured spreadsheet remains a workable starting point for smaller projects. Common Data Environment platforms centralize drawing revisions and change requests so every stakeholder works from the same version, which matters once a project has more than a handful of active changes running at once.
BIM coordination software plays a particular role in change control because a modeled clash or a proposed revision can be tested against the full coordinated model before anyone commits to a physical change on site. That reduces the number of changes that reach the approval stage only to be rejected on buildability grounds. Construction management platforms typically layer a workflow on top, routing change requests to the correct approver by tier and logging timestamps automatically, which removes the manual chasing that otherwise slows moderate and major approvals.
Whichever combination a project chooses, the underlying requirement is the same: a single, time-stamped record of every request, assessment, decision, and implementation step, accessible to everyone who needs to act on it. A tool that cannot produce that audit trail on demand does not meet the bar regulators and auditors expect, regardless of how convenient it is day to day.
Metrics and KPIs for tracking change control performance
Tracking a handful of consistent metrics turns change control from a reactive process into one that improves over time. Approval cycle time, measured from the date a change request is raised to the date it closes, flags bottlenecks at a specific tier or approver. A rising cycle time at the moderate tier, for instance, often points to a qualified person resource constraint rather than a process flaw.
The ratio of minor to major changes over a project’s duration is worth watching too. A project where major changes climb as a share of total changes, rather than falling as design matures, suggests the original design was not sufficiently developed before construction began. The proportion of changes closed without rework is another useful signal: a high rework rate after a change has been “approved” usually means the impact assessment stage is not catching buildability or coordination issues early enough.
Finally, tracking the volume of immaterial changes recorded but never rolled into a formal record submission flags a compliance gap before an authority inspection finds it. None of these metrics require sophisticated software, a maintained change register with consistent date fields is enough to calculate all of them.
Common challenges and best practices
The most frequent failure in design change control is not a missing process, it is an unused one: teams draft a change register template at project kickoff and then abandon it once schedule pressure builds, reverting to verbal instructions and email threads that leave no audit trail. The fix is procedural discipline rather than a better template: make the change register the only accepted route for authorizing a design modification, with no exceptions for urgency.
A second recurring challenge is tier misclassification, where a change gets logged as minor to avoid the formality of a moderate or major review, often under schedule pressure. Assigning tier classification to the design lead or qualified person, rather than the party requesting the change, removes the incentive to under-classify.
Communication gaps cause the third common problem: a change approved by the design team never reaches the site team, or reaches them without the updated drawing reference. Packaging every approval with its implementation instruction, rather than issuing the two separately, closes that gap. Finally, treating post-implementation review as optional means lessons from one change never inform the next. Building a short review step into the closure stage, even a few lines in the register, is enough to start capturing that feedback consistently.
Why disciplined change control matters in regulated design work
In regulated design work, the projects that run into trouble are rarely the ones with the most changes. They are the ones where changes went unrecorded, misclassified, or implemented ahead of approval. A disciplined, tiered process costs little in overhead and returns real protection: fewer disputes, fewer stop-work orders, and a defensible record when an authority or a client asks how a decision was made. That discipline, not the absence of change, is what keeps a regulated project safe and on schedule.
— Aman
How Aman can help with design change control and authority coordination
Teams managing design changes on structural, facade, or M&E scopes often need a consultancy that can run the technical assessment and the statutory submission together, rather than handing those off separately. Aman Engineering Consultancy provides authority approvals, PE endorsements, and project management support for teams implementing change control on active projects, alongside 3D BIM and shop drawing production to speed the technical review stage.
Consultancies work with property developers, construction firms, and building owners on statutory submissions, inspections, and design coordination across structural, facade, and M&E disciplines. For teams facing a material change that needs authority resubmission, or a project that needs its change control process set up correctly from the start, request a consultation through Aman Engineering Consultancy to scope the submission and coordination work involved.
Sources
- Change control and management (RICS practice information)
- Permit for structural works | Building and Construction Authority
- Building Control Regulations 2003 – Singapore Statutes Online
FAQ
What are the types of change control?
Change control generally splits into material and immaterial changes, distinguished by whether the modification affects safety, structural performance, or regulatory compliance. Many regulated industries further split changes into tiers, commonly minor, moderate, and major, to match review formality to risk level.
What is change control in a project?
Change control in a project is the systematic process of identifying, evaluating, approving, and recording any alteration to the approved scope, design, cost, or timeline. According to RICS guidance, it relies on standardized submissions and a maintained change register to reduce disputes and rework.
What are the six steps in the change control process?
A typical change control process covers capture, impact assessment, decision, approval, implementation, and verification and closure. Each step produces its own documentation, from the initial change request form through to updated as-built records at closeout.
What are the ICH guidelines for change control?
ICH Q10 recommends a risk-based approach to change management in regulated product lifecycles, where the level of review and documentation scales with the potential impact of the change. This same proportionate, tiered logic underpins graded review approaches used in other regulated design and engineering sectors.
When does a design change require authority approval?
A design change requires prior authority approval when it is material, meaning it affects structural performance, safety systems, or other regulated aspects of an approved plan. BCA guidance confirms that immaterial changes may proceed without prior approval but must still be recorded and included in later submissions.