Requirement, answer and evidence
Each requirement stays linked to the buyer’s request, the proposed answer and its supporting material. An unread annex or partial extraction remains visible.
Read the whole request before writing the answer.
Use the original tender, annexes and amendments to identify requirements. Build a source-linked matrix before drafting in your assistant.
A matrix that shows what is left to do
States with a clear meaning
Draft, evidence missing, needs review and approved version describe different situations. Filling in an answer does not automatically establish compliance.
An owner and a next action
Assign the gap to a person, deadline and action: obtain a certificate, confirm a price or resolve a conflict. Review applies to one specific version.
What your team keeps for the next dossier
The dossier’s history
Sources, analyses, answers, versions and decisions let you resume work and understand accepted commitments. History is not a library of approved facts.
Knowledge approved separately
The team selects reusable information or answers, then approves the exact version with evidence, an owner, a validity date and a scope. Approving a dossier does not make every sentence reusable for other clients.
Adaptation with fresh checks
Snipara retrieves relevant context. Helvabase checks access and review status; your assistant adapts the answer to the new requirements. Expired or withdrawn information needs review. This retains and retrieves knowledge; it does not retrain the model.
One row for each requirement
Identify the obligation
Record the requirement verbatim, its source reference, deadline and whether it is mandatory. Include amendments and annexes in the review.
Link answer and evidence
Add the proposed response, source version, owner and remaining caveat. The template is a working aid; its rows do not certify compliance.
Record the review
Record the decision on the exact answer version. Recheck affected rows when a price, requirement or supporting document changes.
Keep the evidence and the decision together
A source is not an approval
An extracted fact is a candidate for review. Confirm its authority, date and relevance to this request before making a commitment.
Missing information stays visible
Identify missing certificates, uncertain prices and contradictory documents explicitly. Do not turn an absence of evidence into a confident answer.
Human responsibility remains
Reviewers remain responsible for external use. Native client confirmation and a model-generated statement are different forms of evidence; the pilot must validate the required review path.