MOP documents and branding
Ask Claude for a MOP as a document and you get a printable page plus Word (.docx) and Markdown (.md) downloads, branded with your organisation’s name and logo. With a run, the document becomes the run record: each step’s evidence, the writes sent and who approved the run. Nothing is sent to the controller.
How do I get a MOP as a document?
Section titled “How do I get a MOP as a document?”Ask Claude, for example “give me MOP 4 as a document for the change board”.
It calls mop.document:
| Argument | Default | What it does |
|---|---|---|
id | — | The MOP |
runId | — | One run of it: the document becomes the run record |
markdown | Off | Also return the document as Markdown in the chat |
tz | Your organisation’s digest time zone, else UTC | The time zone for times in the document |
Claude gives you three links:
| Link | What it is |
|---|---|
The printable page, /mops/<id>/export | The document in the dashboard, with Print, Download .md and Download .docx buttons. PDF is your browser’s print |
.docx | A Word file, A4, with your logo, accent colour on headings and table headers, and page numbers in the footer |
.md | The same document in Markdown |
The links need a dashboard sign-in, and any member of the organisation can open them. The page is titled Method of procedure, or Run record for a run. It is not in the sidebar: you reach it from Claude’s link, or from Open as a document on a MOP approval.
What does the document contain?
Section titled “What does the document contain?”- A cover: the MOP and its version, status (Plan (not run), or the run’s status), risk, the number of steps, the change window, who prepared it and when, and when it was generated. For a run, also when it started and ended, how it was approved and by whom, and what happens on failure.
- Purpose and parameters. A run’s parameter values are masked where they look secret.
- Pre-checks, procedure and post-checks: for each step, the request, operation, risk, repeats, path values, query, expected result, captures, rollback and body. With a run, each step’s evidence.
- The rollback plan, newest write first.
- The MOP linter’s notes.
- For a run, a run record: the writes sent and their rollback, and the downtime.
- A sign-off table.
Secret-looking values are masked throughout. A value that is only a
{{param}} placeholder is shown as the placeholder. A run’s document uses the
version of the MOP the run started with.
Is there a limit?
Section titled “Is there a limit?”20 documents a minute per organisation, shared with the alert quality,
digest and post-mortem reports. Past it the download answers 429 with “at most 20 reports a minute”.
How do I put our branding on the documents?
Section titled “How do I put our branding on the documents?”An admin sets it on the Document branding card on Configure › Team. The card applies to exported MOPs and run records (Word, Markdown and the printable page) only, nothing else. Members see the settings; only admins can change them (“An admin can change these.”).
| Field | Default | Limit |
|---|---|---|
| Company | The organisation’s name | 100 characters. Shown above the title |
| Accent colour | The built-in default (Default resets it) | A #rrggbb colour. Used on headings and table headers |
| Footer line | None | 200 characters. On every page, after the document’s own footer: a classification or a change-board reference |
| Logo | None | PNG or JPEG, at most 128 KB and 4,000 pixels on a side. Shown at most 4.5 cm wide |
Use Upload logo (or Replace logo) and Remove logo for the logo, Save for the rest, and Reset all to put every field back to its default.
| Logo refused | Message |
|---|---|
| Over 128 KB | ”The logo is at most 128 KB.” (the card refuses the file before uploading it) |
| Larger than 4,000 pixels | ”the image is at most 4000 pixels on a side” |
| Not really a PNG or JPEG | ”the body is not a PNG image” (or JPEG) |