RESEARCH-STAGE CONCEPTInspect the synthetic demo

SOURCINGRECORD / Dated margin

Give every renewal a dated review.

Bids Proof is a proposed renewal review module. It surfaces changed clauses and notice dates as dated evidence for a sourcing owner, with proposed terms clearly separated from accepted ones.

DEMO — SYNTHETIC DATA

Dated marginNotice rail reaches the reviewer date; clause change remains unaccepted. DEMO — SYNTHETIC DATAAGR-209 · clause version 1Proposed notice change: 60 → 90 days · unaccepted13 OctNotice received15 OctLina reviews1 NovIllustrative deadline31 DecExpiryDate counting remains held for review.Dated marginDEMO — SYNTHETIC DATASR / 05
01
AGR-209 v1

Expiry 31 Dec 2026 · 60-day clause

02
NOTICE-209 v1

Proposed 90-day change · unaccepted

03
Lina review

15 Oct 2026 · date counting held

DEMO — SYNTHETIC DATA

One clause.
Two versions.

SOURCE · COMPARISON · REVIEW

THE JOB / THE BASIS

Are change notices reviewed against the version you actually signed?

For indirect procurement heads and category managers at midmarket companies with repeat tail-spend purchases.

INPUT

Permissioned agreement versions and change notices.

OUTPUT / PROPOSED

A clause comparison, source dates, assigned owner and review action.

THE WORKFLOW

A specific job.
A visible review point.

Each step retains the source and the unresolved exception.

01

Read the versioned clause

Preserve the agreement version, source page and stated notice period.

02

Expose the change

Distinguish the existing 60-day clause from a proposed, unaccepted 90-day change.

03

Assign a dated review

The reviewer confirms counting and delivery rules before treating a date as settled.

THE EXAMPLE

A notice is not
an accepted change.

AGR-209 and NOTICE-209 are fictional. The existing 60-day clause, proposed 90-day wording and source dates remain separate. The effective date is unknown until review.

Dated marginNotice rail reaches the reviewer date; clause change remains unaccepted. DEMO — SYNTHETIC DATAAGR-209 · clause version 1Proposed notice change: 60 → 90 days · unaccepted13 OctNotice received15 OctLina reviews1 NovIllustrative deadline31 DecExpiryDate counting remains held for review.Dated marginDEMO — SYNTHETIC DATASR / 05
01
AGR-209 v1

Expiry 31 Dec 2026 · 60-day clause

02
NOTICE-209 v1

Proposed 90-day change · unaccepted

03
Lina review

15 Oct 2026 · date counting held

DEMO — fictional renewal notice; date counting held.

LIMITS / INTEGRATION SCOPE

Controls that stay in view.

A proposed module is a bounded workflow, not a general-purpose autonomous agent. Source-to-pay mapping would be assessed within a permissioned pilot; no production integration is claimed.

  • Proposed wording is not an amended contract.
  • No automatic legal deadline determination.
  • No renewal notice or supplier message is sent.
Read all controls

FAQ

Before you choose the module.

Is the example notice date a legal determination?

No. The fictional 1 November 2026 calculation is illustrative and held for a reviewer to confirm date-counting and delivery rules.

Can Bids Proof amend an agreement?

The concept does not amend contracts or send notices. Proposed changes remain unaccepted until the relevant human review and authority are established.

A BOUNDED NEXT STEP

Put Bids Proof under review.

Start with the repeat category, the available permissioned sample and a named sourcing owner.

Discuss a category pilotInquiry form preview · nothing submitted