Run Feature Flag Lifecycle Review — Free

Review Scope and Identification

Review date and time

Record the date and time this lifecycle review is being conducted.

Reviewer name and role

Full name and team role of the person conducting this review (e.g., Platform Engineer, Release Manager, Tech Lead).

System / service under review

Name of the application, microservice, or platform whose feature flags are being audited.

Environment scope

Which environments are included in this review?

Total number of active flags in scope

Enter the total count of active feature flags being reviewed in this session.

Feature flag management platform in use

Identify the tool or platform used to manage feature flags (e.g., LaunchDarkly, Unleash, Flagsmith, custom in-house system).

Flag Inventory and Ownership Verification

All active flags have a designated owner (team or individual) documented in the flag management system critical (required)

Every flag must have an accountable owner who can make retirement or continuation decisions. Flags without owners are a configuration drift risk.

Yes No N/A

Number of flags with no documented owner critical (required)

Count of flags currently lacking an assigned owner. Target: 0.

All flags follow the organization's standard naming convention

Consistent naming (e.g., [team]_[feature]_[type]) enables searchability and lifecycle tracking. Non-conforming names should be flagged for remediation.

Yes No N/A

Each flag has a documented purpose or linked ticket/story critical (required)

Flags must be traceable to a business or engineering requirement. Undocumented flags cannot be safely retired or evaluated.

Yes No N/A

Each flag has a defined flag type documented

Flag type should be recorded (e.g., Release Toggle, Experiment/A-B, Ops Toggle, Permission Toggle) to guide lifecycle expectations.

Yes No N/A

Owner contact information is current and reachable critical (required)

Verify that the listed owner's contact details (email, Slack, team alias) are valid and not pointing to departed employees or disbanded teams.

Yes No N/A

Staleness and Age Assessment

Number of flags active for more than 90 days without a scheduled review critical (required)

Flags older than 90 days without a review are considered stale candidates. Target: 0. Each should have a documented justification for continued existence.

All flags older than 90 days have a documented justification for remaining active

Each long-lived flag must have a written rationale (e.g., permanent ops toggle, ongoing experiment with defined end date) recorded in the flag management system.

Yes No N/A

Flags that are 100% enabled or 100% disabled in all environments

Flags permanently set to a single state in all environments are prime retirement candidates — they are no longer providing toggle value and add dead code risk.

All flags have a defined expiry date or scheduled review date

Best practice requires every flag to have a planned review or expiry date set at creation. Flags without expiry dates accumulate as technical debt.

Yes No N/A

Flags associated with completed or cancelled features have been identified for retirement critical (required)

Features that have been fully released, rolled back permanently, or cancelled should have their flags queued for decommissioning.

Yes No N/A

Configuration Drift and Risk Evaluation

Flag configurations are consistent across environments where consistency is required critical (required)

Flags that should be in the same state across staging and production (e.g., security controls, compliance features) must be verified for parity. Discrepancies are a non-conformance.

Yes No N/A

Number of flags with configuration discrepancies between production and staging

Count of flags where the enabled/disabled state or targeting rules differ unexpectedly between production and staging. Target: 0 unintentional discrepancies.

No flags are overriding security controls, authentication, or authorization logic critical (required)

Flags that bypass authentication, authorization, or encryption must be reviewed with the security team. Such flags represent a critical risk if left enabled or misconfigured.

Yes No N/A

Flags controlling compliance-sensitive features (e.g., data retention, PII handling, audit logging) are reviewed by a compliance stakeholder critical (required)

Any flag that can alter data handling, logging, or regulatory compliance behavior must have documented sign-off from a compliance or legal stakeholder.

Yes No N/A

Flag targeting rules (user segments, percentage rollouts) are documented and intentional

Targeting rules should be reviewed to confirm they reflect current intent and have not drifted from the original design due to ad-hoc changes.

Yes No N/A

Retirement and Decommissioning Actions

Number of flags approved for retirement during this review

Total count of flags that have been approved by their owner for decommissioning as a result of this review.

Each flag approved for retirement has a linked code cleanup ticket critical (required)

Retiring a flag from the management platform without removing the associated code branches creates dead code. A ticket must be created and assigned for each flag being retired.

Yes No N/A

Retirement timeline established for each flag being decommissioned

Each flag approved for retirement must have a target decommission date documented, including flag removal from the platform and code cleanup completion.

Yes No N/A

Flags being retired have been communicated to all dependent teams critical (required)

Teams consuming or depending on the flag behavior must be notified before removal to prevent unexpected breakage.

Yes No N/A

Overall flag inventory health rating

Reviewer's overall assessment of the flag inventory's health based on this review.

Get your results

Enter your email — we'll send you a PDF of your filled-out template, plus the occasional MangoScoop newsletter (templates, workflow tips, product updates). Unsubscribe anytime — link is in every email.

Email (required)

Your name (optional)

Run: Feature Flag Lifecycle Review

Review Scope and Identification

Flag Inventory and Ownership Verification

Staleness and Age Assessment

Configuration Drift and Risk Evaluation

Retirement and Decommissioning Actions

Get your results