tensorgardenChange orderFull documentPDF ↓
Short overviewFictional example

A useful idea should not become a surprise bill.

The operations coordinator asks for a weekly summary of requests by category. It sits outside the agreed priorities, so it is paused, not quietly added.

New request

Weekly workload summary, grouped by category.

Status: paused for a decision.

Agreed baseline

EXHIBIT-PROPOSAL, Priorities A and B.

As agreed in the proposal: flag, explain, decide.

See the week without rebuilding the picture.

Pick a week and see how requests split across Facilities, IT support and Operations. One view of where the workload sat.

Concept preview with sample data. Selected-week workload summary for 24 to 30 August 2026 with 24 sample requests: Facilities 12, IT support 7, Operations 5, beside the approved boundary: work begins only after EXHIBIT-APPROVAL (simulated), local only, no integrations.
Concept preview, sample data. Proposed weekly summary in the existing software; begins only after approval.

Concept preview · sample data

Category totals

Sample week: Facilities 12, IT support 7, Operations 5.

Counted once

Each request created in the selected week counts once, whatever its status.

Sample counts, not results. No forecasting, staffing or performance claims.

Define what the change includes.

Bounded before it begins, so the result can be checked against it later.

Included

Three things in

  • Group requests by category for the selected week.
  • Show an empty-state message when no requests match.
  • Add user-guide instructions and review notes.

Not included

Two things out

  • New integrations.
  • Automated outbound reports.

Sequenced after the baseline priorities. Any further scope or charge needs a new approval before work begins.

EXHIBIT-PROPOSAL → EXHIBIT-CHANGE

Before you approve

See the impact before you decide.

Your delivery lead sets out scope, capacity, sequence and the additional charge. The charge is privately agreed and approved before added work begins.

Concept preview with sample data. Weekly-summary feature request marked Paused for review, work start not authorized in this view, with a human review packet covering scope impact, capacity and sequence, additional charge and exclusions.
Concept preview, sample data. Illustrates the human review step; not an included change-management module.

Concept preview · sample data

Paused, not started

Work start is not authorized while the review is open.

People explain the impact

The approver hears scope, timing and charge from a person.

Approved first. Then the work begins.

The fictional approval covers only this bounded change, and it comes before any extra work.

  1. Flag and pause

    AI flags scope and cost drift. Added work is paused.

  2. Human review

    The delivery lead explains scope, capacity and timing to the approver.

  3. Approval

    EXHIBIT-APPROVAL records the fictional approval of this feature and its privately agreed charge BEFORE added work begins.

  4. Start

    People confirm the decision, then begin only the approved change.

AI cannot approve it. Any further scope or charge needs a new approval.

Simulated approval. No authorization is executed here.

Next: check the delivered work