GITNUXSOFTWARE ADVICE
Technology Digital MediaTop 10 Best Change My Software of 2026
Discover the top 10 best Change My Software solutions to streamline your workflow.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Notion
Databases with relational links plus custom views for change request workflows
Built for cross-functional teams building adaptable change logs and living documentation.
monday.com
Workflow automations triggered by updates to board items
Built for change management teams needing configurable workflows, approvals, and reporting.
Atlassian Jira
Custom workflows with transition validators and conditions for enforcing change policies
Built for teams managing change requests with configurable workflows and strong traceability.
Related reading
Comparison Table
This comparison table evaluates top Change My Software tools that support planning, task tracking, and team collaboration, including Notion, monday.com, Atlassian Jira, Atlassian Confluence, and Microsoft Planner. The table helps readers compare how each platform handles work management workflows, content and documentation, integrations, and day-to-day execution across teams.
| # | Tool | Category | Overall | Features | Ease of Use | Value |
|---|---|---|---|---|---|---|
| 1 | Notion Notion provides customizable databases and page templates for tracking software changes, release notes, and implementation checklists. | all-in-one | 8.5/10 | 8.8/10 | 8.2/10 | 8.4/10 |
| 2 | monday.com monday.com supports workflow boards, approvals, and automations for managing change requests and deployment-ready tasks. | work-management | 8.1/10 | 8.4/10 | 8.2/10 | 7.6/10 |
| 3 | Atlassian Jira Jira tracks change requests as issues with workflows, fields, and release versions to coordinate software changes across teams. | change-tracking | 8.2/10 | 8.9/10 | 7.6/10 | 7.9/10 |
| 4 | Atlassian Confluence Confluence centralizes change documentation with templates, permissions, and page linking to tie decisions to releases. | documentation | 8.1/10 | 8.4/10 | 8.2/10 | 7.7/10 |
| 5 | Microsoft Planner Planner organizes change work into task buckets with assignment, due dates, and shared task plans for software updates. | task-planning | 8.1/10 | 7.8/10 | 8.6/10 | 7.9/10 |
| 6 | Microsoft Project Project schedules software change initiatives with timelines, dependencies, and resource views for implementation planning. | project-scheduling | 8.0/10 | 8.5/10 | 7.4/10 | 7.9/10 |
| 7 | GitHub GitHub manages change delivery with pull requests, branch protections, and release tooling for traceable software updates. | version-control | 8.4/10 | 9.0/10 | 8.1/10 | 7.9/10 |
| 8 | GitLab GitLab provides merge requests, CI pipelines, and release management to coordinate and validate software changes. | devops | 8.2/10 | 8.6/10 | 7.8/10 | 8.1/10 |
| 9 | Trello Trello uses boards and cards to manage lightweight change requests with checklists, labels, and team collaboration. | kanban | 7.8/10 | 7.6/10 | 8.6/10 | 7.2/10 |
| 10 | Linear Linear links software changes to issues and shipping milestones using fast workflows and release-ready status tracking. | issue-tracking | 7.6/10 | 7.6/10 | 8.4/10 | 6.8/10 |
Notion provides customizable databases and page templates for tracking software changes, release notes, and implementation checklists.
monday.com supports workflow boards, approvals, and automations for managing change requests and deployment-ready tasks.
Jira tracks change requests as issues with workflows, fields, and release versions to coordinate software changes across teams.
Confluence centralizes change documentation with templates, permissions, and page linking to tie decisions to releases.
Planner organizes change work into task buckets with assignment, due dates, and shared task plans for software updates.
Project schedules software change initiatives with timelines, dependencies, and resource views for implementation planning.
GitHub manages change delivery with pull requests, branch protections, and release tooling for traceable software updates.
GitLab provides merge requests, CI pipelines, and release management to coordinate and validate software changes.
Trello uses boards and cards to manage lightweight change requests with checklists, labels, and team collaboration.
Linear links software changes to issues and shipping milestones using fast workflows and release-ready status tracking.
Notion
all-in-oneNotion provides customizable databases and page templates for tracking software changes, release notes, and implementation checklists.
Databases with relational links plus custom views for change request workflows
Notion stands out for turning notes, databases, and pages into one unified workspace that teams can reshape without code. It supports relational databases, custom views, and workflow-friendly pages that can act as change requests, SOPs, or product documentation. Built-in permissions, version history, and collaboration tools help keep revisions traceable across distributed teams. APIs and automation options enable integrations and repeatable processes for change management workflows.
Pros
- Relational databases with multiple view types support structured change tracking
- Granular page permissions make it easier to separate teams and sensitive change details
- Version history and inline comments keep change decisions reviewable over time
- Templates and reusable page structures speed up repeatable change workflows
- APIs enable custom integrations with ticketing, docs, and internal systems
Cons
- Complex multi-relational models can become hard to govern at scale
- Automation depth is limited compared with dedicated workflow platforms
- Performance and navigation can degrade in very large workspaces
Best For
Cross-functional teams building adaptable change logs and living documentation
More related reading
monday.com
work-managementmonday.com supports workflow boards, approvals, and automations for managing change requests and deployment-ready tasks.
Workflow automations triggered by updates to board items
monday.com stands out with highly configurable boards that can model projects, workflows, and cross-team processes without code. It combines customizable fields, automation rules, dashboards, and reporting views to track work from intake through delivery. Permissions, integrations, and workflow templates support multi-team operations while keeping work visible in one place. Change My Software teams benefit most when they need flexible change workflows, approvals, and operational reporting in a shared system.
Pros
- Highly configurable boards with custom fields for varied change workflows
- Automation rules reduce manual status updates across processes
- Dashboards and reports centralize operational visibility and metrics
- Strong integrations for connecting tools like calendars, chat, and file storage
- Granular permissions support controlled access across change teams
Cons
- Advanced configurations can require time to design correctly
- Some reporting needs extra setup to match specialized KPIs
- Complex workflows can become harder to maintain as boards grow
- Automation coverage depends on available triggers for each use case
Best For
Change management teams needing configurable workflows, approvals, and reporting
Atlassian Jira
change-trackingJira tracks change requests as issues with workflows, fields, and release versions to coordinate software changes across teams.
Custom workflows with transition validators and conditions for enforcing change policies
Jira stands out with issue-based work tracking that ties software and operations work into one configurable system. Teams can model change processes using customizable workflows, then connect tasks, releases, and approvals through Automation rules and integrations. Core capabilities include issue types, statuses, fields, dashboards, reporting, and permission-controlled projects. Change requests can be traced end to end with labels, components, and links to other work items.
Pros
- Configurable workflows with statuses, transitions, and conditions for change gates
- Strong traceability via issue links across requirements, work, and releases
- Dashboards and reporting that reflect live change funnel stages
- Automation rules reduce manual updates for routine change steps
- Granular permissions support controlled change intake and approvals
Cons
- Workflow configuration can become complex for multi-team change processes
- Reporting setups need careful field and transition hygiene to stay accurate
- Automation and integrations may require admin attention to prevent workflow drift
Best For
Teams managing change requests with configurable workflows and strong traceability
More related reading
Atlassian Confluence
documentationConfluence centralizes change documentation with templates, permissions, and page linking to tie decisions to releases.
Page history and versioning with inline comments
Confluence stands out with wiki-style pages that connect discussions, assets, and documentation into a shared knowledge base. It delivers team collaboration features like page editing, permissions, search, and integrations with Atlassian tools such as Jira. Strong workflow support comes from structured spaces and content templates for repeatable change processes. Change tracking is supported through version history and activity logs rather than purpose-built change management tooling.
Pros
- Fast wiki authoring with inline comments and mentions
- Space structure supports consistent documentation for change records
- Granular permissions and page-level access control
Cons
- Change management depends on conventions rather than native approvals
- Deep change history queries can feel manual across many pages
- Not designed for structured risk, impact, and rollback tracking
Best For
Teams documenting and collaborating on software changes with wiki workflows
Microsoft Planner
task-planningPlanner organizes change work into task buckets with assignment, due dates, and shared task plans for software updates.
Planner charts that show bucket progress and task status at a glance
Microsoft Planner stands out with a simple board-and-card workflow built for quick task creation and lightweight collaboration. It delivers core project features like task buckets, assignments, due dates, checklists, and attachments inside a web and mobile experience. It also connects natively to Microsoft 365 through Teams notifications and Outlook-compatible mail links. Reporting stays focused on charts for bucket and task status rather than deep analytics or custom dashboards.
Pros
- Fast task entry with bucketed boards for clear visual work stages
- Assignments, due dates, and checklists keep tasks actionable without extra setup
- Microsoft 365 integration supports Teams notifications and shared documents
Cons
- Limited dependency management compared with full project planning tools
- Reporting and automation options stay basic for complex workflows
- Board-centric structure can feel restrictive for large multi-project programs
Best For
Teams managing everyday work with visual boards inside Microsoft 365
Microsoft Project
project-schedulingProject schedules software change initiatives with timelines, dependencies, and resource views for implementation planning.
Critical Path Method scheduling with dependency-driven dates and baseline variance tracking
Microsoft Project stands out for its deep support of schedule building with task dependencies, critical path logic, and resource assignments in a desktop-focused workflow. It delivers core project controls such as Gantt and timeline views, baseline tracking for progress measurement, and resource leveling to manage over-allocations. Strong integration with Microsoft 365 keeps task updates and reporting aligned with common enterprise collaboration patterns, including work tracking via Microsoft Planner when used together. The tool is best leveraged for structured planning and monitoring rather than lightweight agile delivery.
Pros
- Critical path scheduling with dependency links for disciplined schedule control
- Resource leveling reduces over-allocation across tasks and roles
- Baseline variance reporting shows schedule slippage and trend shifts
- Multiple scheduling views support planning, execution, and stakeholder updates
- Strong compatibility with Microsoft ecosystem for enterprise workflows
Cons
- Advanced scheduling setups require a steep learning curve for many teams
- Agile-style backlog execution is limited compared to dedicated agile tools
- Collaboration and real-time editing depend heavily on connected Microsoft services
Best For
Project teams needing dependency-driven scheduling and baseline variance reporting
More related reading
GitHub
version-controlGitHub manages change delivery with pull requests, branch protections, and release tooling for traceable software updates.
Pull requests with code review, checks integration, and merge protections
GitHub stands out by turning Git-based development into a collaborative workflow with pull requests and review. Code repositories support branching, commit history, issues, and integrated project management through GitHub Projects. Automation features like Actions enable CI and CD pipelines that run on events such as pushes and pull requests.
Pros
- Pull requests with review comments, approvals, and required checks
- Actions automate CI and CD using event triggers and reusable workflows
- Rich repository features include issues, projects, and discussions
Cons
- Merge and workflow configuration can get complex across multiple repositories
- Large organizations often need governance to prevent inconsistent practices
- Automation sprawl can increase debugging time for failing pipelines
Best For
Software teams needing strong collaboration, review, and automated delivery workflows
GitLab
devopsGitLab provides merge requests, CI pipelines, and release management to coordinate and validate software changes.
Merge request pipelines with required status checks and approval rules
GitLab stands out by combining source control, CI/CD, and governance in one integrated DevOps workflow with a single project model. It delivers code review, branching and merge workflows, automated pipelines, and security scanning tied directly to commits and merge requests. Teams also get built-in planning and issue tracking that can link work items to code changes across the full lifecycle. This tight coupling supports faster feedback loops than stitching separate tools together.
Pros
- Single project workspace links issues, code, pipelines, and security checks end to end
- Merge request workflows enforce review gates with approvals and required checks
- Flexible CI pipelines support complex jobs using reusable templates and artifacts
Cons
- Complex configurations can slow teams when pipelines, runners, and policies interact
- Granular permissions and project inheritance can be difficult to model correctly
- Self-managed deployments require operational maintenance for runners and storage
Best For
Product and engineering teams needing integrated CI/CD with governance in one platform
More related reading
Trello
kanbanTrello uses boards and cards to manage lightweight change requests with checklists, labels, and team collaboration.
Automation Butler rules for triggering card updates and workflows across boards
Trello stands out with a Kanban board interface built around draggable cards and clear visual status columns. It supports assignments, due dates, checklists, labels, file attachments, and team notifications so workflows stay trackable. Power-ups and automation rules extend boards with integrations like calendars, dashboards, and process triggers without requiring a custom build. Reporting is practical for operational visibility through board views and filtered lists, but deeper cross-board analytics need additional tooling.
Pros
- Kanban boards map naturally to change request stages and approvals
- Cards support checklists, labels, due dates, and attachments for audit-ready detail
- Power-ups add integrations and views such as calendars and dashboards
- Automation rules reduce manual updates across cards and boards
Cons
- Cross-board reporting and rollups are limited without added integrations
- Custom workflows can become complex across many boards and power-ups
- Fine-grained permissions and governance controls are not as robust as enterprise changemanagement systems
Best For
Teams needing visual change tracking with lightweight automation and collaboration
Linear
issue-trackingLinear links software changes to issues and shipping milestones using fast workflows and release-ready status tracking.
Issue timeline with inline edits, comments, and status history tied to each change request
Linear stands out with its fast, lightweight issue tracking and clean boards that keep teams focused on delivery. It supports change management through customizable issue workflows, status updates, and linked discussions that capture request context and decisions. Core capabilities include projects, labels, milestone planning, team notifications, and automation via integrations. Audit-friendly change trails come from issue history that records edits, comments, and state changes.
Pros
- Clean issue workflows make change requests easy to track end to end
- Realtime collaboration with comments keeps decision context attached to the request
- Labels, milestones, and projects support practical change reporting
- Automation and integrations reduce manual triage and status chasing
Cons
- Limited built-in governance controls for formal approvals and compliance
- Change impact tracking across services requires external modeling and linkage
- Reporting and audit exports are weaker than dedicated change management systems
Best For
Engineering teams managing change requests with fast issue workflows and automation
Conclusion
After evaluating 10 technology digital media, Notion stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Change My Software
This buyer’s guide explains how to select a Change My Software solution for tracking requests, approvals, releases, and delivery work. It covers Notion, monday.com, Atlassian Jira, Atlassian Confluence, Microsoft Planner, Microsoft Project, GitHub, GitLab, Trello, and Linear. It maps concrete workflow, traceability, and governance capabilities to the type of change process the team runs.
What Is Change My Software?
Change My Software tools manage the full lifecycle of software change intake, review, planning, delivery, and release coordination. They keep decisions and work linked so teams can trace what changed, who approved it, and where it shipped. In practice, Atlassian Jira tracks change requests as issues with configurable workflows and linked releases, while GitLab coordinates merge requests with CI pipelines and required status checks. Many teams also pair documentation-heavy workflows with Atlassian Confluence page history and versioning to record decisions tied to releases.
Key Features to Look For
The strongest fit comes from capabilities that match how change requests move from intake to approval to delivery.
Structured change workflows with gates
Atlassian Jira enforces change gates with configurable workflows that use statuses, transitions, and conditions. GitLab adds review gates by requiring approvals and required status checks on merge request pipelines.
Traceability across requests, work items, and releases
Atlassian Jira delivers end-to-end traceability by linking issues, releases, and related work items through labels, components, and issue links. GitHub supports traceable delivery through pull requests with code review approvals and merge protections tied to checks.
Automation triggered by workflow events
monday.com automates manual updates by running workflow automations when board items change. Trello extends automation with Automation Butler rules that trigger card updates and workflows across boards.
Living documentation and revision history
Atlassian Confluence centralizes change documentation with templates, page linking, and page-level permissions. It records decisions using page history and versioning with inline comments rather than purpose-built change approvals.
Relational intake data with custom views
Notion supports database-driven change intake using relational links and custom views for change request workflows. Its version history and inline comments keep change decisions reviewable over time.
Delivery-integrated planning and execution
Microsoft Project supports disciplined scheduling with dependency-driven dates using critical path logic and baseline variance tracking. Microsoft Planner complements this with bucket progress charts and lightweight task status for everyday work inside Microsoft 365.
How to Choose the Right Change My Software
Selection works best by matching the team’s change process to the tool’s workflow model, traceability approach, and automation depth.
Match the core change object to the team’s workflow
If change is managed as a structured request with review gates, Atlassian Jira is a strong match because it models change requests as issues with configurable workflows and transition validators. If change is managed as software delivery, GitHub and GitLab are strong matches because pull requests and merge requests include review approvals and checks integration.
Require approvals and enforcement, not just tracking
For strict enforcement, GitLab supports merge request workflows with required status checks and approval rules tied to CI pipelines. For configurable enforcement inside an issue system, Atlassian Jira supports workflow conditions that control change intake and approvals.
Decide how decisions and documentation must be stored
If the change record is expected to live as documentation that multiple teams edit, Atlassian Confluence supports wiki-style pages with page history, inline comments, and permissions at the page level. If the change record must combine documentation with relational intake and multiple views, Notion supports relational databases with custom views and version history.
Evaluate automation depth based on how updates happen
Teams that need operational automation across a board model often get fast wins from monday.com because automations trigger based on updates to board items. Teams that prefer a lightweight Kanban approach can automate card updates with Trello’s Automation Butler rules across boards.
Fit planning and delivery to the execution style
If change work needs dependency-driven scheduling and baseline variance reporting, Microsoft Project supports critical path scheduling with dependency links and baseline tracking. If the team needs fast, visual task execution inside Microsoft 365, Microsoft Planner delivers bucketed task status charts with assignments, due dates, and checklists.
Who Needs Change My Software?
Change My Software tools serve teams that must coordinate work across intake, approvals, and shipping so changes remain auditable and repeatable.
Cross-functional teams building adaptable change logs and living documentation
Notion is the best fit because it combines relational databases with custom views for change request workflows and keeps decisions reviewable through version history and inline comments. Teams that want a wiki-led approach can use Atlassian Confluence for page templates, permissions, and page history with inline comments.
Change management teams needing configurable workflows, approvals, and reporting
monday.com is a strong match for configurable boards with custom fields, automation rules, and dashboards that centralize operational visibility. Atlassian Jira is a strong match when change requests must be enforced with configurable workflows and transition validators that support strong traceability.
Teams managing change requests with strong traceability across work and releases
Atlassian Jira supports traceability by linking change requests to requirements, work, and releases using issue links, components, and labels. Linear also supports change request context using issue history with edits, comments, and state changes tied to each request.
Engineering and product teams coordinating delivery with governance in CI/CD
GitLab fits product and engineering teams that want merge request pipelines with required status checks and approval rules integrated into a single platform. GitHub fits software teams that need pull requests with review comments, required checks, and merge protections integrated with CI and CD via GitHub Actions.
Common Mistakes to Avoid
Common failures come from selecting a tool that tracks the work but does not enforce the change policy, or from building a structure that breaks at scale.
Choosing documentation-only tools for policy enforcement
Atlassian Confluence excels at wiki authoring and page history with inline comments but it does not provide native approvals and structured risk, impact, and rollback tracking. Pairing it with Atlassian Jira helps enforce gates using workflow transitions and conditions for change intake.
Overbuilding complex workflow configurations without governance time
Atlassian Jira workflows can become complex across multi-team change processes and require careful workflow hygiene for reporting accuracy. monday.com boards can also become harder to maintain as boards grow, especially when advanced configurations require significant design time.
Assuming a lightweight board tool can replace enterprise permissions and governance
Trello supports checklists, labels, due dates, and automation via Automation Butler, but fine-grained permissions and governance controls are not as robust as dedicated change management systems. Linear provides fast issue workflows and an issue timeline history, but it includes limited built-in governance controls for formal approvals and compliance.
Using pure scheduling tools for agile delivery execution
Microsoft Project delivers dependency-driven scheduling with critical path logic and baseline variance tracking, but agile-style backlog execution stays limited compared with dedicated agile tools. Microsoft Planner provides lightweight board execution and charts, but it offers limited dependency management for complex projects.
How We Selected and Ranked These Tools
We evaluated every tool on three sub-dimensions using a weighted average. Features carry a weight of 0.4, ease of use carries a weight of 0.3, and value carries a weight of 0.3. The overall rating is the weighted average using overall = 0.40 × features + 0.30 × ease of use + 0.30 × value. Notion separated itself from lower-ranked tools on the features dimension by combining relational database links with custom views for change request workflows while also keeping change decisions reviewable through version history and inline comments.
Frequently Asked Questions About Change My Software
Which tool best models change requests as structured data with traceable revisions?
Notion fits teams that need change requests stored as relational database records with custom views for intake, approval, and status tracking. Confluence supports revision history and page activity logs, but Notion’s database relationships plus view filtering create cleaner end-to-end change flows.
What platform supports approval workflows with reporting in one configurable system?
monday.com supports change workflows using customizable boards, automation rules triggered by item updates, and dashboards for operational reporting. Jira also supports approvals through configurable issue workflows, but monday.com emphasizes board-based workflow changes and visibility over issue-centric configuration.
How can teams enforce change policy rules during status transitions?
Atlassian Jira provides custom workflows with transition validators and conditions that block noncompliant changes during specific steps. Linear and Trello can track statuses and decisions, but Jira’s workflow conditions are designed to prevent policy violations at the transition layer.
Which option works best for documenting change context and decisions alongside work tracking?
Confluence fits teams that need wiki-style change documentation with version history and inline comments tied to shared spaces. Jira integrates strongly with Confluence, while GitHub and GitLab capture decisions in code review threads and pipeline outcomes rather than a general documentation wiki.
What tool suits lightweight change tracking for day-to-day operational tasks?
Microsoft Planner fits teams that need quick task creation with assignments, due dates, checklists, and attachments inside Microsoft 365. Trello also supports quick Kanban updates with draggable cards and checklists, but Planner’s built-in Microsoft notifications and simpler reporting make it easier for everyday execution.
Which platform is best for dependency-driven scheduling and baseline progress tracking for change programs?
Microsoft Project fits change programs that require dependency-based dates, critical path logic, and resource assignments. monday.com and Jira can visualize progress and workflow status, but Microsoft Project’s baseline tracking and resource leveling are purpose-built for schedule variance and capacity control.
How do software teams connect change requests to code review and automated checks?
GitHub supports change workflows through pull requests, code review, and merge protections paired with Actions-based checks. GitLab connects merge request pipelines to required status checks and approval rules, tying governance directly to the commit and merge lifecycle.
Which tool best combines CI/CD, governance, and security scanning with unified DevOps workflows?
GitLab fits teams that need source control, CI/CD, security scanning, and governance in one platform with a consistent project model. GitHub also supports Actions and security workflows, but GitLab’s merge request pipeline requirements and built-in scanning linkage are tighter for end-to-end governance.
What’s a practical way to start change tracking without building a custom system?
Trello works well for immediate change tracking by using Kanban columns, labels, and due dates with automation rules via Power-ups. Notion also enables fast setup using database templates and custom views, while Linear offers a simpler issue-workflow approach that starts with minimal configuration.
Which platform provides the clearest audit trail for edits and workflow state changes?
Linear offers an issue timeline that records inline edits, comments, and status history for each change request. Jira also provides strong traceability via issue history, configurable workflow transitions, and linkable work items, while GitHub and GitLab track audit signals through commit history, pull request activity, and pipeline checks.
Tools reviewed
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Technology Digital Media alternatives
See side-by-side comparisons of technology digital media tools and pick the right one for your stack.
Compare technology digital media tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.