Skip to content

EFOVEX finds the evidence for each tender requirement in the documents your organisation already keeps.

It matches that evidence to each requirement, shows what complies and flags what is missing, and every match links back to its source document. Your bid team works from a desktop app on one computer, and writes the bid itself.

How it works

Four stages
  1. Find

    EFOVEX
    Finds the evidence in your unstructured files as soon as you connect them, whether they sit on local drives, network shares or in cloud storage, and maps it into a knowledge graph, each entry traced to its source document. New and changed files join the graph as they arrive.
    You
    Connect your sources, mark any folders off-limits, and confirm what it found.
  2. Requirements

    EFOVEX
    Reads the tender and builds a typed checklist of the buyer’s requirements, linked back to the clauses they came from.
    You
    Upload the tender and review the checklist.
  3. Match

    EFOVEX
    Matches evidence from your files to each requirement and grades the fit, showing “no confident match” when nothing is strong enough.
    You
    Accept or reject each match.
  4. Flag

    EFOVEX
    Shows what complies and flags the requirements it could not find evidence for in your files. Evidence it found that nobody has confirmed yet is shown apart, for you to check.
    You
    Add documents that close a gap, then write the bid.

What goes in, what comes back

One tender

Intake

  • The tender, as the buyer issued it
  • The folders, network shares and cloud storage your team already works from
  • Any folders to keep off-limits, either unread or never matched
  • Your sector and country
EFOVEX

Deliverables

  • A typed requirements checklist, linked to the tender’s clauses
  • A browsable map of your evidence, traced to the documents it came from
  • A list of the requirements it could not find evidence for
  • A compliance view: each requirement, its matched evidence, its source document and a status (complies, partial or gap)

Specification

The appliance
  • SourcesFolders, network shares and cloud storage. Same permissions as the user: sees only what that user can already see.
  • AppA desktop app where your bid team reviews the requirements, the evidence matched to them and the gaps flagged
  • ConnectionInternet-isolated: connects to one workstation only; never initiates a connection
  • BoxNo files stored: files stay where they live; the box keeps only an encrypted index

Tenders

Any industry and any jurisdiction, defence included.

Logs

Fully auditable: security logs record every action on the box.

By design

What it does not do
  • It does not need a content library or an onboarding project.

    It maps the evidence in the files you already keep and asks your team to confirm what it found. New and changed files are picked up as you work.
  • It does not silently match an expired certificate or a superseded document.

    Expired certificates and superseded documents go back for review, and a nightly check of validity dates flags anything due to lapse before a known closing date.
  • It does not write the bid.

    It finds, matches and flags the evidence. Your team writes the bid, with every match linked back to its source document.