Record the requirement and the review boundary
Identify the scheme, agreement or procedure being reviewed, its version and the activity covered. State the criterion against which evidence was examined and who carried out the review. Keep their authority, relevant competence and any conflict visible. A platform note about missing documents should not be presented as a formal independent audit unless that actual role and process have been established.
Describe facts separately from judgement
Reference the observed information and explain how it relates to the criterion. Distinguish a demonstrated failure, an unresolved question and an improvement suggestion. Record which entity, product, site or permission is affected rather than expanding the conclusion to an entire network. Keep the original finding when new information arrives, with attributable dates and versions that show why the decision changed.
Assign response and verification responsibilities
Describe the proposed correction and the action intended to address the cause, then identify the owner and due date. State what evidence is needed for verification and who can make the closure decision. Do not treat a self-reported completed task as automatically verified resolution. Preserve disagreement, appeals or restrictions through the applicable real process and avoid publishing unsupported allegations or unnecessary private details.
Prepare the transparent local trail
Use the Review finding and Corrective action templates to organise the criterion, evidence, response, verification and remaining limits. Export the record for the responsible review body or organisational team. Public wording should explain only the current supported scope and actual authority. Leaf Accord's local templates do not operate a live certification scheme, suspend a member, decide an appeal or independently assure corrective action.
