On this page
Sooner or later most agencies move their accreditation files. Binders become scans, a shared drive becomes a system, one system is replaced by another. Done well, a move is a chance to clean up years of clutter. Done badly, it’s how proofs go missing a few months before an assessment.
The moves that go wrong usually have the same cause: someone tries to move everything at once without a map of what they have. This guide is the map.
Take inventory first
Before you move a single file, write down what you have and where it lives. For most agencies, that’s some mix of:
- Paper binders, often one per chapter or one per assessment
- Folders on a shared drive, organized however the last accreditation manager liked
- An existing accreditation system, with its own structure and export options
- Email inboxes, where proofs arrived and never left
- Records held by other units that were never copied into the accreditation files
For each source, note which standards and which period it covers, roughly how much is there, and who knows it best. If your manual has changed editions since some of the files were created, note that too, because standard numbers may not line up.
The inventory will feel slow. It’s the step that saves you the most time later.
Decide what moves
Not everything needs to come across. A sensible rule of thumb:
- Move your current written directives and the proofs for the period your program cares about now.
- Keep, but archive separately, older policy versions and proofs from past cycles. You may need them to answer a question, so don’t throw them away.
- Leave behind true duplicates, abandoned drafts and personal notes that were never part of the file.
Whatever you decide, keep the originals until you’ve checked the new files. A binder that’s been scanned is still worth keeping on a shelf until you’re sure the scans are complete and readable. Never destroy evidence as part of a move.
Get files out of the old system
If you’re leaving an existing accreditation system, find out early how to export from it. Ask the vendor what an export includes and what it leaves out. Common surprises:
- File names come out as codes rather than readable titles.
- Comments, notes and highlights stay behind in the old system.
- Attachments come out in one big folder, with no link to the standard they belonged to.
- Older file formats need converting before they’ll open.
Do a small test export first, a single chapter, and check it before exporting everything. If the structure isn’t usable, it’s much better to find out while you still have access to the old system.
Scan binders properly
If you’re working from paper, scanning quality matters more than speed.
- Scan to searchable PDF where you can, so the text can be read and matched later.
- Keep one record per file. A single PDF containing forty unrelated documents is hard to cite and hard to check.
- Check orientation and legibility. A crooked, faint scan of a signature page doesn’t prove much.
- Name each file as you go. It’s far easier than going back to rename hundreds of “scan0047.pdf” files.
Organize by standard
The most useful structure for accreditation files is the one your manual already uses: one folder per standard, with written directives and proofs kept apart inside it.
| Folder | WD (written directives) | Proof (proofs of compliance) |
|---|---|---|
| 1.1 | Policy 101 Agency Jurisdiction.pdf | 2026-01 Jurisdiction map.pdf |
| 1.2 | Policy 102 Mutual Aid.pdf | 2025-11 Signed agreement, Harbor County.pdf |
| 1.3 and so on | One folder per standard |
Pick a naming convention and stick to it. Putting the date first, as year then month, means files sort in order. Add a short plain description of what the record is. “2026-03 Firearms qualification roster” tells an assessor what they’re looking at before they open it.
When one document supports several standards, such as a policy that covers more than one requirement, put a copy in each standard’s folder rather than leaving a note saying “see 4.2.”
Clean up as you go
A move is the right moment to fix things you’ve been meaning to fix:
- Replace drafts with final, signed versions.
- Remove documents that don’t prove anything for the standard they’re filed under.
- Redact personal details that never should have been in the file, such as names, case numbers and dates of birth.
- Flag standards where you notice a gap, so they go on your list rather than getting lost in the move.
Don’t let the clean-up turn into a full review of every standard, though. Move first, then review on your normal schedule. Trying to do both at once is how moves stall.
Check after the move
Once files are in their new home, check them before you rely on them:
- Compare against your inventory. Did every source come across?
- Count files for a sample of standards and compare with the old location.
- Open a random selection and make sure each one is readable and complete.
- Look at a few standards end to end, the way an assessor would.
Only when you’re satisfied should you retire the old location, and even then, archive it rather than delete it.
Moving into Badge 6
Badge 6 has a folder import built for this. Under Moving from another system?, you upload one .zip of up to 5 GB with a folder per standard and WD and Proof subfolders inside, the same structure described above. Badge 6 files each document under its standard and runs automatic redaction on every file, across documents, images, audio and video. Your agency’s own details are never redacted.
You don’t have to import everything at once. Your manual is loaded from the start, so you can upload policies to the Document Library one at a time and start working standards right away, then bring the rest in as you’re ready. Once your files are in, Quick Check and Full Manual Analysis show which standards each document supports and quote the supporting lines, which is a fast way to check that the move put things where they belong.
For the steps around a move, such as setup, roles and training, see Implementation.