Municipal PDFs: Check the Release Copy After Redaction

Start with an approved release decision

Imagine a township employee preparing a PDF attachment for the municipal website. The document owner has identified information that must be removed from the release copy. Before the publisher uploads it, the office needs to confirm which file was prepared, whether the redactions were completed, and who checked the result. Give that handoff the same attention as the document's visible content.

For Michigan township, village, and city teams, decisions about what to release or withhold belong with the designated municipal officials and advisers. Have them identify the approved treatment before technical preparation begins. Name the preparer, reviewer, and publisher, even when one person performs more than one role. Keep the original and its handling under the municipality's established records process while preparing a clearly identified working copy.

Complete the approved redaction workflow

Use the office's approved redaction software and have IT confirm the available features and configuration. Adobe's Acrobat Pro instructions, for example, describe selecting content with the redaction tool, applying the redactions, and saving the resulting document. Have the preparer demonstrate those completion steps using harmless sample information before relying on the process for a real release.

Adobe also explains that redaction is permanent once applied and saved. Preserve the original through the approved process and use a deliberate release filename and location. Check every page against the authorized instructions, including repeated information in another part of the document. Resolve unclear selections with the municipal reviewer before completing the release copy. Record which version was prepared so the next employee can identify the same file.

Include hidden information in the review

A PDF can contain information beyond the visible page. Adobe's sanitization guidance identifies items such as metadata, comments, and hidden layers. Its redaction overview distinguishes removal of visible content from sanitization of hidden information. Ask IT to explain the appropriate inspection and removal process for the actual PDF and approved software your office uses.

Have the document owner and technical reviewer agree on how that process fits the release instructions. Review the saved result after any removal, including the information that should remain available to readers. If the file contains embedded material, complex forms, or features the preparer cannot confidently assess, assign that review to someone with the appropriate technical knowledge before authorizing publication. Keep unresolved questions with the working record.

Have a reviewer inspect the saved release file

Close the preparation view and open the saved file from its intended release location. Have the reviewer compare it with the authorized instructions, checking page count, selected areas, repeated references, and the remaining document's readability. Confirm the filename and version being reviewed. A second person should be able to follow the handoff without guessing which of several similarly named files is current.

During a rehearsal, use invented test values and have IT demonstrate checks such as searching the finished PDF and inspecting text copied from a selected area. Those checks can help reveal mistakes; they supplement the approved verification process and do not establish that every kind of hidden content has been removed. For real documents, keep the review and any test output within the authorized handling arrangements. Record the review result and any correction required.

Verify the file reached through the public link

Give the publisher the reviewed release file and its approval record. Confirm that the website upload selects that exact file from the approved location. Use a clear public label that identifies the document's purpose and date where appropriate. Keep access to source documents and working copies within the municipality's approved storage and publishing arrangements.

After publication, open the actual website link and check the downloaded file against the approved release copy. Confirm that the intended document opens and that its pages match the reviewed result. If the website offers more than one link to the document, include those routes in the check. Have staff use the municipality's established correction and escalation process if they find a different version or an unexpected disclosure.

Give each replacement a fresh review

Treat a replacement attachment or newly combined packet as another release candidate. Identify what changed and repeat the relevant preparation, verification, and approval steps. Keep the reviewed version connected to the publishing record so a corrected source document does not quietly bypass the release process. Have the publisher confirm the new download after the update.

Use recurring problems to improve the handoff. Clarify naming when reviewers receive the wrong file, update the preparation instructions when a completion step is missed, and arrange training when staff need help with the approved tool. Include a backup preparer or publisher so the process remains workable during absences. Bring one synthetic example to the next IT review and use it to check the complete workflow.

Keep this checklist with the release record

Use the same handoff for each PDF that requires approved redaction before publication.

• Identify the authorized release instructions and responsible people.
• Prepare a working copy with the approved redaction tool.
• Complete the apply-and-save steps and the hidden-information review.
• Have the reviewer check the saved file and record the result.
• Publish the approved version and verify the public download.
• Repeat the review when a file is replaced or a packet is recombined.