The One Document That Keeps Your Business Running When Your Tech Person Is Unavailable
It is a Tuesday morning in 2026, and the person who handles your office technology is out sick. Or on vacation. Or, worse, gone. The website is still up, but nobody knows who owns the domain. Payroll runs this week, but the administrator login is in someone's personal email. The phone system has an issue, and the only phone number anyone has is for a rep who left two years ago.
This is not a rare crisis. It is a common small business condition. Most companies do not have an IT department, and they do not need one. What they need is a tech playbook: a plain, current document that explains how the business actually runs on the inside.
A playbook is not a 60-page IT policy
Let us clear up what this is not. It is not a security manifesto, a disaster recovery novel, or a binder that gets printed once and never opened again. It is a working document, short enough to maintain and specific enough to be useful when someone is panicking.
The goal is simple: if the owner, office manager, or unofficial tech person is unavailable, another trusted person can find the accounts, contact the right vendors, understand the backup process, and keep the lights on. That is resilience without a full-time IT staff.
Start with the systems that would stop the business
Do not try to document everything at once. Start with the systems that touch money, customers, communications, and access. For most US small businesses, that means email, the domain and website, accounting and payroll, the customer database or CRM, file storage, backup, phones, and any industry-specific software that runs daily operations.
For each system, answer four questions: who owns it, who else can get in, what does it cost, and when does it renew? That alone will uncover a surprising number of mysteries.
The bare-minimum tech playbook template
You can build this in a shared document or a secure note in your password manager. Keep the structure boring and consistent.
1. Access map
List each core system, the primary administrator, a backup administrator, the multi-factor authentication method, the recovery email, and where the credentials are stored. Do not put actual passwords in the document. Point to the password manager entry instead. If everything lives in one person's head or text messages, fix that first.
2. Vendor directory
For each vendor, record what they do, the account number, the support phone number and website, the sales or account rep, the contract owner, the renewal date, and the cancellation notice period. Include the boring ones: domain registrar, web host, internet provider, phone provider, payment processor, and software subscriptions.
3. Renewal calendar
Put every renewal date in a shared calendar with reminders. Include auto-renewal deadlines, not just expiration dates. A $99 tool that renews unnoticed is annoying. A $9,000 contract that renews because nobody gave 60 days notice is a budget problem.
4. Backup and restore steps
Write down what is backed up, where the backup lives, how often it runs, and who checks it. Then add the step most businesses skip: how to restore a file. A backup you have never tested is a hope, not a plan. Include the vendor or support contact for the backup system.
5. Escalation contacts
List who to call when something breaks: your IT consultant or managed service provider, key software vendors, the internet provider, the landlord or building manager if network equipment is affected, and your cyber insurance contact if you have one. Add a short note about what counts as an emergency versus a next-business-day issue.
6. Change log
Add a simple date and description field. When you switch email providers or add a new tool, update the playbook. A document that was accurate in 2024 and untouched since is not a playbook. It is an artifact.
Make it living, not laminated
A tech playbook only works if people know it exists and can access it when needed. Store it somewhere secure but reachable by more than one person. Review it quarterly for twenty minutes. Update it when a vendor changes, a key employee leaves, or a renewal date shifts.
Do not use the playbook as a place to hide passwords. Use it as a map to the password manager, the vendor contacts, and the recovery steps. The best version is slightly imperfect and current, not perfect and stale.
The payoff is quieter than a crisis
You will not get a thank-you note because the domain renewed on time or because someone found the payroll admin login during a vacation. That is the point. A tech playbook removes the drama. It reduces the odds that one person's absence becomes everyone's emergency, and it makes onboarding, vendor negotiations, and insurance conversations easier.
Your small business does not need an IT department to be resilient. It needs a document that tells the truth about how the technology works, where the keys are, and who to call when something goes sideways.