The handout you'd actually keep.
Manager briefings. New-hire welcome packs. Compliance memos. The leave-behind from a workshop. MLtitude composes these in your brand voice from a single brief — typeset properly, on real pages, ready to share or print.
The doc, on brand, in an afternoon.
L&D teams write more documents than they admit. Every training is followed by a briefing, a handout, a leave-behind. They all need to look like they came from the same organisation. They rarely do.
- Draft in Google Docs. Look-and-feel is whatever Google does.
- Paste into the corporate template. Margins fight back.
- Ask brand for the right shade of grey. Wait.
- Discover three rogue versions in three Drive folders.
- Ship the closest one. Apologise on Slack.
- Type the brief. What it's for, who reads it, what to land.
- Pick the shape — briefing, memo, policy, leave-behind.
- MLtitude composes it on brand. Real typography, real margins.
- Read through. Tighten the wording. Export the PDF.
- Done. The next quarter, regenerate. Brand still holds.
The docs you ship every week.
Four shapes L&D teams reach for most. There are twenty-one in the library; these are the workhorses.
The welcome pack a new hire actually reads.
Five to ten pages, on brand, the same for every cohort. Set the tone for how the org communicates: opinionated, well-typeset, written for an adult.
Two pages before every cohort session.
Managers don't have time for a 40-page playbook. A two-page brief — what to teach, the questions that work, the practice loop — gets read on the train.
The two-page version of the forty-page policy.
Legal owns the long version. L&D writes the version a manager will actually read and act on. Same source brief; one official, one human.
What we taught. What to do Monday.
The handout that lands in the inbox on Friday afternoon. Three sections: what was covered, the commitment we made, the resource if you need to revisit.
21 ways a doc wants to look.
Every shape locks the right typography for that job. A policy doesn't look like a welcome pack. A leave-behind doesn't look like a white paper. The grammar of the page does most of the work; your words finish it.
From welcome pack to policy memo. Each shape sets the right typography and rhythm for the job.
Why this exists, who it's for, the key points to cover, the call to action. Optionally: data, source material, a brand kit.
The doc renders to the locked design system. Margins, callouts, columns, footers — done.
Export as PDF for print. Or share the live HTML — re-themable forever as your brand evolves.
People shapes
5 shapesFor the human side of the org.
Policy shapes
4 shapesWhen the long version is for legal.
Workshop shapes
4 shapesPre-reads, leave-behinds, follow-ups.
Strategy shapes
4 shapesInternal communication that lasts.
Process shapes
4 shapesSteps, checklists, runbooks.
The questions L&D leads ask.
Procurement, security, and brand teams ask their own questions too. If we missed yours, talk to us — we read every message.
Will it really look like our docs?
Yes — once your brand kit is set. Accent colour, headline colour, body font, the headline mark; all overlay every doc. The shapes themselves lock the rest (margins, type hierarchy, callout style) so the result looks composed, not collaged.
PDF or web?
Both. Every doc lives as semantic HTML — you can share the link to a colleague who reads it on their phone. When you need to print or attach, one click exports a typeset PDF. The PDF and the web version come from the same source.
What happens when our brand changes?
Re-theme any doc in place. The content is stored separately from the theme, so a brand refresh doesn't strand old documents in last year's colours. Old archives become current docs without re-doing the typography.
Can the long version stay in the policy management tool we already use?
Yes — and it should. MLtitude composes the readable version. The policy management tool keeps the legal version with version control and acknowledgements. Many teams brief MLtitude from the policy PDF and use MLtitude's doc as the manager-facing summary.
Do we lose editability?
No. Every doc opens in MLtitude for live editing — you can re-word a paragraph, replace a callout, swap an example. The shape holds; your edits land in the right slot. For deep edits, export the PDF and edit downstream.
Is customer content used for model training?
No. Briefs and docs are never used for model training — by us or by our sub-processors. EU data residency by default.
Compose a doc you'd put your name on.
Bring a real one this week — the manager briefing for Monday, the policy memo for Friday, the welcome pack for the next cohort. Compose it in MLtitude. If it doesn't look like something your org would ship, tell us. We read every note.