Administration & governance

Procurement that arrives at a contract someone manages

Need, procedure, award, contract, execution and closure, in a single file that survives the procurement officer moving on.

Request a demo See how it works

Procurement procedures with their lifecycle states
The procedureEvery procedure carries its state, its owner and its file.Need · procedure · award · contract

Why it matters

The file an audit asks for, already assembled

Public procurement is scrutinised more than any other administrative process, and the scrutiny happens years later. Keeping the need, the procedure, the evaluation, the contract and every delivery in one place means the file that answers an audit already exists.

Need, procedure, evaluation

The reasoning is kept with the award.

The contract and every delivery

Performance is recorded against the clauses it answers.

Years later, still one file

The scrutiny arrives long after the process; the file does not have to be rebuilt.

What it covers

From the need to the last delivery

One file that keeps its shape from the annual plan to contract closure.

Annual procurement plan

Needs consolidated, valued, and matched to budget lines.

Procedure

Threshold, procedure type and timetable, with the approvals each step requires.

Evaluation

Criteria, committee, scores and the reasons behind the award.

Contract

Obligations, deliverables, prices, guarantees and deadlines.

Execution

What was delivered, accepted, invoiced and paid, against what was agreed.

Suppliers

One supplier record across procedures, contracts and performance.

How it works

Planned, procured, awarded, executed

The route is decided by the threshold and the rules, not by who has done it before.

01

Consolidate the need

Departments submit needs into one plan, so the administration sees the total before it splits it into procedures.

02

Run the procedure

Thresholds decide the route; approvals, publication and deadlines follow the configured procedure rather than local habit.

03

Award and contract

The evaluation record becomes the award decision, and the contract inherits its terms and deliverables.

04

Manage execution

Deliveries, acceptance, guarantees and amendments are recorded on the contract until it closes.

Outcomes

What changes

A contract portfolio that is managed while it runs, not reconstructed when it ends.

One file per procurement

Need, procedure, award and contract stop living in three systems.

Contracts that are managed

Deadlines and deliverables carry owners and reminders.

Supplier performance visible

Across contracts, not one contract at a time.

Configured per administration

What is configured

  • thresholds and the procedure applied to each
  • approval limits and who signs at which value
  • evaluation criteria and committee rules
  • the documents each procedure must produce
  • publication obligations and where they are met
  • contract templates, guarantees and penalties
  • acceptance and payment certification steps
  • the reports oversight bodies require

Connected to

The rest of the platform

  • Budget, for commitments and available funds
  • National procurement platforms
  • Contractor and SLA management, for what the contract delivers operationally
  • Registry and audit, for the evidence trail

On your own thresholds

See procurement run end to end.

We configure one of your procedure types with its real approval limits and documents, and follow it through award, contract and a delivery.

Request a demo All administration & governance