Every Word Matters
Brand System v10.0 — Micro-Copy
Micro-
Copy
& UI Text
Copy
& UI Text
The complete library of every piece of text in the GFS system.
Words are interface. Every loading message, every empty state, every error, every button label is designed to sound like GFS: clear, calm, precise, human.
Loading
Empty States
Feedback
Terminology
01Loading Messages
Never show "Loading..." — every loading state should reflect what the system is actually doing. These messages rotate contextually based on the operation being performed. They reinforce GFS's domain: cold chain, compliance, logistics, data.
Cold Chain
Checking the cold chain...
Temperature data screens, compliance views
Inventory
Scanning inventory...
Warehouse views, stock lookups
Compliance
Verifying temperature logs...
Audit reports, compliance dashboards
Network
Connecting to the network...
Initial load, reconnection attempts
Data Sync
Pulling the latest data...
Dashboard refresh, data tables
Shipments
Syncing shipment status...
Shipment tracking, logistics views
Analytics
Crunching the numbers...
Reports, analytics, aggregated views
Routes
Mapping your routes...
Route planning, delivery maps
Validation
Validating compliance...
Form submission, record verification
Security
Securing your session...
Login flow, session refresh
Dashboard
Preparing your dashboard...
First load of main dashboard view
General
Almost there...
Fallback for extended load times (>3s)
Rule: Match the loading message to the operation context. If the system is fetching temperature data, say "Checking the cold chain..." not "Loading..." Use "Almost there..." only as a fallback after 3+ seconds of wait time.
02Empty States
Empty states are opportunities, not dead ends. Each one acknowledges the absence of data while guiding the user toward action. The tone is calm, slightly warm, and never alarming. Icons provide instant visual context.
No shipments yet.
Ready to ship?
Your order queue is clear.
Time to grow?
Nothing matches those filters.
Try adjusting.
All quiet on the supply chain.
No new notifications.
No outstanding invoices.
Nice work.
Welcome to GFS.
Let's get you started.
Frosty lost signal.
Check your connection.
Something broke.
We're already on it.
Voice rules for empty states: Lead with what happened (no data, no results). Follow with what to do next. Keep it under 15 words. Use action buttons when there is a clear next step. Never blame the user.
03Success Messages
Success messages are brief confirmations. They confirm the action, state the result, and get out of the way. The tone is satisfied but not celebratory. No exclamation marks. No "Congrats!" — just clean confirmation.
Shipment
Shipment locked in. Tracking is live.
Order
Order confirmed. Your rep has been notified.
Save
Changes saved. You're good.
Payment
Payment received. Balance updated.
Upload
File uploaded. Processing now.
Export
Export ready. Check your downloads.
Delete
Removed. This can't be undone.
Login
Welcome back, Michael.
Pattern: [What happened]. [What's next or current state]. Two short sentences. First confirms the action. Second tells the user what to expect. Delete confirmations use warning color — they are successes with weight.
04Error Messages
Error messages must be honest about what happened and clear about what the user can do. Never use technical jargon. Never say "Oops!" — this is a professional system. State the problem, suggest a fix.
Network
Can't reach the server. Check your connection and retry.
Permission
You don't have access to this. Contact your admin.
Validation
Some fields need attention. Check the highlighted items.
Timeout
That took too long. Try again or contact support.
Conflict
Someone else edited this. Refresh to see the latest.
Not Found
That doesn't exist anymore. It may have been removed.
Rate Limit
Too many requests. Wait a moment and try again.
Generic
Something went wrong. Try again or reach out to support.
Pattern: [What happened]. [What to do about it]. Never blame the user. Never use "Oops", "Uh oh", or any cutesy language. Rate limit uses warning color because it is recoverable without action — just wait. Generic is the fallback; use specific messages whenever possible.
05Button Labels
Every button in the GFS system uses one of these standard labels. Labels are verb-first, specific, and under 3 words. Button text is always title case. No "Click here". No ambiguity.
Primary Actions
Secondary Actions
Destructive Actions
Navigation
Label rules: Primary = the main action on any screen. Only one primary button per view. Secondary = alternative or back-out options. Destructive = irreversible. Always requires confirmation. Navigation = non-committed browsing. Ghost style only.
06Tooltip Text
Tooltips provide concise help text when a user hovers or focuses on an element. They are under 80 characters, action-oriented, and never repeat the label they describe.
Temperature Badge
Last recorded temp for this reefer unit
Compliance Score
Percentage of shipments within threshold this period
Route ID
Click to view full route details and stops
Signal Indicator
Green = live data. Gray = last sync 5+ min ago
Export Button
Download this view as CSV or PDF
Filter Badge Count
Number of active filters applied to this view
Timestamp
All times shown in Eastern (ET)
Lock Icon
This record is finalized and cannot be edited
Sparkline Chart
7-day trend. Click to expand full chart
User Avatar
Last active 2 hours ago
Notifications Bell
3 unread alerts. Click to view all
Keyboard Shortcut
Press / to search from anywhere
Tooltip rules: Max 80 characters. No period at end unless multi-sentence. Use sentence case. Never duplicate the element label. Provide information the user can't already see.
07GFS Internal Language
These are the proprietary terms used within the GFS system. Each term is deliberately short, memorable, and functional. They create a shared vocabulary that makes communication faster and more precise across the organization.
Cold Lock
A verified temperature-compliant shipment. The shipment has maintained required temperatures from origin to destination without any breach events.
"Shipment SH-4471 achieved Cold Lock — all 14 checkpoints confirmed within range."
Signal
A real-time tracking data point from any sensor, device, or system in the GFS network. Signals include GPS, temperature, humidity, and door-open events.
"We're receiving strong Signal from the reefer unit every 30 seconds."
Chain Check
A cold chain verification scan performed at transfer points. Confirms that custody handoff maintained temperature integrity throughout the transition.
"Run a Chain Check at the dock — we need confirmation before accepting the load."
Source Lock
Verified origin and traceability confirmation. Confirms the product's source facility, production date, lot number, and chain of custody from origin.
"This lot has full Source Lock — traced back to Bongards plant, batch B-2026-0419."
Frost Line
Temperature threshold alarm. Triggered when a reefer unit, warehouse zone, or transit container approaches the boundary of its acceptable range.
"Frost Line alert on Unit R-3302 — temp hit 38.5F, threshold is 40F."
Pulse
The real-time operations dashboard. Shows live status of all active shipments, temperature readings, alerts, and system health across the entire GFS network.
"Check the Pulse — I want to see where all active shipments are right now."
Grid
The GFS distribution network. Refers to the complete system of warehouses, routes, carriers, and facilities that make up GFS's operational footprint.
"We've expanded the Grid to include three new distribution points in the Midwest."
Trace
A full product traceability record. The complete history of a product from source to shelf, including every handler, temperature reading, location, and timestamp.
"Pull the Trace on lot L-7829 — the customer wants full provenance documentation."
Usage rules: Always capitalize GFS terms when used as proper nouns in the system. In UI, bold the term on first use. In documentation, italicize. Never abbreviate these terms. They are short enough already.