Sample deliverable

See what a renewal decision calendar looks like.

This walkthrough is fictional and contains no client data or claimed result. It shows the structure, review states, and evidence a real delivery uses.

Fictional exampleRenewalNorth · review pack

Prepared for demonstration · no customer data

Working artifactrenewal decision calendar
Input profilebuyer-confirmed contract register metadata
Decision authorityBuyer retained
Example IDOutput sectionReview stateEvidence note
EXAMPLE-001120-day decision calendarReady for reviewRule and source retained
EXAMPLE-002Owner portfolio viewOwner confirmationNamed role assigned
EXAMPLE-003Notice-window registerInput rejectedNo value inferred
EXAMPLE-004Decision-state queueHuman decision requiredNo action taken

How to read it

Every important state carries its reason.

The report is designed for review, not theatre. A buyer can trace why a row appeared, which definition was used, what is missing, and who decides what happens next.

  1. 01

    Every date has a source page and confirmation state.

  2. 02

    Decision dates are distinct from renewal and notice dates.

  3. 03

    Owner changes and unresolved terms remain visible.

  4. 04

    No negotiation, cancellation, notice, or legal conclusion is performed.

Included sections

The complete pack is more than one table.

  1. 01120-day decision calendar
  2. 02Owner portfolio view
  3. 03Notice-window register
  4. 04Decision-state queue
  5. 05Source evidence index
  6. 06Escalation history

A useful first conversation

Want to compare this structure with your current review pack?

Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.