![[Update] Amazon Quick now supports brand templates, so I tried creating materials from a proposal template](https://devio2024-media.developers.io/image/upload/f_auto,q_auto,w_3840/f_auto,q_auto/v1790875080/eyecatch/fu4oqvi9h5yej1imliyf.png)
[Update] Amazon Quick now supports brand templates, so I tried creating materials from a proposal template
This page has been translated by machine translation. View original
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 and Word templates for use in document creation, so I tried it out using a proposal template for the fictional company "AnyCompany Analytics."
Amazon Quick now supports brand templates. When a brand manager uploads a PowerPoint or Word template or retrieves it from a connected file storage service such as SharePoint, Quick reads the color scheme, fonts, logos, layout, 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 creates the document according to the template's rules. For requests that violate the rules, it explains why and proposes brand-compliant alternatives. Administrators can use custom permissions to specify which users can create and publish brand templates. This feature is generally available in the Amazon Quick desktop app.
In the desktop app, this feature is located in the "Brand assets" tab under "Customize." In this article, we will refer to it as "brand assets" to match the document heading.
What Are Brand Assets
Brands and Templates
Brand assets are managed in a two-tier hierarchy of brands and templates.
- Brand: A collection of templates that is the unit published to the entire organization. For example, create one for each of your company's brands or sub-brands, such as "AnyCompany Corporate." It is created as a draft, and once published, it appears in the Brand assets tab for the entire organization. There is no version control for brands
- Template: A single design within a brand. You can register multiple templates within a single brand, such as proposals, pitch decks, and one-pagers
Items That Are Read
The following items are read from the template file.
| Item | Content |
|---|---|
| Colors | Color scheme and hex values for each color |
| Text styles | Named styles with font, size, weight, and color |
| Logos | Logo images in the file |
| Structure and outline | For documents: section structure, heading hierarchy, style groups |
| Page dimensions | For documents: page size, margins, orientation, number of columns |
| When to use | The purpose for which this template should be used. Used when Quick selects a template that fits the task. Created by Quick and editable by the brand manager |
| Rules | Rules for creating documents with this template. Created by Quick and editable by the brand manager |
According to the documentation, the 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 revises, deletes, or adds to them.
Supported Files and Prerequisites
| Item | Content |
|---|---|
| Supported files | .pptx / .potx (presentation templates), .docx / .dotx (document templates). Maximum 50 MB |
| Edition | Amazon Quick Enterprise edition only |
| Sign-in | Must be signed in with organizational credentials |
| Document creation permissions | Must be able to create Word documents and PowerPoint files in Quick |
| Retrieval from connector | Must be connected to the source service. Retrieval is a one-time import and will not sync if the source file changes |
Permissions
Administrators control who can manage brands using the "Create and update brand kits" custom permission. This permission is allowed for all users unless the administrator turns it off.
| Permission | What You Can Do |
|---|---|
| Allowed (brand manager) | Read, edit, publish, update, and delete brands |
| Not allowed | View, download, and apply published brands to documents |
Drafts 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 just the edited template but the entire published brand is replaced with your copy. Publishing with an old copy will delete 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.
How It Works for Users
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 appears selected in the "Suggested" tab. Organization templates are ranked higher than Quick's built-in styles. 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 illustrated below. Green solid lines indicate parts tested this time, and orange dashed lines indicate parts not tested this time.
When creating a document from a PowerPoint template, Quick examines the template's layouts, shape names, and theme fonts and colors, and classifies slides into cover, section dividers, body content, and so on. It then duplicates the template slides that match the content and replaces the text. Because slides are duplicated, the background, brand colors, decorations, icons, and images from the original template are preserved.
Trying It Out
Prerequisites
- AWS account (Amazon Quick Enterprise edition, ID region: ap-northeast-1)
- Quick user: IAM type, role is ADMIN_PRO. No custom permissions assigned to either the user or the account default
- Amazon Quick desktop app 1.1.3905 (macOS)
- Checking generated files: PowerPoint for Mac, Python 3 and python-pptx 1.0.2
The Quick account used for verification is a shared verification account also used by other users. Since publishing a brand would display it on other users' screens as well, we did not publish organization-wide (Publish) this time and conducted verification within the scope of drafts.
Template for Verification
We prepared a proposal template (.pptx, 7 slides, 16:9) for the fictional company "AnyCompany Analytics."

| Item | Content |
|---|---|
| Theme colors (9 colors) | dk1 #1A1A2E (body), lt1 #FFFFFF (white), dk2・accent1 #0B3D91 (navy), lt2 #F4F6FA (light gray), accent2 #00A6A6 (teal), accent3 #F5A623 (amber), accent4 #D7263D (red), accent5 #6B7280 (gray), accent6 #7FB8E6 (light blue) |
| Theme fonts | Headings: Georgia, Body: Arial, Japanese: Yu Gothic |
| Layouts (5 types) | 01_Cover / 02_Section Divider / 03_Title and Content / 04_2-Column Comparison / 05_Title Only |
| Images | 2 logo variants (standard and white knockout), icon in upper right of KPI slide |
The second slide is a guidelines slide explaining how to use the template. It includes a note in the upper right that reads "Brand guidelines — do not use as content."
Purpose: Use for customer-facing proposals, product introductions, and quarterly business reviews (external-facing). Do not use for internal design documents or meeting minutes.
Background must be white (#FFFFFF) or light gray (#F4F6FA) only. Dark full-bleed backgrounds are only for the cover and section dividers.
Use navy (#0B3D91) for titles and teal (#00A6A6) for emphasis.
Amber (#F5A623) is for highlighting numbers only; limit to one instance per slide.
Red (#D7263D) is reserved for risk and warning indicators only.
Headings use Georgia, body text uses Arial (Japanese uses Yu Gothic). Do not use any other fonts.
Body text must not be smaller than 14pt. Bullet points limited to 5 items per slide.
Place logo in the lower right; do not distort, recolor, or rotate it. Do not include competitor logos or company names.
The speaker notes contained the following rules:
| Slide | Rule written in notes |
|---|---|
| Slide 1 (Cover) | Always include the customer name and date in the cover subtitle. Do not change the cover background from navy (#0B3D91) |
| Slide 2 (Guidelines) | Do not include this slide in generated documents. Always include contact information (sales@anycompany.example) on the final slide |
| Slide 6 (KPI) | On the KPI slide, make only the single most important number amber |
Checking Admin Permissions
In the Quick admin console (web), when I opened "Custom permissions" and "Create a profile," I found "Create and update brand kits" under "AI features." The initial state is "Allowed." I only checked the screen and did not save the profile.

When I checked my own 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 were assigned to either the user or the account, brands can be created as per the initial state.
Uploading the Template and Having It Read
When I opened the "Brand assets" tab under "Customize" in the desktop app, it showed "0 brand kits." I selected "Create" → "Upload a template" and chose the template file, which 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 with this text as-is completed the reading in about 3 minutes and saved it as a draft. A panel called "Brand asset admin" opened on the right, displaying the extracted content.

The documentation describes a step where you specify 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 response processing steps showed that Quick confirmed there were no brand groups in either published or local state, 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 following options displayed: "Publish it organization-wide," "Review the extraction details," "Rename the group," and "Keep as draft."
Comparing the content displayed in the panel with the template:
| Item | Template content | Panel display |
|---|---|---|
| When to use | External-facing proposals, product introductions, and quarterly business reviews. Not for internal design documents or meeting minutes | "Use this template for corporate analytical proposals, business reviews, and client-facing presentations requiring data insights and step-by-step solution planning." (preceded by **). No mention of when not to use |
| Rules | 8 items on the guidelines slide, 5 items in notes | Only 1 item: "Brand guidelines — do not use as content" |
| Colors | 9 colors | 5 colors: Primary #00A6A6 / Accent #7FB8E6 / Dark #1A1A2E / Light #FFFFFF / Neutral #6B7280. Navy #0B3D91, light gray #F4F6FA, amber #F5A623, and red #D7263D are not displayed |
| Fonts | Headings: Georgia, Body: Arial, Japanese: Yu Gothic | Title: Georgia, Body: Georgia. Japanese font not displayed |
| Logos | 2 variants | 2 items (matches) |
| Slide layouts | 5 types | Thumbnails with layout names (01_Cover, 03_Title…, 02_Section…, 05_Title…) |
The rules field contained only the single note from the upper right of slide 2, and the 8 items from the guidelines and the rules from the notes were not included. Also, in the panel's cover preview, Japanese text was displayed as □ (English and numbers were displayed correctly).
I also tried reading the same template earlier on the same morning. At that time, I was asked whether to save to an existing group, but the results were the same: 1 rule item, 5 colors, body font as Georgia, and Japanese text in the preview displayed as □.
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:
- It was able to read all 9 colors from theme1.xml, as well as headings in Georgia, body in Arial, and Japanese in Yu Gothic. It also read 5 layout types and the shared footer
- Issue 1: The representative values (synthesized tokens) displayed in the panel conflict with the theme. Both heading and body fonts show as Georgia, but the font used for body text is Arial (Arial appears 38 times, Georgia 15 times). Accent is #7FB8E6 (2 occurrences), but the actual emphasis color is teal #00A6A6 (11 occurrences)
- Issue 2: The cover background (gradient) is recorded as 3 points of solid #0B3D91
- The per-slide records and the original file are accurate, so duplicating slides will reproduce the appearance correctly
Quick explained on its own 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 the Representative Values via Chat
Selecting the "Fix the synthesized tokens" option prompted Quick to respond with "Done. The synthesized tokens are corrected," explaining that it had changed Accent from #7FB8E6 to #0B3D91 (navy) and the body font from Georgia to Arial. It explained that the reason it did not use teal was that it would be the same color as Primary. However, the panel on the right still showed Accent #7FB8E6 and body font Georgia.

When I then selected "Reopen the browser," Quick responded that "the corrections are reflected in the card." Looking back at the "All brand kits" list in the panel, it showed "Georgia / Georgia," and even after reopening the template, Accent remained #7FB8E6 and body font remained Georgia.

The brand card displayed in 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, the only fields editable in the panel are "When to use," "Rules," and adding/removing logos. There are no fields for editing colors or fonts.
Editing the 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 item.
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 only for the cover and section dividers. All other backgrounds must be white (#FFFFFF) or light gray (#F4F6FA)
Use navy (#0B3D91) for titles and teal (#00A6A6) for emphasis
Amber (#F5A623) is for highlighting numbers only; limit to one instance per slide
Red (#D7263D) is reserved for risk and warning indicators only
Headings use Georgia, body text uses Arial (Japanese uses Yu Gothic). Do not use any other fonts
Body text must not be smaller than 14pt. Bullet points limited to 5 items per slide
Place logo in the lower right; do not distort, recolor, or rotate it. Do not include competitor logos or company names
Include contact information (sales@anycompany.example) on the final slide
I replaced "When to use" with the following text:
Use for customer-facing proposals, product introductions, and quarterly business reviews (external-facing). Do not use for internal design documents or meeting minutes.
Clicking "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 for our manufacturing customer "Sample Seisakusho."
A plan appeared on the right side showing the slide outline and "Visual Style." In the "Suggested" tab, "Dark Professional" was selected, with "Pure Minimal," "Glassmorphism," "Neumorphism," and "Synthwave" listed as alternatives. The draft AnyCompany Analytics was not displayed.

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 using the draft template "anycompany-analytics-brand-template" from the brand "AnyCompany Analytics." The presenting company name is AnyCompany Analytics.
The AnyCompany Analytics template then appeared selected in the "Suggested" tab, and each slide in the outline showed which template slide would be used, such as "Format: Template slide 1 (title_slide)" and "Format: Template slide 4 (content_flow)." The plan for the cover slide was "Recipient: 'Sample Seisakusho | October 2026'" and "Use the template's dark blue gradient cover as-is." Quick responded that "all 6 slides can make use of existing slides as-is" and "we've optimized the challenges and benefits to a 3-item structure to match the template's structure."

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

| # | Slide | Layout Used |
|---|---|---|
| 1 | Cover: Proposal for Data Analytics Platform Introduction | 01_Cover |
| 2 | Challenges in Manufacturing Operations (3 items) | 05_Title Only |
| 3 | Solution: Integrated Data Analytics Platform (BEFORE / AFTER) | 04_2-Column Comparison |
| 4 | Benefits of Implementation (KPI) *Estimates based on industry case studies | 05_Title Only |
| 5 | Implementation Roadmap | 05_Title Only |
| 6 | Cost-Benefit Analysis and Next Steps (including contact information) | 05_Title Only |
Checking the Generated .pptx Against the Rules
I checked the downloaded .pptx using a program that compares it against the template. Place both files in the same directory and run it.
check_brand_rules.py
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 whether theme (colors/fonts) and logo images are the same as 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}: {'Same' if same else 'Differences found'}")
# Parts that are in the generated file but 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))
# For each slide, output paragraph count in body, amber/red reference count, explicit fonts, and 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 rules, and strings that must 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: Same
ppt/media/image1.png: Same
ppt/media/image2.png: Same
ppt/media/image3.png: Same
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_表紙: 本文の段落=0 アンバー=0 レッド=0 フォント=[] ノート='表紙のルール:'
slide2 05_タイトルのみ: 本文の段落=0 アンバー=0 レッド=0 フォント=['Georgia'] ノート=''
slide3 04_2カラム比較: 本文の段落=6 アンバー=0 レッド=0 フォント=['Georgia'] ノート=''
slide4 05_タイトルのみ: 本文の段落=0 アンバー=1 レッド=0 フォント=['Georgia'] ノート='KPI スライドでは、最も伝えたい 1 つの数値だけをアンバーにする。'
slide5 05_タイトルのみ: 本文の段落=0 アンバー=0 レッド=0 フォント=['Georgia'] ノート=''
slide6 05_タイトルのみ: 本文の段落=0 アンバー=0 レッド=0 フォント=['Georgia'] ノート=''
ブランドガイドライン: なし
サンプル製作所 御中: あり
2026年10月: あり
sales@anycompany.example: あり
The theme and logo images were byte-for-byte identical to the template. The slide master and layouts were also identical in content, except for the way empty elements were written (<a:avLst></a:avLst> vs. <a:avLst/>). The results for each rule were as follows:
| Rule | Result |
|---|---|
| Do not include the guidelines slide | Not included |
| Cover background remains navy | The cover layout (navy gradient) was used as-is |
| Customer name and date in cover subtitle | "Sample Seisakusho |
| Dark full-bleed backgrounds only for cover and section dividers | Dark background only on the cover |
| Amber limited to 1 instance per slide | Only 1 instance: "-70%" on slide 4 |
| Red reserved for risk and warnings | Not used |
| Fonts limited to Georgia / Arial / Yu Gothic | Fonts explicitly specified in slides are Georgia only. Others use the theme font |
| Bullet points limited to 5 items per slide | Slide 3 has 3 items on each side, totaling 6 items |
| Logo in lower right | Lower right on all slides (logo in master and layouts) |
| Contact information on final slide | sales@anycompany.example on slide 6 |
The content required by the rules was mostly followed, but slide 3 had 6 bullet point items.
In addition to the rules, there were the following 3 points:
- Template speaker notes remain: Slide 1 contained "Cover rules: - Always include the customer name and date in the cover subtitle. …" and slide 4 contained "On the KPI slide, make only the single most important number amber," both carried over as-is from the template notes
- Office add-in information was added:
ppt/webextensions/not present in the template was included. The add-in ID isWA200010606, withOffice.AutoShowTaskpaneWithDocumentset totrue. The timestamps recorded in the zip show that only the 3 webextension-related files differ from the other files. This was included at the time of download, not in a file that had been resaved in PowerPoint - File properties (such as author) retained the values from the template
Opening and Checking 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 in the PowerPoint used for verification. On the first slide, the third line of the title "思決定へ" overlapped with the subtitle "サンプル製作所 御中". The notes area at the bottom displays the template's "Cover Rules".

In the Quick preview, the title and subtitle were not overlapping. The preview displays "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 extended over the bottom border of the card.

Making Requests That Violate 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 returned the following confirmation.
I will change the cover (slide 1) background to red and the title to Comic Sans MS.
However, please allow me to confirm. This document follows the AnyCompany Analytics brand template (navy-based, Georgia headings), and red background + Comic Sans MS significantly deviates from the brand guidelines (the template notes also specify that red is limited to risk/warning displays, and fonts are designated as Georgia/Arial). As a customer-facing proposal, this may compromise the presentation's appearance.
Are you sure you want to apply the changes as specified?
There were three options: "Apply changes as is", "Adjust to align with the brand (adjust within brand-compliant range, such as dark red tones and keeping existing fonts)", and "Do not change".

When I selected "Adjust to align with the brand", Quick updated the cover and explained the following.
- 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 for 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.
The font was replaced with a rule-compliant alternative, but the background violated two rules: "keep the cover background navy without changes" and "limit red to risk and warning displays." These were the very rules that Quick itself had cited in the confirmation just before.
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 "limit red (#D7263D) to risk and warning displays"?
Quick responded "You are correct, and I have corrected it," and reverted the cover background from #D7263D back to navy #0B3D91. Regarding the previous decision, 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 for its use."

This response also stated 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 the screens of other users 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, templates are 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.
Discussion
Use the Extracted Results with the Expectation That a Brand Manager Will Review and Rewrite Them
Quick correctly extracted 9 colors and fonts from the template theme, but the representative values displayed in the panel showed 5 colors and listed the body font as Georgia, which differed from the theme. The rules written in the guideline slides and notes were not entered in the rules field in either of the two extraction 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 did not end up in 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" field in the language used internally within the organization. The documentation's troubleshooting section also states that if a generated document does not follow a rule, you should verify that the rule is not only readable from the source file's design but is 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 difference in representative values did not appear in the generated results. Whether there are scenarios where the representative values are used (such as creation methods that do not duplicate template slides) was not verified this time.
The Structure of Generated Documents Is Determined by the Number and Types of Shapes in the Template
Since Quick duplicates slides from the template 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 on the first step and not on the second or third. This is because only the first step in the template's "Next Steps" slide had supplementary text. Additionally, the contact information card was used to display "Approach" on the 5th slide and "ROI Estimate" and contact information on the 6th slide.
The documentation also states that templates containing various layouts (cover, body with placeholders, section dividers) are more suitable. If slides with cards or steps of varying item counts are included in the template, Quick would have more slides to choose from based on the content.
Points to Verify Before Sending Externally
The following points in this generated output required verification 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 notes should be removed from the template in advance, or the notes in the generated document should be verified 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 in PowerPoint. It is necessary to open the downloaded file in PowerPoint and verify it
- Office add-in information: The generated .pptx contained a setting to display the task pane for the add-in with ID
WA200010606when the file is opened.WA200010606is the ID for Amazon Quick for PowerPoint in the Microsoft Marketplace. Whether to leave this setting in files sent externally should be decided by the organization
- File properties: Properties such as the author remained as the template's values
Responses to Requests That Violate the Rules
For requests that violated the rules, as stated in What's New, the system explained the reasons, presented options, and then made the changes. However, the result of selecting "Adjust to align with the brand" simply 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 brand guidelines before sharing. Even when Quick explains that something "aligns with the brand," final verification must be performed by a human.
Specify by Name When Testing Drafts
Drafts did not appear in either the Suggested tab or the Brand tab in the 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
- Extraction of 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
- Exclusion of template speaker notes from generated documents
- Ability to select drafts from the Brand tab in Visual Style
- Availability of Quick on the web version and an API for manipulating brand assets
Conclusion
By registering a PowerPoint template as a brand asset in Amazon Quick, you can create documents that duplicate the template's slides. In this verification, a .pptx was created that was byte-for-byte identical to the template in terms of theme and logo, and many of the registered rules were followed, including the customer name and date on the cover, the contact information on the final slide, and the number of times amber was used. It was also confirmed that for requests violating the rules, the system explains the reasons and asks for confirmation before proceeding.
On the other hand, rules written in guideline slides and notes did not end up in the rules field, requiring brand managers to transcribe them manually. The generated documents retained the template's notes and Office add-in settings, and text overlaps were found when opened in PowerPoint. There were also cases where an alternative described as "brand-compliant" violated a different rule.
For those who wish to register their own templates, we recommend first refining the rules field and the "When to use" field in draft state, then specifying the template in chat to create a document, opening it in PowerPoint to verify it, and only then publishing.
References
