Every AI tool you touch has the same default personality: a chipper regional sales manager who just discovered adjectives. Left alone, it will describe your 1970s garden-style asset in Tulsa the exact same way it describes a Class A high-rise in Denver. Both are "nestled." Both "offer the perfect blend of comfort and convenience." Both are unusable.
The fix isn't better prompting every single time. It's building a voice document once, then pasting it into everything.
This is the highest-leverage two hours you'll spend this quarter, and I mean that structurally: a voice spec turns every future AI output from a rewrite job into a light edit. That difference compounds across 40 properties, 12 review responses a day, and every renewal email your team sends.
Why "write in our brand voice" does nothing
Because the model has no idea what that means. It has read your website, maybe. It has definitely read ten thousand other apartment websites, and those are pulling the average toward "luxury living redefined."
Vague instructions get you the average. Specific instructions get you you.
"Friendly but professional" describes roughly every company that has ever existed. "We use contractions, we never use the word 'luxury', we lead with the floor plan not the lifestyle, and our sentences run under 20 words" describes exactly one company. Guess which one produces copy your regional doesn't rewrite.
The five-part voice spec
Don't write a brand book. Nobody reads brand books, including the people who wrote them. Write a working document, one page, five sections.
1. Banned words and phrases. This is the most powerful section and the easiest to build. Open your last three email campaigns and your website. Highlight every phrase that could appear on any competitor's site. "Nestled." "Your oasis." "Luxury living." "Come home to." "Resort-style." "Perfect blend." "We're excited to announce." Write them all down under a heading that says NEVER USE. Models follow negative constraints surprisingly well when the list is concrete. They ignore "avoid clichés" completely, because they don't think their clichés are clichés.
2. Sentence mechanics. Average length. Contractions, yes or no. Do you use fragments? Do you start sentences with "And" or "But"? Em dashes or commas? Oxford comma? Sounds fussy. It's the difference between text that reads like your team and text that reads like a press release. Write it as rules: "Sentences average 12 to 18 words. Use contractions always. Fragments are fine. No semicolons, ever."
3. Structural habits. How do your emails open? Do you lead with the offer or the greeting? Do you sign off with a name or a team? For review responses: do you apologize first or thank first? Do you name the resident? Do you invite them to the office or to a phone call? These patterns are what make outputs feel like your property, and they're invisible until you write them down.
4. Three annotated examples. Paste in a real email you're proud of, a real review response, and a real ad headline set. Then, and this is the part people skip, annotate why each one works. "Notice this opens with the concession, not a greeting." "Notice this response takes ownership in the first sentence without admitting a policy failure." The model learns pattern faster from labeled examples than from adjectives. Two good examples with notes beat a page of description.
5. Register by channel. You don't write a Google Ads headline like you write a renewal letter. Give it a quick table in prose: paid search headlines are blunt and numeric, Instagram captions are short and dry, renewal emails are warm and specific, review responses are calm and never defensive, ILS descriptions are factual and feature-forward.
Building it in 90 minutes
Pull ten pieces of your own writing. Real ones, the ones that performed, not the ones legal rewrote.
Paste them into your AI tool and ask it to reverse-engineer the pattern: average sentence length, recurring structures, words used more than once, how you open and close. It will produce a first draft of your voice spec faster than you'd write it yourself. Then you edit it hard, because the model will flatter you and describe your writing as "engaging and approachable," which is not a rule anyone can follow.
Cut everything that isn't testable. If you couldn't check whether an output followed the rule, delete the rule.
Then test it. Take the spec, paste it into a fresh chat, and ask for three versions of the same renewal email. If they sound like you, you're done. If they sound like a brochure, your banned list is too short.
The fair housing line, and it matters here
When you generate listing copy or ad headlines, models default to describing the person who should live there rather than the apartment. "Perfect for young professionals." "Ideal for a growing family." "Great for students." Those describe a protected-class preference, and they create fair housing exposure regardless of intent.
Put a permanent line in your voice spec: describe the unit and the community, never the resident. Features, dimensions, finishes, location, amenities, terms. No inferences about who lives there or who would be happiest there. If your marketing team is generating copy at volume, this rule in the spec catches it before a human has to, and it should be in every version of the document you distribute.
Where to put it so it actually gets used
A voice spec in a shared drive is a voice spec nobody uses. Put it where the work happens.
If you're on ChatGPT Team or Enterprise, build a Custom GPT per use case and paste the spec into the instructions field. One for review responses, one for email, one for ad copy. Claude Projects works the same way: the spec lives in project knowledge and applies to every conversation inside it. Gemini Gems, same idea.
If your team is on free tools, make a Google Doc titled VOICE SPEC and train everyone to paste the whole thing at the top of every session. Less elegant. Works fine.
Version it. When you rebrand or when a new operator takes over a portfolio, you update one document, not 40 people's habits.
What breaks
Voice specs drift on long outputs. A model holds your rules tight for 200 words and starts sliding back to house style by 800. Generate in shorter chunks and the problem mostly disappears.
The other failure: a spec built from writing you didn't actually like. If your last three campaigns were mediocre, you're about to industrialize mediocre. Pick your best work, not your most recent.
And one honest limit. The spec makes outputs sound like you. It does not make them true. Concession amounts, availability, pet policy, square footage: check every one, every time, because the model will state a number with total confidence and no idea where it came from.