Book the annual technical inspection

When to use

A company vehicle is approaching its periodic technical inspection due date and needs to be booked and passed. Not for renewing the mandatory civil insurance that usually rides along — use vehicles.octa-renewal. Not for a vehicle just bought or imported — its first registration and inspection belong to vehicles.add-vehicle.

Before you start

• The due date is known: read it from the vehicles module or look it up on csdd.lv by registration number.
• The company has an account on the CSDD e-services portal, or the booking is made by phone at the station.
• Any known defects (warning lights, worn tyres, cracked glass) are listed — they change S3.

What a run requires2

The trail8 steps

1. S1

   Confirm the due date and the windowagent

   Look up the vehicle's inspection due date and the earliest date a new certificate counts from. In Latvia the inspection must be done by the deadline tied to the vehicle's registration ⚠ verify exact rule for the current vehicle category (passenger, van, truck differ), csdd.lv.

   Done when the due date and the last valid booking date are written in the vehicles module.

2. S2

   List defects and pre-checkagent

   Collect driver complaints and last year's remarks; walk the obvious items: tyres, lights, brakes feel, fluids, registration certificate present.

   Done when a short defect list exists, each item marked fix-before / risk-it.

3. S3

   Decide on repairsownerneeds approval · owner

   Approval · S3 · owner — the run stops until a named person records the decision

   Present the defect list with rough repair cost vs the risk of a failed visit.

   Done when the owner has named which defects get fixed before the inspection and by whom.

4. S4

   Book the slotagentneeds approval · owner

   Approval · S4 · owner — the run stops until a named person records the decision

   Find a station and a slot before the due date, with enough margin for a re-visit. Confirm the fee for the vehicle category ⚠ verify current fee per category, csdd.lv or the station's price list. Book it.

   Done when a booking confirmation with date, time, station and vehicle exists.

   ⛔ Do not book a slot after the due date "because it was easier" — that is a planned offence, not a booking.

5. S5

   Bring the vehicleowner

   A named driver takes the vehicle to the station with the registration certificate.

   Done when the vehicle is at the station at the booked time.

6. S6

   Record the resultagent

   If passed: store the certificate number, date, station and odometer reading in the vehicles module. If failed: record the defect list, send it to the owner with a repair proposal, then re-book (back to S4 for the re-visit; the owner approves only the new cost, not the whole playbook).

   Done when the vehicles module shows either a passed certificate or an open failure with an owner decision pending.

7. S7

   Re-arm the watchagent

   Set the next deadline from the new certificate date and add a reminder well before the window opens — bc tasks add "inspection <plate> window opens" --due <date>.

   Done when the deadline watch shows the vehicle with its next due date and a reminder task exists.

8. S8

   Hand backagent

   Send the owner a three-line summary: passed/failed, certificate date, next due date, and any defects deferred to next year.

   Done when the owner has the summary.

Checks — how we know it worked

• The certificate in the vehicles module shows this registration number, a date inside the window, and a
• The next due date in the watch matches the certificate date plus the inspection period for that category.
• OCTA policy is valid at least through the inspection date (if it lapses first, run vehicles.octa-renewal).
• No open failure without an owner decision.

If it goes wrong

What each step leaves behind

1. S1the due date and the last valid booking date are written in the vehicles module.
2. S2a short defect list exists, each item marked fix-before / risk-it.
3. S3the owner has named which defects get fixed before the inspection and by whom.
4. S4a booking confirmation with date, time, station and vehicle exists.
5. S5the vehicle is at the station at the booked time.
6. S6the vehicles module shows either a passed certificate or an open failure with an owner decision pending.
7. S7the deadline watch shows the vehicle with its next due date and a reminder task exists.
8. S8the owner has the summary.

Evidence to keep

Booking confirmation · passed certificate (number, date, station, odometer) or failure defect list · owner decisions in S3 and S4 (who, when, cost approved) · next due date as written to the watch.

How this playbook improves

After every 6 runs ask: how many vehicles passed first time, and which deferred defect caused a repeat visit? Was any deadline missed because the window was read wrong, and did the reminder fire early enough? If a category's fee or period keeps needing a lookup, record the value once in the vehicles module and cite it from the step; a new version says in its change note which step moved and why.