Treat each download as a maintained page
A downloadable document is part of your website, even when it opens outside the usual page layout. Visitors may save it, share its link or find it through a search engine long after you upload it. That makes a form, guide or policy more than an attachment: it needs an owner, a purpose and a review date.
Start with a small inventory. Record each document’s public title, file location, format, owner and the pages that link to it. Add a short note about what the document is for and when someone should check it again. A spreadsheet is enough for a small site. The goal is not elaborate recordkeeping; it is to make it possible to answer two questions quickly: “Is this still correct?” and “Where do we need to update it?”
Decide whether a file is the right format
Before updating a download, ask whether visitors need a file at all. Information that people mainly read online is often easier to maintain as a web page. A page can be revised without asking visitors to identify the latest attachment, and it generally fits the site’s navigation better. Keep a download when its format serves a clear task, such as printing a worksheet, completing a form or using a template offline.
When a file is necessary, give its link a descriptive label. “Download the volunteer application form (PDF)” is more useful than “Click here.” If visitors need particular software or will receive a large file, say so near the link. Provide the essential instructions on the web page too, rather than hiding every explanation inside the document. Check that headings, reading order and form fields in the file work for people using assistive technology; a readable page does not make an inaccessible attachment accessible.
Use names and labels that distinguish versions
Choose a naming pattern your team can apply consistently, such as volunteer-application-2026-03.pdf or volunteer-application-v3.pdf. A date may help when updates follow a calendar; a version number may work better when changes happen irregularly. Avoid names such as final-new-revised.pdf, which quickly become ambiguous. The filename should help maintainers identify the file, while the visible link text should tell visitors what they are downloading.
Put a title and a meaningful revision date or version inside the document as well. A person who saved an earlier copy may never see the website again, so the file should carry enough context to identify it on its own. If an old form must no longer be used, state that clearly on the new file’s landing page. Do not rely on the filename alone to communicate an important change.
Replace the file without losing track of old links
Before uploading a replacement, identify every place the existing file is linked: website pages, menus, resource lists and any reusable content blocks. Then decide what should happen to the old file address. Reusing the same address can keep existing links working when the new document has the same purpose, provided your publishing system actually replaces the file at that address. If the new file serves a different purpose, a new address and an updated explanatory page may be clearer.
Do not assume that removing a link removes the old file. It may still be reachable through a saved URL. Where your system permits it, redirect an outdated file address to a page explaining the replacement, or remove the file if no one should use it. Keep an archived copy privately if your organization needs a record, rather than leaving obsolete versions mixed into the public downloads area. Check any permissions or recordkeeping requirements that apply to your organization before deleting files.
Test the replacement and set the next review
After publishing, open the link as a visitor would and confirm that the correct file downloads. Check its title, contents, accessibility features and any links inside it. Visit the pages in your inventory that pointed to the old version, and test the old file address if you changed it. If visitors may have cached a previous file at an unchanged address, use a new filename and update links when a clear break from that version matters.
Finish by recording what changed, who approved the replacement and when it should be reviewed again. A recurring review is especially useful for forms, fees, contact details and instructions that depend on an internal process. You do not need to inspect every document every week. A manageable schedule, paired with a named owner, makes it much less likely that a forgotten download will contradict the rest of your site.
