All Courses
Upcoming Course Dates
Professional Courses
Academy & Short Courses
IPM Courses
PMI Courses
IPMA Courses
Prince2 Courses
Corporate Training
Corporate Partnership
Strategic Partnership
IPM Competency Pathway
Growth Partner
Certification Overview
IPM Certification
IPMA Certification
PMI Certification
PRINCE2® Certification
About IPM Hub
IPM Membership
EMEA Monthly Events
Mentorship Programme
IPM Jobs Portal
All Insights & Resources
Expert Insights
Ebooks, Templates, and Toolkits
Publish Your Work
Who We Are
Faculty of Excellence
Global Advisory Board
Become a Lecturer or Volunteer
Become an Intern or Student Partner
Speak to an Advisor
hamburger__close
If you’ve ever watched a straightforward project spiral into chaos because someone “just made a small change” without telling anyone, you’ve experienced the cost of poor change control.
In Ireland’s project-driven economy (from construction programmes transforming Dublin’s skyline to pharmaceutical validations in Cork’s manufacturing hubs, from software releases in Galway’s tech sector to public infrastructure upgrades nationwide) changes are inevitable. Requirements evolve. Stakeholders request additions. Issues force modifications. Technology advances. Regulations update.
The question isn’t whether your project will face changes. It’s whether you’ll manage them effectively or let them derail your schedule, budget, and team morale.
Change control provides the answer. It’s the structured process ensuring that every modification to your project baseline gets properly evaluated, approved, documented, and communicated before implementation. It’s the difference between controlled adaptation and chaotic disruption.
The reality? Projects without formal change control processes are six times more likely to exceed budgets and timelines than those with robust change control systems.
Change control is the systematic process through which all requests to modify a project’s approved baseline are captured, evaluated, and then approved, rejected, or deferred. It ensures that changes serve the project’s interests rather than undermining them.
This definition contains several critical elements often misunderstood by Irish project managers:
Your project baseline is the approved version of your project plan that includes:
Scope baseline: What deliverables, features, and work the project will produce, documented in the project scope statement, work breakdown structure (WBS), and WBS dictionary.
Schedule baseline: When the work will be completed, captured in your approved project schedule showing activities, dependencies, durations, and milestones.
Cost baseline: How much the project will spend, reflected in your approved budget showing allocated funds across work packages and time periods.
Quality baseline: What standards the deliverables must meet, specified in your quality management plan and acceptance criteria.
Once your project sponsor and key stakeholders approve these baselines, they become the reference point for measuring performance. Any modification to these baselines requires formal change control.
When Irish Water approved its National Water Resources Plan, they established baselines for scope (which infrastructure upgrades), schedule (phased implementation through 2050), and budget (estimated investment requirements). Subsequent modifications(adding projects, accelerating timelines, or increasing budgets)all triggered change control procedures rather than happening informally.
This distinction particularly confuses Irish project managers because both address “change” but focus on entirely different dimensions:
Change control is a project management process managing technical modifications. When Transport Infrastructure Ireland needs to modify the route of a proposed greenway due to environmental concerns, change control evaluates the impact on scope, budget, schedule, and risks, then follows approval procedures. It’s about managing modifications to project parameters.
Change management is an organisational capability managing human adaptation. When the HSE implements new electronic health records across hospitals, change management helps clinicians adjust behaviours, learn new workflows, and adopt the technology. It’s about managing transitions in how people work.
You need both. Change control prevents unauthorised technical modifications. Change management ensures authorised changes get adopted. When CRH restructured its European operations, they needed change control to manage project modifications (timelines, budgets, scope adjustments) and change management to help employees navigate the organisational transition (new reporting lines, different processes, cultural shifts).
Without proper change control, Irish projects face predictable problems:
Scope creep: Small additions accumulate into massive scope expansion. What started as a simple website redesign becomes a complete digital ecosystem overhaul; with no additional budget or time allocated.
Budget overruns: Untracked changes consume resources without corresponding budget increases. By the time you realise you’re over budget, you’ve made commitments that can’t be easily unwound.
Schedule delays: Each change introduces work not originally planned. Multiple uncontrolled changes compound into significant delays that couldn’t have been predicted from any single modification.
Resource conflicts: Teams working on unapproved changes can’t work on planned activities. Priorities become unclear, conflicts emerge, and productivity suffers.
Quality problems: Rushed changes implemented without proper assessment often introduce defects, create technical debt, or fail to meet requirements.
Stakeholder confusion: When different people work from different versions of requirements, scope, or specifications, miscommunication and rework become inevitable.
Accountability gaps: Without formal approval processes, no one takes responsibility for change consequences. When problems emerge, finger-pointing replaces problem-solving.
Consider a recent Irish example: A County Council approved a €2 million community centre renovation. Without rigorous change control, stakeholder requests accumulated(additional meeting rooms, upgraded AV systems, expanded parking, sustainable features. Each seemed reasonable individually. Collectively, they represented €800,000 in additional scope with no budget increase. The project stalled mid-construction whilst funding solutions were sought. Proper change control would have forced explicit decisions about each addition)either increase the budget, descope something else, or reject the change.
Whilst variations exist across organisations and methodologies, effective change control follows a consistent pattern. Here’s the process Irish project managers should implement:
Change control begins when someone identifies a needed or desired modification. This could come from anywhere:
Stakeholders requesting additional features or different functionality Team members discovering better approaches or identifying problems Sponsors adjusting priorities based on business conditions External factors like regulatory changes or market shifts Project managers recognising risks or issues requiring scope adjustments
The critical requirement: changes must be formally requested, not just discussed informally or implemented without documentation.
A proper change request form captures essential information:
When Dublin Airport Authority needed to modify terminal expansion plans due to passenger growth projections exceeding expectations, they didn’t just informally discuss it in meetings. They submitted formal change requests documenting the required modifications, business justifications, and preliminary impact assessments.
Every change request(regardless of its apparent merit or urgency)must be logged in a change control register (also called a change log).
This register serves as the single source of truth for all proposed, approved, rejected, and deferred changes. At minimum, it tracks:
The act of logging serves multiple purposes: it creates accountability, prevents duplicate requests, enables tracking of all modifications, and provides an audit trail for project governance.
Irish organisations subject to regulatory oversight(pharmaceutical manufacturers, financial institutions, healthcare providers)find robust change logs particularly valuable during audits and inspections. When the Health Products Regulatory Authority reviews medical device manufacturing processes, comprehensive change control documentation demonstrates compliance with quality management requirements.
Before investing significant effort in detailed analysis, conduct a quick initial assessment determining whether the change warrants further investigation.
This triage process asks basic questions:
Is this change within project scope? Some “change requests” are actually just clarifications or details within approved scope. These don’t require change control; they require good communication.
Does this clearly conflict with approved objectives? Some changes are obviously misaligned with project goals and can be rejected quickly without detailed analysis.
Is this change even feasible? Some requests violate constraints (regulatory requirements, physical limitations, technical impossibilities) making them non-starters.
Is this urgent enough to interrupt current work? Not all changes need immediate attention. Some can be deferred to future phases or releases.
The goal isn’t to approve or reject changes at this stage, but to determine whether they merit detailed evaluation. Quick rejection of clearly inappropriate changes saves time. Fast-tracking of obviously beneficial changes accelerates improvement.
When Bank of Ireland receives change requests for their mobile banking app, their product team conducts rapid triage. Requests for features clearly outside regulatory compliance get rejected immediately. Requests aligning with strategic priorities and technical feasibility move to detailed assessment. This prevents wasting effort analysing changes that obviously won’t proceed.
For changes passing initial assessment, conduct thorough analysis examining implications across all project dimensions:
Scope impact: What additional work is required? What existing work becomes unnecessary? How do deliverables change?
Schedule impact: How much time will implementing this change require? Which activities are affected? Will critical path shift? Does this delay the finish date?
Cost impact: What are the direct costs (labour, materials, equipment)? What indirect costs (overhead, administration, support)? Where will funding come from?
Quality impact: How does this change affect deliverable quality? Are new quality standards required? Do testing requirements change?
Resource impact: What skills and capacity are needed? Are resources available? Will this create conflicts with other work?
Risk impact: What new risks does this change introduce? Does it mitigate existing risks? How does the overall risk profile change?
Stakeholder impact: Who is affected by this change? How significantly? What communication and engagement are needed?
Dependency impact: What other projects, systems, or processes does this affect? Are there integration implications?
This assessment requires input from subject matter experts across relevant domains. A change to construction specifications needs input from engineers, quantity surveyors, contractors, and safety professionals. A change to software requirements needs input from developers, testers, business analysts, and end users.
When ESB Networks needed to modify specifications for smart meter rollout due to supplier issues, their impact assessment revealed effects beyond just the technical specifications; installation timelines, training requirements, customer communications, regulatory reporting, and integration with existing systems all needed adjustment. This comprehensive assessment enabled informed decision-making about whether and how to proceed.
Based on the impact assessment, the project manager or change analyst makes a recommendation: approve, reject, or defer the change request.
The recommendation should clearly articulate:
This recommendation then goes to the appropriate decision-making authority, which varies based on change magnitude:
Project manager may approve minor changes within delegated authority (e.g., modest schedule adjustments that don’t affect major milestones or require additional budget).
Project sponsor typically approves moderate changes affecting budget, schedule, or scope within certain thresholds.
Change control board (CCB) reviews and approves major changes exceeding delegated authorities or affecting multiple projects.
Programme board or steering committee approves changes with significant strategic, financial, or risk implications.
The key principle: authority should match impact. Don’t burden senior executives with trivial decisions, but don’t let project teams make major commitments without appropriate governance.
For major Irish infrastructure projects like MetroLink or the National Children’s Hospital, formal change control boards comprising representatives from the project team, client organisation, funding bodies, and technical specialists meet regularly to review change requests. This ensures decisions balance technical feasibility, cost implications, schedule impacts, and strategic priorities.
Whether approved, rejected, or deferred, every change request decision must be documented with clear rationale.
For approved changes:
For rejected changes:
For deferred changes:
This documentation serves multiple purposes: it creates accountability, prevents revisiting settled questions, provides learning for future projects, and satisfies audit and governance requirements.
Irish public sector projects face particular scrutiny. When Citizens Information Board implemented their new case management system, comprehensive change control documentation proved essential during Value for Money reviews, demonstrating that modifications were justified, properly assessed, and appropriately approved.
Approved changes don’t implement themselves. They require:
Updated project plans: Revise schedules, budgets, resource plans, and other project documentation reflecting the approved change.
Work authorisation: Brief team members on the change, clarify what work is now required, and ensure they understand modified priorities or approaches.
Resource allocation: Ensure people, equipment, materials, and funding are available for the additional or modified work.
Progress tracking: Monitor implementation to ensure the change is delivered as approved and produces expected outcomes.
Configuration management: Update all relevant documentation, designs, specifications, and records to reflect the change. Version control is critical; everyone must work from current information.
When Cement Roadstone Holdings implemented approved changes to their digital transformation programme, they didn’t just note the approval and move on. They updated project schedules in Microsoft Project, revised budget allocations in their financial systems, communicated changes through team meetings and documented updates, and ensured configuration management processes captured all specification modifications.
Once implementation completes, verify that:
Then formally close the change request in your change log, updating its status and recording completion dates.
This closure prevents requests lingering indefinitely in “approved but not implemented” status and provides data on change control process performance; how long does assessment take? What’s the approval rate? How often do implementations run into problems?
Based on experience with Irish organisations across sectors, several challenges repeatedly emerge:
This thinking leads project managers to handle “minor” changes informally; a conversation here, a quick email there, no paperwork required.
The problem? Small changes accumulate. What seems insignificant individually becomes substantial collectively. More importantly, you lose visibility into the total change impact. That “minor adjustment” combined with five other “minor adjustments” might represent significant scope growth.
The solution: establish clear thresholds defining what requires formal change control. Perhaps changes affecting budget by less than 1% or schedule by less than one day can be managed informally. Everything else goes through the process. This balances rigour with pragmatism.
When projects fall behind schedule, change control feels like bureaucratic overhead delaying progress further.
The reality? Skipping change control doesn’t save time; it wastes time through rework, confusion, and unintended consequences. The hours spent on proper change control are dwarfed by the days or weeks lost to problems created by uncontrolled changes.
The solution: Streamline your process for genuine urgency. Emergency change procedures can accelerate assessment and approval whilst maintaining essential rigour. But don’t make “emergency” the default; that defeats the purpose.
Some change control boards develop reputations for rejecting everything, creating cultures where people avoid submitting legitimate change requests.
This dysfunction stems from several sources: insufficient education about the board’s purpose, membership lacking appropriate authority or expertise, excessive risk aversion, or disconnection from project realities.
The solution: Ensure your CCB comprises individuals with appropriate authority, expertise, and stake in project success. Train them on their role; not to prevent all change but to enable good changes whilst preventing bad ones. Measure and discuss approval rates. If you’re approving less than 30% of requests, you might be too conservative. If you’re approving more than 90%, you might not be sufficiently rigorous.
Approved changes that aren’t reflected in project plans, specifications, and other documentation create dangerous situations; people work from incorrect information, testing validates against wrong requirements, and deliverables don’t match expectations.
The solution: Make documentation updates mandatory before closing change requests. Include configuration management as an explicit step in your change control process. Use tools that automatically propagate changes across linked documents.
The most serious change control failure: team members or stakeholders implementing modifications without following the process.
Sometimes this stems from ignorance(they don’t understand the process or why it matters. Sometimes it’s impatience)the process feels too slow. Sometimes it’s arrogance; they believe their judgment supersedes governance.
The solution: Training, clear communication about the process, and accountability when violations occur. Make it easy to submit change requests; complicated procedures encourage workarounds. But also make clear that unauthorised changes violate project governance and carry consequences.
When construction firms ignore change control on Irish building projects(implementing modifications requested by clients without formal approval and documentation)they often face payment disputes at project completion. Without proper change orders, they struggle to demonstrate that additional work was authorised and warrants additional payment. This painful lesson reinforces why change control matters.
Implementing robust change control requires more than just creating forms and procedures. Here’s how Irish organisations can build this capability:
Project managers and team members need to understand:
The Institute of Project Management’s Certified Project Management Diploma covers change control as part of comprehensive project management training. For organisations managing complex programmes, the Strategic Project Programme Management Diploma addresses change control at the portfolio level.
Create practical templates and guidelines:
Make these easily accessible; preferably in your project management information system or shared repository. The easier you make compliance, the better your adherence.
Whilst change control can work with spreadsheets and document templates, dedicated tools significantly improve effectiveness:
Many Irish organisations use tools like Microsoft Project, Jira, ServiceNow, or specialised construction management systems to support change control processes.
Define your change control board:
For smaller projects, a single sponsor might constitute your “board.” For major programmes, you might need multiple boards at different levels handling changes of varying significance.
Track change control metrics:
Use this data to identify improvement opportunities. Are assessments taking too long? Is the board rejecting most requests for similar reasons? Are certain types of changes consistently causing problems? Address systemic issues rather than treating each occurrence as isolated.
Whilst change control principles apply universally, their implementation varies by context:
Irish construction projects(from Dublin’s docklands development to motorway upgrades nationwide)rely heavily on formal change control due to contractual, safety, and regulatory requirements.
Changes trigger variation orders with clear cost and schedule implications. The National Roads Authority’s project management guidelines mandate rigorous change control procedures. Building Control Regulations require documentation of changes affecting compliance.
Change control in construction typically emphasises detailed cost estimation, contractual implications, and physical impossibility constraints (you can’t easily “undo” poured concrete).
Irish software companies (from multinationals like Google and Microsoft to indigenous firms like Teamwork and Intercom) handle change control differently depending on their development methodology.
Waterfall projects use traditional change control processes similar to construction. Agile projects embrace change but still control it through product backlog management, sprint planning, and product owner prioritisation. The mechanisms differ but the principle remains: changes should be deliberate, assessed, and managed.
Ireland’s pharmaceutical sector faces perhaps the most rigorous change control requirements globally. Changes to validated manufacturing processes, quality systems, or product specifications require extensive documentation, risk assessment, and regulatory approval.
Companies like Pfizer, Johnson & Johnson, and Novartis maintain sophisticated change control systems ensuring compliance with Good Manufacturing Practice (GMP) regulations. Change control here isn’t just best practice; it’s legal requirement enforced by regulatory inspections.
Irish government departments and agencies manage change control through formal approval processes, often involving multiple governance layers.
The Office of Government Procurement mandates change control procedures for major projects. The Public Spending Code requires documentation of significant changes to publicly funded projects. Political sensitivity around cost increases or schedule delays makes rigorous change control particularly important.
Irish banks and financial institutions implement change control as part of broader risk management frameworks. Changes to trading systems, customer data, or regulatory reporting systems require particular rigour due to financial and compliance implications.
The Central Bank of Ireland expects robust change management capabilities, particularly for institutions implementing major technology transformations or responding to regulatory updates.
Organisations sometimes view change control as bureaucratic overhead. Here’s the evidence supporting investment in proper processes:
Reduced budget overruns: Projects with effective change control stay within budget significantly more often than those without formal processes.
Fewer schedule delays: Uncontrolled changes are a primary cause of project delays. Proper change control prevents this through informed decision-making and realistic adjustment of timelines when changes are approved.
Lower risk exposure: Change control forces explicit consideration of risks before implementation, reducing surprises and unintended consequences.
Better stakeholder satisfaction: When stakeholders understand why their requested changes were approved, rejected, or deferred(with clear rationale)satisfaction improves even when not all requests are granted.
Improved organisational learning: Well-documented change processes create valuable data about what kinds of changes typically occur, what drives them, and how they affect projects. This learning improves future project planning.
Enhanced regulatory compliance: For regulated Irish industries, robust change control documentation demonstrates governance maturity and satisfies audit requirements.
If you’re leading an Irish project and want to implement effective change control, start here:
The ability to manage change effectively distinguishes successful Irish projects from troubled ones. Every project faces changes. The question is whether those changes strengthen the project through deliberate improvement or undermine it through uncontrolled drift.
Change control isn’t about preventing change or creating bureaucracy. It’s about ensuring changes serve project interests, happen deliberately rather than accidentally, and reflect informed decisions based on complete information.
For Irish project managers, mastering change control delivers multiple benefits: better project outcomes, satisfied stakeholders, reduced risk exposure, and demonstrated professionalism that enhances career prospects.
Whether you’re managing a small internal initiative or a major national infrastructure programme, the principles remain consistent: capture changes formally, assess them thoroughly, decide deliberately, implement carefully, and document completely.
The organisations that excel at change control don’t treat it as administrative overhead to be minimised. They recognise it as essential project discipline that protects value, enables adaptation, and maintains control even as circumstances evolve.
Your project will face changes. The question is whether you’ll manage them or let them manage you.
Ready to master change control and other essential project management competencies? The Institute of Project Management offers comprehensive training for Irish project professionals:
Download practical resources from our Knowledge Hub including change control templates, impact assessment frameworks, and implementation guides.
Connect with Ireland’s project management community through IPM Hub Membership to share experiences and learn from peers managing change across diverse sectors.
Founded in Ireland in 1989, the Institute of Project Management is the specialist body in project management education and training, supporting Irish project professionals to deliver successful projects through proven methodologies and best practices.
