Mainfolk

Police departments

Moving a Police Department Website: Public Files, Forms and Alerts

Moving a Police Department Website: Public Files, Forms and Alerts

Photo by David Guerrero on Pexels

Why this move matters

If your police department or sheriff’s office is moving its website, the main risk is not the design. It is losing something people rely on: reports, forms, meeting notices, public records links, or emergency alerts. A careful move protects public trust, saves staff time, and keeps the phone from ringing with the same question over and over: “Where did the form go?”

The goal is simple. When the new site goes live, the public should still be able to find what they need without hunting through broken links or outdated pages. That means planning the move around the documents and alerts people use most, not just the homepage.

What to inventory before anything changes

Start with a full list of what is on the current site. Do this before any pages are moved or redesigned. A plain spreadsheet is enough. Divide it into sections so nothing gets missed.

  • Public files, such as annual reports, policies you make public, meeting agendas, minutes, budgets, audits, and press releases
  • Forms, such as report request forms, complaint forms, employment applications, records request forms, and permit or event forms
  • Alerts and notices, such as emergency notices, road closures, weather-related closures, and special announcements
  • Department information, such as contact pages, station addresses, division pages, staff directories, and command staff bios
  • Public service pages, such as crime prevention tips, community programs, records information, and recruitment pages

For each item, note where it lives now, who uses it, and whether it must stay public after the move. Example: if residents use a records request form every week, that form should be treated as a priority item, not left for later.

Which items should stay online during the switch

Some content can wait. Some cannot. During a move, keep the most-used public items available until the new site is fully ready. That often means leaving the current site online while the new one is checked behind the scenes.

Keep these items available if people rely on them now:

  • Emergency or urgent alert pages
  • Frequently used forms
  • Public contact information
  • Public records request instructions
  • Active notices, closures, or announcements
  • Downloadable files that the public still needs

If your office uses an emergency banner, make sure it is tested on the new site and easy to update fast. A delay of even a few minutes can matter when you need to get the word out quickly.

That is also where a service like a website service for police and sheriff offices can help, because the move can be handled without leaving the public guessing where to find the basics. Mainfolk can also free-move public content, which helps reduce the chance of losing files that people still need.

How to move forms without creating confusion

Forms cause the most frustration when they change names, move to a new page, or disappear without warning. Before launch, check every form as if you were a member of the public.

  1. Open each form from the public side of the site.
  2. Fill it out far enough to confirm it works.
  3. Make sure the download link works if the form is a file.
  4. Check that the form still sends people to the right place when they submit it.
  5. Confirm the form title is clear, so visitors know what it is for.

Example: if a citizen complaint form used to be tucked under several layers of menu pages, put it somewhere obvious on the new site. That saves staff from having to answer avoidable calls and helps people finish the task on their first try.

How to handle alerts during the transition

Alerts should be treated differently from normal pages. They need to be visible, simple, and quick to update. Before the move, decide who can post an alert, who approves it, and what the backup process is if one person is unavailable.

Keep the alert location the same on the new site if possible. People remember where urgent notices usually appear. If the location changes, put the alert banner in a very obvious place and test it on a phone as well as a computer.

Keep a short list of situations that may require a banner, such as road closures, weather problems, evacuation notices, station closures, or a public safety event. Do not bury urgent information on a general news page if people need it right away.

What to check after launch

Once the new site goes live, do a simple post-launch review within the first day. The check does not need to be fancy. It just needs to be methodical.

  • Open the homepage and the top public pages on a phone and a computer
  • Test each important form from start to finish
  • Click the links to public files and confirm they open
  • Check that the alert banner appears where it should
  • Look for broken links on pages people use most
  • Search the site for common terms the public would use, such as records, complaints, reports, or recruiting

Then ask one staff member who was not part of the move to try the site. A fresh set of eyes catches things the project team may miss, such as a page name that makes sense internally but not to the public.

Example: a records request page may look fine to staff, but if a resident cannot find it in less than a minute, the page is not doing its job.

What to ask your web partner before the move

Before you switch over, ask direct questions. You want clear answers, not vague reassurance.

  • Will public files be moved for us?
  • Will our own web address stay the same?
  • Can we keep the current alert setup working during the change?
  • Will the new site meet accessibility needs for people with disabilities?
  • Can we export our content anytime if we ever need to?

Mainfolk includes those basics for public bodies, and the work is done for you so your staff is not left cleaning up the details after the move. Mainfolk Civic is $149 a month or $1,490 a year, everything included, no contract and no setup fee, and a public body can ask for a written quote.

A final note if you were told your current provider is winding down

If you have heard that your provider is winding down, confirm your own date with them directly. Mainfolk is not affiliated with 911Webs and does not know any department's date. If you have heard that your provider is winding down, confirm your own date with them directly.

The safest move is the one that protects your public files, keeps your forms working, and leaves your alerts easy to use on day one.

Free download: grab our police department website checklist: the short, plain-English list of what your site needs to get found and bring in calls. No cost, no obligation.

Common questions

What should a police department inventory before moving a website?

Make a list of every public file, form, alert page, contact page, and notice that residents may still need. Then mark the items that get the most use so they stay visible during the move.

Should we keep the old website online during the switch?

Usually, yes, at least for the pages people use most. That helps avoid broken links and keeps public information available while the new site is being checked.

How do we make sure forms still work after launch?

Test each form like a member of the public would, from opening it to submitting it. Also check that any file downloads and submission messages still work as expected.

← All posts

Want a site like the one we just described?

Accessible by construction. Live in days. No contract, no RFP.