CAYPAXLoading
Loading
F-Procure
What does an F-Procure evidence package actually contain? Walk through a fictional procurement below — four connected records, their verification results, and the exceptions an auditor would see.
Synthetic scenario — not a client deployment
A fictional public authority — the Harbour District Works Authority — runs a competitive tender for a road-resurfacing programme. The walkthrough below shows the evidence package F-Procure would assemble for the award decision: four connected records, each independently verifiable, plus the exceptions an auditor would see.
The evidence package
Expand each record to see the events, sources, and verification results it contains. All values are illustrative.
Each tender response was fingerprinted (hashed) at the moment of receipt and the fingerprint anchored to an independent ledger. The documents themselves never leave the authority's sourcing platform — only the fingerprint is anchored, so a later change to any submission would be detectable.
Before the evaluation panel met, vendor checks were completed and their completion state was recorded as evidence. The package shows which checks were done, by whom, and — critically — that they were completed before the award decision, not backfilled afterwards.
The chronology of approvals is linked into a single chain: evaluation panel recommendation, budget confirmation, and final sign-off by the delegated authority. Each step references the one before it, so the sequence cannot be silently reordered.
The executed contract is durably linked back to the winning submission and the approval chain that authorised it. An auditor can start from the signed contract and trace to the exact submission fingerprint and approvals — or start from the tender and trace forward.
Exceptions
A credible evidence package does not hide irregularities — it records them with their explanations. This fictional scenario includes two.
A fifth response arrived 2026-03-27 17:22 UTC — 22 minutes after the deadline. The package records its receipt fingerprint and its exclusion decision, so the exclusion itself is evidenced rather than undocumented.
Execution exceeded the authority's 10-day policy target by 4 days. The exception is visible in the package with the recorded explanation, instead of being discoverable only by manual reconciliation.
The auditor's view
Reminder: this walkthrough is a synthetic illustration. It is not a client deployment, and no production evidence has yet been published. F-Procure's current maturity is described on the research page.
Next steps