Most businesses keep records for their building, vehicles and equipment: leases, warranties, service histories and who to call when something breaks. Websites rarely get the same treatment, even though they are just as important to daily operations. A modest amount of documentation turns the website from a mystery into a managed asset.
What documentation is for
Good website documentation answers the questions that come up when something changes or goes wrong. Where does the website live? Who do we call? How do we renew the domain? What does this plugin do? When those answers live only in one person’s memory, every problem takes longer to solve. When they are written down, anyone with the right access can find them.
What to include
Documentation does not need to be technical or long. A clear document, or a small set of them, covering these areas goes a long way:
- Accounts and services. Registrar, DNS provider, host, email provider, store platform, payment processor, analytics and any other tools, with what each one does and where the login is stored. Never write the passwords themselves into the document. Keep those in a password manager.
- Renewals and billing. Renewal dates, billing frequency and which payment method is used for each service.
- Technical setup. The platform and theme, important plugins or extensions, and any custom code with a note about what it does.
- DNS records. A current export or screenshot, with notes on what each non-obvious record is for.
- Backups and recovery. Where backups are stored, how often they run and the steps to restore one.
- People. Who has administrator access, outside partners and how to contact them.
Routines and how-tos
Beyond the setup, document how common tasks are done. Short, practical instructions are ideal:
- How to update business hours or a holiday notice.
- How to add a product, event or blog post.
- How to clear the site cache when changes do not appear.
- What to check when an uptime alert arrives.
- How to process an online order from start to finish.
Screenshots or short screen recordings make these far easier to follow. Write them for someone who is new and slightly nervous, because that is who will be reading them.
A change log
Keep a simple running list of significant changes: when a plugin was added, when hosting moved, when a form was rebuilt. Each entry needs only a date, what changed and who did it. When something breaks, the change log is often the fastest route to the cause.
Keeping it alive
Documentation is only useful if it is current. Store it somewhere the business controls, such as a shared drive, and make sure more than one person can reach it. Review it a couple of times a year, ideally alongside renewal checks. Update it whenever a service, vendor or staff member changes. It will never be perfect, and it does not need to be. A mostly complete binder that people actually use is far better than a perfect one that nobody can find.
A Simple Way to Organize the Binder
Whether your binder is a shared folder, a single document or an actual three-ring binder on a shelf, a consistent structure helps people find what they need quickly. One layout that works well for many small businesses:
- Front page: the emergency sheet. One page with the most important facts: where the website is hosted, who to contact for support, where logins are stored and who inside the business can authorize changes.
- Accounts and renewals. One entry per service, each with the same fields so they are easy to compare.
- Technical setup. Platform, theme, plugins and DNS notes.
- Backups and recovery. Where backups live and the restore steps, written out.
- How-tos. Short guides for common tasks, each on its own page.
- Change log. The running list, newest entries at the top.
- Contacts. Vendors, partners and internal people with their roles.
Keep the emergency sheet short enough to read in a minute. Its job is to get a stressed person to the right place, not to explain everything.
A Template for Each Account Entry
Using the same fields for every service makes gaps easy to spot. For each account, fill in:
- Service and purpose: what it is and what it does for the business.
- Account owner: the business name on the account.
- Contact email: ideally a role-based address the business controls.
- Who has access: names and roles.
- Where the login is stored: the name of the entry in your password manager.
- Renewal: date, frequency and which payment method is used.
- Support: how to reach the provider’s help team.
- Notes: anything unusual, such as settings that should not be changed.
Blank fields are useful, too. Each one is a question someone needs to answer before it becomes urgent.
Writing a How-To That Actually Helps
Good instructions share a few traits. Use this pattern for each routine task:
- A clear title that names the task, such as Posting a holiday closure notice.
- When to do it and how long it usually takes.
- What you need before starting, such as a login or an image.
- Numbered steps, one action per step, with a screenshot where a button is hard to find.
- How to check it worked, such as viewing the page on a phone in a private window.
- What to do if it does not work, including who to ask.
Ask someone who did not write the guide to follow it once. Wherever they get stuck, add a step or a screenshot.
Common Documentation Mistakes
- Passwords written into the document. Point to the password manager entry instead.
- Documents stored in one person’s personal account. If they leave, the binder may leave with them.
- Screenshots without dates. Software screens change. A date tells the reader whether the picture might be out of date.
- Trying to document everything at once. Start with the emergency sheet and the accounts list, then add how-tos as tasks come up naturally.
Where to Begin This Week
If you have nothing written down today, pick the smallest useful step: create the emergency sheet. Then add one account entry each time a renewal email arrives and one how-to each time someone asks how something is done. In a few months, the binder will be mostly complete without ever feeling like a big project. Set a reminder twice a year to skim the whole thing, fix what has changed and remove what no longer applies.




