Clarification responses should be structured, version-controlled, and directly mapped to the questions raised. Weak responses usually create more review cycles, not fewer.
This protocol sets out how applicants should respond when additional information, explanation, or supporting evidence is requested during review.
A clarification response should reduce uncertainty. It should not create new ambiguity, introduce random documents without explanation, or force reviewers to guess what changed.
Each answer should begin by identifying the exact clarification item or question being addressed.
Answer the point clearly before attaching supporting documents. Do not bury the actual answer inside attachments.
State which document, annex, workflow, log, or revised file supports the answer.
Where a document was revised, include the file name, version number, and date of revision.
Briefly explain whether the response is explanatory only, partially revised, or supported by a fully updated document.
If a document is updated in response to clarification, the revised version should be clearly marked and distinguishable from earlier versions.
A simple and consistent naming method should be used, for example:
Where practical, applicants should also maintain a short internal change log showing what was revised and why.
Applicants are strongly encouraged to maintain a clarification response tracker with columns such as:
This reduces confusion across multiple review rounds and helps preserve a clean submission history.
Registered agents may help coordinate clarification responses, but applicants remain responsible for the accuracy, consistency, and completeness of all information submitted.
A bad clarification response can delay review more than the original gap. Random attachments, weak mapping, and inconsistent versions are classic self-inflicted damage.
