How do I ensure my permit intake workflow with a case management platform is compliant with public records rules?

To keep a permit intake workflow compliant with public records rules, design it so that every record created, received, or used in the process is retained, searchable, and retrievable, and that the platform supports disclosure, redaction, and auditability.

Here’s a practical checklist.

1) Confirm what counts as a public record in your process

Work with your legal/public records officer to define:

• Application forms
• Attachments and plans
• Emails and messages related to the permit
• Notes, comments, internal reviews
• Approvals, denials, conditions
• Fee records
• Metadata such as timestamps, user IDs, and status changes

If it relates to agency business, assume it may be a public record unless clearly exempt.

2) Use a platform that can preserve the record

Your case management system should:

• Store documents in original form
• Keep version history
• Log who created/edited/viewed items
• Preserve timestamps and status changes
• Support export in common formats
• Allow retention policies aligned with your records schedule

Avoid workflows where important communications live only in private inboxes, chat tools, or untracked spreadsheets.

3) Centralize intake

Make the platform the official intake point for:

• Online submissions
• Email intake, if allowed
• Staff-entered paper applications
• In-person submissions

Every intake channel should feed into the same case file so the record is complete and searchable.

4) Capture metadata at intake

Make sure each submission is tagged with:

• Applicant name
• Permit type
• Parcel/address
• Submission date/time
• Case number
• Source channel
• Staff handler
• Document type

Metadata often determines how records are found and produced later.

5) Separate public and exempt information

Set up fields and document categories so sensitive information can be identified early:

• Personally identifiable information
• Security-sensitive details
• Trade secrets or proprietary material
• Medical or financial information
• Attorney-client privileged communications

Use a redaction workflow, not informal editing, for records that must be disclosed partially.

6) Build a redaction and review process

Before release:

• Review the record set for exemptions
• Redact only what is legally exempt
• Keep an unredacted master copy if required by policy
• Document the legal basis for each redaction
• Track who performed the review

7) Maintain an audit trail

Your platform should record:

• Intake events
• Document uploads
• Edits and deletions
• Status changes
• Notes added
• Redactions
• Exports and disclosures

This helps prove the integrity of the record and respond to records requests.

8) Define retention and disposition rules

Align the workflow with your records retention schedule:

• How long permit files are kept
• When they become inactive
• When they can be destroyed
• Whether certain case types require permanent retention

Do not delete records from the system unless the retention schedule permits it and deletion is logged.

9) Train staff on messaging and notes

A major compliance risk is staff using off-system channels. Train staff to:

• Avoid conducting permit business in private text/email accounts
• Copy case-related communications into the system
• Use standardized notes
• Understand what not to put in free-text fields

10) Make public records requests easy to fulfill

Design the platform so you can:

• Search by case number, applicant, address, date, and staff
• Export complete case files
• Produce logs of actions and communications
• Apply redactions consistently
• Distinguish responsive from nonresponsive records

11) Set access controls without hiding records

Role-based access is useful, but public records obligations still apply. Ensure:

• Access restrictions are for operational/security reasons, not to avoid disclosure
• Administrators can retrieve all records as needed
• Restricted records are still retained and discoverable internally

12) Coordinate with your records officer and counsel

Because public records laws vary by jurisdiction, confirm:

• Definition of public record
• Exemptions and redaction rules
• Retention schedule requirements
• Response deadlines
• Requirements for metadata, emails, and logs
• Rules for contractor-managed systems and cloud storage

A good compliance design looks like this

• One official case file per permit
• All communications routed into the case file
• Standard metadata at intake
• Immutable audit logs
• Document classification for exempt content
• Redaction/review workflow
• Retention and export controls
• Staff training and written policies

Questions to ask your platform vendor

• Can you export the full case file, including metadata and audit logs?
• Can you retain version history?
• Can you search all records across documents, notes, and messages?
• Can you apply and track redactions?
• Can you support retention schedules and legal holds?
• Can you show complete activity logs for a case?
• Can you prevent deletion except by authorized records admins?

If you want, I can also give you:

1. a public-records compliance checklist for permit intake, or
2. a sample workflow diagram/policy language you can adapt.