Date, Time, and Timezone Copy Audit Workflow in Figma

Your report will be ready Friday at 9:00. That sentence looks finished until the product has customers in three countries, daylight saving changes, a report crosses midnight, and support asks which Friday the interface meant.

Date and time bugs are often treated as formatting bugs. Many are content-model bugs: the design never established whose timezone applies, whether the value is exact or estimated, or what should happen after the event passes. CopyDoc helps teams export, review, update, and sync text across Figma. It can make the audit systematic, but product and engineering must define the underlying temporal rules.

Find every place time appears

Export the relevant Figma text and classify strings by job rather than searching only for colons or month names. Include:

• scheduled starts and ends;
• deadlines and expiries;
• relative timestamps such as 3 minutes ago;
• activity and audit history;
• date ranges;
• recurring schedules;
• durations and countdowns;
• estimated delivery or processing times;
• timezone selectors and settings;
• empty, unknown, delayed, cancelled, and overdue states.

Search for words such as today, tomorrow, soon, later, until, ago, remaining, and local time. These are easy to miss in a numeric date review and are often the most ambiguous strings.

This is different from a broad localization workflow or an audit-log copy review. The focus here is temporal meaning across product surfaces, including boundaries that translation alone cannot resolve.

Give every value a contract

For each surface, record:

Question	Example decision
What event does the value represent?	webinar start, not room opening
Is it exact or estimated?	estimated processing window
Which timezone governs it?	venue timezone
Can the viewer change timezone?	yes, account preference
Does the date include a year?	include when outside current year
What happens after it passes?	replace countdown with Expired
What is stored by the system?	UTC instant plus named timezone

Do not let a static Figma label such as 9:00 AM PST substitute for these decisions. Timezone abbreviations can be ambiguous and daylight-saving labels change. Prefer a recognizable location or explicit offset when the context requires certainty, for example 9:00 AM America/Los_Angeles (UTC-8).

Design boundary fixtures, not happy-path samples

Replace the repeated 12 Jun, 10:00 AM placeholder with a fixture set that forces decisions:

• an event today and tomorrow;
• a date near midnight;
• a range crossing a month or year boundary;
• a daylight-saving transition;
• two viewers in different timezones;
• a locale using 24-hour time;
• a long translated month name;
• an unknown or not-yet-scheduled value;
• an expired deadline;
• a duration longer than 24 hours.

Create expected strings for each fixture. A design that fits May 3 may break with a long localized date. A countdown that says 1 days reveals plural rules the ideal mockup hid.

Match wording to certainty

Use an exact timestamp only when the system can honor it. For uncertain processes, write Usually ready within 2 hours or Estimated by 4:00 PM rather than promising a deadline.

Relative time works for recency but becomes vague around decisions. 3 minutes ago is useful in an activity feed; Your access expires soon is poor guidance for a security link. Show the exact deadline when action depends on it.

Words like today and tomorrow should use the viewer’s defined timezone and update correctly after midnight. Consider pairing them with an absolute date where mistakes matter: Tomorrow, 7 November, 9:00 AM.

Use CopyDoc to review the system as a set

Export the text to a spreadsheet and add columns for screen, state, event, timezone source, certainty, locale fixture, owner, and implementation key. Group strings that express the same event. This reveals drift such as:

• Ends at, Expires, and Available until used for one rule;
• a booking page showing venue time while confirmation copy implies viewer time;
• one screen using 12-hour time and another using 24-hour time;
• a Figma countdown that engineering never intended to implement.

Agree on preferred patterns, update the source rows, and sync approved copy back into Figma where the workflow supports it. Review the resulting layouts rather than assuming a successful import means every string fits.

For reusable terminology and approved patterns, the Figma content source-of-truth strategy is a helpful companion.

Reconcile with implementation

Ask engineering to demonstrate values around timezone and calendar boundaries. Compare actual UI strings with the approved fixtures. Check browser locale, account preference, event timezone, and device timezone independently; they may not be the same.

Verify screen readers announce the date coherently, machine-readable date controls have useful labels, and color is not the only indicator of an overdue or expired state. Support documentation and emails should describe the same deadline using the same governing timezone.

Audit completion checklist

• Every temporal string has a defined event and owner.
• Exact and estimated values are visibly different.
• The governing timezone is known and shown when needed.
• Relative labels have clear rules and absolute fallbacks.
• Boundary, locale, plural, and daylight-saving fixtures have been reviewed.
• Unknown, cancelled, delayed, expired, and overdue states exist.
• Figma text, implementation behavior, emails, and support language agree.
• Approved strings have been rechecked in the actual layouts.

Clear time copy does more than choose a date format. It tells people exactly when something happens, whose clock governs it, and what they can do before or after that moment.

Read as Markdown · Related resource index · Site index for AI agents