Onboarding
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.
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.
A short briefing for your first week. Five things we believe, written down so you can point at them when something gets confusing.
We don't have a wiki of rules — we have a few principles, and we trust people to apply them. If you're unsure, ask your manager in your next 1:1.
Manager fundamentals, rolled out to 47 sites in one quarter.
Compliance refresh in an afternoon, not a quarter.
AML training for 8,000 staff, evidenced for audit.
Safety training, six languages, one source of truth.
A two-page brief for managers running a coaching conversation. The kind of doc you'd normally have to draft in Google Docs, format in Word, and re-typeset every time the brand changes. Composed from a four-sentence brief.
Compose your own brief→Done well, it compounds. Done poorly, it produces the quietest form of attrition: people who haven't left yet. This briefing is what we wish every new manager had read before their first one.
Start broad. "What's been on your mind this week?" lands better than the usual status check, because it gives the person room to choose what to bring.
Find the friction before the fix. "What's the part that feels stuck?" gets a different answer than "what's the plan?"
One commitment per session. "What will you have done by Friday?" — and write it down so you both remember on Friday.
End with a check. "What didn't we talk about that I should know?" surfaces the thing that wouldn't have made it in any other way.
Run one 1:1 this week using the four parts. Note what felt clumsy. Try the same structure next week with a different person. After three weeks you'll feel the difference.
Two pages from a "Manager · Coaching 1:1" briefing. Same brief produces the deck and the SCORM module too — different shapes, one source.
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.
Four shapes L&D teams reach for most. There are twenty-one in the library; these are the workhorses.
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.
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.
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.
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.
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.
For the human side of the org.
When the long version is for legal.
Pre-reads, leave-behinds, follow-ups.
Internal communication that lasts.
Steps, checklists, runbooks.
Procurement, brand, and legal teams ask their own questions too. Those live in the trust center.
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.
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.
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.
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.
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.
No. Briefs and docs are never used for model training — by us or by our sub-processors. EU data residency by default. Full posture at /trust.
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.