You tell someone about your car, they take careful notes, and the details are all there. The noise, the problem, the thing you asked them to check. Then you notice the name at the top.
It belongs to someone else.
That’s a situation I wanted the design to make harder to miss. A note can sound completely convincing while being attached to the wrong visit. Reading it more closely won’t necessarily reveal the mistake, because the words themselves might be fine.
When I worked through an example of a service advisor’s workspace, I found myself asking a more basic question than “Did we get that sentence right?”
Whose visit is this?
The example uses made-up customer details and two conversations. There’s an early check-in that hasn’t been connected to a visit. Later, there’s a discussion about an inspection, attached to an appointment but waiting for that earlier check-in.
The advisor has to work out where the first conversation belongs. Marking it as a walk-in doesn’t connect it to the appointment. Attaching it to another visit doesn’t help this customer either.
Once the check-in is connected to the intended visit, the inspection note becomes available to review. It still needs to be read. Finding the right home for a note doesn’t make everything inside it correct.
I care about that order because the customer shouldn’t have to discover the mix-up after everyone has started treating the record as settled.
Leaving a blank takes some nerve
An empty customer field looks unfinished. There’s a temptation to fill it so the page feels complete. But “we haven’t worked this out yet” is useful information, especially to the next person who opens the screen.
I’d rather leave that uncertainty visible than give a guess the appearance of a fact.
When the advisor does choose a visit, the name and car details should change together. Otherwise, they could select the right appointment and still leave the previous customer’s vehicle on screen. A person reading quickly would have to spot a contradiction the software could have avoided creating.
And the choice needs to be easy to revisit. The screen can keep the details together, but it can’t prove the advisor chose the right customer. Someone should be able to open the conversation, see where it was attached, and correct it.
Then we can talk about the words
Another draft in the example says the front brake pads measure 4 mm. The conversation says three.
That mistake needs a different kind of attention. The advisor has to compare the note with what was said, change the number, and leave a reason. Keeping the old and new values makes the correction understandable to someone who comes along later.
I’d test these problems separately. Could an advisor notice a perfectly readable note under the wrong visit? Could they notice the wrong measurement under the right one? I don’t yet know how often either mistake would be caught.
From the customer’s side, this is a fairly ordinary expectation. I shouldn’t need to understand how the notes were made to expect that they describe my car, belong to my visit, and can be corrected when something is wrong.