Skip to main content

​
Best Practices

Explore best practices for displaying date and time across ServiceTitan.

​
Use standard formats

Use standard, easily recognizable formats for dates and times.
  • Date (US): Use MM/DD/YYYY format.
  • Time: Use 12-hour format with am/pm (e.g., “3:00 pm”)
Use full month names when clarity is critical or ambiguity is likely (e.g., in global contexts).
  • Example: The appointment is on September 10, 2026, at 3:00 pm PST.
Do
Use MM/DD/YYYY for US regions or clear full month names.
Don’t
Avoid informal or inconsistent formats that may confuse users.

​
Global Audiences

Consider using the 24-hour format for a global audience to avoid ambiguity. Default to UTC when:
  • The user’s time zone isn’t known.
  • The action is system-level (logs, audit trails, global reporting).
  • The user is part of a distributed or international team.
Use tenant time zone when:
  • The user expects the time to be “local” (e.g., scheduling, invoicing, time tracking).
  • The UI can clearly communicate the time zone (e.g., “PST,” “CST,” or “Tenant Time Zone: Pacific Time”).
Do
Consider using the 24-hour format for a global audience to avoid ambiguity.
Don’t
Avoid mixing 12-hour and 24-hour formats incorrectly.

​
Include Time Zones

Do
Specify time zones when times are relevant to users in different regions.
Don’t
Avoid omitting time zones when the time is relevant to a geographically diverse audience.

​
Be Consistent

Do
Be consistent with formats throughout your content to avoid confusion.
Don’t
Avoid switching between different date and time formats within the same content.

​
Leading Zeros

When using UTC, use two digits for the hour and two digits for the minutes. When specifying a 12-hour time with a time-zone abbreviation, a leading zero is not required for a single-digit hour.
Do
Use a leading zero for single-digit UTC hours. You may omit it for 12-hour times that include a time-zone abbreviation.
Don’t
Avoid omitting the leading zero from a UTC hour.

​
Relative Time References

Do
Use relative time references where appropriate for user convenience.
Don’t
Avoid vague or unclear time references.

​
Avoid Ambiguity

Do
Use full month names to avoid ambiguity.
Don’t
Avoid using abbreviated month names if they can be misinterpreted. The exception is in Toolbar Filters, where additional context is provided by the date icon and the surrounding component.

​
Date Ranges

Do
Use en-dashes for date ranges and ensure clarity.
Don’t
Avoid using hyphens for date ranges.
Last modified on September 16, 2026