About 30 minutes to set up · claude.ai only

Get a runbook out of the one engineer who knows

Today

One person can rebuild that client's line of business app server, and the procedure exists as a chat thread and their memory. Every tier one tech routes the ticket to them, and the week they take vacation the whole thing waits.

With Claude

You talk through how it actually runs, answer six clarifying questions, and get a downloadable runbook with prerequisites, non-reversible steps marked, verification, failure modes, and escalation triggers. It also tells you which steps you described too vaguely to trust.

The prompt

Paste this into claude.ai and replace anything in brackets.

Act as a senior engineer helping me turn one person's knowledge into a runbook a tier one tech can follow without calling them.

The procedure: [name it, for example onboarding a new user at a client, or restoring a single file from backup]
How it actually runs today, in whatever order it comes out of my head: [describe the steps, the tools involved, the client specific variations, and what usually goes wrong]
Who will run this: [experience level of the person following it]
What must never appear in this document: [for example passwords, keys, addresses, client names]

First, ask me up to six questions about the steps that are ambiguous, the decision points where a tech has to choose between two paths, and anything that would cause damage if done out of order. Wait for my answers before writing.

Then produce the runbook as a document I can download, containing:
1. When to use this, and when to escalate instead, at the very top.
2. Prerequisites: access needed, approvals needed, and who grants each. Reference every credential by where it lives, for example the password manager entry name, never by value.
3. Numbered steps in the order they must happen, each one an action a tier one tech can perform without asking what it means. Mark every step that cannot be undone.
4. Verification: how the tech proves it actually worked, not just that a tool returned no error.
5. The common failure modes, each with the first two things to check.
6. Rollback, if there is one, and a plain statement when there is not.
7. An escalation path with the trigger for each level.
8. A change log line with today's date and a placeholder for the owner's name.

Finally, list every place where my description was thin enough that you had to guess, so I can fix those before this goes into our documentation library.

What to skip in IT services firms and MSPs

  • Credentials and live infrastructure detail. Passwords, API keys, certificates, connection strings, firewall or VPN configs, network diagrams with real addressing, and security assessment or penetration test findings do not belong in a chat window, yours or your client's. On Free, Pro, and Max accounts whether your chats are used to improve Claude is a setting you control in Privacy Settings, and Anthropic does not use Team or Enterprise account data to train its models by default. Either way, a secret that leaves your password manager is a secret you no longer control. Reference credentials by where they live, never by value.
  • Security configuration and compliance attestations. Claude will hand you a confident conditional access policy, firewall rule set, or control mapping that looks right and is wrong in the details that decide whether it holds. It does not know the client's real environment, the current version of the framework, or what your assessor will accept. Use it to draft the explanation and the client facing summary, have a named engineer verify configuration against vendor documentation, and never sign an attestation or a security questionnaire on the strength of a chat.
  • Incident communication that carries legal weight. Once an event looks like unauthorized access, exfiltration, ransomware, or loss of regulated data, the message stops being a service update. Breach notification requirements vary by state and by contract, the clocks are short, and most cyber policies require you to involve the carrier and counsel before you communicate. Draft internally if it helps you think, then route anything client facing through counsel and your carrier before it is sent.

Want all 4 workflows for IT services firms and MSPs in your inbox?

Every prompt on this page plus the rest, so you still have them on Monday. One email, then four short ones on making it stick. Unsubscribe any time.

Or answer four questions and Claude writes three workflows for your specific business rather than the industry generally.

Before you try it

More for IT services firms and MSPs

Full guide for IT services firms and MSPs