Identify the obligation
Record the requirement verbatim, its source reference, deadline and whether it is mandatory. Include amendments and annexes in the review.
Answer the question. Keep the proof.
Link each answer to current control evidence. Preserve the issuer’s format, allowed values and unresolved questions; confirm the required spreadsheet workflow in your pilot.
One row for each requirement
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.