The Technician

A technician profile is the digital record that represents a workshop technician in BayWise Scheduler. It is not a login account. It is a resource record — the information the scheduler uses to understand what a technician can do, when they are available, how many jobs they can carry at once, and whether they are present on the floor right now.

A technician can be linked to a login so they can access the system themselves, or they can be managed entirely by service advisors on their behalf. Both modes are common. A master technician who wants to view their own job queue will have a linked account. A sublet tech or a casual who never touches the system directly is still represented as a full technician profile so that advisors can assign jobs to them, track their workload, and capture their contribution to the day’s throughput.

Every scheduled job in BayWise Scheduler has both a bay assignment and a technician assignment. The technician record is what makes the second half of that pair possible.

Skills

Each technician has one or more skill types assigned to their profile. Skills are the primary signal the scheduler uses when generating AI assignment suggestions. When a job requires electrical work, the scheduler restricts its suggestions to technicians who carry the Electrical skill. When a job is flagged for paint preparation, it looks for Surface Prep or Spray Painting skills.

BayWise Scheduler recognises the following 16 skill types:

Skill types at a glance

At Tanaka Auto Service in Osaka, a senior technician might carry Master Technician, Diagnostics, and Electrical — reflecting a broad expertise in modern vehicle systems. At Santos Body Works in São Paulo, a specialist might carry only Denting, Body Assembly, and Frame Straightening — a narrower but deep skill set suited to a collision repair environment.

Skills are assigned and managed in the technician’s profile settings. There is no system-enforced restriction on how many skills a technician can carry, but the quality of scheduling suggestions improves when skill assignments reflect actual daily work patterns rather than theoretical capability.

Availability schedule

A technician’s availability schedule defines their planned working hours for each day of the week. It is a per-day configuration: you set whether Monday is a working day, what time the shift starts, and what time it ends. The same applies individually for Tuesday through Sunday.

This schedule is distinct from clock-in. Availability is the planned schedule — the hours the workshop expects the technician to be present. Clock-in is actual presence — confirmation that they have physically arrived and are ready to take work. Both are required for a technician to be assignable on a given day.

The availability schedule drives two important scheduler behaviours:

1. Constraint checking. When a job is being assigned to a technician, the scheduler checks whether the job falls within that technician’s available hours for the day. A job that extends past a technician’s scheduled end time will produce a conflict warning.

2. Future scheduling. When advisors are scheduling jobs for future dates, availability drives which technicians appear as viable candidates on each day. A technician not scheduled to work on a given Thursday will not appear in the suggestion pool for that Thursday.

Beyond the weekly recurring schedule, technician profiles support exception dates — one-off overrides for a specific date. Common uses:

• Day off. Mark a specific date as unavailable without changing the weekly schedule. At Müller Werkstatt Berlin, where technicians occasionally take a personal day on short notice, advisors add an exception date rather than editing and re-editing the weekly template.
• Half day. Adjust the start or end time for a single date. A technician attending a morning training session might not be available until 13:00 on that date.
• Extended hours. Some workshops schedule technicians for a longer shift on a specific date — for example, a Saturday before a public holiday when demand is unusually high.

Exception dates apply only to the date specified. They do not affect the underlying weekly schedule.

WIP limits

A technician’s WIP limit (Work In Progress limit) sets the maximum number of active concurrent jobs that technician can carry at any point in time. The default is configurable per technician and is typically set between 1 and 3 depending on job type and workshop operating model.

For Al Futtaim Auto in Dubai, where service jobs are often long-duration — full services, gearbox replacements, electrical fault-finding — a WIP limit of 1 or 2 per technician reflects the reality that deep-focus work cannot be split across many simultaneous jobs without quality degradation. At a high-volume tyre and quick-service centre, a WIP limit of 4 or 5 might be appropriate for technicians rotating between short-cycle jobs.

When an advisor attempts to assign a job to a technician who is already at their WIP limit, BayWise Scheduler surfaces a conflict warning. The advisor can see that the technician is at capacity and is prompted to choose a different technician or adjust timing so that one of the active jobs is expected to complete before the new one begins.

The WIP limit interacts directly with conflict detection. The scheduler does not silently allow over-allocation — it makes the constraint visible. The decision to proceed or reassign remains with the advisor, but the system ensures the decision is an informed one.

Clock-in status

A technician must be clocked in to be considered available for live job assignment. Clock-in represents physical presence on the floor and is the trigger that moves a technician from “scheduled to work today” to “available to take work now.”

Technicians can clock in by tapping their name in the technician roster — a single tap that takes under two seconds. BayWise also supports voice clock-in for workshops that have enabled voice commands. Clock-out ends the active shift and removes the technician from the live assignment pool.

The separation between availability schedule and clock-in serves a practical purpose: workshops do not want the morning’s calendar to be built on the assumption that every scheduled technician will actually appear. At Sharma Motors in Mumbai, where the workforce is large and late arrivals are a managed operational variable, advisors monitor the clock-in board from the morning briefing and adjust assignments in real time as the day’s actual staffing picture becomes clear.

Key behaviours:

• A technician who is scheduled but not clocked in appears in the roster but is visually flagged as absent. They can still be assigned to future-dated jobs; they are excluded from live same-day assignment suggestions.
• A technician who is clocked in but whose shift ends before a job finishes will generate a scheduling conflict for that job.
• Clock-out does not automatically unassign active jobs. Any jobs in progress at clock-out remain assigned — the advisor receives a notification and decides whether to transfer the job or confirm the technician will complete it on overtime.

Technician efficiency

Efficiency is a metric computed for each technician from the history of their completed jobs. It compares actual job duration — the time from when a job was marked started to when it was marked complete — against the estimated duration set on the job at creation.

An efficiency score above 100% means the technician consistently completes jobs ahead of the time estimate. A score below 100% means jobs routinely run longer than estimated. Neither is inherently a performance failure — estimated durations may be systematically generous or tight depending on how the workshop sets them — but the metric gives workshop managers a consistent, comparable data point.

Efficiency feeds into the AI scheduling assistant as a weighting factor. When two technicians are otherwise equally suitable for a job — same relevant skills, similar current workload — the AI will give a marginal preference to the technician with the higher historical efficiency on that job category. Over time, this tends to route well-matched work to technicians who execute it quickly, while the scheduler avoids over-concentrating premium work on a single high-performer.

Efficiency is visible in the analytics view. At Tanaka Auto Service in Osaka, workshop managers review efficiency trends monthly as part of their technician development process — not as a rigid KPI, but as a conversation-starter about where training investment or job routing adjustments might improve throughput.

Inactive technicians

A technician can be deactivated without being deleted. Deactivation is appropriate when a technician is on extended leave, on secondment to another location, or has left the workshop but the historical record of their work needs to be retained for auditing or payroll reconciliation.

When a technician is deactivated:

• They no longer appear in the assignment interface as a selectable option.
• They are excluded from AI scheduling suggestions.
• All historical job records in which they appear remain fully intact and queryable.
• The technician profile remains in the system and can be reactivated at any time.

This is preferable to deletion in almost every case. Deleting a technician profile breaks the historical record for every job they were ever assigned to, replacing their name with a blank. Deactivation preserves the record while eliminating them from the live scheduling pool.

At Al Futtaim Auto in Dubai, where technicians sometimes rotate between workshop locations over the course of a year, deactivation and reactivation at the correct location is a normal part of the roster management workflow.