Workshop: plan work and complete quality checks
Use this guide after intake and estimate decisions. It follows an operation from dispatch through technician work and accepted quality checks, then prepares the repair order for the advisor's handover.
The steps are grounded in the reviewed Odoo 20 source, with no new runtime test. The failed-QC path has known verification limitations described below; do not treat this as proof that a complete rework cycle has passed acceptance testing. Begin with the setup guide if operation types, resources or QC templates are missing.
Put the responsible people in place
A Workshop Dispatcher, Workshop Manager or Workshop Administrator controls operations and bookings, subject to company and site access. A Technician needs an active assignment to the specific operation to record work. A Quality Inspector, Workshop Manager or Workshop Administrator can record QC outcomes, with access to the relevant records. The Dispatcher role alone does not grant editing access to QC results. A Service Advisor, manager or administrator handles delivery closure.
Before dispatch, check the customer's current decision and agreed scope. Creating an operation or selecting Mark Ready does not itself record customer authorization. Ask the parts team to establish the required stock readiness, and configure the applicable operation and final-release QC checklists.
1. Prepare and assign the operation
- Open Workshop → Work Execution → Operations and create the work under the correct open repair order. Give it a clear operation name, select the applicable operation type, and record planned dates and labor estimates.
- In Instructions and Notes, write the instructions the assigned technician should follow. Add blocking predecessor operations under Dependencies when work must wait for another operation. Review parts readiness and any active holds.
- If the operation requires QC, enable QC Required and select the configured checklist version. A draft checklist cannot be assigned. The eventual accepted QC must use this same version.
- Under Assignments, add the technician user and assignment role, with the assignment active. Select Mark Ready, then Dispatch. Dispatch requires an active assignment.
Use Unassigned Ready, Blocked Operations and Planned Finish Passed for dispatcher follow-up. The Ready state alone does not mean every execution blocker has cleared.
2. Book suitable resources
For work that needs workshop capacity, open Planning → Schedule and create a booking for the operation. Choose the site and the needed technician resource, bay or equipment; at least one resource is required. Set the planned start and end, then check setup, cleanup and travel buffers. Buffered occupancy can be longer than the planned work interval.
Select Confirm. The booking checks resource qualifications, working hours, maintenance availability and overlapping bookings. Correct unsuitable or unavailable resources before proceeding. The Capacity Schedule Override role and recorded reason apply only to eligible overlap conflicts; they do not override qualification or availability failures.
Check that the planned technician also has an active operation assignment. A manually created booking is not a substitute for that assignment. The optional Dispatch Recommendations workspace supports a separate review-and-accept path: acceptance rechecks readiness, creates and confirms the booking, and adds the technician assignment when needed. Review the result of each acceptance; a batch can contain both successes and failures.
The dispatcher selects Start on the confirmed booking when its occupancy begins. Starting rechecks suitability and availability. Operations with mandatory capacity requirements need a confirmed or in-progress suitable booking before execution. Keep that booking active through the operation's completion checks, then complete it when the occupancy is finished.
3. Record the technician's work
- The assigned technician opens Work Execution → My Work Queue or Ready to Start, checks the vehicle, operation and instructions, and selects Accept.
- Select Start Work when work begins. This starts a productive work session. If a blocker is reported, have its responsible team resolve it before starting.
- Use Pause when work is interrupted and provide a reason. Use Resume when work resumes; readiness is checked again. Stop ends the technician's current work or pause interval without completing the operation.
- Record progress and the completed work in the technician notes. When QC is required, stop the productive interval when hands-on work ends and arrange the quality check while the operation remains in progress.
Common blockers include a closed repair order, incomplete predecessors, blocking holds, parts that are not ready, linked stock execution that has not reached its readiness gate, an unaccepted required incoming handoff, or a missing suitable mandatory capacity booking. Visible Blockers helps the technician identify work needing attention. Do not mark a part ready merely because it was ordered; the parts team must verify the required stock actions.
4. Complete operation QC before completing the operation
The quality reviewer opens Quality & Customer → Quality Control, Open QC, or the operation's QC button. Create the QC inspection for this repair order and operation, choose Operation scope, and use the configured checklist version.
- Select Start QC. Applicable checkpoints are copied into the inspection, preserving the checklist instructions and requirements for that attempt.
- Under Checkpoint Results, record an outcome for each checkpoint. A required checkpoint cannot be marked Not Applicable. Add the required evidence through Result / Evidence and record useful notes.
- Select Submit QC. Missing outcomes or required evidence block submission. A failed blocking checkpoint rejects the QC and creates a defect; without a blocking failure, the inspection becomes Accepted. Review any nonblocking failures as part of the quality team's procedure.
- For an accepted inspection, return to the operation. The assigned technician selects Complete after checking the work and completion note. A QC-required operation cannot complete until matching operation QC is accepted. Other technicians must have ended their intervals, all active holds must be resolved, and the execution gates must still pass.
- The dispatcher completes the in-progress booking when its resource occupancy has finished. Booking completion and operation completion are separate records.
When QC fails
Keep the rejected inspection and defect history. For an operation-level defect, a dispatcher, manager or administrator can use Create Correction to create a linked correction operation. That correction needs normal planning, assignment and execution. The source requires a completed correction operation before the quality team can verify its defect.
However, the reviewed version has both a defect Verify control visibility mismatch and an access-permission limitation in verification. The control can remain hidden after correction creation, and the supplied roles do not grant the update access needed for the linked rework record. Ask the manager and implementer to correct and validate this path before relying on it; do not bypass the defect or change its audit fields to force closure.
The same Create Correction route is not available for a final-release defect with no operation. A rejected final inspection therefore also needs explicit manager and implementer follow-up. All unverified QC defects block repair-order closure, even if a later inspection is accepted. This guide does not promise a complete failed-QC recovery path for the reviewed version.
5. Prepare final release and customer handover
When the repair order requires final QC, the quality reviewer creates an inspection with Final Release scope using the order's configured final checklist version. Complete its checkpoints and evidence, then submit it. The order requires an accepted inspection for that configured version before it can close.
The advisor uses Home → Delivery & Follow-up to review the visit. Confirm all operations are completed or legitimately cancelled, the configured final QC is accepted, and every QC defect is verified. Review the customer's outstanding decisions and follow-up needs.
On the repair order's Delivery tab, choose the closure outcome. For Delivered, select the actual recipient from the order's customer, owner or contact, confirm vehicle custody completion and record the customer's delivery acknowledgement. Record the outgoing odometer and follow-up information when available, then select Close when the handover is complete.
Closing records the visit's closure and delivery details. It does not create an invoice, collect payment or settle an insurer claim. Complete those tasks through your separately configured Sales and Accounting procedures.