Skip to Content
BayWise SchedulerHow-To GuidesWrite a bay description

Write a Bay Description

Every bay carries a written description, and it does real work. Where two bays look identical in their structured setup, the description is what separates them.

If you do one thing before going live, do this one.

Who can do this: Location Managers, Org Admins and Account Owners.


What a good description contains

Three things, in this order:

  1. What the bay is for — the work it does, in the words your shop uses
  2. The key equipment — what makes it suitable
  3. What it must not receive — the exclusion

The third is the one most shops leave out and the one that pays for itself fastest.

“Mechanical bay with a two-post lift for general service, brakes and suspension. Also handles exhaust work. Not for bodywork, paint, alignment, or EV high-voltage jobs.”


Writing one

Open the bay and find the Notes field

Beside it is a quality indicator and a word count.

Write what the bay is for

Be specific. “General mechanical” is weaker than “general service, brakes, suspension and exhaust”.

Name the equipment that matters

The equipment that makes this bay the right or wrong choice — the lift type, the rack, the booth. Not an inventory.

State what it is not for

Explicitly. This is the sentence that stops the wrong work arriving.

Check the quality indicator


What the quality indicator is telling you

ReadingMeansDo
Add a descriptionEmptyWrite one
A bit shortNot enough to distinguish this bayAdd the key capabilities
Too genericCould describe any bay in the shopName specifics, and what it is NOT for
GoodUsableConsider adding the exclusion
GreatNames capabilities and exclusionsNothing

The top rating requires an exclusion. That is deliberate: a description without one tells BayWise what a bay can do but nothing about what it should be protected from.


Worked examples

A rapid-service bay at Sharma Motors, Mumbai

“Express bay for quick-turnaround work — oil and filter changes, fluid top-ups, bulbs, wipers, battery replacement and basic diagnostic scans. Two-post lift, high turnover, several cars a morning. Not for brakes, suspension, engine work, bodywork, or anything expected to take more than an hour.”

A body bay at Santos Body Works, São Paulo

“Collision repair bay with a frame bench and welding equipment. Handles structural straightening, panel replacement and denting on cars and light commercials. Vehicles typically hold this bay for two to four days. Not for paint or refinishing — the booth handles those — and not for routine mechanical service.”

A diagnostics bay at Müller Werkstatt, Berlin

“Electrical and diagnostics bay with a full scan tool set, oscilloscope and ADAS calibration targets. Fault-finding, ECU work, wiring faults, sensor faults and calibration after windscreen or camera work. Bay time is unpredictable by nature. Not for routine servicing, tyres, or heavy mechanical work needing a two-post lift.”

A detailing bay at Al Futtaim Auto, Dubai

“Detailing and final preparation bay. Wash, machine polish, ceramic coating, interior valet, and the final prepare before customer handover. Also takes standalone detailing bookings. Not a repair bay — no lift, no mechanical or body work.”


What makes a description weak

WeakWhyBetter
”General bay”Describes every bayName the specific work
”Can do most things”Invites everythingName what it cannot do
”Bay 4”Says nothingDescribe the work, not the number
”Big bay for big jobs”Not a distinction BayWise can useName the jobs
A list of every tool in the drawerBuries the signalName the equipment that decides suitability

Using AI to draft one

On plans that include AI-assisted features, Compose with AI drafts a description from the bay’s role, capabilities and equipment.

Treat it as a first draft. It will describe what the bay can do accurately; the exclusion — the part that matters most — is the part you know and it does not.

Use AI to set up a bay


Keeping them true

Descriptions go stale. A bay that gains an alignment rack, loses a lift, or is repurposed needs its description updated the same week.

Re-read all your bay descriptions once a quarter. It takes fifteen minutes and it is the cheapest maintenance in the product — a description that no longer matches the shop is the commonest cause of a plan people distrust.


Common questions

How long should it be? Two to four sentences. Long enough to distinguish the bay, short enough that somebody will actually read it.

Does the description override the capabilities? No. Capabilities are the boundary — work never lands in a bay whose capabilities do not cover it. The description is what distinguishes bays that the structured data does not separate.

Should I write about the technician who usually works here? No. Describe the bay. People move; bays do not.

We have eight identical bays. Then describe them identically. Real interchangeability is useful information — it means the plan can use whichever is free.

Can I write it in a language other than English? Write it in the language your team thinks in. It is your workshop’s description of your workshop.