← Other Athentra features

Hub: Lifecycle · Scheduling

Retirement Planning

A retirement date can be set against a managed object, together with a note explaining the decision. The object's state reflects that a retirement has been planned, and both the date and the reasoning are held with the record rather than in a calendar reminder or a side conversation. Planning and its rationale stay attached to the thing being retired.

  1. 01

    Pain Point

    What's the problem?

    Deciding that something should go is easy. Recording when, and why, is where it usually falls apart.

  2. 02

    Remedy

    How do we attack it?

    Set the date an object should leave active use and record the decision behind it

  3. 03

    Your Value

    What do you get out of it?

    Keeps the intended end date and its reasoning with the object rather than in somebody's calendar