The Practice Files & Chart
Your practice shouldn't have to remember how it runs.
______________
The five documents built into every engagement, whether you work with me through Advisory or Private Consulting, and what they add up to. This page explains what they are, what they're used for, and what's different about how each option builds them.
What is a Practice File?
A Practice File is a living document, built through a guided AI process, not typed up from memory or filled in on a template. One gets built at the end of each of the five frameworks, and each one pulls in everything built before it. By the time the final file gets built, the sequence is working from the full history of what's been observed, decided, built, and delegated, not a fresh conversation started from scratch.
The point isn't the file itself. It's the process of building it: pulling operating knowledge out of where it usually lives, your head, a team member's head, old emails, half-finished documents, and turning it into a real reference that’s ready the next time a decision needs to get made.
What is the Practice Chart?
Taken together, the five files are what I call the Practice Chart. Not a separate piece of software, not a product you buy on top of the work, the accumulated memory, practice-specific context that makes every later pass through the five-practice cycle faster and sharper than the one before it.
You already know what a chart is for. It's the record you read before you act, built up over time, never starting from nothing. This is the same idea, pointed at the practice instead of the patient. The second time you move through Observation, you're not starting from a blank page. The AI already has the structural history of your practice, and so do you.
The Guardrail
Every part of this AI process stays scoped to business and operational context, scheduling, staffing, systems, internal communication, not anything patient-identifiable or clinical. That boundary holds regardless of how useful it would be to cross it, unless a dedicated privacy and compliance environment gets built specifically for that.
The 5 Practice Files
-
From Observation. The first file, and the foundation everything else builds on. A guided sequence starts by interviewing you without proposing solutions yet, then looks across everything you've shared for the threads connecting what looked like separate problems, then searches specifically for what's missing, the contradictions, the things nobody's said out loud.
What comes back is a structured read on where things stand today, the pattern underneath the presenting complaints, with no fix prescribed yet.
Every other file opens with this one already in hand.
-
From Vision. The second file, and the only one where the job is to challenge you rather than organize what you've already said. It opens with your completed Practice Diagnostic as context, so the work doesn't start from a blank page, then pushes past the version of what you want that's just a negation of what you don't, until it lands on Stop, Slow, or Go. Then a real operational decision is made about how big and how fast and not from a “feeling”.
That decision isn't permanent. It gets remade every time you cycle back through the framework.
-
From Operating. The third file, and usually the one with the most raw material behind it. It opens with both your Diagnostic and your Vision as context, then works through where information lives today, scattered across email, texts, and whoever happens to remember, and documents the single source of truth that replaces it:
The systems
The workflows
The automations
What gets tested with one person before it goes live to everyone.
-
From Leadership. The fourth file, built with your Diagnostic, Vision, and Operating Manual all in context. It works through what's still routing through you that doesn't need to, the decisions your team could make without you, and the harder conversations you've been sitting on.
What comes back is a real, tested line between what's yours to decide and what's theirs, not a guess at where that line should sit.
-
From Trust. The fifth and final file in a given pass through the five practices, and the richest one, built with all four prior files as context. It helps separate what requires your attention from what you're still watching out of habit, evidence versus anxiety, so stepping back has something real behind it instead of just hoping it holds.
When you cycle back through Observation after this, you're not starting from nothing. The file carries forward, and the whole loop moves faster the second time.
HOW ADVISORY AND CONSULTING BUILD THEM DIFFERENTLY
__________________
Both options move through the same five practices and produce the same five files. What changes is who's doing the building.
-
You do, with guidance at every step.
-
You run it yourself, learning to give it context and iterate as you go
-
You learn to build and manage it, so you can keep using it after we're done
-
The Founder - You!
-
Mostly in your hands, between meetings with easy access for questions to me via Slack
-
The ability to build and adjust these files yourself
ADVISORY
CONSULTING
-
Built directly, alongside you.
-
Set up and run together
-
Set up directly, decided and configured together.
-
You and your team.
-
Mostly shared, but I have dedicated working capacity reserved between sessions.
-
The files already built, and an understanding of how to run them
Practice Files aren't a separate product or a standalone purchase. They get built as part of Advisory or Private Consulting, both six-month engagements that start with the same $750 Practice Assessment. If you're deciding between the two, the Assessment is what tells you which one fits, not a guess made from a page like this one.