UX Writing Guide
Section 2 — Vallejo 1.1.1
Design system
UX Writing Guide
Words are interface. Every label, message, and instruction shapes how members understand and trust Copart. The same rigor we apply to color and spacing applies to language. UX Writing is the one section that carries both the "why" (from the Copart Design Vault) and the "how" (from Vallejo).
Vallejo 1.1.1 — March 2026
Voice & tone charter
Copart's voice is consistent across every touchpoint. Tone adapts to context — but the voice never changes.

Brand voice

Professional
We respect the member's time and money. No fluff, no filler.
"Your bid of $4,500 has been placed."
not "Awesome! You just bid!"
Straightforward
Say exactly what's happening. No jargon unless the audience expects it.
"This lot has a clean title."
not "This vehicle's documentation status is clear."
Confident
We know our platform. Statements, not hedging.
"Bidding closes at 2:30 PM EST."
not "Bidding should close around 2:30 PM EST."
Helpful
Every message moves the member toward their goal.
"Enter your VIN to check eligibility."
not "VIN required."
Vault triad mapping: Professional + Straightforward = Precision (the warmth of competence). Confident = Institutional Confidence (we don't hedge or over-explain). Helpful = Vitality (every message moves the member forward).

Tone spectrum

ContextToneExample
InformationalNeutral, factualThis lot is located in Dallas, TX.
EncouragingWarm, supportiveYou're all set — your watchlist will notify you when bidding opens.
UrgentDirect, clearBidding closes in 2 minutes. Place your bid now.
ErrorCalm, solution-focusedPayment failed — update your payment method to continue.
Rule: Never use humor, sarcasm, or playful language in error states. Members may be frustrated or anxious — meet them with clarity, not cleverness.
Capitalization & punctuation
Sentence case everywhere. Capitalize the first word and proper nouns only.

Sentence case examples

ElementCorrectIncorrect
Page headingsMy saved vehiclesMy Saved Vehicles
Button labelsPlace bidPlace Bid
Nav itemsFind vehiclesFind Vehicles
Tab labelsBid historyBid History
Table headersSale dateSale Date
Menu itemsAccount settingsAccount Settings
Exceptions — always capitalize: Copart, CrashedToys, Copart Dealer Services (CDS), Copart Wholesale Auction, Copart Alliance Gateway, VIN, CDV, NMVTIS, and product names used as proper nouns.

Punctuation rules

RuleExample
No periods on buttons, labels, table headers, nav items, badgesPlace bid not Place bid.
Periods on full sentences in descriptions, helper text, tooltipsEnter the 17-character VIN found on the vehicle dashboard.
Serial (Oxford) comma requiredYear, make, and model not Year, make and model
Em dash (—) for interruption or clause joiningPayment failed — update your payment method.
En dash (–) for ranges$1,200–$3,500 or Mon–Fri
No exclamation marks in UI copyBid placed successfully not Bid placed!
Grammar & tense conventions
Active voice always. Second person for the member. Contractions are fine — but not all of them.

Active voice always

Correct (active)Incorrect (passive)
We saved your bid.Your bid has been saved.
Enter your lot number.The lot number should be entered.
Copart charges a buyer fee.A buyer fee is charged.

Tense rules

ContextTenseExample
Current statePresent3 items in your watchlist
Completed actionPastBid placed successfully
InstructionImperativeEnter your VIN
Future eventFutureBidding opens tomorrow at 10:00 AM EST

Person & pronouns

Use
Second person ("you/your") for addressing the member. First person plural ("we") when Copart is the subject.
"We'll notify you when bidding opens."
Contractions
Allowed: don't, won't, can't, it's, you'll, we'll, you're, we're, that's
Avoid: ain't, y'all, would've, could've
Terminology glossary
Use these terms consistently. Never alternate between synonyms within the same flow or page.
Preferred termNever useNotes
LotListing, item, productCopart's canonical term for an auctioned vehicle
VehicleCar, automobile, unitThe physical object, not the auction entity
BidOffer, price, amountFor both the action and the value
Place bidSubmit bid, make bid, enter bidCanonical CTA verb
WatchlistFavorites, saved items, bookmarksSingle canonical term
MemberUser, customer, clientFor all Copart users
Sign in / Sign outLog in, login, log outTwo words as verb; one word as adjective ("sign-in page")
RegisterSign up, create account, joinCanonical onboarding term
VINVehicle identification number (in UI)Always abbreviation in interface
Clean titleNon-salvage, clear titleIndustry-standard term
SalvageDamaged, wrecked, total lossLegal/industry classification
Pre-bidPreliminary bid, early bidCanonical short form everywhere
Live auctionReal-time auction, active auction"Live" is the canonical modifier
Buy it nowInstant purchase, direct buyCapitalize first word only: "Buy it now"
Buyer feeService fee, transaction feeCopart-specific term
Sale dateAuction date, event dateCanonical field label
LocationYard (internal only), facilityPublic-facing term for Copart sites. "Yard" is internal only.
Item numberRun number, lane numberFor auction ordering
Title typeTitle status, title categoryField label
Damage typeDamage category, loss typeField label
OdometerMileage, milesField label; "miles" in conversational copy
HighlightsFeatures, specs, detailsVehicle summary section
ConditionQuality, gradeVehicle state descriptor
SellerConsigner, provider, vendorEntity listing the vehicle
Storage feesYard fees, holding feesCanonical term
Copart Alliance GatewayLounge, Copart LoungeOfficial name for on-site member facilities
Wholesale / Copart WholesaleSelect, Copart Select, WholecarCurrent brand. Full product name: "Copart Wholesale Auction"
Rule: If a term is not in this glossary, choose the simplest, most common word and use it consistently. Add new terms to the glossary when they appear in more than one flow.
Copy length guidelines
Every UI element has a character budget. These limits maintain scannability and prevent layout breakage.
ElementWord countMax charactersExample
Button label1–3 words20 charsPlace bid
Field label1–4 words30 charsLot number
Placeholder text2–5 words30 charse.g., 12345678
Helper text1 sentence80 chars8-digit number found on the vehicle page.
Error message1–2 sentences120 charsEnter a valid lot number (8 digits).
Toast message1 sentence60 charsLot added to watchlist.
Empty state heading3–8 words40 charsNo saved lots yet
Empty state body1–2 sentences120 charsSearch for vehicles and save them here.
Modal title3–8 words50 charsConfirm your bid
Table header1–3 words20 charsSale date
Badge / tag1–2 words15 charsClean title
Tooltip1–2 sentences100 charsYour maximum bid. Copart bids on your behalf up to this amount.
Nav item1–2 words15 charsMy bids
Rule: If copy exceeds the character budget, rewrite — don't just truncate. Truncation is a last resort for dynamic content only.
Component microcopy patterns
Specific copy patterns for every component type. These are rules, not suggestions.
Buttons
  • Start with a verb. The label describes the action: Place bid, Save to watchlist, Remove lot
  • Be specific. Place bid beats Submit. Remove from watchlist beats Delete.
  • No numerical values in buttons. Never put pricing, amounts, or counts inside button labels. Display values elsewhere in the UI. Buttons are for actions only.
  • Never use: Click here, Submit, OK, Yes, No
  • Destructive: State what will be destroyed — Remove from watchlist
  • Loading state: Present participle — Placing bid…, Saving…
Text fields
  • Labels describe what to enter: Lot number — not Enter lot number here
  • Placeholders show example format only: e.g., 12345678 — never repeat the label
  • Helper text adds context the label can't: 8-digit number found on the vehicle page.
  • Error messages say what went wrong AND how to fix it: Enter a valid lot number (8 digits). — not Invalid input
Alerts & banners
  • Lead with what happened, then what to do.
  • Success: Bid placed — you'll receive a confirmation email.
  • Warning: Your session expires in 5 minutes — save your work.
  • Error: Payment failed — update your payment method to continue.
  • Never use: Oops, Uh oh, Whoops, Something went wrong
  • Never blame the member: We couldn't process your payment — not You entered an invalid card
Toasts & snackbars
  • Confirmation of the action just taken. Past tense, one sentence.
  • Lot added to watchlist. / Bid placed successfully. / Settings saved.
  • Include undo where reversible: Lot removed from watchlist. Undo
  • Auto-dismiss after 5 seconds. No exclamation marks.
Modals & dialogs
  • Title = what this modal is about: Confirm your bid, Remove lot from watchlist
  • Body = what the member needs to know. 1–3 sentences.
  • Primary button = specific action: Place bid, Confirm purchase — never OK or Yes. No pricing in buttons — display amounts in the modal body.
  • Secondary button = Cancel — not No, Go back, Dismiss
  • Destructive: Repeat the consequence — This will permanently remove the lot from your watchlist.
Empty states
  • Heading: Describe what's missing — No saved lots yet
  • Body: Explain how to fill it — Search for vehicles and tap the heart icon to save them here.
  • CTA: Action to resolve — Browse vehicles
  • Never say: No data, Nothing to show, Empty
Tables
  • Headers: Short noun or noun phrase — Sale date, Current bid, Damage type
  • No verbs in table headers
  • Null values: Em dash "—" — never N/A, null, none, or blank
  • Monospace for VIN, lot numbers, bid amounts, timestamps
Badges & tags
  • 1–2 words maximum
  • Status badges: Past participle or adjective — Sold, Awarded, Active, Upcoming
  • Category tags: Nouns — Clean title, Salvage, Flood damage
  • Count badges: Numerals only — 3, 12, 99+
Navigation
  • Top-level items: 1–2 word nouns — Vehicles, My bids, Dashboard
  • Never use verbs in primary navigation items
  • Breadcrumbs match the page title exactly — no abbreviations or rewording
Inclusive language
Copart serves a global audience. Write for everyone.
Gender & identity
  • Gender-neutral by default: "they/them" for unknown members
  • Member — not he or she, his/her
  • Salesperson — not salesman/saleswoman
Jargon & accessibility
  • If a term needs explanation, add a tooltip or inline definition
  • Reading level: Aim for grade 8 (Flesch-Kincaid)
  • No idioms, colloquialisms, or cultural references
  • Person-first language: "members who use screen readers"
Dynamic & adaptive copy
Rules for formatting dates, times, numbers, and handling pluralization and truncation.

Numbers & formats

RuleExample
Spell out 1–9 in body copythree vehicles
Numerals for 10+42 results
Always numerals for prices, bids, lot numbers, counts in UI$1,200 · Lot 78901234
Currency: commas, no cents unless partial$12,500 · $0.50

Date & time formatting

FormatExampleUsage
Abbreviated dateFeb 22, 2026Default for all dates in UI
Relative dateToday, Yesterday, 3 days agoUse within 7 days; absolute after that
Time2:30 PM EST12-hour clock, full timezone abbreviation (EST, CST, PST)
Date rangeFeb 22–28, 2026En dash, no spaces around dash

Pluralization

Always handle three states: zero, one, and many.
CountCopy
0No results or No saved lots
11 result or 1 saved lot
2+24 results or 8 saved lots
Rule: Never show "0 results" — use the zero-state phrasing instead.

Number formatting

TypeFormatExample
Currency$X,XXX$4,500
Large numbersComma-separated1,234,567
PercentagesNo decimal unless needed85% or 99.5%
Lot numbersMonospace, no separators78901234
VINMonospace, uppercase1HGCM82633A004352

Truncation rules

  • Ellipsis (…) after the last full word — never mid-word
  • Minimum 3 visible words before truncation
  • Always provide the full text via tooltip on hover
  • Vehicle titles: truncate after year + make + model — 2024 Toyota Cam…
Do / Don't library
Real examples of correct and incorrect copy across common patterns.

Button labels

Do
"Place bid" / "Save to watchlist" / "Remove lot"
Don't
"Submit" / "Click here" / "OK" / "Yes" / "Process"
Specific verbs tell the member exactly what will happen. Generic labels force them to guess.

Error messages

Do
"Enter a valid email address (e.g., name@example.com)."
Don't
"Invalid input." / "Error." / "Please try again."
Good error messages name the problem and show the fix. Bad ones make the member figure it out alone.

Empty states

Do
"No saved lots yet" → "Search for vehicles and tap the heart icon to save them here." → "Browse vehicles"
Don't
"No data." / "Nothing to show." / "Your list is empty."
Empty states are onboarding opportunities. Guide the member toward the next action.

Confirmation messages

Do
"Your bid of $4,500 on Lot 78901234 has been placed."
Don't
"Success!" / "Done!" / "Action completed."
Specific confirmations prove the system did what the member intended. Vague ones create doubt.

Field labels

Do
"Lot number" / "Email address" / "Zip code"
Don't
"Enter your lot number here" / "Type email" / "Input zip"
Labels name the field. Instructions belong in placeholder or helper text, not the label.

Tone in errors

Do
"We couldn't process your payment. Update your payment method to try again."
Don't
"Oops! Something went wrong. Please try again later!"
Members dealing with payment failures are already frustrated. Be calm and direct — never cute.

Placeholder text

Do
"e.g., 12345678" / "Search by make, model, or VIN"
Don't
"Enter lot number" / "Type here" / "Lot number"
Placeholders demonstrate format — they don't replace labels. Repeating the label wastes the placeholder.

Modal actions

Do
Primary: "Place bid" / Secondary: "Cancel"
Display bid amount in modal body, not in the button.
Don't
Primary: "OK" / "Yes" / Secondary: "No" / "Go back"
The member should understand what each button does without reading the modal body.

Toast messages

Do
"Lot added to watchlist." / "Settings saved."
Don't
"Success! Item has been added to your favorites list!" / "Your changes have been saved successfully."
Toasts are glanceable confirmations. Short, past tense, no exclamation marks.

Navigation labels

Do
"Vehicles" / "My bids" / "Dashboard"
Don't
"Find vehicles" / "View my bids" / "Go to dashboard"
Navigation items are nouns (destinations), not verbs (actions). Members click to go somewhere, not to do something.

Status communication

Do
"Bidding closes Feb 22 at 2:30 PM EST" / "Lot sold — final bid: $12,400"
Don't
"Auction ending soon!" / "This item has been sold."
Specific status copy includes the data the member needs. Vague status creates anxiety and follow-up questions.