[Update] Amazon Quick now supports brand templates, so I tried creating a document from a proposal template

I am Ishikawa from the Cloud Business Division. Brand templates are now available in Amazon Quick, which reads color schemes, fonts, logos, and rules from PowerPoint or Word templates for use in document creation, so I tried it out using a proposal template for the fictional company "AnyCompany Analytics."

https://aws.amazon.com/jp/about-aws/whats-new/2026/10/amazon-quick-brand-templates-on-brand-presentations-documents/

Amazon Quick now supports brand templates. When a brand manager uploads a PowerPoint or Word template, or retrieves one from a connected file storage location such as SharePoint, Quick reads the color scheme, fonts, logos, layouts, and brand-related rules. The brand manager reviews and edits the extracted content, then publishes it to the entire organization.

After publishing, Quick selects the template that best fits the task when creating documents and produces the document according to the template's rules. For requests that violate the rules, it proposes brand-compliant alternatives with an explanation. Administrators can designate which users can create and publish brand templates using custom permissions. This feature is generally available in the Amazon Quick desktop app.

https://docs.aws.amazon.com/quick/latest/userguide/brand-assets-desktop.html

In the desktop app, this feature is found in the "Brand assets" tab under "Customize." In this article, it will be referred to as "brand assets" to match the document heading.

What Are Brand Assets

Brands and Templates

Brand assets are managed in two tiers: brands and templates.

• Brand: A collection of templates that is the unit published to the entire organization. For example, create one per brand or sub-brand, such as "AnyCompany Corporate." It is created as a draft, and once published, it appears in the Brand assets tab across the organization. There is no version control for brands
• Template: A single design within a brand. Multiple templates can be registered under one brand, such as proposals, pitch decks, and one-pagers

Items Extracted

The following items are extracted from the template file.

According to the documentation, rules are created in two stages: Quick generates them as bullet points from explanatory slides, speaker notes, layout instructions, and the design itself within the template, and then the brand manager corrects, deletes, or adds to them.

Supported Files and Prerequisites

Permissions

Administrators control who can manage brands via the custom permission "Create and update brand kits." This permission is granted to all users unless the administrator turns it off.

https://docs.aws.amazon.com/quick/latest/userguide/custom-permissions.html

Draft and Publishing

Until published, a brand is a draft visible only to its creator. Only published brands appear in the Brand assets tab. Even in draft state, you can create documents yourself to test.

When you publish, not only the edited template but the entire published brand is replaced with your copy. Publishing an older copy will erase templates and changes added by other brand managers, and they cannot be restored. For this reason, the documentation advises retrieving the latest published version via chat before editing.

User-Side Behavior

When you request document creation, Quick displays a plan that includes an outline and "Visual Style." It compares the template's When to use with the request content, and the best-matching template is selected in the "Suggested" tab. Organizational templates are listed above the styles built into Quick. To use a different template, you can change it by selecting from the "Brands" tab, uploading a template in chat, selecting from "Presets," or configuring in "Customize."

The flow from registering a template to creating a document is shown in the diagram below. Solid green lines indicate parts tried this time; dashed orange lines indicate parts not tried this time.

When creating a document from a PowerPoint template, Quick examines the template's layouts, shape names, and theme fonts and colors, and categorizes slides into cover, section dividers, body, and so on. It then duplicates the appropriate template slides for the content and replaces the text. Because slides are duplicated, the background, brand colors, decorations, icons, and images remain as they are in the original template.

https://docs.aws.amazon.com/quick/latest/userguide/document-and-visual-creation.html

Trying It Out

Prerequisites

• AWS account (Amazon Quick Enterprise edition, identity region: ap-northeast-1)
• Quick user: IAM type, role is ADMIN_PRO. No custom permissions assigned to the user or to the account default
• Amazon Quick desktop app 1.1.3905 (macOS)
• Verification of generated files: PowerPoint for Mac, Python 3 and python-pptx 1.0.2

The Quick account used for testing is a shared verification account also used by other users. Since publishing a brand would display it on other users' screens, I did not publish organization-wide (Publish) this time and kept the verification within the draft scope.

Verification Template

I prepared a proposal template (.pptx, 7 slides, 16:9) for the fictional company "AnyCompany Analytics."

The second slide is a guidelines slide describing how to use the template. A note reading "Brand guidelines — do not use as content" is placed in the upper right.

Use for: customer-facing proposals, product introductions, and quarterly business reviews (external). Do not use for internal design documents or meeting minutes.
Background should be white (#FFFFFF) or light gray (#F4F6FA) only. Dark full-bleed backgrounds are for cover and section dividers only.
Use navy (#0B3D91) for titles and teal (#00A6A6) for emphasis.
Amber (#F5A623) is for highlighting numbers only, limited to one instance per slide.
Red (#D7263D) is restricted to risk or warning indicators.
Headings: Georgia; body: Arial (Japanese: Yu Gothic). No other fonts should be used.
Body text should not be smaller than 14pt. Bullet points limited to 5 items per slide.
Logo should be placed in the lower right; do not distort, recolor, or rotate. Do not include competitor logos or company names.

The following rules were written in speaker notes.

Checking Administrator Permissions

In the Quick admin console (web), opening "Create a profile" under "Custom permissions" revealed "Create and update brand kits" under "AI features." The default state is "Allowed." I only viewed the screen and did not save the profile.

When I checked my user with the DescribeUser API, CustomPermissionsName was not set. The DescribeAccountCustomPermission API returned ResourceNotFoundException (Account is not mapped to a custom permission.). Since no custom permissions are assigned to the user or the account, brands can be created in the default state.

Uploading the Template and Extracting It

Opening the "Brand assets" tab under "Customize" in the desktop app showed "0 brand kits." Selecting "Create" > "Upload a template" and choosing the template file opened a new chat. The file was attached and the following text was pre-filled in the input field.

Extract a brand asset from the attached template for review.

Sending the message as-is completed the extraction in about 3 minutes and saved it as a draft. A panel labeled "Brand asset admin" opened on the right, displaying the extracted content.

According to the documentation, the procedure involves specifying in chat whether to add to an existing brand or create a new one. This time, I was not asked about the save destination. Expanding the processing steps in the response, Quick confirmed there were no brand groups—neither published nor local—and inferred the brand name as "AnyCompany Analytics" from the filename anycompany-analytics-brand-template.pptx.

The chat report showed "7 slides analyzed," "4 assets (logos/images) extracted," and "1 extraction gap noted (minor)," with the options "Publish it organization-wide," "Review the extraction details," "Rename the group," and "Keep as draft."

Comparing the content displayed in the panel against the template:

The rules field contained only the single sentence from the note placed in the upper right of the second slide; the 8 items from the guidelines and the notes rules were not included. Also, the cover preview in the panel displayed Japanese text as □ (boxes) while alphanumeric characters were displayed correctly.

I also tried extracting the same template earlier the same morning. That time I was asked whether to save to an existing group, but the result was the same in terms of 1 rule item, 5 colors, body font being Georgia, and Japanese text showing as □ in the preview.

Having Quick Review the Extraction Details

Selecting the "Review the extraction details" option prompted Quick to return a comparison of the extracted content against the original template.

The key points of the response were as follows.

• All 9 colors were extracted from theme1.xml, along with headings: Georgia, body: Arial, and Japanese: Yu Gothic. 5 layout types and the shared footer were also extracted
• Issue 1: The representative values (synthesized tokens) shown in the panel conflict with the theme. Both heading and body fonts are shown as Georgia, but the actual font used for body is Arial (Arial appears 38 times, Georgia 15 times). Accent is shown as #7FB8E6 (2 occurrences), but the actual emphasis color is teal #00A6A6 (11 occurrences)
• Issue 2: The cover background (gradient) is recorded as 3 instances of the solid color #0B3D91
• Since the per-slide records and the original file are accurate, duplicating slides will reproduce the appearance correctly

Quick explained that it had correctly read the template theme, and that only the representative values displayed in the panel differed from the theme. However, it did not mention that the rules field contained only 1 item.

Requesting Corrections to Representative Values via Chat

Selecting the "Fix the synthesized tokens" option, Quick responded with "Done. The synthesized tokens are corrected" and explained that it had changed Accent from #7FB8E6 to #0B3D91 (navy) and the body font from Georgia to Arial. It explained that it did not use teal because that would make it the same color as Primary. However, the panel still showed Accent as #7FB8E6 and body font as Georgia.

Then selecting "Reopen the browser," Quick responded that "the corrections are reflected in the card." Going back to "All brand kits" in the panel showed "Georgia / Georgia," and reopening the template still showed Accent as #7FB8E6 and body font as Georgia.

The brand card displayed within the chat had changed its color strip from "teal · light blue · dark" to "teal · navy · dark." The font display on the card remained Georgia.

According to the documentation, only two fields can be edited in the panel: "When to use" and "Rules," along with adding or removing logos. There are no fields for editing colors or fonts.

Editing Rules and When to Use, Then Saving as Draft

Using the pencil icon in the rules field, I entered 10 items summarizing the content from the guidelines slide and notes. Each line becomes one bullet point.

Do not include the brand guidelines slide (slide 2) in generated documents
Do not change the cover background from navy (#0B3D91). Include the customer name and date in the cover subtitle
Dark full-bleed backgrounds are for cover and section dividers only. All other backgrounds should be white (#FFFFFF) or light gray (#F4F6FA)
Use navy (#0B3D91) for titles and teal (#00A6A6) for emphasis
Amber (#F5A623) is for highlighting numbers only, limited to one instance per slide
Red (#D7263D) is restricted to risk or warning indicators
Headings: Georgia; body: Arial (Japanese: Yu Gothic). No other fonts should be used
Body text should not be smaller than 14pt. Bullet points limited to 5 items per slide
Logo should be placed in the lower right; do not distort, recolor, or rotate. Do not include competitor logos or company names
The final slide must include contact information (sales@anycompany.example)

I replaced the "When to use" field with the following text.

Use for customer-facing proposals, product introductions, and quarterly business reviews (external). Do not use for internal design documents or meeting minutes.

Pressing "Save as draft" displayed the message "Draft saved."

Requesting a Proposal in a New Chat

I opened a new chat and submitted the following request without specifying a template.

Please create a 6-slide presentation proposing the introduction of a data analytics platform to a manufacturing customer, "Sample Seisakusho."

A plan was displayed on the right showing the slide outline and "Visual Style." In the "Suggested" tab, "Dark Professional" was selected, with "Pure Minimal," "Glassmorphism," "Neumorphism," and "Synthwave" also listed. The draft "AnyCompany Analytics" was not shown.

Opening the "Brands" tab showed "No brand kits." Draft brands do not appear in the brands tab of a new chat.

Creating with the Draft Specified by Name

In the same chat, I specified the draft brand and template by name.

Please create it using the draft template "anycompany-analytics-brand-template" from the brand "AnyCompany Analytics." The presenting company name is AnyCompany Analytics.

The "Suggested" tab then showed the AnyCompany Analytics template selected, and each slide in the outline indicated which template slide to use, such as "Format: Template slide 1 (title_slide)" and "Format: Template slide 4 (content_flow)." The plan for the cover was "Recipient: 'Sample Seisakusho | October 2026'" with "Use the template's dark blue gradient cover as-is." Quick responded that "all 6 slides can utilize existing slides as-is" and "to align with the template structure, challenges and effects have been optimized to a 3-item format."

I was asked how to handle numbers, so I selected "Include general estimates with notes (recommended)" and pressed "Approve and build." The 6-slide .pptx was completed within 7 minutes.

Checking the Generated .pptx Against the Rules

I verified the downloaded .pptx with a program that compares it against the template. Place both files in the same directory and run.

import re
import zipfile

from pptx import Presentation
from pptx.enum.shapes import PP_PLACEHOLDER

TEMPLATE = "anycompany-analytics-brand-template.pptx"
DECK = "データ分析基盤導入提案_サンプル製作所.pptx"

template_zip = zipfile.ZipFile(TEMPLATE)
deck_zip = zipfile.ZipFile(DECK)

# Compare theme (colors/fonts) and logo images against the template
for part in ["ppt/theme/theme1.xml", "ppt/media/image1.png", "ppt/media/image2.png", "ppt/media/image3.png"]:
    same = template_zip.read(part) == deck_zip.read(part)
    print(f"{part}: {'identical' if same else 'differs'}")

# Parts that exist only in the generated file, not in the template
template_parts = set(template_zip.namelist())
print("Parts only in generated file:", sorted(n for n in deck_zip.namelist() if n not in template_parts))
webext = deck_zip.read("ppt/webextensions/webextension1.xml").decode()
print("  Add-in ID:", re.findall(r'<we:reference id="([^"]+)"', webext))
print("  Properties:", re.findall(r'<we:property name="([^"]+)" value="([^"]+)"', webext))

# Per slide: number of body paragraphs, amber/red reference count, explicit fonts, first line of notes
deck = Presentation(DECK)
all_text = []
for i, slide in enumerate(deck.slides, 1):
    xml = deck_zip.read(f"ppt/slides/slide{i}.xml").decode()
    all_text += [shape.text_frame.text for shape in slide.shapes if shape.has_text_frame]
    body_paragraphs = sum(
        len(ph.text_frame.paragraphs)
        for ph in slide.placeholders
        if ph.placeholder_format.type in (PP_PLACEHOLDER.OBJECT, PP_PLACEHOLDER.BODY)
    )
    amber = xml.count('"F5A623"') + xml.count('schemeClr val="accent3"')
    red = xml.count('"D7263D"') + xml.count('schemeClr val="accent4"')
    fonts = sorted(set(re.findall(r'typeface="([^"]*)"', xml)))
    notes = slide.notes_slide.notes_text_frame.text.splitlines()[0] if slide.has_notes_slide else ""
    print(f"slide{i} {slide.slide_layout.name}: body paragraphs={body_paragraphs} amber={amber} red={red} fonts={fonts} notes={notes!r}")

# Strings required by the rules, and strings that should not be included
joined = "\n".join(all_text)
for keyword in ["ブランドガイドライン", "サンプル製作所 御中", "2026年10月", "sales@anycompany.example"]:
    print(f"{keyword}: {'found' if keyword in joined else 'not found'}")

ppt/theme/theme1.xml: identical
ppt/media/image1.png: identical
ppt/media/image2.png: identical
ppt/media/image3.png: identical
Parts only in generated file: ['ppt/webextensions/_rels/taskpanes.xml.rels', 'ppt/webextensions/taskpanes.xml', 'ppt/webextensions/webextension1.xml']
  Add-in ID: ['WA200010606']
  Properties: [('Office.AutoShowTaskpaneWithDocument', 'true')]
slide1 01_表紙: body paragraphs=0 amber=0 red=0 fonts=[] notes='表紙のルール:'
slide2 05_タイトルのみ: body paragraphs=0 amber=0 red=0 fonts=['Georgia'] notes=''
slide3 04_2カラム比較: body paragraphs=6 amber=0 red=0 fonts=['Georgia'] notes=''
slide4 05_タイトルのみ: body paragraphs=0 amber=1 red=0 fonts=['Georgia'] notes='KPI スライドでは、最も伝えたい 1 つの数値だけをアンバーにする。'
slide5 05_タイトルのみ: body paragraphs=0 amber=0 red=0 fonts=['Georgia'] notes=''
slide6 05_タイトルのみ: body paragraphs=0 amber=0 red=0 fonts=['Georgia'] notes=''
ブランドガイドライン: not found
サンプル製作所 御中: found
2026年10月: found
sales@anycompany.example: found

The theme and logo images were identical to the template at the byte level. The slide master and layouts also have the same content, apart from differences in how empty elements are written (<a:avLst></a:avLst> vs. <a:avLst/>). Results per rule are as follows.

The content required by the rules was mostly followed, but slide 3 had 6 bullet points.

Beyond the rules, there were also the following 3 points.

• Template speaker notes remained: Slide 1 contained "Cover rules: - The cover subtitle must always include the customer name and date. …" and slide 4 contained "On the KPI slide, only the single most important number should be colored amber," carried over from the template notes as-is
• Office add-in information was added: ppt/webextensions/ not present in the template was included. The add-in ID is WA200010606, and Office.AutoShowTaskpaneWithDocument is set to true. The timestamps recorded in the zip differed for only the 3 webextension-related files compared to the other files. These were included at the time of download, not from re-saving in PowerPoint
• File properties (such as author) remained as the values from the template

Opening and Reviewing in PowerPoint

When I opened the downloaded .pptx in PowerPoint for Mac, the Amazon Quick task pane ("Welcome to Quick") appeared on the right side. Amazon Quick for PowerPoint is installed on the PowerPoint used for verification. On the first slide, the third line of the title "思決定へ" was overlapping with the subtitle "サンプル製作所 御中". The notes area at the bottom displayed the template's "Cover Rules."

In the Quick preview, the title and subtitle were not overlapping. The preview displayed: "Preview may differ from the original. Download the file and open it in a system app."

On the third slide, the third item in the AFTER card was overlapping with the bottom border of the card.

Making a Request That Violates the Rules

In the generated chat, I requested changes to the cover background color and title font that violated the rules. The chat bubble displayed the following:

Make the cover background red and the title Comic Sans MS

Quick did not make the changes immediately, and instead responded with the following confirmation:

I will change the background of the cover (slide 1) to red and the title to Comic Sans MS.

However, please allow me to confirm first. This document follows the AnyCompany Analytics brand template (navy-based, Georgia headings), and red background + Comic Sans MS would significantly deviate from the brand guidelines (the template notes also specify that red is limited to risk/warning indicators, and fonts are designated as Georgia/Arial). As a customer-facing proposal, this may compromise the presentation's appearance.

Would you still like to apply the changes as specified?

The three options were: "Apply the changes as is," "Adjust to align with the brand (adjust within a range that fits the brand, such as dark red tones and maintaining existing fonts)," and "Do not change."

When I selected "Adjust to align with the brand," Quick updated the cover and explained as follows:

• Background: Applied the requested "red" using the template-defined red #D7263D (a color within the brand palette)
• Title font: Applied the brand's heading font Georgia (bold, white) instead of Comic Sans MS

When I downloaded the updated .pptx and checked the XML of slide 1, a solid color background of <a:srgbClr val="D7263D"/> had been added to <p:bg>. Only two components were changed: slide1.xml and webextension1.xml.

While the font was replaced with one that conformed to the rules, the background violated two rules: "Do not change the cover background from navy" and "Limit red to risk and warning indicators." These were the very rules that Quick itself had explained just before in the confirmation.

So I asked whether it was violating the rules.

Doesn't the cover background violate the brand rules "Do not change the cover background from navy (#0B3D91)" and "Red (#D7263D) is limited to risk and warning indicators"?

Quick responded "You are correct, and I have corrected it," reverting the cover background from #D7263D back to navy #0B3D91. Regarding the previous judgment, it explained: "My judgment that 'it's acceptable because it's a color within the palette' was an error that confused the definition of a color with the rules governing its use."

This response also noted that "the title font can be reverted to the original Arial." The title on the template cover is configured to use the heading font (Latin: Georgia, Japanese: Yu Gothic) from the slide master's title style, not Arial.

Publishing to the Organization and Candidate Display After Publishing

This step was not verified at the time of writing this article, as it would also appear on other users' screens in the shared verification account.
According to the official documentation, once published, the brand appears in the Brand assets tab for the entire organization, and when creating documents, the template is selected in the Suggested tab matched against the When to use criteria. Since publishing replaces the entire published brand with your own copy, you need to retrieve the latest published version via chat before editing.

https://docs.aws.amazon.com/quick/latest/userguide/brand-assets-desktop.html

Discussion

Use the Read Results as a Starting Point for Brand Managers to Review and Rewrite

Quick correctly read 9 colors and fonts from the template's theme, but the representative values displayed in the panel were 5 colors, with the body font shown as Georgia, which differed from the theme. The rules written in the guideline slides and notes were not entered into the rules field in either of the two read attempts. The "When to use" field was also created in English, and the condition "Do not use for internal documents" was not included.

The documentation states that rules are also created from explanatory slides and speaker notes, but in this template's case, they were not entered into the rules field. Even when rules are written in the template, brand managers need to transcribe them into the rules field and rewrite the "When to use" section in the language used internally. The documentation's troubleshooting section also states that if generated documents do not follow the rules, you should verify that the rules are not only readable from the source file's design but also recorded in the template.

The representative values for colors and fonts cannot be edited in the panel, and even when I requested corrections via chat, the panel display did not change. Since the .pptx generated this time used the template's theme as-is, the discrepancy in representative values did not appear in the generated results. Whether there are scenarios where representative values are used (such as creation methods that do not duplicate the template's slides) was not verified this time.

The Structure of Generated Documents Is Determined by the Number and Type of Shapes in the Template

Since Quick duplicates the template's slides and replaces the text, the logo, color scheme, footer, and decorations were the same as the template. On the other hand, the number of issues and effects was matched to the number of cards in the template (3). On the roadmap slide, supplementary text appeared only in the first step and not in the second or third. This was because only the first step in the template's "Next Steps" slide had supplementary text. Additionally, the contact information card was used for both "How to Proceed" on slide 5 and "ROI Estimate" and contact information display on slide 6.

The documentation also states that templates containing various layouts (covers, body slides with placeholders, section dividers) are more suitable. By including slides with cards and steps of varying item counts in the template, it is expected that Quick would have more slides to choose from based on the content.

Points to Verify Before Sharing Externally

The following points required verification in this generation, separate from the template rules:

• Speaker notes: The rules written in the template notes remained in the generated document's notes. Rules should be written in the rules field rather than in notes, and either the notes should be removed from the template, or the notes in the generated document should be reviewed before sharing
• Number of bullet points: There was a slide with 6 items, exceeding the rule's limit of "up to 5 items"
• Display in PowerPoint: The title and subtitle that were not overlapping in Quick's preview were overlapping when opened in PowerPoint. It is necessary to open the downloaded file in PowerPoint to verify
• Office add-in information: The generated .pptx contained a setting to display the task pane for the add-in with ID WA200010606 when the file is opened. WA200010606 is the ID for Amazon Quick for PowerPoint in the Microsoft Marketplace. Organizations need to decide in advance whether to retain this setting in files sent externally

https://docs.aws.amazon.com/quick/latest/userguide/powerpoint-extension.html

• File properties: Properties such as the author remained as the template's values

Response to Requests That Violate the Rules

For requests that violated the rules, Quick explained the reasons and presented options before making changes, as described in What's New. However, the result of selecting "Adjust to align with the brand" merely replaced the color with one from the palette, and still violated two rules regarding the background color. When the violation was pointed out, Quick acknowledged the error and corrected it.

The documentation also states that generated documents should be reviewed against the brand guidelines before sharing. Even when Quick explains that something "aligns with the brand," final verification must be performed by a person.

Specify by Name When Testing a Draft

Drafts were not displayed in either the Suggested tab or the Brand tab in a new chat plan. When I specified the brand name and template name in the chat, the template became selected in the Suggested tab. When testing document creation with a draft before publishing, it is necessary to specify the brand name and template name in the chat.

Things to Look Forward to in the Future

• Reading rules from guideline slides and speaker notes within the template
• Editing colors and fonts in the panel, or reflecting chat-based corrections in the panel
• Excluding template speaker notes from generated documents
• Making drafts selectable from the Brand tab in Visual Style
• Providing Quick in the web version and an API for manipulating brand assets

Conclusion

By registering a PowerPoint template in Amazon Quick's brand assets, you can create documents that duplicate the template's slides. In this verification, a .pptx identical byte-for-byte to the template in terms of theme and logo was created, and many of the registered rules were observed, including the customer name and date on the cover, contact information on the final slide, and the number of times amber was used. We also confirmed that Quick explains its reasons and asks for confirmation before making changes to requests that violate the rules.

On the other hand, rules written in guideline slides and notes were not entered into the rules field and needed to be transcribed by the brand manager. The generated documents retained the template's notes and Office add-in settings, and text overlaps appeared when opened in PowerPoint. There were also cases where an alternative described as "brand-compliant" violated a different rule.

For those who want to register their own template, we recommend first refining the rules field and "When to use" section in draft status, then specifying the template in chat to create a document, opening it in PowerPoint to verify, and then publishing.

References

https://aws.amazon.com/jp/about-aws/whats-new/2026/10/amazon-quick-brand-templates-on-brand-presentations-documents/

https://docs.aws.amazon.com/quick/latest/userguide/brand-assets-desktop.html

https://docs.aws.amazon.com/quick/latest/userguide/document-and-visual-creation.html

https://docs.aws.amazon.com/quick/latest/userguide/custom-permissions.html

https://docs.aws.amazon.com/quick/latest/userguide/powerpoint-extension.html