Small Brand Consistency Audit / Action kit
Brand consistency audit checklist
Identify inconsistent typography, colors, spacing, and reusable components across a small set of assets.
Made for teams maintaining everyday branded materials.
Price and availability
Catalog price: $9 USD
One-time purchase · No subscription
- FilesZIP with five editable Markdown documents, an offline HTML workbook, a reading edition. A five-document worked case follows one fictional project.
- To useExtract the ZIP. Open the workbook in a current desktop browser; edit Markdown in a text editor. No account needed for the workbook or Markdown files.
- LicenseUse for your own or client work; do not redistribute the original templates or tools. Full terms.
- SupportProduct questions and corrections by email; no custom implementation or professional review. 14-day refund policy.
Checking the live price and secure checkout…
The task
What you'll make
A short rule set and prioritized corrections for recurring inconsistencies.
Gather before you start
- Representative assets
- Current rules
- Asset owners
Mark missing information so you can check it before using your work.
When to skip this kit
- You need a native Excel, Canva, or Word template. This download contains Markdown documents and an offline HTML workbook.
- You need autosave or cloud sync. Export Markdown or save a backup before closing the offline workbook.
- You need someone to complete the work. These are worksheets to fill in yourself.
Read the first worksheet below to see whether its questions help with your task.
Included files
What's inside
- 01Asset sample
- 02Pattern inventory
- 03Rule selection
- 04Template correction
- 05Owner guidance
Each document has instructions, questions, and space for your answers. The final document includes a common mistake to check for before using your work.
The worked case contains five completed documents, one for each worksheet. Follow the evidence, decisions, and corrections across the same fictional project. The case is included in the workbook, reading edition, Markdown example.
Your completion check
Bound the sample, preserve purposeful exceptions and required content, test named rules in the actual tools with difficult content, and distinguish tested corrections from remaining assets and coverage gaps.
Before you finish
Check this before you use it
Every difference is treated as an error despite different use cases.
Keep intentional exceptions and fix only differences that reduce clarity.
Use the final worksheet to record what needs fixing and what you still need to check.
Free worksheet
Start with worksheet one
Asset sample
Jump to a section
{{project}} / audit owner {{business}} / approval {{contact}} / review {{deadline}}
Purpose: bound the audit and preserve a representative baseline. Scope: channels/tools [ ]; audience tasks [ ]; time period [ ]; assets included/excluded [ ]; why this sample covers routine and difficult uses [ ]. A few screenshots are not a complete audit of every business output. Asset register: ID | actual file/URL/version/date | owner | channel/tool | user task | frequency | content difficulty | existing rule/reference | status/access/rights. Preserve the original candidate or version reference before changing it. Include long titles, dense text, small formats, different backgrounds, required fields, and editing tasks rather than only ideal mockups. Record private/redacted fields separately and avoid copying customer information into a shared audit. Baseline observation: location | current hierarchy/type/color/spacing/component | visible inconsistency | task effect or hypothesis | evidence category | limitation. Distinguish measured/observed behavior, reviewer opinion, and inferred user impact. Production constraints: approved fonts and rights [ ]; actual tools/editor ability [ ]; platform/output requirements [ ]; required legal or finance fields [ ]; accessibility/production owners [ ]. Unknown requirements remain open, not a reason to create a universal style. Sample coverage gaps: missing use | likely consequence | owner/date for follow-up [ ]. Verify the asset is current; an obsolete version should not determine the new rule. Decision: sample ready / add evidence / hold. Retain intentional differences until their function is understood; consistency alone is not a reason to remove a necessary exception.
Your decision
Does the sample cover both routine and difficult applications? My answer: [ ] Source and date: [ ] Still to check: [ ] Next action, owner, and due date: [ ]
Before you start
- Representative assets: [Source or notes]
- Current rules: [Source or notes]
- Asset owners: [Source or notes]
What you will make
A short rule set and prioritized corrections for recurring inconsistencies.
View plain worksheet text
{{project}} / audit owner {{business}} / approval {{contact}} / review {{deadline}}
Purpose: bound the audit and preserve a representative baseline.
Scope: channels/tools [ ]; audience tasks [ ]; time period [ ]; assets included/excluded [ ]; why this sample covers routine and difficult uses [ ]. A few screenshots are not a complete audit of every business output.
Asset register: ID | actual file/URL/version/date | owner | channel/tool | user task | frequency | content difficulty | existing rule/reference | status/access/rights. Preserve the original candidate or version reference before changing it.
Include long titles, dense text, small formats, different backgrounds, required fields, and editing tasks rather than only ideal mockups. Record private/redacted fields separately and avoid copying customer information into a shared audit.
Baseline observation: location | current hierarchy/type/color/spacing/component | visible inconsistency | task effect or hypothesis | evidence category | limitation. Distinguish measured/observed behavior, reviewer opinion, and inferred user impact.
Production constraints: approved fonts and rights [ ]; actual tools/editor ability [ ]; platform/output requirements [ ]; required legal or finance fields [ ]; accessibility/production owners [ ]. Unknown requirements remain open, not a reason to create a universal style.
Sample coverage gaps: missing use | likely consequence | owner/date for follow-up [ ]. Verify the asset is current; an obsolete version should not determine the new rule.
Decision: sample ready / add evidence / hold. Retain intentional differences until their function is understood; consistency alone is not a reason to remove a necessary exception.
Your decision
Does the sample cover both routine and difficult applications?
My answer: [ ]
Source and date: [ ]
Still to check: [ ]
Next action, owner, and due date: [ ]
Before you start
- Representative assets: [Source or notes]
- Current rules: [Source or notes]
- Asset owners: [Source or notes]
What you will make
A short rule set and prioritized corrections for recurring inconsistencies.This is the complete first worksheet from the current edition. The full kit adds the remaining four documents, a worked scenario, and the offline editing workbook.
Worked example
See the worked-case summary
Fictional example included in edition 2.49.1.
Fictional case: Northline Studio audits eight recurring assets, chooses four named typography roles with application-specific sizes, and corrects a proposal, a slide deck, and a web service page. A long project title exposes a fixed-height layout failure; an intentional invoice exception stays. Five completed documents distinguish sampled assets, approved rules, three corrected outputs, five remaining assets, and a named change owner. All checks and results are teaching examples.
Before you choose
What should I have ready for this kit?
Bring representative assets, current rules, asset owners. Mark anything you still need to check.
How do I know the work is finished?
A short rule set and prioritized corrections for recurring inconsistencies. Check your answers against the original records and note anything unresolved before sharing your work.
Does it include a spreadsheet or native app template?
No. You receive editable Markdown documents and an offline HTML workbook. These are not native Excel, Canva, Notion, or Word templates. Extract the whole ZIP before opening the HTML files. Mobile file managers may not run local scripts; the text files and reading edition remain available.
Will this do the work for me?
The kit supplies structure, questions, and examples. You provide the facts, make the decisions, and adapt the finished output. You are responsible for checking the finished work. Custom implementation and professional review are not included.
Created by Pagemage with AI-assisted writing and development. Read how the content and tools are checked. Questions or corrections: hello@pagemage.tech. 14-day refund policy.