[ SOLUTION / BID MANAGERS ]

Get to a defensible go/no-go before the week runs out

A bid manager’s job is not finding tenders. It is deciding, with evidence, which ones deserve the team’s next six weeks, and then not being caught out when the buyer changes a clause. Defense Explorer reads the tender package with citations, checks each requirement against your approved evidence and keeps the decision on record.

Start free trial See cited briefs
UPDATED 15 SEP 2026

The short version

[ TL;DR ]

Defense Explorer is built for the part of the bid cycle between “this looks relevant” and “we are writing it”: reading the package, finding the gaps, deciding, and staying current when the tender moves.

  1. 01Briefs where every claim cites the document page and quotes it, so you check a sentence instead of re-reading 140 pages.
  2. 02A requirements matrix you can correct, linked to certificates and references that only count when they are approved and in date.
  3. 03Material amendments on followed tenders, shown clause by clause, with the affected requirements flagged for re-review.
  4. 04A bid/no-bid decision with a written rationale that stays on record, superseded rather than overwritten.
  5. 05It does not write the proposal. It stops at qualification and the decision, deliberately.

Your week, and where it breaks

[ THE JOB ]

Four moments every bid manager recognises.

Monday is the capture meeting. Somebody has a list of new notices, somebody else has a spreadsheet of live pursuits, and half the hour goes on working out what changed since last week. Tuesday a promising NSPA or TED notice turns out to have a 90-page annex in French and a mandatory certification buried in section 7. Thursday the go/no-go needs a rationale that will still make sense to the commercial director in three months. And two days before a deadline the buyer publishes a corrigendum that quietly changes a mandatory requirement.

None of that is a search problem. It is a reading, evidence and memory problem, and that is what Defense Explorer is designed around.

Reading the package

For watchlisted and pursued notices, Defense Explorer fetches the public documents, parses them page by page, and generates a cited brief. Each claim carries the document and page it came from and the verbatim quote. If the quote cannot be found in the cited text, the claim is downgraded to unknown rather than shown as fact. Where two documents disagree, the claim is marked conflict for review. Portals that require a login are labelled gated, not scraped, and a scanned PDF without text is reported as unreadable rather than guessed at.

Checking requirements against what you can prove

Requirements are extracted into a matrix. You can correct or dismiss a line and add your own; corrections are kept for your company and survive re-extraction. Each requirement is then assessed against your evidence library. The rule is strict on purpose: only an approved evidence item inside its validity dates can satisfy a requirement, and an ISO 9001 certificate never satisfies an ISO 27001 requirement. When an item does not count, the matrix names the rule that blocked it.

Deciding, and keeping the reason

Decisions in the capture pipeline are append-only: pursue, hold (with a review date and reason) or decline, each with the author, the rationale, and the profile and document versions it was taken against. A new decision supersedes the old one; nothing is deleted.

The late amendment

Followed notices are re-checked for new document versions. Cosmetic differences such as reflowed text or pagination never notify anyone. A material change produces an event with the original and updated clause side by side, notifies the owners of the affected assessments and pursuit, marks those requirements for re-review, and recommends revisiting the current decision. It never rewrites the decision for you.

A week with Defense Explorer

[ 05 DAYS ]

What the same week looks like when the reading and the memory are handled.

  1. STEP 01

    Monday: run the capture meeting from the weekly review

    The review screen groups what needs the room: undecided pursuits, holds that have reached their review date, approaching deadlines and changed requirements. Record decisions and assign owners inline, then close the meeting so it is on record.

  2. STEP 02

    Tuesday: triage new fits

    Your digest and the match dashboard show new notices scored against each product line, with the reasons, the unknowns and any hard blockers listed separately. Add the promising ones to the pipeline in the Reviewing stage.

  3. STEP 03

    Wednesday: read the brief, not the whole package

    Open the brief, click through the citations that matter, correct any requirement the extraction got wrong, and ask follow-up questions in Q&A, which answers with citations to the indexed text.

  4. STEP 04

    Thursday: go/no-go

    Check the requirements matrix against approved evidence, export the qualification pack as PDF or XLSX for the reviewer, and record the decision with its rationale.

  5. STEP 05

    Friday: stay current

    Acknowledge any material amendment, re-check the flagged requirements, and let the Today view and the calendar feed carry next week’s actions and deadlines.

What you will use most

[ 06 TOOLS ]

What to set up on day one

[ 07 STEPS ]

Roughly an afternoon. The matrix is only as good as the evidence behind it.

  • 01Describe your company and add one product line per thing you actually sell, with keywords, CPV codes and markets.
  • 02Add exclusions for work you never bid, so it stops appearing.
  • 03Upload or record your certificates, clearances and references in the evidence library, with issuer and validity dates.
  • 04Have a second person review and approve those evidence items; drafts never satisfy a requirement.
  • 05Create a saved search per pursuit theme and set daily or weekly frequency.
  • 06Add current live bids to the pipeline, with an owner and a next action each.
  • 07Subscribe to the calendar feed so deadlines and next actions land in your calendar.

Try it on a live tender

The fastest way to judge a qualification tool is on a tender you already know. Start a trial, add one notice you have bid before, and compare the brief and requirements matrix with your own notes.

Start free trial

Questions

[ 05 ANSWERS ]
01

Does Defense Explorer write the bid response?

No. Proposal drafting is deliberately out of scope. Defense Explorer covers finding, reading, qualifying and deciding, and the record of why. Your writing process starts from a qualified tender with a checked requirements matrix.

02

How do I know a brief is not hallucinating?

Every claim cites a span of the source document and quotes it. The quote is checked against that span; if it is not there, the claim is shown as unknown with “citation could not be verified”. Claims backed by disagreeing documents are marked as a conflict. The brief makes no fit recommendation, only facts and unknowns.

03

Can I share a qualification pack with a reviewer outside the platform?

Yes. The qualification pack exports as PDF or XLSX, the brief as PDF with its citations, and the requirements matrix as CSV. See cited briefs for what each contains.

04

What happens when the buyer publishes a corrigendum?

If the notice is followed, a new document version is compared with the previous one. Cosmetic changes are ignored. A material change notifies the people who own the affected assessments and the pursuit, marks those requirements for re-review, and recommends revisiting the decision without changing it.

05

Which plan do I need?

Document library, grounded AI and company-profile matching are on Analyst (€129/month); the shared team workspace is on Team (€89 per seat per month, three-seat minimum). See pricing for the full list.

Keep reading

[ 07 PAGES ]

See which defence opportunities fit your company.

Set up a company profile in minutes and get a ranked, explained shortlist today.

Start free trial Talk to our team