Renewal decisions

Pytheus classifies each renewal as actionable, monitor, or insufficient data, and never treats unknown auto-renew as no action.

Last updated September 22, 2026

Not every upcoming renewal needs a decision today, and treating them all the same either buries the urgent ones or cries wolf. Pytheus classifies each renewal so the ones that need you now stand out, and it is deliberately careful about auto-renewal.

The three outcomes

  • Actionable. A decision is needed now. The renewal, or its notice deadline, is close enough that acting late means losing leverage or auto-renewing by default.

  • Monitor. Worth watching, but not yet urgent. A renewal may be approaching while its auto-renew terms are unknown, so the right move is to confirm those terms rather than assume.

  • Insufficient data. Pytheus does not have enough on the contract to classify it. That is a prompt to fill in the missing dates or terms.

Unknown auto-renew is never "no action"

The most dangerous assumption in renewal management is that silence means safety. Pytheus never treats unknown auto-renew terms as if no action is needed. An unconfirmed auto-renew clause is exactly the kind of thing that quietly locks you into another term, so it lands in Monitor with a clear nudge to confirm, not in a done pile.

If you do not know whether a contract auto-renews, that is a finding, not a non-issue. Confirm the terms before the notice window closes.

These classifications also feed the renewals view in My Work, so the people who own contracts see what needs attention. For the underlying dates, see Renewal tracking.