Every contract, every pound, monitored in one place.
Sightline keeps the council's contract portfolio under continuous watch: expiry and extension clocks, statutory publication duties, price benchmarks and supplier relationships, with the source citation behind every figure.
Spend under management by category
Whole-life valueCommitted spend, rolling 12 months
£ per monthPriority alerts
5 need attentionAdd a contract
Upload a signed contract and the platform reads it for you, pulling out the fields that matter for the register. Every value is proposed with its confidence and the exact page it came from. Nothing is added until an officer has reviewed it.
Source document
Wyvern Borough Council contract registerReading the document
Contract added to the register
Source document viewer
Every extracted value is anchored to the exact place it was read from. Open any field to see the original contract page beside the value, with the source region highlighted, so an officer can confirm the figure against the signed document before it is relied on for audit, spend control or committee.
Contract register: expiry, extension and compliance monitoring
Every live and recently expired contract in one register, with the expiry clock, extension options, break clauses and publication duties tracked against statutory obligations. Rows flagged for a live breach or an approaching decision are surfaced first.
| Supplier & contract | Category | Annual value | Expiry clock▲ | vs peer | Award route & compliance |
|---|
Three-way reconciliation
Every contract is matched to its procurement notice, its payments and any waiver record. Records that do not line up stay visible: off-contract spend, payments continuing after expiry, missing or unpublished notices, and waivers awarded without the required publication.
Matching is on contract reference, supplier identity and payment dates against the recorded term. Figures, company numbers and supplier names are illustrative demonstration data and imply no wrongdoing by any real organisation. Open any record to see its full chain and the source clause behind each linked field.
Spend, supplier and benchmarking analysis
Consolidated supplier exposure across Wyvern Borough Council, with trading-name and legal-entity aliases reconciled to a single Companies House number, unusual spend surfaced, and unit prices benchmarked against the peer median to support evidence-based negotiation.
Supplier identity reconciliation
Ltd / Limited / trading names merged to one legal entityLedger lines arrive under inconsistent names. Each cluster below is matched to a single Companies House number so exposure is counted once, not scattered across spelling variants. Common ownership across separately named entities is surfaced as a related-party link.
Total supplier exposure
Price benchmarking against peer median
Signed variance, outliers highlighted| Supplier / service | Unit price | Peer median | Variance | Position vs peers |
|---|
Evidence-based negotiation framing
Unusual spend
| Type | Supplier | Detail | Value at risk |
|---|
Ask a question, or search an exact term
Every clause across the contract portfolio is split into meaningful sections, indexed for exact wording and for meaning, so you can ask in plain English or paste a precise phrase. Results cite the contract, document, page and section, with a snippet and a link to the source.
Search the contract portfolio
Ask a natural-language question or paste an exact clause. Try one of the examples above.
GraphRAG Explorer
Every contract, supplier, payment, notice and Companies House entity as one connected graph. Ask a question and the retrieval engine walks the relationships, then returns an evidenced answer with citations.
Every record is held as OCDS so the same contract is portable to Find a Tender, the audit committee and the public transparency feed without re-keying. Two defined extensions carry the council-specific fields.
Extensions in use: contractProcedureWaiver and beneficialOwnership (Companies House linkage), both declared in the package metadata.
Every material change is appended as a hash-chained event: what changed, when, and who. Nothing is rewritten or deleted, so this stream is the audit basis a Section 151 officer or external auditor can rely on.