Every agreement in Murmur has an expiration date. This could be as little as two weeks, or as long as a year. The clock starts toward expiration as soon as a proposal secures consent and becomes active.
When the expiration date arrives, the agreement is no longer active in your workspace, and your team will get to decide what to do with it moving forward.
Extend – Give it another go! When an agreement has gone well (and the team doesn’t feel the need to make any changes), you can simply extend it for the same amount of time it was active before (i.e. if it was active for a month, it will extend for another month).
Change – Keep it going, but change things up. When things could have gone better, propose changes to the agreement so it better fits your team’s needs. Any changes you propose will need to reach consent before they become active again.
Archive – Ditch it. Sometimes an experiment doesn’t go well, or maybe it did and your team just no longer needs the agreement. In these cases, toss it in the archive. You can always bring it back in the future.
Expiration is also linked to feedback frequency. Murmur automatically collects feedback on an agreement a week before it expires, asking members of your workspace how they think the agreement has gone so far and what they’d vote to do with it next. Based on the team’s feedback, admins can extend, change, or archive the agreement to make sure it stays relevant to your organization’s current context.