We make extensive use of flags in Hudu to indicate the current state of documentation — for example:

• 🟡 In Progress

• 🔴 Outdated / Needs Review

• 🟢 Reviewed / Up-to-Date

• 💎 Verified / Production Ready

However, documentation is never permanent. Even high-quality or recently verified entries eventually become outdated as systems, integrations, and processes evolve.

Currently, flags in Hudu remain static unless changed manually, which often results in outdated material staying marked as “Up-to-Date” indefinitely.

We propose adding flag expiration and automatic status transitions to help maintain documentation accuracy and freshness.

Desired functionality

• Each flag type can have an optional expiration period (e.g., 90 days, 6 months, 1 year).

• When that period passes since the item was last updated or re-flagged, Hudu automatically downgrades the flag — for example:

• Up-to-Date → Needs Review after 90 days of inactivity

• Verified → Needs Re-Validation after 6 months

• Admins can configure:

• Default expiration values per flag type

• Which flag should be applied when the current one expires

• Whether notifications or reminders are sent to assigned users or groups

Benefits

• Keeps documentation automatically rotating through review cycles

• Reduces manual maintenance overhead

• Ensures content accuracy over time

• Enables MSPs to easily identify stale or unverified materials

In short, we’re requesting an enhancement where flags can expire and automatically revert to a review-needed state after a configurable period of time — enabling continuous, semi-automated documentation lifecycle management directly within Hudu.