# Managing change with Rollout Flags

**URL:** <https://discourse.haskell.org/t/managing-change-with-rollout-flags/12534>\
**Category:** Links\
**Created:** [July 22, 2025, 11:50am UTC](https://discourse.haskell.org/t/managing-change-with-rollout-flags/12534 "2025-07-22T11:50:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rumaan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/rumaan/32/5158_2.png) [@rumaan](https://discourse.haskell.org/u/rumaan)\
**Post date:** [July 22, 2025, 11:50am UTC](https://discourse.haskell.org/t/managing-change-with-rollout-flags/12534/1 "2025-07-22T11:50:03Z")

</div>

My first post on the Scrive engineering blog was about our change mechanism called “Rollout Flags”, how it differs from other kinds of flags and its implementation in Haskell:

> **[Managing change with Rollout Flags](https://tech.scrive.com/2024-03-19-managing-change-with-rollout-flags/)**
>
> Rollout flags are a software component used to control the progressive activation of features throughout a system.