Legal & Advice

Requirements Coverage Agent

The gap only shows up once writing starts. By then the technical departments are already involved.

Calculates the coverage rate for a tender, technology by technology, piece of evidence by piece of evidence.

Open agent
Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

STACKIT Sovereign hosting in Germany, single-tenant from the first user.
Rödl Legal, tax and compliance expertise for legally sound deployment.
4P Consulting Advisory and implementation for the public sector, starting with the AI readiness assessment.

The coverage rate is in none of the documents; it only emerges when someone counts the lines.

The tender lists its requirements in tables, often spread across several annexes. Anyone who wants to know the coverage rate goes through it line by line and asks the relevant department about each technology area. By the time the answers are back, the table is circulating in three versions, and nobody knows which one counts.

146requirement linesThat is how many individual lines the annex to the specification contains.
4technology areasEvery line belongs to one area and therefore to a different contact in the organisation.
23lines without evidenceThese lines are still open after the first round.
3table versionsPassing it round by email produces three versions of the same assessment.

With the three table versions gone, assessment effort falls by 55%, and the 23 open lines are in one place rather than spread across three email attachments.

The 55% reduction in assessment effort is this agent's headline figure. The number of requirements, the areas involved and the table versions describe a typical procedure in bid management; they are illustrative, not measured.

Three steps through the process.

The agent checks every requirement against the stored evidence and calculates the coverage rate per technology area; the bid manager weighs up whether to bid with 23 lines still open.

Assign requirements to technology areas

The agent reads the requirement tables from all the annexes and assigns every line to an area. It merges duplicate lines from different annexes.

Procedure AS-2026-118, 146 lines spread across 4 technology areas

Match evidence against requirements

For every line, the agent checks whether evidence is stored in the repository and calculates the coverage rate from that. The figure is recalculated from the dataset on every call.

123 of 146 lines evidenced, 23 without evidence

Pass the gap list to the departments

The agent lists the lines without evidence by area and names the responsible unit. The list goes to the four departments with a field for their rationale.

deckungsgrad_as-2026-118.xlsx, 23 open lines, 4 recipients

What the agent does not do.

It does not decide whether to take part in the procedure.

It shows the coverage rate and the open lines. Bid management and executive management decide whether the organisation bids.

It does not fill in missing evidence.

For the 23 open lines, it names the technology area and the responsible department. The department says whether a reference can be supplied.

It does not weight the four technology areas against each other.

It calculates the coverage rate separately for each area and states the number of open lines for each. The bid manager reads from the procedure's scoring matrix whether one area carries more weight for the award than another.

Connected systems

  • Requirements database
  • departmental file store
  • procurement portal

Operations

  • Deployment modelEU cloud, private cloud or on-premises
  • Data processingGDPR-compliant, no model training on your data
  • Responsible teamsBid management, technical departments

The questions that come up before the first meeting.

How quickly is the Requirements Coverage Agent ready to use?

A pilot typically runs on your own data within 4 to 6 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.

Where is the data processed?

EU cloud, private cloud or on-premises. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.

Where does the figure “55% less assessment effort” come from?

It is based on experience from comparable projects and process benchmarks, not a commitment. We work out the realistic effect for your organisation during the assessment before the pilot.

Related agents.

Intake review, case 2026/04711

Skip to content

Page footer