Run an authority design review cycle

Pick the exact document or drawing version the authority will review, so the remarks that come back can be tied to a fixed point rather than a moving target.

Why: If the design keeps changing while the review is open, nobody can say which remark applies to which version. Fixing the reviewed version first is what keeps the cycle honest.

Start a review cycle against the document version, set the reviewing body and the response deadline, and share it with the team that will handle the remarks.

Why: An open cycle with a deadline is what stops a review sitting unanswered until it becomes a programme problem. Everyone can see it is live and whose turn it is to act.

Log every remark the authority raises as its own item, assign it to whoever owns the answer, and record the response against the specific point it addresses.

Why: A remark answered in a general reply is a remark that is easy to argue was never actually addressed. One remark, one response, is what makes the closeout defensible.

Mark each remark as accepted, addressed or disputed, then close the cycle once every remark has a decision, leaving a full record of what changed and why.

Why: An unclosed remark is a risk the design can still be challenged on later. Closing the cycle with a decision on every point is what turns the review into a finished design check, not an open thread.