How to Document Your Firm's Processes (A One-Week Method)

To document your firm's core processes effectively, capture them as they are performed, focusing on one workflow per day for a single week. Maintain this documentation with a light monthly review. Most documentation efforts fail because firms attempt to capture everything at once, often in excessive detail as a separate project. This usually leads to overwhelm and collapse. Instead, constraining the process makes it manageable and successful.

---

Steps to Follow

Before you start: Identify the eight processes that are most critical to your firm. It's not necessary to document every process, just the core ones that occur frequently and are dependent on specific individuals. For a professional services firm, these typically include:

1. Client intake (from inquiry to qualification)
2. Client onboarding (from qualification to active status)
3. Service delivery (1–2 processes per main engagement type)
4. Client communication and status updates
5. Time capture and billing
6. Collections and overdue follow-up
7. Engagement close-out
8. Internal reporting (to provide an overview of ongoing activities)

This approach will take roughly a week, with one process per day and two days allocated for delivery.

Documentation Format (Keep It to One Page Each)

For each identified process, document the following:

• Purpose: A one-sentence description of the outcome this process produces.
• Trigger: What initiates the process.
• Owner: The role responsible for managing the process.
• Steps: Numbered action-first statements (e.g., “Send the engagement letter for e-signature”), specifying the tools used.
• Handoffs: Indicate where the process transfers to another person and what they need to receive.
• Definition of done: Criteria for determining when the process is correctly completed.
• Common exceptions: Identify two or three scenarios that may disrupt the standard flow, along with instructions for handling them.

More elaborate documentation is rarely read or maintained.

The One-Week Method

1. Day 0 (preparation, 30 minutes): Create a separate document or page for each of the eight processes, filling in the headings. Assign the person who performs each process to draft its documentation.
2. Days 1–5 (one process per day): The designated individual narrates the process while executing it in real time; this can be done through screen-sharing or a walkthrough, while another person fills in the documentation template. Avoid scheduling a separate “documentation meeting”; capture the process in the flow of actual work. Expect this to take between twenty and forty minutes per process.
   • Same day, 15 minutes: The person who executed the process reviews the draft to ensure nothing was missed or misordered. Make necessary corrections and label it “v1.”
3. Day 5 afternoon (review, 1 hour): Review all eight processes as a complete set. Look for mismatches in handoffs, such as outputs from one process that don't align with the next process's inputs, because these discrepancies are often where work slips through the cracks.

Addressing Mismatches

The discrepancies found during the review are valuable insights and can highlight common issues, such as:

• The intake process collects information necessary for onboarding but then requests it again from the client.
• The delivery process lacks crucial details that the close-out phase cannot retrieve, leaving future engagements without vital information.
• Billing relies on data from delivery that is not appropriately transferred.

Each identified gap represents an opportunity for a small standardization fix, typically agreeing on what information needs to flow from one process to the next. Make these adjustments before attempting to automate anything.

Keeping Documentation Current

• Owner updates: The owner of each process should update their documentation the same day any changes occur, adding a single line in the changelog at the top.
• Monthly review (20 minutes): The individual managing operations should review the documentation set to ensure it accurately reflects current practices and flag any areas that have drifted.
• Onboarding new hires: New employees should be trained using the documented processes and are encouraged to point out any unclear sections; this serves as a useful test of the clarity and effectiveness of the documentation.

Recommended Tools

A shared document or wiki (such as Notion, Google Docs, Confluence, or your intranet) is sufficient. Tools that automatically generate step lists (like Scribe, Tango, or Guideflow) can speed up documentation for workflows that involve many clicks. Avoid over-investing in software; what matters more is adherence to the established format and maintaining discipline in the documentation process.

Why This Approach Is Valuable

Documenting and standardizing your firm's core processes is essential to achieve consistent quality, facilitate rapid training for new hires, reduce dependency on specific individuals, and enable effective automation. Automating without a well-documented process can perpetuate existing inconsistencies.