Bid / no-bid decision

A bid no-bid decision needs visible evidence and explicit judgement.

The decision should be supported by the current requirement and evidence state. It should not be inferred from vague intent signals or delegated to an automatic score.

Authentic interfaceLocal-first Windows workspaceSix production languagesOne-time licence
In one minute

Separate evidence from judgement.

The workflow should make the current requirement state, proof gaps and blockers visible. It should not pretend that a machine score can replace commercial judgement about whether the opportunity is worth pursuing.

Decision basis

Four inputs should be visible before the team decides.

01

Current buyer requirement state

VerifyKnown amendments and changes are reflected before the opportunity is judged.
02

Evidence position

VerifyMaterial claims are separated into supported, review-needed and unsupported states.
03

Named blockers

VerifyA HOLD state explains exactly what is unresolved and what action would change the decision basis.
04

Verified intent only

VerifyEngagement or buying intent advances only from first-party evidence, not inferred signals.
Human decision

The system can clarify the state. The team still decides.

GOCommit deliberately

The opportunity is supported strongly enough to justify the effort.

HOLDResolve the decision basis

A material uncertainty should be cleared before commitment.

NO-BIDDecline explicitly

The team records the judgement rather than hiding it behind a score.

Boundary

Decision visibility is not decision automation.

REQVERA can expose what the decision rests on. Commercial judgement and release authority remain human-controlled.

Fail closedWhen verified evidence is absent, the workflow should not invent intent.
Explore by need

Keep the next control question clear.

The resource hub is organised by buyer task, not by page type. Move sideways only when the question changes.