Elements

Overview

Tone of voice

Instant Strata helps strata managers run schemes with less friction and gives owners a clearer picture of their building. The way we write should feel as dependable as the product: professional, plain, and respectful of people's time.

There is one Instant Strata voice. Tone flexes with context: a hero headline can carry more energy than a levy overdue badge, but both should sound like they come from the same team.

Principles

The foundations that guide every headline, label, notification, and email. When you are unsure, return to these three.

Trustworthy

Owners and committees hand us their homes and their money. Every word should feel capable, honest, and calm. We explain what is happening and what happens next, without hedging or hiding behind process.

Plain

Strata has enough complexity already. We use everyday language in the UI and reserve legal precision for documents that need it. If a manager would not say it out loud to an owner, it does not belong on screen.

Efficient

Managers work at pace. Owners scan on their phones between meetings. Copy is direct, scannable, and free of filler. Say the thing once, in the fewest words that still feel human.

How to speak Instant Strata

01

Lead with the benefit

Tell people what they gain or what changes for them. Marketing headlines and empty states should answer "why should I care?" before "how does it work?"

02

Be concise

Aim for full clarity in as few words as possible. Headlines should work without subcopy. Body text stays under 65 characters per line where layout allows.

03

Use Australian English

Colour, organisation, levies, and strata plan numbering follow local convention. Dates read as 30 Jun, not June 30. Currency is AUD unless context says otherwise.

04

Name things consistently

Scheme, lot, owner, levy, and work item mean specific things in this product. Use the domain vocabulary table below. Do not mix synonyms (building vs scheme, unit vs lot) in the same surface.

05

Match the moment

Marketing can be confident and warm. Product UI stays neutral and helpful. Errors and compliance notices are direct and reassuring, never playful.

Right place, right tone

The voice stays consistent. The energy changes. Dial up confidence on marketing surfaces; dial down to calm precision in product UI and when something has gone wrong.

Standing out

Hero bands, social proof, billboards, and anywhere you have seconds to land the message.

How

  • Short and confident
  • Benefit-first
  • Young Serif headlines, plain subcopy

Write like this

  • Strata management, simplified.
  • Everything in one place, from day one.
  • Levies, compliance, and correspondence. One platform.

Not like this

  • Revolutionary next-generation strata ecosystem.
  • Leverage synergistic OC management solutions.

Converting customers

Landing pages, pricing, feature rows, and App Store listings where people need a reason to sign up.

How

  • Direct and concrete
  • Real outcomes, not feature lists
  • One primary CTA per section

Write like this

  • Send levy notices and track payments without switching systems.
  • See every open task across your portfolio in one inbox.
  • Owners get a portal for levies, documents, and updates.

Not like this

  • Our best-in-class modular workflow engine empowers stakeholders.
  • Unlock holistic visibility across your asset portfolio.

Product UI

Labels, table headers, navigation, form fields, and metadata in the manager and owner experience.

How

  • Noun-first labels
  • Sentence case
  • No marketing adjectives

Write like this

  • Needs your attention
  • Levy overdue
  • Awaiting review
  • SP 1042

Not like this

  • Supercharge your workflow!
  • Mission-critical action items
  • Leverage the dashboard

Adding clarity

Hints, empty states, onboarding steps, and microcopy that guides without patronising.

How

  • Helpful, not cute
  • One idea per line
  • Optional humour only when stakes are low

Write like this

  • No open tasks. New items from email and the portal appear here.
  • Upload the AGM minutes to close this work item.
  • Owners with overdue levies cannot hold a proxy.

Not like this

  • You're all caught up! Time for a cuppa.
  • Oopsie! Something went wrong.

Providing reassurance

Errors, failed payments, blocked actions, statutory deadlines, and compliance warnings.

How

  • State what happened
  • Say what to do next
  • No jokes, no blame

Write like this

  • Levy payment failed. Check the account details and try again, or contact the owner.
  • This transfer is taking longer than usual. We will email you when it completes.
  • We have temporarily locked this account after several failed sign-in attempts.

Not like this

  • Uh oh, something broke!
  • Invalid input detected in field 3.
  • User error: payment declined.

Examples in UI

Reassurance · danger and warning notifications

AGM date not confirmed

Set the date in scheme settings before sending the notice pack.
Product UI · metadata and labels

Harbour View Towers

SP 1042 · South Brisbane, QLD

Scheme name first, plan number and location as metadata. No adjectives.

Marketing · hero headline pattern

For strata managers

Everything in one place

Levies, compliance, correspondence, and owner requests. One inbox, one roll, one source of truth for every scheme you manage.

Strata vocabulary

Domain terms are intentional. Use them consistently so managers and owners learn the product language once.

Scheme

The owners corporation for a building. Always scheme in product UI, not OC or body corporate.

Example: Harbour View Towers · SP 1042

Lot

An entry on the strata roll. Pair with lot number.

Example: Lot 12

Owner

Registered proprietor on the roll. Distinct from tenant or occupant.

Example: James Chen

Levy

Owner contribution to scheme funds. Status: paid, due, overdue, not assessed.

Example: Levy overdue

Work item

Operational task in a workflow. Prefer over ticket or case in UI.

Example: Review AGM minutes

SP number

Strata plan identifier. Uppercase SP prefix, mono styling.

Example: SP 1042

AGM

Acceptable abbreviation when context is clear. Spell out once on public marketing if needed.

Example: AGM minutes due

R-A-S

Review-and-sign gate for automatable work. Use the badge label, not the full phrase in dense UI.

Example: R-A-S

Statement library

Prefer the left column. The right column shows common drift: too long, too vague, or too casual for the context.

Primary CTA

Try for free

Get started now!

Secondary CTA

Request demo

Book a discovery call with our team

Danger notification

Levy payment failed

Error: transaction unsuccessful

Warning notification

AGM date not confirmed

Warning: pending calendar event

Empty inbox

No open tasks

Your inbox is empty. Enjoy the silence!

Required field

Scheme name

Please enter the mandatory scheme name field

Rules

  • No legal jargon in the UI. Reserve formal language for generated documents and contracts.
  • Sentence case for labels and buttons. ALL CAPS only for eyebrows and mono identifiers (SP, Lot).
  • One primary CTA per section. Button labels are verbs: Try for free, Request demo, View inbox.
  • Never blame the user in error copy. State the problem, then the next step.
  • Do not use exclamation marks in product UI. Marketing may use one sparingly in hero copy.
  • AI-generated copy in the product should follow the same rules as human-written copy.
  • Tagline: Strata management, simplified. Use it consistently, do not rephrase for variation.