Every part of the board, in detail.

The assignment board

The board is the product: every vehicle or unit, every bay, and every technician's status in one place, updated as the day moves — not a whiteboard photo or a group chat thread.

• Passenger and Commercial. Two workflows in one board — light-truck/passenger jobs and semi/equipment/commercial work, each with its own catalog and service-call handling.
• Find work fast. Shop-order sorting, free-text search, and Tire Work, Oil & Upkeep, Mechanical, and Selected filters to build a job without hunting.
• Duty and quantity selection. Every job is built from the shop's own service catalog — common oil changes sit beside the shop's most-used tire services, not a generic parts list.
• Waiting or Call When Done. Each job records how the customer wants to be handled, plus the repair order number, vehicle or unit, and separate work notes vs. office-only notes.
• Custom "Other" work. When nothing in the catalog fits, the job still needs a real title — not an unlabeled line item.
• Oil-change stickers. The next service date and mileage from the windshield sticker are captured before a job can move to Ready — oil work cannot be marked complete without it.
• Print and CSV export. The live board prints with repair order, vehicle, zone, disposition, technicians, and timer, and exports to CSV for offline review — without turning the export into the system of record.
• Conflict-safe saves. If someone else changes a job before your save lands, BayLineup reloads the current database state and asks you to review, instead of silently overwriting it.

Permission-aware recommendations

A job is only ever suggested for a technician actually approved to do that work. Every recommendation shows the highest-ranked Lead-qualified employee with a short reason, and every rule shown on screen is enforced independently by the API, not just the interface.

• Lead / Assist / No. Every employee has a permission level per duty. Assist-qualified employees may join a job, but only alongside a qualified Lead.
• Override reasons. Assigning anyone other than the top recommendation requires recording why — physically unavailable, supervisor choice, training or assistance, customer priority, workload balance, or another operational reason. Both the recommendation and the actual assignment are kept, so acceptance can be measured later.
• Group safeguards. A running job can't lose its last employee or its last qualified Lead, and changing duties revalidates the whole active group.
• Ready-only assignment. Selected employees must be Ready when a job starts, and active employees must be pulled off their job before lunch, Out, Unavailable, or Ready status changes.

Technician status, lunch, and coverage

Every technician is Ready, Active, on Lunch, Out, or Unavailable, with the active employee group kept in sync as people join, leave, or step out — no separate whiteboard for who's available.

• Lunch escalation. Posted lunch times and buddy coverage are tracked against the schedule, with escalation when coverage is at risk.
• Service-call coverage. On-call employees and their assigned service trucks are tracked and dispatched from the same board.
• Warnings and overdue jobs. Jobs running past their buffered target surface on the board instead of only being noticed after the fact.

Job lifecycle

An assignment isn't just started and finished — it moves through states the board tracks and times, so a documented completion is the natural end point, not an afterthought.

• Live timers. Every active job counts down to its target, shows a warning as it approaches, and counts up once overdue — with a dedicated overdue list so nothing waits to be noticed.
• Hold and resume. A job can be put on hold — waiting for parts, waiting for authorization, waiting for equipment, a customer decision, or an office check — and the timer pauses and resumes without discarding the work already recorded.
• Work-order drawer. Every active job opens into a full editing surface: vehicle class, work, quantities, assigned employees, disposition, repair order, notes, and hold status, plus a print view.

TPMS

TPMS is one part of the board, not a separate product — it's a set of catalog job types on the same passenger workflow, with two features at different stages.

• TPMS Sensor, TPMS Relearn, TPMS Diagnostic, Valve Stem. Catalog job types available today — assigned, permission-checked against Lead/Assist skill levels, and timed like any other duty.
• Direct sensor hardware reading. Reading a sensor's ID and pressure straight from a shop tool into the job, instead of a technician logging it by hand — this is in hardware testing today, not yet available to every shop.

SOP library

Searchable, expandable shop procedures live next to the board instead of in a binder — from opening the board and dispatching a service call to closing the day and handing off open work.

• Categorized. Office, Assignment, Passenger, Commercial, People, and Quality & Safety procedures, each with owner, trigger, steps, required records, and escalation path.
• Versioned. Every procedure carries a revision number and last-reviewed date.

Analytics

Every assignment and completion is written to Postgres, so analytics reflect what actually happened on the floor, not a manual recap — and BayLineup shows an honest empty state instead of a fabricated trend when there isn't enough history yet.

• Shop KPIs. Completed jobs, percentage completed within target, median job duration, staffed employee count, completed service calls, and recommendation acceptance rate.
• 6, 12, or 24-month reporting. Completion-time trend and target attainment over the window you pick — the 24-month view gives real year-over-year context once enough history exists.
• Employee and job-type breakdowns. Passenger vs. Commercial work distribution across employees, plus the shop's most-worked job types by completed count and median duration.
• Recommendation acceptance. How often the top-ranked recommendation is actually assigned versus overridden, and why — a tuning signal for the model, not a scorecard on the office.

Skills & Permissions

A supervisor-managed matrix of Lead, Assist, or No for every employee and every duty in the catalog — the same matrix the recommendation engine and API safeguards read from.

SQL workbench

A read-only workbench for supervisors who need an answer the dashboards don't already show — without giving out production database credentials.

• Read-only transactions. Every query runs inside a read-only transaction, so it can't modify data.
• Statement timeout and row limit. Long-running or unbounded queries are cut off automatically.
• Audited. Every query is logged for later review.
• CSV export. Results export directly for further analysis.

Settings

Shop-level configuration lives in one place instead of scattered across code or a spreadsheet.

• Shop buffer. The planning percentage applied on top of the catalog's duty targets.
• Lunch escalation and service-truck coverage. The rules that drive the status board's warnings.
• Skills coverage. Flags any duty in the catalog with zero active, Lead-qualified employees — a gap that would otherwise only surface as a blocked assignment on the board — and links straight to the row in Skills & Permissions to fix it.
• Database instructions and security status. Operational reference for whoever is running the shop's instance.
• User accounts. Supervisors create and manage staff and supervisor accounts here.