Branch Manager
New to this role? Follow the first-day checklist.
Use the labeled sidebar to find your permitted work areas, grouped by task. On a smaller screen, open the navigation menu in the header to reach the same destinations. The current page stays highlighted; the tenant and branch scope still determine which records and actions you can use. Choose Account in the header for appearance controls and Log out. Daily workshop tasks come first; Management holds reporting and feedback, and Administration holds setup. Only the groups and destinations your role can use are shown.
Branch Managers oversee branch workload, service flow, staff coordination, and operational reporting.
Responsibilities
- Monitor calendar, appointments, check-in, no-shows, repair-order queues, and blockers.
- Create branch-scoped walk-ins when front-desk coverage requires it, using the same duplicate, consent, ownership, and active-work checks as Service Advisors.
- Review workload, technician assignment, fallback ownership, and final delivery support.
- Watch customer, vehicle, document, and verification state when it affects service flow.
- Review branch-scoped public registration requests when the explicit read/review permissions are granted; verify the applicant, plate, vehicle, consent, and current Pending state before a confirmed decision.
- Track estimate, invoice, payment, QC, and delivery handoffs.
- Use dashboard, revenue, operational, integration, and payment-outcome reports for branch decisions.
- Review service-catalog details and availability returned for assigned branches. Escalate pricing, checklist, service-status, or tenant-wide availability changes to a Tenant Admin.
Today’s work stays within your assigned branches. Begin with Approval & parts review, choose a branch or stage, and search by plate or reference. Use pagination for every matching job or the optional board for stage previews with complete-queue links. The row’s technician is the assigned work owner, not necessarily the customer follow-up owner. Read the manual update time and choose Refresh before a handoff. A recorded approval or parts wait does not establish a missed deadline.
Inside a repair order, use the stable plate/customer/status header to avoid handoff mix-ups. Overview starts with readable facts; Edit job facts reveals the occasional editing fields. Estimates, billing, timeline, and documents have separate tabs, and the selected section survives reload. Review the current estimate and line decisions before making a revision. Delivery requires an explicit vehicle handoff confirmation, and unresolved payment still needs the existing permission-controlled override reason.
Branch Managers should use reports to make branch-level decisions, but sensitive changes still need the appropriate permission and audit trail. Appointment confirmation, rescheduling, cancellation, no-show, and check-in remain separate capabilities even when the appointment is visible.
The Reports workspace is limited to your resolved branch scope. Filters use inclusive UTC calendar days, technician choices come from the scoped operational result, and each chart has a complete data table and CSV alternative. Read partial or unavailable evidence literally; do not treat a missing rate as zero or add revenue across currencies.
Feedback uses the same resolved branch scope. Filter private ratings by branch, rating, or inclusive UTC date, then distinguish complete-scope summary counts from the bounded newest-first comment page. The workspace is not public publishing, sentiment analysis, or a follow-up queue. Open a linked Repair Order only when you need the authorized service context.
Appointments starts with Today. Check Past unresolved for earlier open bookings and History for terminal bookings; checked-in work belongs in the repair-order queue. List search, branch/date filters and pagination stay in the URL. Calendar counts matching bookings, not available capacity. Internal appointment/customer/vehicle identifiers are not human references. Manager override appears only for active work visible in the manager’s branch scope and always needs a reason.
Use Customers and Vehicles to confirm the customer, plate, current owner, and verification state before intake or handoff. Search the existing customer directory before vehicle creation. The workspace shows only actions granted by your branch-scoped capabilities; an unavailable owner or document section does not erase the vehicle identity or authorize a workaround.
Use Invoices to filter the authorized branch list and open a plate-anchored invoice workspace. Confirm the current balance and payment history before issue, payment-request, or manual-payment handoff. Void and issue remain separate permissions, and the backend rechecks invoice state on submission.