Skip to content
AI New Zealand
Home AI Playbook AI OS Executive AI Briefing AI Lunch & Learn Microsoft Copilot course AI Roadshow Premium membership Toolkits Webinars Insights AI Academy Contact us

Free toolkit

Your AI writes good documents. They just don't look like your business.

The On-Brand Documents Toolkit is the setup that gets Microsoft Copilot and Claude applying your fonts, colours, logo and layout to everything they produce. Two standards files, three platform tracks, and the admin steps to turn it on for everyone rather than just you.

22 files 3 platform tracks 2 page printable checklist Copilot, Claude Design and Claude skills

The idea

You are describing your brand in the prompt. That is why it does not work.

Ask any AI tool for a proposal "in our brand colours, forest green and ochre gold, Georgia headings and Calibri body" and you get content that is fine and formatting that is generic. Typed brand instructions do not reliably become actual Word styling. They never have.

What works is giving the tool something to read. Your brand standards as a file, and a document that already has the styles in it. Then every prompt inherits them and you stop retyping your own brand at your own software.

LAYER 1

The prompt.

"Use our brand colours." Lives one message, and Word mostly ignores it.

LAYER 2

The brand kit.

Configured once per platform. Real, but only reaches where that platform reaches.

LAYER 3

The standards file.

One file both platforms read. Survives whatever either vendor ships next.

LAYER 4

The styled template.

The file every document starts from. Does more work than the three above it.

What is inside

Three parts, one download.

Everything from the session, in the form you would actually use it.

The standards files.

Two templates that hold your brand, written the way an AI tool needs to receive it. Hex codes and style names, not adjectives.

  • Brand and visual standards
  • Document standards and structures
  • A completed worked example
  • A styled Word template to pull apart
  • Numbered to continue the Organisational Brain Toolkit

The platform tracks.

Wiring each platform to read those files, including the admin steps most people never get to.

  • The Copilot official Brand Kit, end to end
  • Both Microsoft policies, and the trap between them
  • Claude Design, published organisation wide
  • A brand skill, with a starter SKILL.md
  • Where each one reaches, and where it does not

The format explainers.

What to do differently, and what to check, in each of the formats your business actually sends.

  • Word: proposals, SOWs and SOPs
  • PowerPoint: decks and the Slide Master rule
  • PDF, export and the traps in between
  • Baseline prompts, deliberately short
  • A printable two page checklist

The method

Seven rules, and your first afternoon.

Seven rules that do the work.

  1. Write the standards down. Hex codes and font names, never adjectives.
  2. Never start from a blank document. Start from a file that already has the styles.
  3. Save templates as .docx. Copilot in Word does not read .dotx files at all.
  4. Link fonts and colours into the Slide Master, not onto individual slides.
  5. Publish it to everyone. Until you do, you have solved this for one person.
  6. Brand the source file, then export. There is no separate branded-PDF step.
  7. Check the first three documents. Then trust the fourth.

Your first afternoon.

TimeWhat you do
30 minWrite the brand and visual standards
20 minWrite the document standards
40 minBuild one .docx with real named styles
30 minSet up your platform track
20 minTest it on a document you already sent
24 hrsWait, if you are on the Microsoft track

Copy the hex codes out of your brand guidelines rather than sampling them off a logo. A few points out shows up on every document from then on.

Both platforms

Which one, for what.

Most businesses we work with end up running both. The pack covers both, and the standards file is what makes that work, because both platforms are reading the same thing.

Microsoft CopilotClaude
Reach Strongest in the Create tab and PowerPoint. Word, Excel and chat are partial. Any output in any format, including web pages, with no per-format setup.
Set-up cost An admin, two policies, a paid Copilot Premium licence tier. One toggle, then one person builds the design system or the skill.
Best at Sitting inside the apps your team already has open all day. Portability. One brand setup covers docx, pptx, pdf and html.
Watch for It will not pick a brand kit from your prompt, and there is no version history. Claude Design is still a beta. Large codebases and shared editing are rough.

Before you start

The five ways this fails.

Describing the brand in the prompt every time instead of writing it down once.
Building a personal brand kit and stopping, which fixes this for exactly one person.
Pointing Copilot at a .dotx template, which it silently ignores with no error.
A deck template whose fonts were typed onto slides instead of set in the master.
Choosing a licensed brand font and expecting AI to render it on everyone else's machine.

Get the toolkit

Send it to me.

Tell us where to send it and the download starts on the next page. The templates are yours to edit, rename and put to work.

We will email you occasionally about practical AI for New Zealand businesses. Unsubscribe any time.

Keep going

The AI Toolkit webinars.

This toolkit came out of one of them. Every week we take a working problem, build the thing live, and hand over what we used. Premium members get the full back catalogue and the resource library that goes with it.

The natural next one is the Organisational Brain Toolkit. The two standards files in this pack are numbered to slot straight into it.

Premium membership.

  • Weekly AI Toolkit webinars, live and recorded
  • The full resource and template library
  • Every session's working files, like this one
See Premium membership →