Data requirements

A smaller, documented input makes the service safer and easier to audit.

The normal starting point is buyer-confirmed contract register metadata. Nothing operational should be sent through the public website.

Accepted profile

Fields the working schema is designed around.

The field list is a planning profile, not a request to email data. The exact schema and secure exchange are agreed in writing after fit review.

Explicit exclusions

No legal advice, negotiation, autonomous cancellation, unsupported date interpretation, or claim that reminders guarantee savings.

Credentials, unrestricted system access, and unrequested free text are never part of the published plan.

Data lifecycle

01
Agree
Write down the permitted fields, purpose, owner, transfer, retention, and deletion rule.
02
Prepare
The buyer exports and normalizes only the agreed minimum input.
03
Validate
Schema failures and unknown values are rejected without inference.
04
Deliver
Portable outputs carry definitions, exceptions, and confirmation states.
05
Delete
Working data follows the written retention rule; the buyer keeps the final pack.

Field glossary

Renewal date: The reported date on which an agreement may renew.
Notice window: The reported period in which an authorized notice may be required.
Decision date: An internal date chosen to preserve review and action time.
Decision state: Undecided, review, renew, renegotiate, cancel, or closed as set by the buyer.
Source evidence: The page reference supporting the recorded contract fact.
Runway: The time band remaining before the buyer's decision date.

A useful first conversation

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