Category: Blog

Spending less on routine decks without cheapening the ones that matter

Most presentation budgets have never been divided sensibly. The same agency, the same retainer, the same designer queue handles the weekly operations update and the board presentation. The routine work, being more numerous, consumes more of the budget. The high-stakes work, being more urgent, gets whatever capacity is left.

Copilot creates an opportunity to fix that. Routine decks can increasingly be generated by employees from a well-built system, reducing what you spend on them. The risk is that “spend less on presentations” becomes a blanket instruction — and the decks that genuinely matter get cheapened along with everything else.

This post is about capturing the first without causing the second.

Step 1: Separate the two kinds of spending

Start by sorting last year’s presentation spending — agency fees, contractor time, a share of in-house designer time — into categories:

Category Examples Characteristics
Routine Status updates, briefings, internal proposals, reformatting High volume, recurring structure, internal, moderate stakes
Important internal Leadership reviews, strategy updates, major proposals Moderate volume, real decisions, internal audiences
High-stakes Board, investor, major pitches, keynotes, sensitive announcements Low volume, high consequence, often external
System Templates, brand assets, standards Periodic historically; ongoing with Copilot

If your budget has never been tracked this way, the split alone can be revealing.

Step 2: Move routine work to the system

Routine decks are what Copilot drafts best, particularly from a template built to teach it. The aim is for employees to generate routine decks that are usable with light cleanup, so fewer of them become requests to designers or agencies.

That depends on the system, not on the license. Microsoft’s guidance is that Copilot learns primarily from the template’s sample slides, uses its placeholders to decide what goes where, and takes colors and fonts from its theme — and that without enough sample slides, it falls back to the Slide Master, “which may result in less optimal output.” A template that teaches poorly produces decks that still need a designer, and the spending doesn’t move.

So the first investment is in the system: the template rebuilt for how Copilot learns, a set of example slides covering routine deck types, written rules for recurring problems, and strict brand adherence once testing shows the template covers real content.

Step 3: Measure whether it’s working

The signal that routine spending can safely fall is fix-up time: how much work generated routine decks need before use. Score a sample on a simple scale — usable as generated, light cleanup, skilled correction, senior judgment, rebuild.

  • If most routine decks need light cleanup or less, routine requests to designers and agencies should fall, and the budget can follow.
  • If many still need skilled correction, the system needs more work before the budget moves — otherwise the cost reappears as employees’ time, or as decks going out unfixed.

Step 4: Protect the decks that matter

This is the step that gets skipped. When routine spending falls, it’s tempting to cut presentation budgets across the board. Resist that. High-stakes presentations are hard because of argument, audience and stakes — not formatting — and generated drafts don’t change that. Microsoft’s own position is that Copilot output should be reviewed by a person; for the presentations that matter most, that means experienced people.

A healthier move is to redirect part of the routine savings:

  • more time and senior attention for high-stakes work, which was often squeezed when the queue was full of routine requests;
  • investment in the system itself, including upkeep.

Step 5: Fund the system properly

The system is what makes routine savings possible, and it needs ongoing care. Microsoft made two significant template-related changes in September 2026 alone; organizations change too. A quarterly cycle of re-testing and updating keeps fix-up time low. Without it, the system degrades, fix-up rises, and routine work drifts back to designers and agencies — reversing the savings.

Step 6: Change how you buy

If you use an agency, the shift suggests revisiting how you buy from them:

  • Routine production should shrink. If a retainer was sized for routine volume, it may be oversized.
  • High-stakes work may deserve more senior time per project, not less.
  • System work — template, examples, rules, testing, upkeep — is a different kind of engagement from production, and it’s worth scoping it as an outcome rather than drawing it from a production-hours pool.

What this looks like when it’s working

  • Routine decks are generated by employees and need light cleanup at most.
  • Requests to designers and agencies are mostly for important and high-stakes work.
  • The high-stakes decks get more senior attention than before.
  • The system has a named owner and a quarterly routine.
  • Presentation spending is lower overall, and better aligned with where the stakes are.

We’re careful not to promise a percentage reduction. It depends on your mix of deck types, your template, and how well the system is maintained. But the direction is achievable, and the method is measurable.

Common questions

How quickly can routine spending fall?
It depends on how well the system works and how fast people adopt it. Use fix-up time as the signal. When routine generated decks mostly need light cleanup, the budget can follow.

Should we cut our agency?
Consider reshaping the relationship rather than cutting it: less routine production, more senior time on high-stakes work, and system work scoped as outcomes.

What’s the risk of cutting too fast?
Routine work moves to employees’ own time, or decks go out unfixed. Both are hidden costs, and the second is a brand risk.

Key takeaways

  • Separate presentation spending into routine, important internal, high-stakes and system.
  • Move routine work to a well-built Copilot system; the license alone doesn’t move the spending.
  • Use fix-up time to decide when routine budgets can safely fall.
  • Protect — and ideally increase — attention on high-stakes decks, and fund the system’s upkeep.
  • Rethink how you buy from agencies: less routine production, more senior time on what matters, system work scoped as outcomes.

Want to know whether your routine decks are ready to move? Have your template scored.**

Related reading

Sources

What “on-brand” really means for a generated deck

Ask whether a generated presentation is “on-brand” and most people check three things: the logo, the colors, the fonts. If those are right, the deck passes.

By that standard, getting Copilot to produce on-brand decks is mostly a solved problem — put the brand in the theme and a Brand Kit, and those three things come out right. Yet brand teams keep looking at generated decks with the right logo, colors and fonts and feeling that something is off. They’re right. Visual identity is the most visible layer of a brand in a presentation, and the thinnest.

This post sets out a fuller definition — six layers — and which of them Copilot can learn from your template and rules.

Diagram of six layers of on-brand, from identity to voice and structure, with what teaches each layer to Copilot

Layer 1: Identity

What it is: logo, color palette, typography.

How Copilot learns it: the theme and the Brand Kit. Microsoft recommends defining colors as theme colors and heading and body fonts in the theme, and Brand Kits can hold logos, palettes with hex values and fonts.

Typical failure: charts and new shapes in default colors, because brand colors were painted onto elements rather than defined in the theme.

This layer is necessary. It’s also the one people confuse with the whole brand.

Layer 2: Composition

What it is: how slides are laid out — grids, margins, alignment, where titles sit, how much whitespace surrounds content.

How Copilot learns it: layouts and placeholders. Microsoft notes Copilot uses placeholder type, position and size to decide what goes where. Consistent layouts produce consistent composition.

Typical failure: text boxes instead of placeholders, placeholders overlapping decoration, content forced into the nearest layout because the right one doesn’t exist.

Layer 3: Density and rhythm

What it is: how much your organization puts on a slide, and how that varies — a single statement, then a balanced explanation, then a detailed table.

How Copilot learns it: example slides at the light, medium and heavy densities Microsoft recommends, and rules such as note instructions (“Keep the text minimal”) and Brand Skills.

Typical failure: every slide at the same density, usually too full.

Layer 4: Hierarchy and emphasis

What it is: what you make prominent and how. A brand that leads with bold statements feels different from one that leads with evidence.

How Copilot learns it: example slides that show emphasis done well — highlighted statistics, key takeaways, a clear single message. Microsoft specifically recommends layouts for highlighted statistics and key takeaways.

Typical failure: the most important point buried in a bullet list.

Layer 5: Visual language

What it is: imagery style and treatment, icon style, how data is visualized, recurring graphic devices.

How Copilot learns it: approved assets in the Brand Kit (including a connected SharePoint asset library), picture placeholders, image and chart styles in the template, and examples showing how your brand uses images — Microsoft cites “full bleed background images on title slides or inset images on content slides” as the kind of pattern to show.

Typical failure: generic imagery, default chart styling, images cropped or overlaid in ways your brand wouldn’t.

Layer 6: Voice and structure

What it is: how titles are written, how arguments are ordered, how you open and close, the words you use and avoid.

How Copilot learns it: written rules — Brand Skills, rolling out from late September 2026 — plus voice guidance in the Brand Kit and the phrasing in your example slides.

Typical failure: topic titles (“Q3 Results”) where your brand writes takeaways (“Q3 grew in every region but one”); a recommendation on the last slide where your leadership expects it first.

Why the deeper layers matter

Layers 1 and 2 make a deck look like it came from your organization. Layers 3 to 6 make it sound and think like your organization. Audiences notice the difference even if they can’t name it. A deck with perfect identity and generic density, hierarchy and voice reads as templated — technically branded, recognizably generated.

The deeper layers also carry most of the value of a brand in presentations. A consistent way of structuring recommendations makes decisions faster. A consistent way of presenting data makes numbers easier to trust. These aren’t cosmetic.

Where each layer lives

Layer Primary home Owner
Identity Theme, Brand Kit Brand manager, template builder
Composition Layouts, placeholders Template builder
Density and rhythm Example slides, note instructions Designers, brand manager
Hierarchy and emphasis Example slides Designers
Visual language Brand Kit assets, styles, examples Designers, asset librarian
Voice and structure Brand Skills, examples Brand manager, standards owner

Brand teams have traditionally invested most in the first row. Almost all the opportunity is in the others, and most of it runs through one asset: the example slides Microsoft describes as Copilot’s primary learning source.

A better definition for review

When you review generated decks, try replacing “is it on-brand?” with six questions:

  1. Right identity?
  2. Consistent composition?
  3. Appropriate density?
  4. Clear hierarchy?
  5. Our visual language?
  6. Our voice and structure?

The answers tell you not only whether a deck is on-brand, but which layer of the system to fix when it isn’t.

Common questions

Isn’t a Brand Kit enough to be on-brand?
A Brand Kit covers identity well: logos, colors, fonts and approved imagery. The deeper layers, density, hierarchy and voice among them, are taught mainly by example slides and written rules.

How do we test the deeper layers?
Use a fixed set of realistic prompts and review the output against all six layers, not just identity. Note which layer each problem belongs to; that tells you what to fix.

Which layer should we fix first?
Fix identity first if it’s broken, because everything else builds on it. Then fix whichever deeper layer causes the most problems in your own review.

Key takeaways

  • Logo, colors and fonts are the thinnest layer of brand in a presentation.
  • A fuller definition has six layers: identity, composition, density, hierarchy, visual language, voice and structure.
  • Copilot learns identity from the theme and kit, composition from layouts, and the deeper layers mainly from example slides and written rules.
  • Brand investment has traditionally gone to identity; most of the opportunity is in the rest.

Want to know which layers your template teaches? Have your template scored.**

Related reading

Sources

Designing example slides a model can learn from

Designers are used to designing slides for an audience of people. Example slides in a Copilot template have a different audience: a model that will study them and then generate thousands of slides in their image.

Microsoft’s guidance describes sample slides as the primary way Copilot learns from a template, and warns that without enough of them, Copilot falls back to the Slide Master. So example slides are no longer decoration at the back of the template file. They are the teaching material. This post is about designing them to teach well.

What an example slide teaches

When a person looks at an example slide, they see one slide. When Copilot learns from it, it picks up a set of patterns:

  • Structure: which layout serves which kind of content.
  • Density: how much content belongs on this kind of slide.
  • Hierarchy: what is most prominent, and what is secondary.
  • Visual language: how color, typography, imagery and icons are used.
  • Content patterns: how titles are phrased, how long bullets are, how data is labeled.

Every one of those is learned whether you intended to teach it or not. That is the central discipline of designing examples: every detail is a lesson.

Six properties of a good example slide

1. One clear purpose

Microsoft recommends slide types “with a clear, recognizable purpose” and complete, end-to-end layouts that demonstrate “a single, clear use case.” An example that tries to show a comparison, a statistic and a process at once teaches a muddled pattern. One job per example.

2. Realistic content

“Lorem ipsum” and “Insert text here” teach nothing about what real content looks like — its length, its tone, its structure. Example text should read like real slide copy: real-length titles, real-length bullets, plausible labels.

3. Durable content

This rule is easy to miss. Generative models can reproduce example content closely. A market statistic in an example slide — “The market will grow 14% by 2028” — can surface, near-verbatim, in someone’s generated deck about something else entirely. A figure that was harmless as filler becomes a false fact in a real presentation.

So example content should be realistic but durable: things that are true about your organization for years and harmless if copied, or clearly generic structure. No market statistics, no dated figures, no customer names, no forecasts. If an example needs numbers to demonstrate a chart, use obviously illustrative round figures and label them as such — and test whether Copilot copies them.

4. Good judgment, visible

The most important element should be the most visible one. The reading order should be obvious. Whitespace should be deliberate. This is where design quality translates directly into output quality: Copilot learns emphasis from examples that show good emphasis.

5. Correct construction

Examples must be built on the template’s layouts, with content in real placeholders and colors and fonts from the theme. An example with a hand-drawn text box or a hardcoded color teaches that shortcut. Microsoft’s guidance about placeholders, overlap and decoration applies to examples as much as to layouts.

6. Representative, not aspirational

The temptation is to fill the template with showpieces — the most beautiful slides the brand has ever made. But Copilot will mostly generate everyday slides: updates, explanations, summaries. Examples should reflect what your people actually need to make, at the quality you want them made. A set of award-worthy keynote slides teaches a model very little about a quarterly operations update.

Covering the set

Microsoft’s guidance lists the slide intents templates usually need — title, agenda, section divider, content, data visualization, timelines, processes, lists, quotes, Q&A, summary, conclusion, closing — and asks for light, medium and heavy densities, plus examples of how the brand uses color, typography, imagery and data.

In practice we plan the set as a grid: slide intents down one side, densities across the top, and a mark in each cell your organization actually uses. Each marked cell needs an example. Unmarked cells don’t — adding examples nobody needs dilutes the lesson.

Common mistakes

Too many covers. Templates often carry a dozen cover variations and two content slides. Copilot learns that the brand is mostly covers.

Near-duplicates. Three versions of the same comparison with trivial differences leave Copilot choosing arbitrarily.

Instruction slides. “How to use this template” slides are examples too. Microsoft recommends keeping instructional content outside the template.

Sparse idealism. Every example is a single elegant headline. Copilot never sees a slide carrying real content, so it has no model for density.

Stale content. Examples that mention last year’s strategy, retired products or former executives. Copilot may carry them into new decks.

Test what the examples teach

Examples are a hypothesis: “if Copilot learns from this, it will produce slides like this.” The only way to check is to run a fixed set of realistic prompts and look at the output.

Look specifically for:

  • copied content — phrases or numbers from examples appearing in unrelated decks;
  • wrong generalization — a pattern from one example applied where it doesn’t fit;
  • missing coverage — content forced into layouts meant for something else;
  • density drift — slides consistently fuller or emptier than the examples.

When you find a problem, fix the example that taught it, not the generated slide. Then rerun the same prompts and compare.

Who should design them

Example slides are design work of a specific kind: part art direction, part information design, part teaching. They should be designed by experienced presentation designers and approved by whoever owns the brand. They should not be generated by Copilot and tidied up — that teaches the model its own habits.

Key takeaways

  • Example slides are Copilot’s primary teaching material; every detail is a lesson.
  • Good examples have one purpose, realistic and durable content, visible judgment, correct construction and everyday relevance.
  • Never put statistics, dates, forecasts or customer names in example copy — models can reproduce it.
  • Plan the set as a grid of real intents and densities, and avoid covers, duplicates and instruction slides.
  • Test what the examples teach, and fix the example, not the output.

Want example slides designed to teach? Have your template scored.**

Related reading

Sources

What drives the cost of a Copilot-ready template

“How much does a Copilot-ready template cost?” is a fair question with an unsatisfying honest answer: it depends, a lot. Two organizations with templates that look similar can need very different amounts of work, because the cost is driven less by how the template looks than by what’s underneath it and what your people need it to do.

We don’t publish a rate card for full builds yet. We start every engagement with a fixed-price audit, precisely because the scope of the rest depends on what the audit finds. What we can do is explain the factors that drive the cost, so you can anticipate scope, compare quotes sensibly, and decide where to spend.

The seven cost drivers

1. The state of the theme

If your brand colors and fonts are properly defined in the theme, this part is quick. If they’ve been painted onto elements by hand — common in long-lived templates — every layout needs re-pointing to theme colors and fonts. Microsoft’s guidance is to define colors and fonts in the theme, because anything Copilot creates takes them from there. The more layouts and hardcoded values, the more work.

2. The number and condition of layouts

A template with a focused set of well-built layouts needs little structural work. One with many layouts, several masters, duplicate covers, text boxes where placeholders should be, and decoration overlapping content areas needs cleanup and rebuilding. Microsoft recommends real placeholders instead of text boxes, and non-overlapping placeholders kept clear of decoration.

3. Coverage gaps

Layouts your people need but the template lacks have to be designed from scratch. Gaps matter more with Copilot because, with strict brand adherence on, it can’t create a layout to fill them.

4. The example set

The most variable driver. Microsoft describes sample slides as Copilot’s primary learning source and asks for examples across the slide types an organization uses, at light, medium and heavy densities. How many examples your organization needs depends on the variety of presentations your people make: more deck types, more densities and more distinctive patterns mean more examples. Each is a finished, designed slide with realistic, durable content.

5. Brand complexity

A single brand with one audience is simpler than a master brand with sub-brands, regional variations or distinct external and internal styles. Multiple official Brand Kits are supported, but each kit’s template and examples need building and testing.

6. Rules and constraints

Written rules — note instructions and Brand Skills — take time to draft, test and revise. Regulated organizations need more: protected disclosure slides, rules against unsupported claims, and testing designed to tempt omissions and invented figures.

7. Testing depth

A fixed prompt set, a baseline run, scored output, diagnosis, changes and re-runs. More deck types and higher stakes justify a larger test set and more iterations.

Costs after launch

The build isn’t the whole cost. The platform changes — Microsoft made two significant template-related changes in September 2026 alone — and your organization changes. Upkeep, at least quarterly, is an ongoing cost whether it’s done in-house or by a partner. Budget for it at the start rather than discovering it a year later.

How to reduce cost without cutting what matters

Start with an audit. It’s the cheapest way to find out which drivers apply to you, and it prevents paying for work you don’t need.

Clean up before you build. Removing duplicate and unused layouts reduces everything downstream: fewer layouts to rebuild, fewer examples to design, fewer choices for Copilot to get wrong.

Build examples from real decks, not wish lists. The right example set covers what your people actually make. Examples for deck types nobody produces cost money and can dilute what Copilot learns.

Prioritize by volume. If budget is limited, cover the most common routine deck types first — that’s where generated decks are most frequent — and extend coverage later.

Keep rules short. A handful of tested rules outperforms a long, untested document.

Do the mechanical work in-house if you have capacity. Re-pointing colors and rebuilding placeholders is methodical; example design and testing method are where outside experience tends to add most.

Where not to cut

Testing. A template that hasn’t been tested with realistic prompts is a guess. Skipping testing saves a little up front and risks multiplying flaws across every generated deck.

Example quality. Examples are the teaching material. Cheap examples teach cheap patterns.

Upkeep. A system nobody looks after degrades quietly until someone sends the wrong deck.

Comparing quotes

When comparing proposals, check that they cover the same scope. A lower quote that excludes examples, testing or upkeep isn’t cheaper; it’s smaller. Ask each provider:

  • Does the price include an audit, and will we see the findings?
  • How is the number of example slides determined?
  • Is testing with a fixed prompt set included, and will we see the output?
  • Are note instructions and Brand Skills included?
  • What happens after launch, and what does it cost?

Key takeaways

  • Cost depends on what’s underneath the template and what your people need, not on how it looks.
  • Seven drivers: theme state, layout condition, coverage gaps, the example set, brand complexity, rules, and testing depth.
  • The example set is the most variable driver; its size follows from the variety of decks your people make.
  • Reduce cost with an audit, cleanup, real-deck examples, volume priorities and short rules.
  • Don’t cut testing, example quality or upkeep, and compare quotes on the same scope.

Want to know which drivers apply to you? Start with a fixed-price audit — have your template scored.**

Related reading

Sources

Brand consistency when everyone can generate a deck

For as long as organizations have had brands, presentations have been the leakiest part of them. Websites go through agencies and approvals. Ads go through legal. Presentations are made by everyone, in a hurry, from whichever file they had open last. Brand teams have always known this and mostly accepted it, because policing thousands of decks by hand was never possible.

Generative tools change the shape of the problem. When every employee can produce a polished-looking presentation in minutes, the volume of branded material leaving the organization goes up, and the traditional safety net — a designer catching problems — catches a smaller share of it. At the same time, the tools give brand teams a new kind of control they never had before.

This post is about using that control well.

Why consistency gets harder first

Three things happen when employees start generating decks.

Volume rises. People make decks they previously wouldn’t have bothered with, and they make them faster.

Polish hides problems. A hand-built deck with the wrong colors looks wrong. A generated deck can look finished — clean layout, confident typography — while using an outdated image, a non-standard color on its charts, or a structure nobody in the brand team would choose.

Fewer decks pass through experts. The whole point is that employees don’t need a designer for routine work. So fewer decks get a designer’s eye before they’re sent.

If brand consistency depends on review, it will decline. There simply isn’t enough review to go around.

Why it can get better than ever

Here’s the opportunity. For the first time, the thing producing most routine decks can be governed centrally.

Microsoft 365 Copilot gives brand teams several levers:

  • An official Brand Kit, controlled by designated brand managers, holding the logos, palettes, fonts, imagery, templates and voice guidance Copilot uses when employees select the brand.
  • Strict brand adherence, introduced in September 2026, which restricts Copilot to approved template and slide master layouts. Employees can’t override it.
  • Note instructions, which put rules in template speaker notes — “Always include this cover slide,” “Don’t modify this slide,” “Keep the text minimal.”
  • Brand Skills, rolling out from late September 2026, which publish written presentation rules across the organization.

A human-made deck is only as consistent as the person making it. A generated deck is as consistent as the system it came from. That moves brand consistency from an enforcement problem — catching mistakes — to a design problem: building a system that doesn’t make them.

Consistency is more than colors

When people say “on brand,” they often mean the visible identity: logo, colors, fonts. Those are the easiest things to make consistent, because they live in the theme and the Brand Kit and apply automatically.

The harder layers are the ones that make an organization’s presentations recognizable as its own:

  • Structure: how you open, how you make a recommendation, how you close.
  • Density: how much you put on a slide, and when.
  • Hierarchy: what you emphasize and how.
  • Data style: how you present numbers — takeaway titles, highlighted statistics, clean tables.
  • Imagery: what kinds of images you use and how you treat them.
  • Voice: how slide titles and text are written.

These don’t live in a color palette. Copilot learns them from the template’s example slides — which Microsoft describes as its primary learning source — and from written rules in note instructions and Brand Skills. A template with a perfect theme and no examples produces decks that are consistent in color and inconsistent in everything else.

Building a consistent system

In order:

1. One source of truth. One official Brand Kit per real brand, and old templates retired. Consistency is impossible when three templates compete. Multiple official kits are supported — use them for genuine sub-brands, not for rival versions.

2. The brand in the theme. Colors, fonts and chart, table and shape styles defined in the theme so everything Copilot creates inherits them.

3. Examples of the deeper layers. Finished example slides showing your structure, density, hierarchy, data style and imagery, across the slide types your people actually make.

4. Rules for what examples can’t show. Voice, terminology, required and protected slides, density limits — in note instructions and Brand Skills, short and testable.

5. Deliberate enforcement. Strict brand adherence once testing shows the template covers real content.

6. Measurement. A fixed set of realistic prompts, run regularly, and a periodic sample of real generated decks reviewed for consistency failures.

What review is still for

Review doesn’t disappear; its purpose changes. Instead of checking every deck for brand errors — impossible at scale — brand teams review samples of generated output to find patterns, then fix the system that caused them. One fix to an example slide or rule corrects the pattern in every future deck.

Individual review still matters for high-stakes, external presentations. Microsoft’s own guidance is that Copilot output should be reviewed by a person, and the more a deck matters, the more that applies.

Common questions

Is brand consistency the same as brand compliance?
Not quite. Compliance means following the rules. Consistency means decks feel like they came from the same organization, which includes structure, density, hierarchy and voice, not just colors and logos. Rules help with compliance; examples do most of the work for consistency.

Can we lock everything down?
Strict brand adherence locks layouts, and note instructions can protect specific slides. But a generative model still makes choices inside those layouts. Microsoft’s guidance is that its output should be reviewed by a person.

What about teams that need their own look?
Organizations can have more than one official Brand Kit. Use that for genuine sub-brands with their own identities, not to let each team keep its own version of the same brand.

Key takeaways

  • Generated decks raise volume, hide problems behind polish, and bypass designers, so review-based consistency declines.
  • The same tools let brand teams govern routine decks centrally for the first time.
  • Consistency is more than colors: structure, density, hierarchy, data style, imagery and voice are taught by examples and rules.
  • Build one source of truth, a theme-defined brand, teaching examples, testable rules, deliberate enforcement and ongoing measurement.
  • Review samples to fix the system; review individual decks when the stakes are high.

Want consistency built in rather than inspected in? Have your template scored.**

Related reading

Sources

Name every layout for its job

Open the Slide Master of almost any large corporate template and read the layout names. You will find “Title and Content,” “Title and Content 2,” “1_Title and Content,” “Custom Layout,” “Layout 14,” and perhaps “Copy of Two Content — DO NOT USE.” Nobody decided those names. They accumulated.

It seems like a cosmetic problem. It isn’t. The way layouts are named is a reliable signal of whether anyone has decided what each layout is for — and with Copilot learning from your template, that decision matters more than it ever has.

Why names matter now

For years, layout names were mostly for the few people who maintained the template. Everyone else picked layouts by their thumbnails. A confusing name cost a few seconds.

Copilot changes the stakes in two ways.

First, the template has to be designed around purpose. Microsoft’s guidance for Copilot templates asks for slide types “with a clear, recognizable purpose,” and for “complete, end-to-end slide layouts that demonstrate a single, clear use case.” A layout you can’t name by its purpose is a layout without a clear purpose — and Copilot can’t infer one that the template’s owners never decided.

Second, maintenance matters more. A Copilot template isn’t a file you ship once. Its layouts, example slides and rules need revisiting as your organization’s needs change and as Microsoft changes the product. Clear names make that maintenance possible. “Layout 14” makes it guesswork.

A caveat worth being honest about: Microsoft’s documentation describes Copilot using placeholder type, position and size — and sample slides — to decide what goes where. It doesn’t say layout names are a signal Copilot uses. We name layouts for their job because it forces good decisions and makes the template maintainable, not because we expect the name alone to steer the model.

Naming as a design exercise

The real value of naming is what it forces you to confront. When you try to name every layout for its job, three things happen.

You find duplicates. “Title and Content,” “Title and Content 2” and “1_Title and Content” turn out to be the same job, with minor differences nobody remembers choosing. Keep the best one.

You find orphans. Some layouts have no job anyone can name — a leftover from an old campaign, a one-off for a single presentation. Remove them.

You find gaps. Once each layout is named for its job, it becomes obvious which jobs have no layout. If your people regularly compare two options and there is no “Comparison — two options” layout, that is a gap Copilot will hit every time someone asks for a comparison. With strict brand adherence on, Copilot can’t create a new layout to fill it.

That last point is the most valuable. A layout list named by purpose is effectively a map of what the template can and can’t do.

A naming convention that works

There’s no official standard. Here’s a convention we find practical:

Pattern: [Job] — [variant]

  • Title — photo
  • Title — plain
  • Section divider
  • Agenda
  • Statement — single message
  • Content — text only
  • Content — text and image
  • Content — dense, two columns
  • Comparison — two options
  • Comparison — three options
  • Process — four steps
  • Timeline — horizontal
  • Data — chart with takeaway
  • Data — highlighted statistic
  • Data — table
  • Quote
  • Team — four people
  • Summary — key takeaways
  • Closing — contact

A few rules behind it:

  • Lead with the job, so the list sorts into groups when you scan it.
  • Use plain words. “Comparison,” not “Juxtaposition module.”
  • Name the variant by what differs — the number of items, the density, the image treatment.
  • No numbers without meaning. “Process — four steps” is fine. “Process 2” isn’t.
  • No status in the name. “DO NOT USE” belongs in a deletion, not a layout name.

Pair names with examples and notes

Naming is one part of making purpose clear. The others:

  • Example slides. Every named layout that matters should have at least one finished example slide showing its job done well. Microsoft describes sample slides as Copilot’s primary learning source; without them, it falls back to the Slide Master.
  • Note instructions. Since September 2026, brand managers can write plain-language instructions in template speaker notes — for example, “Use this layout only for comparing two options.” Unlike placeholder text, which Microsoft says Copilot doesn’t treat as instructions, note instructions are read as guidance.
  • Placeholder design. A “Comparison — two options” layout should have two matched content areas, clearly separated. The structure should say “comparison” even without the name.

How to rename an existing template

  1. Inventory. List every layout under every master, with a thumbnail and a count of how often it’s used in recent real decks if you can get one.
  2. Assign jobs. For each, write the job it does. If you can’t, mark it as a candidate for removal.
  3. Merge duplicates. Keep the best version of each job.
  4. Rename using the convention.
  5. List the gaps — jobs your people need that no layout does — and design those layouts.
  6. Build example slides for each layout that matters.
  7. Test with realistic prompts to confirm Copilot is reaching for the right layouts.

Keep a record of what you merged and removed. Existing presentations built on removed layouts will still open, but anyone updating an old deck to the new template will want to know where things went.

Common questions

Does Copilot read layout names?
Microsoft’s documentation describes Copilot using placeholder type, position and size, and sample slides, to decide what goes where. It doesn’t say layout names are a signal. We name layouts for their job because it forces clear decisions and makes the template maintainable, not because we expect the name alone to steer Copilot.

Will renaming layouts break existing presentations?
No. Existing presentations keep their own copies of the layouts they use. People updating old decks to the new template will need a mapping from old layout names to new ones, so publish one.

How many layouts should a template have?
There’s no correct number. The right set covers the jobs your people actually do, with no duplicates and no orphans. Naming every layout for its job is the quickest way to see which is which.

Key takeaways

  • Layout names reveal whether anyone has decided what each layout is for.
  • Microsoft asks for slide types with a clear, recognizable purpose; naming forces that decision.
  • Naming exposes duplicates to merge, orphans to remove and gaps to fill.
  • Use a [Job] — [variant] convention in plain words.
  • Back names with example slides, note instructions and placeholders that make the purpose obvious.

Want a map of what your template can and can’t do? Have your template scored.**

Related reading

Sources

In-house or outside help: costing a Copilot template project

Once an organization decides its template needs to work properly with Copilot, the next question is who does the work. Your own design team knows the brand intimately. An outside partner may have done this before. Both options have costs, and the obvious ones — salary time versus a fee — are rarely the ones that decide the outcome.

This post gives you a framework for comparing the two honestly. We’re an outside partner, so we have an interest in the answer; we’ve tried to write the framework so it’s useful even if you conclude the work belongs in-house.

What the project involves

Whoever does it, a Copilot-ready template project usually includes:

  1. Audit — assessing the current template against Microsoft’s published guidance: theme, masters, layouts, placeholders, example slides.
  2. Rebuild — moving the brand into the theme, rebuilding layouts with real, correctly sized placeholders, cleaning up duplicates and filling gaps.
  3. Example slides — designing a set of finished examples across the slide types and densities your people use. Microsoft describes sample slides as Copilot’s primary learning source.
  4. Brand Kit and settings — setting up the official kit, deciding strict brand adherence and writing note instructions.
  5. Written rules — drafting and testing Brand Skills.
  6. Testing — a fixed set of realistic prompts, run before and after, with output scored.
  7. Upkeep — re-testing and updating at least quarterly.

The in-house cost

The visible cost is designer time. The costs that tend to be missed:

Opportunity cost. Designer hours spent on the template are hours not spent on the decks that matter or on the routine queue. If your design team is already at capacity, the template project either displaces other work or drags on.

Learning cost. Copilot’s template behavior is specific and new: sample slides as primary teaching material, placeholder type, position and size, the Slide Master fallback, strict brand adherence, note instructions, Brand Skills. Microsoft introduced two significant changes in September 2026 alone. An in-house team doing this for the first time will spend time learning what works — which is valuable, but is a cost.

Testing cost. Building and running a fixed prompt set, scoring output consistently, and diagnosing failures is its own discipline. Teams sometimes skip it and judge the template by eye, which is how templates that look good but teach poorly get approved.

Continuity cost. The upkeep has to survive vacations, departures and reorganizations. If the knowledge lives with one designer, it leaves with them.

Strength in-house: nobody knows your brand, your people and your politics better. Your designers are also the right people to approve example slides and to own the system long term, whoever builds it.

The outside-partner cost

The visible cost is the fee. The costs that tend to be missed:

Onboarding cost. A partner needs to learn your brand, your decks and your people. Good partners minimize this by starting from an audit and real presentations, but your team’s time is still needed.

Approval cost. Your brand team should approve example slides and rules. That review time is real, and shouldn’t be skipped.

Dependency cost. If the partner owns all the knowledge, you depend on them for every change. A good engagement transfers enough understanding — and documentation — that your team could maintain the system.

Upkeep cost. If the partner also handles quarterly re-testing, that’s an ongoing fee. If they don’t, your team inherits it.

Strength outside: experience from having done this before, a tested method, and designer capacity that doesn’t compete with your production queue.

A comparison framework

Rather than comparing a salary estimate with a quote, compare total cost for the same scope:

Cost In-house Outside partner
Audit Designer time Partner fee (often fixed)
Rebuild and examples Designer time + opportunity cost Partner fee + your approval time
Learning Significant, first time Largely absorbed by the partner
Testing Designer time; risk of skipping Included, if the partner has a method
Brand Kit and rules Brand manager time Brand manager time + partner support
Upkeep Ongoing internal time Ongoing fee, or handed to your team
Risk of an untested launch Higher if testing is skipped Lower if testing is part of the scope

Fill in your own numbers. Include the opportunity cost honestly — it’s often the largest in-house line.

Hybrid options

The choice isn’t binary. Splits worth considering:

  • Partner audits, in-house rebuilds. You get an outside assessment against Microsoft’s guidance and a clear plan; your team does the work.
  • In-house rebuilds, partner designs examples and tests. Your team handles the mechanical rebuild; the partner handles the teaching material and the testing method.
  • Partner builds, in-house owns. The partner does the project with your designers alongside, then hands over upkeep with documentation.
  • In-house builds, partner provides oversight. Your team runs the system; the partner re-tests quarterly and reports.

How to decide

Three questions usually settle it:

  1. Does your design team have capacity without starving the decks that matter?
  2. Has anyone on your team done this before — including testing against real prompts?
  3. Who will own upkeep after launch, and do they have the time?

If the answers are yes, yes and “us,” in-house is likely the better value. If any answer is no, some outside help — even just an audit and a testing method — can be worth its cost by avoiding a template that looks right and teaches poorly.

Key takeaways

  • A Copilot template project covers audit, rebuild, examples, Brand Kit and settings, rules, testing and upkeep.
  • In-house costs include opportunity, learning, testing and continuity — not just designer time.
  • Partner costs include onboarding, approval, dependency and upkeep — not just the fee.
  • Compare total cost for the same scope, and consider hybrid splits.
  • Capacity, experience and ownership of upkeep usually decide it.

Want an outside assessment either way? Have your template scored.**

Related reading

Sources

For IT: the settings are the easy half

If you run Microsoft 365 for your organization, Copilot in PowerPoint has probably reached your desk as a configuration task. Licenses assigned. Policies reviewed. And now, a request from marketing — or a question from leadership — about making generated presentations “on brand.”

Here’s a straight answer for IT: the parts of this that are genuinely yours can be done quickly. The part that decides whether generated presentations are any good isn’t a setting at all. Understanding where that line sits will save you from owning a problem you can’t solve with configuration.

What IT owns

These are the tasks that sit naturally with Microsoft 365 administration.

Licensing. Copilot requires the appropriate licenses on top of a qualifying Microsoft 365 plan, and some Brand Kit capabilities list specific license requirements in Microsoft’s documentation. License names and bundles have changed several times, so confirm current requirements with your Microsoft account team.

Designating brand managers. Only designated brand managers can create and edit official Brand Kits. IT designates them under the organization’s brand manager policy. Microsoft notes it can take up to 24 hours for the permission to take effect after designation.

The asset library. Official Brand Kits can reference your SharePoint Organization Assets Library, so approved images don’t have to be uploaded twice. The library, its permissions and its structure are IT’s.

Change awareness. Microsoft announces changes to Copilot in PowerPoint through the Message Center. In September 2026 alone, it announced strict brand adherence and note instructions (MC1470415, 10 September) and Brand Skills (MC1473166, 16 September). IT sees these first. Passing them to the brand managers promptly is one of the most valuable things IT can do.

Governance scaffolding. Microsoft’s guidance for Brand Skills recommends governance review — security, privacy, accessibility, legal and brand — before publishing, testing before broad release, and periodic audits. IT is well placed to set up that process, even though brand should own the content.

What IT shouldn’t own

The brand manager role itself. Because IT grants the permission, it’s easy for an administrator to become the brand manager by default. Resist it. The brand manager decides which template is official, whether Copilot is locked to it, and which written rules Copilot follows across the organization. Those are brand decisions, and they carry brand accountability.

The template. Uploading a template to a Brand Kit takes a minute. Deciding whether that template is fit to teach Copilot is a design question.

The written rules. Brand Skills and note instructions encode presentation standards. They should be written by the people who own those standards and tested against real output.

Why the template is the hard half

It’s worth understanding why configuration alone doesn’t produce good decks, because you’ll likely be asked why the settings are “done” and the output is still generic.

Copilot in PowerPoint learns from the template’s content, not from its settings. Microsoft’s guidance says:

  • Copilot learns primarily from the template’s sample slides, and “falls back to the Slide Master” when there aren’t enough — “which may result in less optimal output.”
  • It uses placeholder type, position and size to decide what content goes where, and doesn’t treat placeholder text as instructions.
  • It draws colors and fonts from the theme, which must be defined properly rather than applied by hand.

None of these can be configured. They’re built, by designing a template: brand colors moved into the theme, layouts rebuilt with real placeholders, and a set of finished example slides at the light, medium and heavy densities Microsoft recommends. That’s design work, and it’s where most of the quality comes from.

Strict brand adherence makes this sharper. It restricts Copilot to the approved template and layouts, and end users can’t override it. That’s an excellent control over a good template. Over a weak one, it enforces consistency in the wrong direction: every generated deck inherits every gap.

A clean division of labor

Task IT Brand / creative
Licenses Owns Informs demand
Brand manager designation Grants Nominates people
Official Brand Kit contents Supports Owns
Template design and examples — Owns
Strict brand adherence, note instructions Advises Decides
Brand Skills Sets up governance review Writes, tests, publishes
Asset library Owns structure and permissions Curates content
Microsoft change notices Monitors, forwards Tests impact
Testing generated output — Owns

Questions IT can ask to protect itself

Before you configure anything on marketing’s behalf, it’s reasonable to ask:

  1. Who are the brand managers? Names, not a team.
  2. Is the template ready to be taught from? Has anyone checked it against Microsoft’s guidance — theme, placeholders, example slides?
  3. How will we know it’s working? Is there a test set of realistic prompts, and who reviews the output?
  4. Who responds to Microsoft changes? When the next Message Center post arrives, who tests its effect?

If those questions have answers, the configuration is straightforward. If they don’t, configuring anyway puts IT in the position of owning output quality it has no way to control.

Common questions

Can IT turn on strict brand adherence?
Only the Brand Kit owner or a brand manager can change Brand Kit template settings, according to Microsoft. IT designates brand managers; it shouldn’t make the brand decision itself.

Does IT need to give an outside partner admin access?
Usually not. The template work, example slides and rules can be done with your brand manager, who configures the kit under your own access rules.

Where do Microsoft’s change announcements appear?
In the Microsoft 365 Message Center. The two September 2026 changes that matter most here were MC1470415 (strict brand adherence and note instructions) and MC1473166 (Brand Skills).

Key takeaways

  • IT owns licensing, brand manager designation, the asset library, change awareness and governance scaffolding.
  • IT shouldn’t own the brand manager role, the template or the written rules.
  • Copilot’s quality comes from the template’s examples, placeholders and theme — built, not configured.
  • Strict brand adherence rewards a good template and multiplies a weak one’s gaps.
  • Ask who owns brand, template, testing and change response before configuring on marketing’s behalf.

Want the hard half done properly? Have your template scored.**

Related reading

Sources

Theme colors vs. hardcoded colors: the setting that decides your output

There is a way to build a PowerPoint template that looks perfect and teaches Copilot almost nothing about your brand. It is very common, and you can’t see it by looking at the slides.

It is hardcoded color. Every shape, line and text element has your brand colors applied directly, by hand — and the theme underneath still holds generic defaults. For a person using the template, it works: they reuse the elements that are already colored. For Copilot, which creates new charts, shapes and text that didn’t exist in the template, it fails. New objects inherit the theme. The theme doesn’t hold your brand.

This post explains the difference, why it matters more with Copilot than it ever did before, and how to fix it.

Diagram of two identical-looking templates: with brand colors in the theme a generated chart uses brand colors; with colors hardcoded it uses Office defaults

How PowerPoint themes work

Every PowerPoint file has a theme: a set of named color slots, a pair of theme fonts, and a set of effects. The color slots include two dark and two light colors for text and backgrounds, six accent colors, and colors for hyperlinks.

When you choose a color from the top section of the color picker — the theme colors — you are not choosing a specific color. You are choosing a slot. The object says “use Accent 2,” and whatever Accent 2 is defined as in the theme is what appears. Change the theme’s Accent 2, and every object pointing to it changes.

When you choose a color from More Colors or type a hex value, you are hardcoding. The object says “use this exact color,” permanently, regardless of the theme.

Theme fonts work the same way. Text set to “+Headings” or “+Body” follows the theme. Text set to a named font by hand does not.

Why Copilot depends on the theme

Microsoft’s guidance for Copilot templates is direct: define colors through Slide Master > Colors > Create New Theme Colors, define heading and body fonts in the theme, and apply consistent styles for charts, icons, shapes and image placeholders.

The reason is that much of what Copilot produces is new. It generates a chart from your data. It adds shapes for a process. It writes text into placeholders and sometimes adds elements. Every one of those new objects takes its colors and fonts from the theme, because the theme is the only definition of the brand those objects can see.

So consider two templates that look identical:

  • Template A has the brand palette in the theme. A chart Copilot generates uses the brand accents, in order. A new shape defaults to a brand color. Text defaults to the brand fonts.
  • Template B has the brand palette painted onto every existing element, with the Office default theme underneath. A chart Copilot generates comes out in default Office colors. New shapes appear in default blue. Headings may fall back to a default font.

Same appearance. Very different output. And nothing in either file’s slides tells you which one you have.

How to tell which you have

A quick diagnostic:

  1. Open View > Slide Master and select the top master slide.
  2. Click Colors in the Slide Master ribbon. The palette shown for the current theme should be your brand palette. If it’s “Office” or an unfamiliar set, the brand isn’t in the theme.
  3. Click Fonts. The heading and body fonts should be your brand fonts.
  4. Close Slide Master view. Insert a new chart on a blank slide. If it appears in your brand colors, the theme carries them. If it appears in default colors, it doesn’t.
  5. Select a colored shape on a layout and open the fill color picker. If the current color is highlighted in the theme colors row, it’s theme-linked. If it’s only in Recent Colors, it’s hardcoded.

How to fix it

Moving a template onto theme colors is methodical work. In order:

1. Decide the slot assignments

Map your brand palette onto the theme slots. The dark and light slots usually take your primary text and background colors. The six accents take your brand colors in the order you want charts to use them, because charts draw accents in sequence. Many brands have more colors than slots; choose the six that matter most for generated content and document the rest.

2. Create the theme colors and fonts

Use Slide Master > Colors > Customize Colors to create a named color set, and Fonts > Customize Fonts for heading and body fonts. Save them with clear names.

3. Re-point every element

This is the laborious step. Go through the master and every layout and change each hardcoded color to the matching theme slot. Do the same for fonts. A template with many layouts can hold hundreds of hardcoded values; a methodical pass, layout by layout, is the only reliable approach.

4. Set chart, table and shape defaults

Format a chart the way your brand presents data and check it draws from theme accents. Set default shape and text box styles. Microsoft recommends consistent styles for charts, icons, shapes and image placeholders; this is where they come from.

5. Check the example slides

Example slides are Copilot’s primary teaching material. If they use hardcoded colors, they teach hardcoded patterns. Re-point them too.

6. Test

Run a set of prompts that force Copilot to create new objects: a chart from data, a process diagram, a comparison table. Check that everything new appears in brand colors and fonts.

What about colors that don’t fit in six accents?

Many brand palettes have secondary colors, tints and special-use colors that don’t fit the theme’s slots. Options:

  • Use tints and shades of theme colors, which PowerPoint generates from each slot and which remain theme-linked.
  • Demonstrate secondary colors in example slides for the specific uses that need them, accepting that they are taught by example rather than by the theme.
  • Put the full palette in the Brand Kit, which can hold color palettes with specific hex values alongside the template.
  • Write a rule in a Brand Skill about when secondary colors are appropriate, and test whether it changes behavior.

The core brand colors — the ones that should appear everywhere — belong in the theme.

Key takeaways

  • Theme colors are slots; hardcoded colors are fixed values. Only the theme reaches objects Copilot creates.
  • A template can look perfectly branded while its theme holds defaults — and Copilot’s output reveals it.
  • Diagnose with the Slide Master Colors and Fonts menus and by inserting a new chart.
  • Fix by assigning brand colors to theme slots in chart order, re-pointing every element, and testing with prompts that create new objects.

Not sure what’s underneath your template? Have your template scored.**

Related reading

Sources

A bad template, multiplied by every Copilot user

Every organization has lived with an imperfect template. A layout that never quite fits. Colors that print badly. A title area too small for real titles. People grumble, work around it, and move on. The cost is real but diffuse — a few minutes here and there, absorbed by whoever is making the deck.

Copilot changes the arithmetic of template flaws. When a model learns from the template and generates decks for many people, a flaw is no longer absorbed by individual judgment. It’s reproduced. And the cost of a reproduced flaw is multiplied by everyone who generates a deck.

How a flaw becomes a multiplier

Consider three common template flaws and what happens to each when Copilot is involved.

Hardcoded brand colors. The template looks right because a designer painted every element. The theme underneath holds defaults. Before Copilot, people reused the painted elements and the problem was mostly invisible. With Copilot, every new chart and shape it creates takes its colors from the theme — so every generated chart can come out in default colors. Microsoft’s guidance is specifically to define brand colors and fonts in the theme for this reason.

No example slides. Before Copilot, a template without examples was merely less helpful. With Copilot, Microsoft states that without enough sample slides it “falls back to the Slide Master — which may result in less optimal output.” Every generated deck inherits that fallback.

A missing layout. Before Copilot, someone who needed a comparison layout that didn’t exist built one by hand. With Copilot — especially with strict brand adherence, which restricts it to approved layouts — comparisons get forced into whatever layout exists, in every deck that needs one.

In each case, a flaw that once cost a few minutes per affected deck now affects every deck Copilot generates for that kind of content.

Thinking about the multiplied cost

We won’t put a dollar figure on this, because it depends entirely on your organization, and we don’t publish numbers we haven’t measured. But the structure of the cost is simple enough to estimate with your own inputs:

Cost of a template flaw = extra fix-up time per affected deck × number of affected decks × loaded hourly cost

Two things make this larger with Copilot than without:

  • More affected decks. Generated decks are produced faster and by more people, so more of them pass through the flaw.
  • Fixes don’t stick. When a person fixes a generated slide by hand, the template isn’t changed. The next generated deck has the same problem. The fix-up cost recurs every time.

There’s also a cost that doesn’t appear in hours: decks that go out with the flaw unfixed. Most generated decks never pass through a brand team. A flaw that people don’t bother fixing reaches meetings, clients and partners.

Why the fix is cheap by comparison

Here’s the other side of the multiplier. If a flaw’s cost is multiplied across every generated deck, so is the benefit of fixing it.

Moving brand colors into the theme is done once. Every future generated chart benefits. Adding a well-designed comparison layout and example is done once. Every future comparison benefits. Writing a note instruction or Brand Skill rule for a recurring problem is done once. Every future deck is guided by it.

That’s the fundamental economics of a Copilot-ready template: the cost of fixing the system is paid once, and the benefit is collected on every deck. The same effort spent fixing individual generated decks is paid again and again, and collects nothing beyond the deck in front of you.

How to find your multiplied flaws

  1. Run a fixed set of realistic prompts against your current template — the kinds of decks your people actually make.
  2. Score the output for how much fixing it needs, from usable as generated to rebuild.
  3. Tag the reason for each fix: technical, brand, hierarchy, structure, density, visualization and so on.
  4. Look for repetition. Any fix that appears across many decks is a multiplied flaw — and a candidate for fixing once in the template.
  5. Fix the biggest one, rerun, compare.

A useful habit is to keep a short list of the top three multiplied flaws at any time, and work down it.

The leadership question

For a marketing or brand leader, the question isn’t “is our template perfect?” None is. It’s: “which of our template’s flaws are now being multiplied, and what would it take to fix them once?”

Usually the answer is a handful of structural problems — theme, placeholders, missing examples, missing layouts — that can be fixed in a focused piece of work. Left alone, they cost a little on every deck, indefinitely.

Common questions

How do we know which flaws are being multiplied?
Run a fixed set of realistic prompts, score the output and tag the reason for each fix. Any fix that recurs across many decks is a multiplied flaw.

Are some flaws worse than others?
Flaws that affect common deck types matter most, because they’re multiplied most. A flaw in a layout used once a month matters less than one in the everyday content layout.

Can Brand Skills fix template flaws?
Rules can reduce some problems, such as density or titles. They can’t fix a theme without brand colors, a missing layout or missing examples. Those need template work.

Key takeaways

  • Before Copilot, template flaws were absorbed by people’s judgment; with Copilot, they’re reproduced.
  • Hardcoded colors, missing examples and missing layouts become multipliers across every generated deck.
  • The cost of a flaw is extra fix-up per deck × affected decks × hourly cost — and hand fixes don’t stick.
  • Fixing the template is paid once and collected on every future deck.
  • Find repeated fixes in generated output; those are your multiplied flaws.

Want to find the flaws your template is multiplying? Have your template scored.**

Related reading

Sources