Three people tend to feel the cost of missing documentation first.
The freelance instructional designer fighting scope creep on a project that started small and grew. The in-house instructional designer who has to rebuild a program from memory because the original designer left and nothing was written down. The L&D manager who has to justify the department's budget with data the rest of the organization can see.
The Documentation Standard: The Instructional Designer's System for Work That Holds Up (The Professional Standards Series) is written for all three. It is 110 pages, organized around four types of documentation that make instructional design work defensible and repeatable: project documentation, design documentation, learner-facing documentation, and process documentation. Each type serves a different audience and a different business function. Knowing the difference changes how you do the work.
Why most documentation fails
Most instructional designers treat documentation as the thing they do after the real work is done. A course map here, a storyboard there, something to hand over and forget about. Documentation is administrative overhead. Documentation is a deliverable for someone else to read later. Documentation is the last 10% of a project.
That approach produces documentation that does not hold up. The project goes sideways because someone changed scope and there was no paper trail. The course falls apart during review because no one agreed on what was approved. The freelance engagement ends and the client calls six months later asking for the same deliverable, and there is nothing reusable.
The Documentation Standard argues the opposite: documentation is where the design actually lives. Not the design document as paperwork, but documentation as the design artifact that makes the work reproducible, defensible, and scalable.
What documentation that holds up looks like
For the freelance instructional designer, the most useful documentation is the design document that protects against scope creep and stakeholder reversals. The book walks through what belongs in a design document: a clear statement of the learning problem, the proposed solution, the assumptions built into the solution, and the change-control process. The change-control part is the part most freelancers skip. The book does not.
When a client asks for a second round of revisions that materially changes the scope, the design document is what you point to. It is not a weapon. It is a shared understanding of what was agreed to, written down at the start. If you skip it, every revision conversation becomes a negotiation. If you write it down at the start, every revision conversation becomes a question of whether the change is in scope or out of scope. That is a much easier conversation to have.
For the in-house instructional designer, the most useful documentation is the kind that survives the person who holds it. When a senior ID leaves and a junior ID takes over, what is left behind? If the answer is "their brain and a folder of old Storyline files," the program has to be rebuilt. If the answer is project documentation plus design documentation plus learner-facing documentation, the new ID has what they need to maintain and improve the program without starting from scratch.
For the L&D manager, the most useful documentation is the kind that makes the budget conversation possible. The book covers how to document training outcomes so they hold up when the budget conversation happens. Not anecdotal evidence. Not "people said the training was good." A documented record of what was delivered, to whom, with what outcomes, and what that means for the next cycle. That is the difference between an L&D function that has to defend itself every year and one that walks into the budget meeting with the data already on the table.
The minimum viable templates
The book includes minimum viable templates for freelance engagements and in-house teams. The point is not to give you a one-size-fits-all template. The point is to give you a starting point that is good enough to use today, so the alternative (no template at all) stops being the default.
For freelancers, the minimum viable template is a one-page design document that captures the learning problem, the proposed solution, the assumptions, and the change-control process. One page. If you cannot fit it on one page, you have not finished the design.
For in-house teams, the minimum viable template is a project documentation structure that captures the business case, the audience, the design, the deliverables, the timeline, and the change log. The change log is the part most teams skip. The change log is also the part that makes the project documentation hold up six months later when someone asks why the program looks the way it does.
Documentation as a system, not a deliverable
The shift the book asks for is small in concept and large in practice. Documentation is not a deliverable that ends when the project ends. Documentation is a system that runs alongside the work, capturing the decisions, the assumptions, and the outcomes as they happen.
That is the difference between documentation that holds up and documentation that does not. The system produces documentation continuously, not at the end. The system captures the why, not just the what. The system makes the work reproducible, not just presentable.
For a freelance instructional designer, that means the design document is a living artifact updated as the project evolves, not a one-time writeup submitted for approval. For an in-house ID, that means the project documentation grows with the program, not just at handoff. For an L&D manager, that means the documentation supports the budget conversation every year, not just the first one.
Who this book is for
The Documentation Standard is written for working instructional designers who know documentation matters but have never been shown a practical system. The book is 110 pages. It is a Kindle edition.
The best fit is a working ID, in-house or freelance, who has been burned at least once by missing documentation and wants a system that holds up. The three audiences the book names (freelancers, in-house teams, and L&D managers) are not separate personas. Most IDs play more than one of those roles over the course of a year.
If you are not sure where to start, start with the minimum viable templates chapter. The book is on Kindle. Here it is: The Documentation Standard on Amazon.