PXLQuill / Guide 15
Review and approval
Separate editorial acceptance from technical validation.
01 / Review a specific version
Select the report version under review. Check completeness, clarity, evidence, scope and remediation. Use review comments to record actionable changes rather than vague approval requests.
02 / Keep validation distinct
Editorial approval means the report has passed your review process. It does not automatically prove every vulnerability. Finding validation should reflect the technical work and evidence separately.
03 / Resolve feedback
Make the required changes in the draft, save them and generate a new version. Review that version again when the changes affect the deliverable.
04 / Check delivery eligibility
Use the current readiness and approval controls before preparing a delivery package. Do not bypass warnings by treating a draft preview as an approved final report.