South Norfolk Council's CRM procurement, 2547-PPT-R
A changed tender.
A fresh task plan.
Connect an official correction to the work it affects. Reopen the right tasks and keep the team's approved work.
One recorded workflow, from evidence to decision.
Query the real sources
Native Zetaris SQL joins notices, REST tasks and a PostgreSQL register: 11 rows, 7 evidence-to-task links and 5 affected tasks.
Keep a colleague's edit
A simulated teammate reopens finance review and adds a note after the first plan has been prepared.
Stop the stale batch
The complete-batch version gate detects the change. The first application stops with zero writes.
Refresh and apply
A fresh query produces four writes and one already-aligned task. Native verification returns zero further changes.
The full colleague note, existing turnover evidence, three case studies and completed architecture remain recorded. Final sign-off stays paused pending the applicable guidance.
Inspect what actually ran.
Zetaris performs the cross-source query. BidDelta's small Python service adds a version-checked atomic write to the illustrative task source.
Clause-to-action rules cover this one historical amendment, with a fixed dependency map and document register.
Source records
Original notice 035490-2024
Correction 036312-2024
Illustrative tasks and document register
Earlier research and data contract
Public notice information: Open Government Licence v3.0.
Read the full narration
1. A tender changes after your team signs off. Which tasks need reopening, and which completed work should stay? BidDelta links each amendment to its affected tasks. This is a historical public tender with an illustrative supplier workspace.
2. One native Zetaris SQL query connects the historical notices, a REST task source, and a PostgreSQL document register. It returns eleven rows, seven evidence-to-task links, and five affected tasks. Each proposed action carries the exact source version. You can inspect the executed SQL and native response.
3. The financial clause adds minimum requirements; the technical clause adds questions. Existing turnover evidence and three case studies remain recorded. Both reviews share one request for the missing guidance, and final sign-off pauses until that guidance is reviewed.
4. Now a simulated colleague reopens the finance review and adds a note. The prepared plan still carries the earlier version. Checking that stale batch stops every write. Zero tasks change, and the colleague's complete note stays intact.
5. Refreshing runs another real Zetaris query. The reopened finance task is already aligned, so the new plan applies four changes and retains one. A final native query confirms the new source snapshot, with zero further writes. The completed architecture task and document records remain intact.
6. My experience building on Zetaris was practical: I installed the supplied platform, registered the sources, and tested the same query before and after a task changed. The useful moment was seeing the fresh task version arrive through the federation query alongside the original clause and document evidence. I also hit two concrete integration issues: local file access and a repeated-view query. Using the platform's PostgreSQL connector for the register and referencing each REST source once made this replay work. Zetaris is amazing here because one SQL result makes scattered evidence reviewable together. BidDelta then adds the version-checked task write-back. That separation gave me a clear, testable route from source evidence to a recorded decision while preserving the colleague's work.
7. The code, source provenance, and genuine execution receipts are public. For a supplier bid manager, the outcome is concrete: a changed tender becomes a fresh, reviewable task plan, with approved work preserved. Explore BidDelta by Blucca on GitHub.
Original commentary by Blucca, spoken by a synthetic English narrator. Recorded and authored 28 October 2026.
Working with a real tender change?
Send the notice, your current task system and the date you need a result.
Discuss a procurement workflow