For contracting authorities

Solutions for Contracting Authorities

From planning and PAAP to supporting documents and procedures, with ePAAP + consulting.

ePAAP Platform

ePAAP — Digitizing PAAP and necessity reports

  • ePAAP.feature1
  • ePAAP.feature2
  • ePAAP.feature3
  • ePAAP.feature4
  • ePAAP.feature5

Error reduction · Full traceability · Audit readiness · Time savings

Request ePAAP demo for your institution
ePAAP Workflow
1
Needs / Budget items
2
CPV Grouping → PAAP
3
Necessity reports
4
Signature workflow
5
Supporting documents

Consulting for Authorities

PAAP Audit & Optimization

We review and correct the annual program, identify inconsistencies and propose solutions.

Award Documentation Support

We prepare complete documentation: data sheet, specifications, contract templates.

Evaluation Committee Assistance

Qualification documents and bid analysis, without legal representation.

Completed Procedures Audit

Concrete recommendations for future procedures based on lessons learned.

The questions an audit asks

An audit does not check whether the plan looks good. It checks whether every figure in it can be justified.

Which stated need does this line rest on?

The needs memo, identifiable by number, date and issuing department.

How was the estimated value determined?

The method recorded alongside the value: market research or historical basis, with source and date.

What else was bought for the same need this year?

The history of identical or similar purchases, which counts towards the cumulative threshold.

Why was this line changed in March?

The documented cause of each update, and the previous version of the plan.

Who approved it, and in what order?

The signature flow, with the approvals required before sign-off.

Where are the supporting documents?

Attached to the line, not in a separate folder reconstructed afterwards.

New area

AI adoption and governance in public institutions

A contracting authority meets artificial intelligence in two different ways: it buys it through procurement, and it uses it internally. Each carries its own obligations.

When you buy AI

Transparency does not come with the product by default. If the obligation is not written into the specifications, it will not appear at acceptance.

  • — Verifiable requirements in the specifications, not general wording
  • — Classifying the system: general purpose, high risk, or public-facing
  • — Award criteria that can be evidenced at evaluation
  • — What is actually accepted: documentation, logs, auditability

When you use AI internally

In most institutions AI is already in use: no institution-level accounts, no training, everyone with whatever tool they like. The first step is an inventory of what is already running.

  • — An inventory of the systems in use, by department
  • — Classifying each one and the obligations it triggers
  • — Internal rules for working documents and personal data
  • — Training the people who use them daily

We work with the ISO/IEC 42001 framework for AI management systems and with the obligations of the EU AI Act. On the legal side we stop at documentary analysis: we do not provide representation.

Tell us about your procurement year

We'll propose a combination of ePAAP + consulting tailored to your needs.

Contact us for a discussion