> ## Documentation Index
> Fetch the complete documentation index at: https://docs.humanintelligence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change Lifecycle

> How metric and segment changes are reviewed and approved.

Human Intelligence treats methodology changes as governed changes, not casual edits. When someone updates a metric formula or redefines a segment, they're changing how the entire organization interprets a business question — so every change follows a structured lifecycle.

## The lifecycle

Every change moves through a clear sequence of steps. You can think of it as a lightweight review process built into the platform.

<Steps>
  <Step title="Validate">
    Before anything else, Human Intelligence checks whether the proposed change is well-formed. Can the formula compile? Do the referenced dimensions exist? Are required fields filled in?

    Validation catches mistakes early so you don't save a definition that can't actually run.
  </Step>

  <Step title="Preview">
    Once validation passes, you can preview what the change will look like in practice. For metric changes, this means comparing the current result with the proposed result side by side.

    Preview helps you confirm that the change matches your intent before anyone else sees it.
  </Step>

  <Step title="Save">
    Saving makes the change active for the organization. Every save requires a reason — a short note explaining why you made the change.

    This reason becomes part of the permanent record. Future reviewers will see it in the audit log.
  </Step>

  <Step title="Approve">
    Approval marks a definition as reviewed and accepted. This is especially useful when a team has evaluated a platform default, accepted a custom override, or confirmed that a new metric is ready for production use.

    Approved definitions signal trust to everyone in the organization.
  </Step>

  <Step title="Revert (if needed)">
    If a saved change turns out to be wrong, you can revert to the previous definition. Revert restores what was there before and logs the action so the team knows what happened.

    Because methodology changes can affect reports, executive decks, and headcount planning, the ability to undo quickly matters.
  </Step>
</Steps>

<Tip>
  Every change captures a reason. Future reviewers will thank you — write a clear, specific note about why you made the change, not just what you changed.
</Tip>

## Source and status

Each definition in Human Intelligence carries a source and a status so you always know where it came from and where it stands.

<Accordion title="Platform default">
  A metric or segment provided out of the box by Human Intelligence. These are industry-standard definitions maintained by the platform.
</Accordion>

<Accordion title="Platform override">
  A customer-specific version of a platform default. Your organization has customized the standard definition to better fit your needs.
</Accordion>

<Accordion title="Custom">
  A definition created entirely by your organization. These don't have a platform equivalent — they're unique to your business.
</Accordion>

<Accordion title="Proposed">
  A change that has been drafted or saved but not yet approved. Proposed definitions are active but haven't been formally reviewed.
</Accordion>

<Accordion title="Approved">
  A definition that has been reviewed and accepted by your team. Approved status signals that this definition is trusted and ready for use.
</Accordion>

<Accordion title="Reverted">
  A definition that was rolled back to a previous version. The revert is logged so reviewers can see what was undone and why.
</Accordion>