Make unresolved pages visible
A cleanup job can succeed on most pages while leaving a watermark on one diagram or clipping a footer-adjacent answer. Kenyan schools need a simple exception register so these failures are not hidden inside an otherwise accepted folder.
Record the file, page, unwanted element, attempted method and visible result. Describe the issue precisely: 'logo remains behind graph' is more useful than 'bad page'. Keep the failed output separate from the approved copy.
Close an exception with evidence
Assign the page to a subject reviewer or support contact. After another attempt, compare the saved output with the source and update the register. Mark an item closed only when the relevant reviewer accepts the result.
If no safe cleanup route is found, obtain an alternative authorised source or revise the editable master. Do not turn an unresolved result into a release by renaming it. The register should show why a file is pending and who can decide its next step.
Practical checks
- Record file and page
- Describe the visible fault
- Keep failed trials separate
- Assign a reviewer
- Close only after output acceptance
Questions and answers
Is a completed job status enough to close an exception?
No. The actual page must pass the relevant review.
What if only one page fails?
Isolate and resolve that page rather than approving the complete pack automatically.