The One-Page Brand Sheet Your Team Will Use

Most brand inconsistency is not a discipline problem. It is a decision problem. Somebody in your team opens Canva at 6pm, needs a Diwali greeting by morning, and nobody has ever told them which orange is your orange. So they pick one. Next month a different person picks a different one. Six months later your feed looks like four companies sharing an account, and you find yourself in a meeting saying the word "brand" a lot without anything changing.

The usual fix is to commission brand guidelines. You get a forty-page PDF with a logo exclusion zone diagram, a mood board, and a paragraph about your brand's "personality archetype". Nobody opens it twice. The person posting at 6pm does not want a document, they want an answer.

What follows is the one page that replaces it. It is deliberately short, because the test of a brand sheet is not how complete it is, it is whether someone follows it when they are in a hurry.

Why consistency slips, mechanically

It helps to know exactly where the drift comes from, because each cause has a different fix.

No stored answer. The colour, the font, the logo file, the standard sign-off — these exist in someone's head or in an old file on a laptop that left the company. Every post re-decides them.
Different tools. Your designer works in one application with the brand colours saved. Your sales person posts from the phone app with a template. The template's default blue wins.
Different source files. There are now five versions of your logo in circulation: one with a white box behind it, one someone screenshotted off the website and it is blurry, one with the old tagline.
No agreed voice. One person writes "Dear Esteemed Customers, we are pleased to inform". Another writes "guys we're open till 9 today 🎉". Both are defensible. Having both is not.
Festival and occasion posts. This is where almost every Indian brand's feed goes to pieces. Generic templates with someone else's diya illustration, a stock rangoli, and your logo squeezed into a corner. These posts outnumber real posts in many feeds.

None of that is solved by a longer document. It is solved by storing a small number of decisions somewhere the person posting will actually look, in under thirty seconds.

What goes on the page

Keep it to one side of A4, or one note in whatever your team already uses. If it spills to two pages, something on it is not load-bearing. Here is the structure.

1. The assets, with links not descriptions

Not "our logo should be used with adequate clear space". Instead: a direct link to a folder containing the logo in PNG with a transparent background, the logo in white for dark photos, and the square version for profile pictures. Three files. Named clearly. If someone has to ask where the logo is, the sheet has failed.

Same for colours — write the hex codes, the six-character codes beginning with a hash that design tools accept, like #C8102E. Two or three codes, no more. One main colour, one accent, one for text. If your sheet lists eight colours, your team will use all eight.

Fonts: name the exact font, and name the fallback for when it is not installed. "Poppins. If unavailable, use Montserrat. Never use the tool's default."

2. The profile text, written out in full

Your Instagram bio, your WhatsApp Business description, your Google Business Profile description and your LinkedIn tagline all have different hard character limits. Write each one once, paste the final approved text onto the sheet, and nobody rewrites it in a hurry again. This also means when you open a new channel, the copy already exists.

3. Voice, as three rules and two examples

Forget personality archetypes. Write three rules a person can obey:

We write in English with Hindi words where that is how people actually speak. We do not write full sentences in Hinglish.
We address one customer, not a crowd. "You", never "Dear Customers".
Prices are written in Indian format with the rupee sign: ₹1,50,000. Never "150000/-".

Then paste one post you were happy with and one you were not, with a sentence saying why. Examples teach faster than rules.

4. The hard noes

Short list. Things that will get a post deleted. For example: no stock photos of white people in boardrooms; no stretched logos; no competitor names; no prices in posts unless signed off; no claims about being "the best" or "number one" that we cannot evidence; no auto-generated festival templates.

5. Who decides what

This is the part most brand documents skip, and it is the part that actually prevents arguments.

Decision	Rule	Who signs off
Routine post, product or update	Follow the sheet, post it	Nobody. Just post.
Festival or occasion greeting	Use the pre-made set, swap the text	Nobody
Anything with a price or offer	Must match the website	Owner or sales head
Replying to a complaint publicly	Acknowledge, move to DM or phone	Whoever handles support
New colour, font or logo variation	Don't	Owner

The point of that table is the first two rows. Most posts should need nobody's approval. An approval chain that covers everything is an approval chain that gets bypassed by WhatsApp at 6pm.

Solve the festival post problem once

Indian businesses post a lot of occasion content. Diwali, Holi, Independence Day, Eid, Pongal, New Year, plus industry days and the founder's anniversary. If each one is improvised, each one is off-brand, and collectively they dominate the impression your feed gives.

Spend half a day with a designer making eight to ten occasion templates in your actual colours and font, with your actual logo placed properly. Store them as editable files in the same folder as the logo. Then the 6pm job becomes changing the words, not making design decisions. This single step fixes more visible inconsistency than any written rule, because it removes the moment of choice.

The same logic applies to your regular formats. Two or three post layouts — a quote card, a product card, an announcement card — covers most of what a small business posts. A limited set of formats looks deliberate. Infinite formats look random, even when each one is individually fine.

What not to buy

Plenty gets sold under the heading of brand consistency that will not change what gets posted on Tuesday.

A full brand book, if you are under about twenty people. Exclusion zones, minimum sizes, co-branding lock-ups, tone-of-voice matrices. These exist because large organisations have people who have never met the founder producing materials at scale. If your whole team fits around one table, the book is expensive shelf decoration. A one-page sheet plus a shared asset folder does the same job. An agency can and will sell you the book. We would rather you spent the money on the templates.

Brand monitoring and sentiment dashboards. For a business posting a few times a week, a dashboard telling you your sentiment score is 68 is not actionable. Read your own comments.

A scheduling tool bought as a governance tool. Scheduling tools are useful for scheduling. They do not enforce brand rules, and buying a more expensive tier with approval workflows usually just adds a step people route around. If your team is three people, the queue is a conversation, not software.

An AI tool that writes "in your brand voice". These can produce serviceable first drafts if you give them good examples, and that is genuinely useful. What they will not do is make an inconsistent team consistent, because the inconsistency is in which human decides to use the tool and which just types something. This whole area is moving fast and we would be guessing if we told you how good it will be in a year. Treat it as a drafting aid, not a control.

Keeping it alive

A sheet that is never revised stops matching reality within a few months, and once it is wrong once, people stop trusting it entirely. Two habits keep it honest.

One named owner. Not a committee. One person who can change the sheet without asking. Everyone else proposes.
A fifteen-minute review each quarter. Scroll your own feed as a stranger would. Anything that looks off-brand, ask why: was the rule missing, unclear, or ignored? Missing and unclear are sheet problems. Ignored is a conversation.

One more thing worth checking at the same review: your website and your social profiles should agree. Same logo file, same colours, same phone number, same business hours, same address format. Mismatched details across your site, your social profiles and your Google listing confuse customers, and consistent business information across the web is one of the few things in local search that is not controversial. If your website has drifted away from everything else, that is usually the thing to fix first — our notes on building and maintaining a site cover the mechanics.

What to do this week

Open a blank document. Put in it: links to three logo files, two or three hex codes, one font name, your four profile descriptions written out, three voice rules, five hard noes, and the decision table. Share it with everyone who posts. That is an afternoon, not a project.

Then book the half day with a designer for the occasion templates, because that is where the visible damage is happening.

If you would rather someone else built the sheet and the template set with you and trained the people who post, that is work we do — tell us who currently posts and how often and we will tell you what is worth doing and what is not. More practical pieces on social, creative and the web are in the blog.

Questions we get asked

How many people should be allowed to post for a small business?

As few as practical, but more than one — a single poster means nothing goes out when they are on leave or busy. Two or three with a shared sheet works well. The number matters less than whether each of them knows where the logo lives and which colours are yours.

Do we need professional brand guidelines before we can post consistently?

No. Full brand guidelines are built for organisations where people producing materials have never met each other. A small team needs stored decisions, not a document: logo files, colour codes, one font, agreed profile text and a short list of things not to do. You can always commission the longer document later if you grow into needing it.

Our festival posts always look generic. What is the fix?

Stop improvising them. Have a designer build eight to ten occasion templates in your own colours, font and logo, and store them as editable files. Then each festival is a text change rather than a fresh design decision taken at short notice, which is where generic template artwork creeps in.

Should every post be approved by the owner before it goes out?

Approval on everything tends to collapse — posts go out unapproved anyway, or they go out late. It is usually better to approve the rules once, let routine posts go without sign-off, and reserve approval for anything involving prices, offers, claims about the business, or public replies to complaints.

Can AI tools keep our social posts on-brand?

They can produce reasonable first drafts if you feed them several of your own past posts as examples, and that saves time. They do not solve inconsistency, because the inconsistency comes from different people choosing different approaches, not from the writing itself. This area is changing quickly, so treat any tool here as a drafting aid you review, not a control you rely on.