Commissioned Research
Top 10 Best Standard Operating Procedure Software of 2026

GITNUXSOFTWARE REVIEW

Business & Finance

Top 10 Best Standard Operating Procedure Software of 2026

Compare standard operating procedure software options for teams, with editorial notes on fit and tradeoffs, including Process Street.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Standard operating procedure software helps teams turn written processes into repeatable execution artifacts with checklist runs, approvals, and tracked outcomes. This comparison is aimed at analysts and operators who need to weigh workflow configuration depth, knowledge access controls, and audit log requirements, with Process Street highlighted for checklist execution and recurring SOP workflows.

Pipefy is the best choice for teams standardizing multi-step operations because its visual SOP workflow builder turns steps into enforceable pipelines with routing, roles, and measurable status tracking, whereas Tallyfy fits groups that want lightweight checklist-style approvals with conditional logic for branching.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Pipefy

Visual workflow builder with automation rules for SOP task routing and execution

Best for: Teams standardizing multi-step operations with visual automation and measurable workflows

2

Tallyfy

Editor pick

Visual workflow builder with conditional logic and role-based approvals

Best for: Teams standardizing checklists and approvals into SOP workflows without heavy documentation needs

3

Process Street

Editor pick

Conditional logic for checklist steps based on form answers and prior task results

Best for: Teams standardizing SOP execution with checklist automation and audit trails

Comparison Table

1
PipefyBest overall
workflow automation
9.4/10
Overall
2
process orchestration
8.9/10
Overall
3
checklist automation
8.8/10
Overall
4
enterprise wiki
8.3/10
Overall
5
knowledge hub
8.2/10
Overall
6
process management
7.7/10
Overall
7
SOP documentation
7.6/10
Overall
8
knowledge management
7.1/10
Overall
9
template workspace
6.9/10
Overall
10
documentation
6.5/10
Overall
#1

Pipefy

workflow automation

Model SOP processes as configurable workflows with steps, roles, SLAs, and status tracking in an operational process system.

9.4/10
Overall
Features9.4/10
Ease of Use9.5/10
Value9.3/10
Standout feature

Visual workflow builder with automation rules for SOP task routing and execution

Pipefy stands out with its visual workflow builder that maps SOPs into configurable process pipelines. It supports standardized forms, task assignments, due dates, and automated routing so procedures execute consistently across teams.

You can track performance with process visibility features like status tracking and analytics for each workflow. Integrations extend workflows to common business tools for triggers and data movement.

Pros
  • +Visual workflow builder turns SOP steps into enforceable process pipelines
  • +Configurable forms capture required fields and approvals for each procedure
  • +Automation rules reduce manual handoffs and keep processes moving
  • +Process analytics show throughput and bottlenecks across workflows
Cons
  • –Complex SOPs can require careful workflow modeling to avoid rework
  • –Advanced governance needs may add setup effort for larger teams
  • –Reporting depth can feel limited for highly specialized SOP metrics
Use scenarios
  • HR and recruiting teams

    Coordinating approvals during onboarding

    Coordinated onboarding progress visibility

  • Sales operations teams

    Managing internal provisioning handoffs

    Fewer missed internal handoffs

Show 2 more scenarios
  • Finance and procurement teams

    Running conditional approval stages

    Traceable decision history

    Sequential or conditional stages assign reviewers and record decisions for each request moving through approvals.

  • High-volume process teams

    Classifying requests before routing

    Faster governed request triage

    AI task steps summarize incoming work and feed classification results into workflow routing rules.

Best for: Teams standardizing multi-step operations with visual automation and measurable workflows

#2

Tallyfy

process orchestration

Design SOP forms and visual workflows with conditional logic, then route tasks and capture outcomes in a process-focused workspace.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Visual workflow builder with conditional logic and role-based approvals

Tallyfy stands out with a visual, form-driven workflow builder that turns SOP steps into interactive checklists and approvals. It supports conditional logic, role-based task assignment, and audit-friendly execution logs for each workflow instance.

The platform focuses on standardizing frontline processes like inspections, onboarding, and checklists using real-time status tracking and notifications. It is less geared toward complex document management and version-controlled policy libraries than SOP tools that centralize full documentation workflows.

Pros
  • +Visual workflow builder converts SOP steps into structured checklists
  • +Conditional logic supports branch-based approvals and exception handling
  • +Real-time task status and notifications keep SOP execution on track
Cons
  • –Document-heavy SOP knowledge bases are not its core strength
  • –Advanced customization can feel limiting versus code-first workflow engines
  • –Reporting depth is narrower than dedicated enterprise workflow suites
Use scenarios
  • Operations and process teams

    Guiding SOP steps with checklists

    More consistent execution

  • Compliance and procedure owners

    Routing drafts through review and release

    Traceable approvals

Show 2 more scenarios
  • Governance teams and auditors

    Running recurring sign-off controls

    Traceable compliance actions

    Role assignments and activity history support repeatable control workflows with recorded execution steps.

  • Process improvement teams

    Finding stalled procedure steps

    Better bottleneck visibility

    Recurring workflow monitoring highlights stalled steps and repeated issues to refine procedure design.

Best for: Teams standardizing checklists and approvals into SOP workflows without heavy documentation needs

#3

Process Street

checklist automation

Create SOP checklists with templates, assign owners, run recurring workflows, and collect results with reporting.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Conditional logic for checklist steps based on form answers and prior task results

Process Street turns SOPs into repeatable checklist workflows using conditional steps and reusable templates that teams apply across recurring operations. Teams can assign tasks dynamically and track completion in real time for each procedure run.

Recurring workflows and structured evidence fields support consistent outputs across locations and work cycles. Reporting and document linking help connect execution records to supporting materials for audit-friendly traceability.

A tradeoff is that the product centers on checklist execution rather than building a full document management system for complex policy libraries. It fits best when SOPs are primarily step-based and need execution visibility with repeatability across teams.

Pros
  • +Checklist-based SOPs with reusable templates and field-driven prompts
  • +Conditional logic routes tasks based on user inputs and outcomes
  • +Real-time completion tracking with audit-friendly run history
Cons
  • –Advanced workflow design can feel complex for simple SOPs
  • –Reporting depth requires setup to match specific KPI needs
  • –Template reuse can become harder without strong naming conventions
Use scenarios
  • Operations managers and process owners

    Executing recurring procedures with checklists

    Consistent execution with tracking

  • Field operations and quality teams

    Recording batch inspection evidence

    Comparable inspection records

Show 2 more scenarios
  • Finance, HR, and compliance teams

    Adding approvals to SOP completion

    Recorded responsibility and status

    Approval steps and conditional routing structure reviews that must finish before checklist completion.

  • Quality assurance teams

    Reviewing work against defined procedures

    Consistent QA outcomes

    Task checklists and structured fields help QA evaluate tickets or work items against SOP requirements.

Best for: Teams standardizing SOP execution with checklist automation and audit trails

#4

Confluence

enterprise wiki

Use structured pages, templates, permissions, and workflow integrations to maintain and execute SOPs across teams.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Approval workflows with version history for controlled SOP documentation

Confluence centers SOP execution around structured pages, templates, and permission-controlled spaces. You can turn SOP drafts into controlled documentation using page templates, inline task assignment, approval workflows, and version history.

Pros
  • +SOP templates and page structures keep procedures consistent across teams
  • +Version history and page approvals support controlled documentation changes
  • +Permissions by space and page enable SOP library governance
  • +Deep Jira integration links SOP steps to tasks and incident follow-ups
Cons
  • –Free-form editing can lead to inconsistent SOP formatting without strict templates
  • –Advanced workflow configuration and governance need admin setup
  • –Real-time checklist automation requires add-ons or custom process design
Use scenarios
  • Operations, quality, and process teams

    Maintaining SOPs with review workflows

    Fewer undocumented procedure changes

  • Engineering and project teams

    Connecting runbooks to delivery context

    Connected delivery evidence

Show 2 more scenarios
  • Enterprise knowledge and IT teams

    Centralizing permissioned SOP knowledge

    Searchable SOP library

    Shared spaces with granular permissions organize policies, guides, and decisions into a searchable internal knowledge hub.

  • Operations and governance teams

    Keeping versioned operational runbooks

    Clear change history

    Versioned runbooks store specifications, test evidence, and access-controlled baselines with approvals.

Best for: Teams maintaining SOP knowledge bases with approval history and Jira-linked execution

#5

Guru

knowledge hub

Centralize SOP content in a searchable knowledge hub that syncs with business tools and drives adoption across teams.

8.2/10
Overall
Features8.2/10
Ease of Use8.1/10
Value8.3/10
Standout feature

Guru’s Knowledge Graph that recommends relevant SOP pages from your content and context

Guru stands out with its knowledge base design that surfaces approved information inside day-to-day work. It centralizes SOP content through searchable pages, templates, and structured documentation that teams can reuse consistently. Guru also supports permission controls, versioning-friendly editing workflows, and integrations that help route SOPs to the right audience without leaving existing tools.

Pros
  • +Strong SOP-ready knowledge base with fast search
  • +Templates and reusable page structure for consistent procedures
  • +Integrations that surface SOPs in tools teams already use
  • +Granular permissions keep SOPs scoped by team or role
Cons
  • –Advanced governance can require setup and change management
  • –SOP approval workflows are less explicit than full workflow engines
  • –Pricing scales quickly with teams that need broad access
Use scenarios
  • Operations and process owners

    Publishing structured procedure references

    More consistent internal execution

  • People operations teams

    Running an intranet-style guidance hub

    Centralized employee information

Show 2 more scenarios
  • Knowledge managers and SMEs

    Keeping SOP answers up to date

    More reliable guidance

    Ownership and review assignments help maintain accuracy as products, policies, and teams change.

  • Sales enablement leaders and reps

    Delivering role-specific process guidance

    Quicker access to approved guidance

    Permissioned guidance delivers approved deal-facing and process information inside sales workflows.

Best for: Teams maintaining SOP libraries with search-first publishing and targeted sharing

#6

iPlanner

process management

Build standardized process maps and SOP libraries that support assignments, execution, and continuous improvement activities.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

SOP approval workflow with controlled procedure updates and versioning

iPlanner stands out with an SOP-first workflow builder that turns policies into structured checklists and step-by-step procedures. It supports reusable templates and versioned updates so teams can maintain consistent operating instructions across departments. The system emphasizes task assignment, approvals, and audit-ready organization of procedures within a centralized workspace.

Pros
  • +SOP templates help standardize procedures across teams
  • +Approvals support controlled updates to official operating instructions
  • +Task assignments connect procedures to accountable owners
  • +Centralized procedure library improves discoverability during audits
Cons
  • –SOP setup takes time to configure roles, steps, and templates
  • –Advanced workflows feel less flexible than full process-management suites
  • –Reporting depth is limited for complex compliance programs
  • –Navigation can be slower with large procedure libraries
Use scenarios
  • Quality assurance teams

    Standardize SOPs across inspection and testing

    Audit-ready procedures maintained

  • Operations managers

    Run department handoffs with version control

    Fewer workflow inconsistencies

Show 2 more scenarios
  • Compliance officers

    Manage regulated process instructions

    Faster regulatory documentation

    Organize procedures in one workspace with approval trails for compliance reviews.

  • Training coordinators

    Create onboarding checklists from SOPs

    More consistent onboarding

    Turn step-by-step procedures into reusable tasks that guide new hires consistently.

Best for: Teams needing SOP templates, approvals, and assigned task execution

#7

SweetProcess

SOP documentation

Document SOPs as process maps and procedures with versioning, approvals, task execution, and audit-ready activity logs.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Checklist-driven SOP steps with role-based assignment and execution records

SweetProcess focuses on turning SOPs into guided workflows with structured steps, roles, and checklists. It provides templates for repeatable operations so teams can standardize work across departments.

Pros
  • +Workflow-style SOPs with step ownership and execution tracking
  • +SOP templates speed up standardization across teams
  • +Built-in checklists and task routing support repeatability
  • +Review flows help enforce consistent procedure completion
Cons
  • –SOP structure setup can feel heavy for simple one-off procedures
  • –Advanced approval logic requires more configuration effort
  • –Reporting depth for SOP compliance is limited versus enterprise workflow suites
Use scenarios
  • Operations managers and process owners

    Building reusable SOP templates

    More consistent handoffs

  • Compliance managers and auditors

    Scheduling checklist-based compliance runs

    Evidence of completion

Show 2 more scenarios
  • Operations and documentation owners

    Publishing controlled instruction versions

    Better instruction control

    Procedure owners maintain current versions and distribute role-specific instructions with controlled access.

  • People operations and department managers

    Delegating onboarding SOP tasks

    More consistent onboarding

    Teams document and assign repeatable onboarding steps for new employees or internal transfers.

Best for: Teams standardizing recurring operations with checklist-driven SOP execution

#8

ProProfs Knowledge Base

knowledge management

Publish SOPs as searchable articles with permissions, analytics, and workflow-friendly knowledge management for internal operations.

7.1/10
Overall
Features7.1/10
Ease of Use7.1/10
Value7.1/10
Standout feature

Article approval workflows for controlled SOP publishing and review.

ProProfs Knowledge Base stands out with built-in review and feedback controls that help teams validate SOP drafts before publishing. It provides a structured knowledge base for creating articles, organizing categories, and applying permissions so different roles can access approved procedures.

Pros
  • +Approval workflows support controlled SOP publishing
  • +Role-based permissions limit SOP access by department
  • +Search and knowledge portal options improve findability
Cons
  • –Advanced customization options can feel limited versus full intranet CMS
  • –SOP version tracking is not as robust as dedicated document control tools
  • –Reporting and analytics are less detailed for process governance
Use scenarios
  • HR, training, and enablement teams

    Sequencing onboarding articles

    Consistent onboarding sequence

  • Customer support teams

    Delivering SOP-based self-service help

    Reduced repetitive inquiries

Show 2 more scenarios
  • Knowledge managers and support leaders

    Improving procedures based on search usage

    Prioritized content improvements

    Search and reader feedback data shows which SOP articles get viewed and which need refinement.

  • Product education and success teams

    Teaching changes with structured paths

    Organized education delivery

    Structured paths guide readers through product updates and related support SOP information in sequence.

Best for: Teams needing approval-based SOP knowledge base with fast internal search

#9

Notion

template workspace

Create SOP databases with templates, checklists, and dashboards that teams can edit, share, and track.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Templates with databases and views for standardized SOP libraries

Notion stands out with a single workspace that turns SOPs into living knowledge bases using databases, templates, and linked pages. You can standardize procedures with repeatable page templates, checklist fields, and status tracking inside database views. Notion also supports role-based access and page permissions for teams that need shared governance of SOP content.

Pros
  • +Database views and templates keep SOP structure consistent across teams.
  • +Relational fields link procedures to forms, owners, and related work instructions.
  • +Checklist blocks and status fields support lightweight SOP execution tracking.
Cons
  • –No dedicated SOP workflow engine for approvals, versioning, and audit trails.
  • –Building complex SOP databases takes setup time and ongoing maintenance.
  • –Rich formatting can cause inconsistent SOP quality across users.
Use scenarios
  • Revenue ops teams

    Centralize SOPs for quoting workflows

    Fewer configuration errors

  • IT support leads

    Maintain runbooks with checklist fields

    Faster incident resolution

Show 2 more scenarios
  • HR operations teams

    Standardize onboarding and policy procedures

    Consistent onboarding delivery

    Role-based access controls approvals while templates keep forms and steps synchronized across locations.

  • Quality assurance teams

    Track SOP versions and signoffs

    Improved audit readiness

    Database views support status tracking and permissions for audit-ready procedure governance.

Best for: Teams needing SOPs as searchable knowledge with flexible templates

#10

Slab

documentation

Store SOPs in a lightweight documentation platform with strong search, editor workflows, and internal linking for procedure clarity.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

SOP-focused documentation with templates and workspaces for consistent procedure structure

Slab stands out as an SOP-first internal knowledge base that turns documentation into structured, navigable procedures. It supports creating templates, organizing pages into workspaces, and building content that teams can update together.

Pros
  • +SOP-first documentation makes procedures easy to structure and navigate
  • +Template support speeds consistent SOP creation across teams
  • +Good collaboration flows for keeping procedures current
  • +Simple search and indexing helps teams find the right step quickly
Cons
  • –Limited workflow automation compared with dedicated SOP automation tools
  • –No native runbooks-to-execution mapping for assigning tasks automatically
  • –Advanced permissioning and governance controls feel lighter than enterprise systems
Use scenarios
  • Operations, compliance, and process owners

    Maintaining SOPs with version history

    Easier procedure traceability

  • Support operations and workflow owners

    Embedding documentation where questions occur

    Faster access to SOP context

Show 2 more scenarios
  • Support and documentation teams

    Publishing searchable answer content

    More consistent customer responses

    Answers can be turned into searchable articles and shared with external collaborators as selected help content.

  • Operations teams and department leaders

    Organizing SOP knowledge for browsing

    Shared source of internal info

    Topic areas store policies, reference material, and meeting notes in a searchable wiki structure.

Best for: Teams documenting SOPs in a living knowledge base

Conclusion

After evaluating 10 standard operating procedure software, Pipefy 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.

Our Top Pick
Pipefy

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Standard Operating Procedure Software

What should I choose for SOPs that need automated step execution and audit trails?
Process Street converts SOPs into checklist workflows with conditional steps and real-time completion tracking, then records outcomes for auditability. SweetProcess also logs execution records per SOP step, but it leans harder on guided checklists and role-based assignment than on complex routing rules.
How do Pipefy and Tallyfy differ for standardizing SOP workflows across multiple teams?
Pipefy uses a visual workflow builder to map SOPs into configurable process pipelines with automated routing, due dates, and performance visibility. Tallyfy is more form-driven and emphasizes interactive checklists with role-based task assignment and approval flows for frontline-style procedures.
Which tool is best when I need approval workflows and controlled updates to SOP content?
iPlanner focuses on SOP-first creation with versioned updates, approvals, and centralized procedure organization. ProProfs Knowledge Base adds article-level review and publishing controls so teams can validate SOP drafts before they become searchable content.
Where can I keep an SOP library that staff can search from day-to-day work?
Guru is designed for search-first access by surfacing approved SOP pages inside workflows, supported by templates and targeted sharing controls. Confluence supports structured SOP spaces with permission-controlled pages and searchable content, plus version history for traceability.
What’s a good fit for SOP documentation that prioritizes readability and structured templates over execution automation?
Slab is built as an SOP-focused internal knowledge base that keeps procedures readable through templates and workspaces without centering heavy task automation. In contrast, Process Street and Pipefy are built to drive execution through checklist steps and routed workflow instances.
How do I handle SOP version history and regulated documentation needs?
Confluence provides version history and permission-controlled spaces, which helps maintain an approval trail for structured SOP documentation. iPlanner also supports versioned SOP updates with approval workflows, while ProProfs Knowledge Base provides review gates before publishing.
Can I build SOPs that adapt steps based on earlier answers in a single workflow run?
Process Street supports conditional logic so checklist steps change based on form answers and prior task results. Tallyfy also supports conditional logic and approval checkpoints, especially for interactive checklist and inspection-style SOPs.
Which tool best fits teams that want SOP templates linked to execution status and records inside a single workspace?
Notion lets you model SOPs as living knowledge bases with databases, reusable templates, checklist fields, and status tracking views. SweetProcess also ties SOP steps to execution records with visibility into who did what and when, but it centers guided workflows rather than database-driven views.
What common setup steps should I plan for when moving from documents to structured SOP systems?
Start by defining SOP steps and responsibilities in a tool that enforces structure, like Process Street or Pipefy, then map ownership and due dates to workflow tasks. If your primary need is governed publishing and discoverability, set up an approval workflow in Guru or ProProfs Knowledge Base and organize content into permission-controlled spaces or categories in Confluence.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Standard Operating Procedure Software

We see the biggest differences come from how well each tool handles version and approval behavior, how tightly it controls the active procedure set, and how traceable changes are when teams ask “which SOP are we using?”. The best standard operating procedure software options make those mechanics obvious during setup and on real documents.

SOP authoring that stays consistent

Why it matters

SOP authoring and templates affect whether procedures stay readable and repeatable across departments. When the structure is consistent, training and updates feel less chaotic.

How to check

Create a small SOP from scratch and then create one using the product’s template approach. Verify you can reuse the same sections, headings, and fields without manual cleanup each time.

Controlled access to the active SOP set

Why it matters

Controlled document access matters because teams need the right SOP at the right time. If the wrong version is easy to open, day-to-day work becomes guesswork.

How to check

Ask for a workspace with multiple SOP versions and try opening the same SOP from two roles (writer vs reviewer). Confirm the system shows the current active version by default and restricts older drafts appropriately.

Approval and review cycles for SOP changes

Why it matters

Approval workflow and review cycle behavior determine who can publish changes and how reliably reviews happen. Strong review mechanisms reduce silent drift in procedures.

How to check

Demonstrate a change from draft to published, then review who must sign off at each step. Check whether the tool supports a predictable review cadence and prevents publishing without the required steps.

Change history and audit log clarity

Why it matters

Change control and audit trail clarity help you answer “what changed, when, and by whom?” without hunting through messages. This protects quality when incidents trigger SOP questions.

How to check

Open a previously revised SOP and inspect its revision tracking details. Confirm you can see what changed and view an audit log style timeline of key events, not just a document download list.

API and automation surface for SOP updates

Why it matters

Integration depth through API and automation surface determines whether SOP updates connect to upstream systems and downstream reporting. When the API is documented, we can treat SOP data as part of the operating model.

How to check

Ask to see API documentation or an example webhook/integration flow for creating or updating an SOP. Try mapping a simple external event (like “SOP published”) to a receiving action in a demo environment.

Red flags

  • Older SOP versions open without obvious “active vs draft” guidance
  • Revisions look like file uploads with no clear what/when/who timeline
  • Approval and review steps can be bypassed or feel inconsistent across teams

Fit by situation

  • If your teams draft SOPs across departments, prioritize SOP authoring that stays consistent.
  • If people frequently ask for the latest procedure during work, prioritize Controlled access to the active SOP set.
  • If SOP changes require approvals and proof for internal reviews, prioritize Approval and review cycles for SOP changes.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

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 Listing

WHAT 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.