# Question - "retiring" a policy how to

**URL:** https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061
**Category:** Forum - Software
**Created:** [March 10, 2022, 8:44am UTC](https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061 "2022-03-10T08:44:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![eramba](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/e/c6cbf5/32.png) [@eramba](https://discussions.eramba.org/u/eramba)
#### Post date: [March 10, 2022, 8:44am UTC](https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061/1 "2022-03-10T08:44:45Z")

</div>

today we got this question:

> _We have a policy that has been replaced by another policy. Is there a way in Eramba to retain it for our records without needing to continue to review it?_

int ref: [https://eramba.zendesk.com/agent/tickets/15811](https://eramba.zendesk.com/agent/tickets/15811)

retiring im sure means different things to different people .. like everything in this bloody industry, but based on the immediate translation of the word and the question i would:

1/ delete all incomplete reviews in the future , that will make sure the polcy is never going to miss a review in the future and you will therefore never hit a yellow status (incopmlete review)

![delete review](https://discussions.eramba.org/uploads/default/original/2X/9/94428ebfadd501d2ee7cbc30f9d0eaff495637d5.gif)

2/ i would create some custom field (you can also use tags) to highlight this polcy as retired (lucky policy, i would like to be retired too!)… i do it with tags now but you can do it with custom fields too.

![screencast 2022-03-10 09-41-57.gif.sb-df8ae133-JxhBfK](https://discussions.eramba.org/uploads/default/original/2X/6/6288c974d0a21c627ae404f94134670e5301bac1.gif)

I think that is at least one way of doing this .. im sure there are other ways. you can also creaet a notification that triggers when retired status switches on (or off) and notify the policy roles…

i hop this helps

---

<div class="post-metadata">

### Author: ![jpeppas](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/j/c57346/32.png) [@jpeppas](https://discussions.eramba.org/u/jpeppas)
#### Post date: [February 14, 2026, 8:42am UTC](https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061/2 "2026-02-14T08:42:38Z")

</div>

I have actually now run into this.. Reviewing various policies, I am simplifying, condensing, migrating to other policies/procedures.

I order to follow this, I have created a custom field “Retired (yes/no)” but I think that there should be some consideration of adding the “Retired” or “Obsolete” or “Superseded” in the Status of the Policy, since it’s (in my opinion) something quite common

---

<div class="post-metadata">

### Author: ![david.davis](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/d/6bbea6/32.png) [@david.davis](https://discussions.eramba.org/u/david.davis)
#### Post date: [February 16, 2026, 10:53am UTC](https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061/3 "2026-02-16T10:53:17Z")

</div>

It is a very basic part of any documentation workflow, I remember requesting a way to do it about 4 years ago too.

My workaround in the meantime has been to add a custom tag for ‘OBSOLETE’ and put the next review 100 years into the future so I will not be bothered by any reminders 🫠

---

<div class="post-metadata">

### Author: ![david.schroth](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/d/43a26b/32.png) [@david.schroth](https://discussions.eramba.org/u/david.schroth)
#### Post date: [February 16, 2026, 1:25pm UTC](https://discussions.eramba.org/t/question-retiring-a-policy-how-to/2061/4 "2026-02-16T13:25:23Z")

</div>

Pro tip. After you create the review (needed to do the last review), you can then delete the review and never be bothered again, even in 100 years.