Nobody Rewrites the CAD Manual. So We Automated It.

TL;DR: Company standards documentation has moved from printed manuals to internal websites, but both break when software changes. This system stores everything in a single structured file that feeds AI training videos, Notebook LM knowledge bases, and Claude Skills. Update one file. Everything downstream rebuilds.

---

Every firm has a standards document. It defines how projects are set up, how models are organized, what naming conventions to follow, how coordination works, and which software to use.

For a long time, this lived in a printed manual. A binder on the shelf. You read it when you started at the firm, and then it sat there. If you needed to check something, you walked to the shelf. If you remembered.

The shift to internal websites

Eventually, firms moved their standards online. Internal websites with dozens of pages covering model setup, naming conventions, coordination procedures, software configuration, and deliverable checklists. Each topic had its own page. Each page had screenshots, step-by-step instructions, and links to related sections.

This was better than print. Searchable. Accessible from any workstation. Easier to distribute to new staff.

But it introduced a new problem: maintenance.

The rename problem

Every time a tool changes, the documentation falls behind. This is not hypothetical. It has happened repeatedly.

BIM 360 became Autodesk Construction Cloud. Construction Cloud is now shifting to Forma. Each rebrand means updating screenshots, rewriting step-by-step instructions, fixing internal links, and re-recording video walkthroughs across dozens of pages.

Nobody has time to do this well. So the manual drifts. Screenshots show old interfaces. Instructions reference features that no longer exist. New users follow outdated workflows because the documentation tells them to.

Standards exist on paper but not in practice.

One file instead of many pages

This project takes a different approach. Instead of maintaining a website with many pages, the entire company standards document lives in a single structured file.

One text file. One JSON. One markdown document. It holds every standard, every convention, every procedure in a structured format that is both human-readable and machine-readable.

That single file becomes the source of truth for everything downstream.

What the file feeds

From one structured file, we generate multiple outputs:

AI training videos. Using Eleven Labs for narration and VEO 3 for visual demonstrations, the system generates tutorial videos directly from the standards content. When a procedure changes, the video regenerates from the updated file.

Notebook LM knowledge bases. The structured file feeds into Notebook LM, creating an interactive knowledge base where users can ask questions about company standards and get context-aware answers. Not a static FAQ. A conversation with the standards document itself.

Claude Skills. The same file becomes a skill that Claude can reference when assisting with BIM tasks. When someone asks "What is the naming convention for structural sheets?" the answer comes directly from the current version of the standards file.

Why this matters

The traditional approach treats documentation as a deliverable. Write it, publish it, move on. The problem is that software does not stop changing. Autodesk alone has renamed, merged, or repositioned major products multiple times in the last five years.

A multi-page website cannot keep pace with that rate of change. Every update creates a maintenance burden that compounds over time.

A single structured file can. When Forma changes its interface, you update one file. The AI videos regenerate. The Notebook LM knowledge base updates. The Claude Skill reflects the new workflow. One change propagates everywhere.

The shift in thinking

This is not about choosing a file format. It is about treating documentation as structured state instead of static content.

The same principle applies to BEP automation, drawing QC, and every other system we have built. When you treat information as structured data with a single source of truth, you can generate any output format from it. Printed manuals, websites, videos, AI assistants. They all become views of the same canonical state.

The manual is no longer a document. It is a system.

Key Takeaways

• Printed manuals and multi-page websites both break when software changes
• A single structured file (text, JSON, or markdown) replaces dozens of pages
• That file feeds AI videos, Notebook LM knowledge bases, and Claude Skills
• One update propagates to every output format automatically
• Documentation becomes structured state, not static content

The goal isn't just better documentation. It's better buildings.