A clearer service scope
Separate a repair task from a change to the underlying design.
Identify first
Equipment identification is the beginning of a useful service conversation. Gather the available history and describe the observed issue without jumping directly to a solution. Missing information should remain an explicit question.
Distinguish the work
Repair, refurbishment and upgrade can involve different reviews and acceptance evidence. Use precise language in the scope. A familiar label is not a substitute for understanding the intended intervention.
Plan the record
Decide what information will be returned at completion while the work is being scoped. This helps connect the activity to the lifecycle record and avoids a handover built from disconnected notes.