On this page
Dates and numbers
How to format dates, numbers, currency, punctuation and lists.
These guidelines apply to dates, numbers and currency in Nebula components and the products built with them. Your product's shared formatter produces these, so what you choose is which one to ask it for.
Dates
Dates come in four lengths.
| Length | Example | Where to use it |
|---|---|---|
| Numeric | 14/01/2026 | Table cells and column headers, where the column is narrow and every row carries a date |
| Short month | 14 Jan 2026 | Cards, summaries, sentences and confirmations, where the date is read once rather than scanned |
| Long month | 14 January 2026 | A page heading, where there's one date and plenty of room |
| ISO | 2026-01-14 | Storage, sorting, filtering, import and export. Never shown to your user |
Numeric is the default.
A numeric date is ambiguous if your reader expects month first, so where the date carries weight, such as a payment date or a contract end, use the short month form.
These four are day-first, because every market Nebula serves today reads dates that way. A market that reads month-first will need its own set.
Where a row needs the time as well, keep the date's length and put the time after it. Show only the parts that carry meaning: a seconds value in a payment history is noise.
Times
Use the 24-hour clock, HH:mm, unless the market or the use case needs something else. The default overrides the locale on purpose, because a timeline read under pressure is where a missing am or pm becomes a real error.
Date ranges
Use to. Avoid hyphens or dashes in running text.
Do
14 Jan to 28 Feb 2025
Don't
14 Jan - 28 Feb 2025
Relative time
When showing elapsed time or time remaining, use natural language units. Switch from smaller to larger units at the appropriate threshold.
Time remaining takes the same units, with About where the estimate is rough.
Do
1 hour ago, 3 days ago, 2 months ago
About 1 hour remaining
Don't
60 minutes ago, 1 days ago
3,600 seconds remaining
Seasons
Avoid references to seasons, they are hemisphere-dependent and ambiguous. Use months or quarters instead.
Do
April to June 2025
Don't
Autumn 2025
Numbers
Use numerals for every number, including one to nine, and including at the start of a sentence. Someone scanning for a figure will find a numeral faster than a word.
Do
3 accounts match this address.
Don't
Three accounts match this address.
Fractions are the exception, because a numeral fraction reads as a date or a ratio. Spell them out in running text.
Do
Two-thirds of accounts on this tariff
Don't
2/3 of accounts on this tariff
The rest is formatting, and applies wherever a number appears.
- Use the % symbol rather than the word, and numerals for measurements, currency and data values in tables.
- Separate thousands with a comma: 1,200 not 1200.
- Use a full stop for decimals: £12.50 not £12,50.
- Spell out large round numbers: 81 million not 81,000,000. Use K, M or B only in a chart or a narrow table cell, with no space: 71M records.
Currency
Don't write a currency format. Pass the amount and the market to your product's shared formatter, which reads CLDR, the locale database every browser ships, and already knows where the symbol goes and which separators to use.
| Market | Locale | Renders as |
|---|---|---|
| UK | en-GB | £1,200.50 |
| Australia | en-AU | $1,200.50 |
| Belgium | fr-BE | 1 200,50 € |
| Belgium | nl-BE | € 1.200,50 |
Belgium needs two answers rather than one. Between fr-BE and nl-BE the symbol moves and both separators swap, which is why there's no single Belgian format to write down.
Two decisions are still yours. Disambiguate a dollar amount only where more than one dollar currency can appear on the same screen, and use the tax term the market uses.
Punctuation reference
| Mark | Rule |
|---|---|
| Full stop | Not at the end of standalone labels, headings, or buttons. Use in body content and multi-sentence messages. |
| Oxford comma | Use in lists of three or more: Name, address, and date of birth |
| Colon | Use to introduce a list or simplify a complex sentence. Not at the end of a form field label. |
| Em dash (—) | Do not use in product content. Use a comma, colon, or full stop instead. |
| En dash (–) | For numerical ranges only when to cannot be used, e.g., in tight table cells: FY2024–25. No spaces around it. |
| Hyphen | For compound modifiers: up-to-date records, third-party supplier. No spaces. |
| Ellipsis (...) | Only for truncated content or loading states: Loading.... Not for effect or in button labels. |
| Ampersand (&) | Use and, which an ampersand doesn't translate cleanly into. Where a navigation label is too wide to fit and nothing else will give, & is the one place it's allowed. |
| Exclamation mark | Avoid. Never in error messages, failure states or alerts. |
| Semicolon | Avoid entirely. Use a full stop or comma instead. |
| Slash (/) | Do not use to combine words: avoid and/or, his/her. Choose one or restructure. |
| Emoji | Never use in product content. |
Lists
- Use bulleted lists for two or more concepts of equal weight.
- Use numbered lists for sequential steps.
- Lead into a list with an introductory phrase ending in a colon: You can choose:
- Use parallel construction, if items are actions, all should start with a verb; if nouns, all should be nouns.
- Capitalise the first letter of each list item.
- Do not use terminal punctuation in list items unless the item is a complete sentence. If one item needs a full stop, all items need one.
Tables and columns
- Write column headers as nouns in sentence case.
- Put a unit or currency symbol in the header rather than in every cell: Amount (£), then 120.50.
- Show an empty cell as a dash, which keeps the column scannable. Write None only where the absence is itself something your user acts on, such as an account with no payment plan.
- Use the same date length in every column. Two lengths in adjacent columns will read as two different kinds of date.