Brand guidelines
Rosta looks like a printed roster and a highlighter: cool paper, navy ink, teal for anything covered, and one yellow for the gap that needs cover. This page is the reference for screens.
Version 2.0, November 2026. Printing something? See the print guidelines.
Logo
A teal rounded tile with three staggered white bars, the rows of a roster, and the word Rosta beside it. It is the same mark the app uses.
The wordmark
Rosta, with a capital R, in Archivo at weight 800 and 84% width. Navy on light surfaces, white on navy. The type size is 0.78 of the tile's height, and the word sits centred on the tile.
The tile alone
Use it where there is no room for the word: the browser tab, the home screen icon, an avatar.
Clear space
Keep clear space of half the height of the tile on every side of the tile or the full logo. No text, images or other logos inside it.
The dashed line is the edge of the clear space.
Minimum size
On screen, the full logo is never shown with the tile under 24 px high. The tile alone can go down to 16 px, the size of a browser tab icon.
Don't
-
Do not stretch or squash it.
-
Do not recolour the tile. It is always teal.
-
Do not put the navy wordmark on navy. Use the white one.
-
Do not reset the word in another typeface or in lower case.
Also retired: the "S" letter mark, and the small accent dot that used to sit on the corner of the tile. Neither appears anywhere.
Colour
Each colour has a job. If a colour is on the page, a reader should be able to say what it is telling them.
-
Navy
#003049
Headings, outlines, rules and the navy bands.
-
Ink
#17394A
Body text on paper, white and mist.
-
Teal
#1B6B88
Covered or confirmed. Also links and the logo tile.
-
Teal deep
#134F66
Hover on navy buttons. Nothing else.
-
Paper
#F2F6F7
The page ground.
-
Mist
#DCEBF0
Quiet fills: the standby chip, a tinted band.
-
Line
#C5D9E0
Hairlines between rows. Never text.
-
White
#FFFFFF
Sheets and alternate bands.
-
Highlighter
#FFDD4A
Needs cover, and the main action.
-
Highlighter deep
#F0C61C
Hover on the yellow button only.
Tokens are CSS custom properties (for example var(--teal-deep)) and Tailwind colour names (for example bg-teal-deep). Both hold the same values.
What the colours mean
- Teal means covered or confirmed. A booked shift, a passed check, a link you can follow.
- Highlighter yellow means needs cover, and it marks the main action on a view. It is a highlighter, so it is used the way one is: on the one thing that matters.
- One yellow moment per view. If the main button is yellow, nothing else near it is. A full yellow band appears at most once on a page.
- Navy is the ink. Structure comes from navy outlines and rules, not from shadows or tints.
Amber is retired, along with every orange and brown. There are no gradients, glows or blurred shapes anywhere in the system.
Contrast
Text pairings that meet WCAG AA, and three that never appear.
Use
- Navy on white 13.8 to 1
- Ink on white 12.2 to 1
- Navy on highlighter 10.4 to 1
- White on navy 13.8 to 1
- Teal on white 6.0 to 1
Never
- Teal on navy 2.3 to 1, fails
- Highlighter on white 1.3 to 1, fails
- White on highlighter 1.3 to 1, fails
On navy, body text is white or the pale blue #D6E6EC. Yellow on navy is for small accents only, such as a tick or a focus ring.
Typography
Two typefaces. Archivo for headings, set narrow and heavy like the top of a timesheet. DM Sans for everything else, because it is the typeface the app uses.
.t-display: Archivo, 68% width, weight 800
Sick call at 6 am.
.t-page: Archivo, 70% width, weight 800
Brand guidelines
.t-h2: Archivo, 75% width, weight 750
Six checks before anyone is booked.
.t-h3: Archivo, 88% width, weight 700
Standby pool
.t-lede: DM Sans, weight 400
When someone can't make their shift, Rosta offers it to your qualified staff, most reliable first.
Body: DM Sans, weight 400
The first eligible person to accept gets it, and you see it filled. Each offer stays open for 15 minutes.
.t-time: Archivo, 80% width, weight 650, tabular numerals
6:30 am to 12:30 pm
6:02:10
6:02:37
Type scale
| Style | Class | Face | Width | Weight | Size | Use |
|---|---|---|---|---|---|---|
| Display | .t-display | Archivo | 68% | 800 | 44 to 90 px | The home page headline |
| Page title | .t-page | Archivo | 70% | 800 | 40 to 76 px | The h1 on every other page |
| Section heading | .t-h2 | Archivo | 75% | 750 | 30 to 48 px | One per section |
| Sub heading | .t-h3 | Archivo | 88% | 700 | 21 px | Blocks inside a section |
| Times and figures | .t-time | Archivo | 80% | 650 | Inherits | Clock times, durations, measurements. Tabular numerals. |
| Lede | .t-lede | DM Sans | Normal | 400 | 18 to 21 px | The paragraph under a heading |
| Body | body | DM Sans | Normal | 400 | 17 px | Everything else |
| Small | .t-small | DM Sans | Normal | 400 | 15 px | Notes and captions |
| Button label | .btn | DM Sans | Normal | 700 | 16 px | Things people press |
Sizes that give a range scale with the width of the screen.
Rules
- Sentence case everywhere, including buttons and navigation.
- Everything is left aligned.
- Clock times, durations and measurements use .t-time so the figures line up.
- No small labels in tracked capitals above headings.
- No single word of a headline in a different colour or in italic.
- Archivo is for headings and figures only. Never set a paragraph in it.
Files
Both faces are variable fonts, served from this site and not from a font service: /fonts/archivo-var.woff2 and /fonts/dm-sans-var.woff2. Archivo's width axis is what makes the headings narrow, so the variable file is required; a regular-width Archivo is not a substitute.
Components
The parts the site is built from, shown live. Structure comes from outlines and rules: a navy outline on an important box, a hairline between rows, a heavy rule above a section heading.
Buttons
.btn-primary is the main action and there is one per view. .btn-navy and .btn-outline are for everything else. Labels say what happens; no arrows.
Tier chips
A tier is a word. No number ever sits beside a person's name.
The highlighter mark
Saturday's barista shift needs cover.
.hi-mark marks the thing that needs attention. It is never decoration.
Sheet and week strip
Barista
6:30 am to 12:30 pm
.sheet is a white box with a 1.5px navy outline and no shadow. .weekstrip is the row of days across the top of a roster, with the day in question highlighted.
Cover log
Barista
6:30 am to 12:30 pm
- 6:02:10 Sam reports sick from My Schedule on their phone.
- 6:02:11 Rosta starts asking. The standby pool first, then Elite staff. Reliable staff are asked from 5 minutes in, At-Risk staff from 20.
- 6:02:37 Mia taps Accept. Rosta runs its six checks, then books her. Availability, qualifications, weekly hours, rest, work rights, clashes.
- 6:02:37 Shift covered. Jordan, the manager, sees it filled.
Times from our demo recording: covered 27 seconds after Sam reported sick. How fast yours fills depends on who is free to say yes.
One sick call as a log, with the times from the demo recording. Shown here without its load sequence.
Offer order, on a navy band
Navy bands are used sparingly. Text on them is white or pale blue, never teal.
Voice and tone
Plain and specific. Say what the app does, in the words the app uses, and stop. Rosta speaks the same way on a shift offer as it does on a poster.
How we write
- Australian English: rostering, organisation, colour.
- No hype and no buzzwords. If a sentence would suit any software, cut it.
- No exclamation marks. No em dashes; use a comma, a colon or a full stop.
- Say what the app does, with the real times and the real order.
- Describe speed as what the demo recording shows, not as a promise.
How we sound
- Reliable. Consistent, and never overpromises.
- Calm. A sick call is routine, not a crisis.
- Respectful. Staff are professionals, not a resource pool.
- Clear. Plain language, and straight to the point.
Name things the way the app does
Screens and features keep their names and capitals: My Schedule, Offers, Standby pool, Ask Roo. For staff, tiers are words (Elite, Reliable, At-Risk) and never numbers. Managers and owners can see scores; nothing written for staff shows one.
Lines we use
Sick call at 6 am. Rosta is already asking who can cover.
The lead line. Home page headline, ads to owners and managers.
Cover for sick calls, without the phone calls.
The one-line description of Rosta. Footers, page titles, bios.
Who gets asked, and when.
Explaining the order of offers.
Six checks before anyone is booked.
Eligibility: availability, qualifications, hours, rest, work rights, clashes.
For your staff, it's one tap.
The staff side, told to owners and managers.
It does the ordinary rostering too.
The week board, invites, holidays, swaps.
Say this, not this
| Say this | Not this |
|---|---|
| Offer | Job alert, notification, ping |
| Needs cover | Urgent, emergency, crisis |
| Cover search | Blast, mass message, spam |
| Standby pool | Backup list, bench |
| My Schedule, Offers | Your roster screen, the shifts tab |
| Ask Roo | The bot, the chatbot, the AI |
| Elite, Reliable, At-Risk | Top, bottom, low-rated, or any number shown to staff |
| SURE Score, reliability record | Rating, star rating, performance score, grade |
| In our demo, 27 seconds | Instantly, guaranteed, in under a minute every time |
| Rosta | Switcharoo, the platform, the solution |
To owners and managers
- Lead with the sick call and what happens next.
- Give the order, the times and the six checks.
- Never frame it as panic or urgency.
To staff
- Say what they will see: the role, the date, the start and end time.
- Recognise turning up. Declining an offer costs nothing, and we say so.
- Never transactional or dismissive.
Motion
Motion should answer a question the reader is about to ask. If it does not, cut it.
- One load sequence per page, at most. The cover log can write itself, line by line, once, when it is the first thing on a page. Lower on a page it is shown finished.
- Nothing is triggered by scrolling. Content is there when you arrive at it.
- Everything is off under prefers-reduced-motion. The finished state is simply shown.
- Short transitions on things people press. Buttons and links change colour quickly, and nothing moves.
| What | Timing | Notes |
|---|---|---|
| Button and link hover | 0.15 s | Background, border and text colour only |
| A cover log line arriving | 0.45 s | Ease out, a short rise and fade, one line after another |
| Needs cover becoming booked | 0.4 s | Once, when the log reaches the accept line |
Trademark and legal
The following names and marks are owned by Rosta Pty Ltd. They must not be used in any context that implies endorsement, affiliation or partnership without written permission.
Rosta™
Rosta
The platform brand name. Used on all product surfaces, marketing and communications.
SURE Score™
Shift Uptake and Reliability Engine Score
The proprietary worker reliability scoring system. Always written as "SURE Score", never abbreviated further.
Roo™
Roo
The name of the Rosta assistant. A proper noun, always capitalised. Never referred to as a "bot" or "chatbot".
Broadcast Engine™
Rosta Broadcast Engine
The tiered shift-fill escalation system. May be referred to in marketing and press materials.
Elite / Reliable / At-Risk / Probation™
Rosta Tier System
The four tier labels within the SURE Score system. Use the full set in context; never cherry-pick a single tier in isolation.
Do
- Use "Rosta" as a proper noun, always with a capital R.
- Append ™ on first mention of any mark in published materials.
- Write "SURE Score" in full on first mention; later references may use "the Score".
Don't
- Do not use Rosta marks as verbs ("just Rosta it").
- Do not modify or combine marks with other words without approval.
- Do not use Rosta branding to imply partnership or endorsement.
Standard copyright notice
© 2026 Rosta Pty Ltd. All rights reserved.
Rosta, SURE Score, Roo and Broadcast Engine are trademarks of Rosta Pty Ltd.
Registered in Australia.
Include this notice in full on all print materials, app store listings and formal partner communications. The footer copyright line (© year Rosta Pty Ltd.) is sufficient for web pages.
Questions about using the brand, or a request for approval: [email protected].