# Controlled Document Export

> Render a markdown source into a branded, controlled-document DOCX with cover page, logo header, version/page footer, classification banner, and optional approval table — suited to ISO, QMS, GxP, and other compliance document sets.



Tags: DOCX, Controlled Document, QMS, ISO, Branding, Quality Manual, SOP, Compliance, Export


## Example Prompts

- Export this Quality Manual as a branded controlled DOCX
- Apply our logo, version 1.0, and effective date to all SOPs and export to .docx
- Generate a controlled-copy DOCX from quality-manual.md with the approval table on page 2
- Rebuild this policy as an ISO-style branded document

URL: https://rakenne.app/skills/controlled-document-export/index.md

Try this skill: https://rakenne.app/a/?skill=controlled-document-export



## Overview

Controlled Document Export turns a markdown source into a branded, controlled-copy Word document for regulated document sets such as Quality Manuals, SOPs, policies, work instructions, and ISO/GxP/QMS deliverables.

It helps teams apply the document-control details reviewers expect:

- Cover page with document title, ID, version, effective date, and organization
- Optional logo header, with SVG logos converted to embeddable PNG when needed
- Footer with page numbering, document ID, version, and controlled-copy classification
- Optional approval table for author, reviewer, approver, title, and date
- Markdown body converted into a structured `.docx` while preserving headings, lists, tables, and paragraphs

## Example Conversation

> **You:** Export `quality-manual.md` as a controlled-copy DOCX for our ISO 9001 documentation set.
>
> **Agent:** I’ll collect the branding profile first: organization name, logo, document ID, version, effective date, classification, and approvers. Then I’ll render the markdown into a branded DOCX and validate the result before sharing the file path.
>
> **You:** Use our SVG logo and add Jane as author, Marco as reviewer, and Priya as approver.
>
> **Agent:** I’ll save those details in `branding.json`, convert the SVG logo to PNG for Word compatibility, build the cover page and controlled header/footer, and include the approval table.
>
> **You:** Please make sure the footer shows page numbers and version 1.0.
>
> **Agent:** Done. The footer includes document ID, version 1.0, “Controlled Copy”, and `Page X of Y`. I also ran DOCX validation and the file is ready at `quality-manual.docx`.

## Sample Output Excerpt

Below is a simplified excerpt of the controlled document structure the skill produces.

---

# Quality Manual

**Document ID:** QM-001  
**Version:** 1.0  
**Effective date:** 2026-05-12  
**Classification:** Controlled Copy

## Approval Record

| Role     | Name        | Title            | Date       |
| -------- | ----------- | ---------------- | ---------- |
| Author   | Jane Doe    | QA Manager       | 2026-05-08 |
| Reviewer | Marco Silva | Operations Lead  | 2026-05-10 |
| Approver | Priya Nair  | Quality Director | 2026-05-12 |

## 1. Purpose

This Quality Manual defines the management system used to control documented information, operational responsibilities, process interactions, and continual improvement activities.

## 2. Scope

This manual applies to all controlled QMS processes, including document control, training, nonconformance management, internal audits, and management review.

<!-- /excerpt -->

## Underlying DOCX Tools

The skill depends on the DOCX Tools package and uses the right tool for each part of the workflow:

- **`docx_convert`** converts SVG, PDF, or other source logo formats to PNG when Word cannot embed the original asset directly.
- **`docx_build`** creates the controlled-document Word file with separate cover/body sections, branded headers, page-number footers, approval tables, and markdown-derived content.
- **`docx_validate`** checks the generated `.docx` before delivery and can attempt safe auto-repair when supported.

The agent does not overwrite the source markdown. Each export writes a new `.docx` so the controlled Word document remains traceable to the markdown source.

## Getting Started

Add the markdown document and any logo asset to your project workspace, then activate the _Controlled Document Export_ skill.

Prepare the core branding details before export:

1. Organization name
2. Document title and document ID
3. Version and effective date
4. Classification, such as “Controlled Copy” or “Uncontrolled Copy”
5. Optional approvers for the approval table
6. Optional logo and preferred accent color

For a batch of SOPs or policies, provide a manifest with each source file, document title, document ID, version, and effective date. The agent will reuse the same branding profile and export each document consistently.



---

Back to [Skill Library](https://rakenne.app/skills/index.md)