Guidance: the team leader should report the conclusions in accordance with the programme in a record that is full, accurate, clear and to the point that includes or refers to the objectives, scope including the auditee and functions or processes audited, the client, the team and auditee participants, dates and locations, criteria, findings and evidence, conclusions, a statement of the degree to which the criteria were fulfilled, unresolved diverging opinions, and the sampling nature of auditing with its risk that evidence is not representative. As appropriate it can include the plan and schedule, a summary of the process and obstacles affecting reliability, confirmation that objectives were achieved within scope, areas not covered with justification, a summary of conclusions and main findings, good practices, agreed follow-up, a confidentiality statement and implications for the programme or later audits.
This control maps to 16 controls across 12 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 16 it maps to, and the evidence behind each claim, over MCP and REST.