Content

Write for the person doing the job. Lead with the action or result, use the terms they already use in the workshop, and remove words that do not change the decision.

Labels and actions

• Name buttons with a verb and object: “Create invoice”, “Assign mechanic”, “Save changes”.
• Use sentence case for headings, labels, tabs, and menu items.
• Match a destructive confirmation to its real consequence: “Delete quote” rather than “Continue”.
• Use consistent Workshop1 vocabulary. The tenant is a Workshop.
• Put explanation in help text, not inside the control label.

Messages

Say what happened and what the person can do next. Preserve their entered values after validation or server failure. Avoid blame, jokes in error states, and raw implementation details.

Dates, times, money, and units need explicit context. Use the customer or Workshop timezone where the workflow expects it, and align comparable numbers with tabular figures.