Your team and your station

Two kinds of login, and the split is the most important thing in the product: your office sees the station; a driver sees their own day and nothing about anybody else. This is where your office gets its jobs and the station gets its shape — the shifts, the waves, the week and the vans — before the first board is built.

The two groups

The office

Owner, Ops Manager, Lead Dispatcher, Dispatcher, HR, Fleet Manager, Fleet Tech and Recruiter. Broad access, narrowed by which stations they work at and what their job may reach.

Drivers

Their own schedule, their own scorecard, their own van, their own messages, their own forms. Never each other’s.

A driver cannot reach an office screen even by typing its address, and the rule that stops them lives in the database rather than on the screen — so a bug on a page cannot leak a name the page was never sent.

Give your office its jobs

1. 1

   Give an office job to somebody already on your roster.

   People › the person › Details › Ops team login › Give an office job…

   Pick the job title and the stations, then Give office access. A lead or a dispatcher who also drives keeps one login: it opens the office as well as their own day. It takes Read & Write on Ops team.

2. 2

   Add the office people who aren’t on the roster.

   Ops team › Members › Add someone

   Their name, work email, job and stations, then Send invite. They get an emailed link good for 24 hours and choose their own password; nobody else ever sees it.

3. 3

   Decide what each job can reach.

   Ops team › Roles

   Every job holds one setting per module — Hidden, Read Only or Read & Write — and each action is Allowed or Not allowed; then Save permissions. Change a job and everybody holding it changes with it, in one press.

4. 4

   Have each of them turn notifications on and add the extension.

   Notifications come from the account menu, on every browser and phone they use — permission is asked per browser. Anybody who runs the board adds the extension in their own Chrome: each login’s sync brings in what that job covers.

Give your station its shape

1. 1

   Type your shifts.

   Settings › Station settings › Shifts

   A shift is the paid window a driver is on the clock for: its name, start, end and paid hours, then Add shift. Station settings has the station picker beside the toggle — do each station.

2. 2

   Type your waves, and pair each with its shift.

   Settings › Station settings › Waves

   A wave is when drivers leave the station, typed as its entry time; the load time above them is the minutes between a route’s planned departure and its wave. A driver on a later shift can be in an earlier wave. Waves are typed, never synced — with no waves the board cannot tell a route from a rescue.

3. 3

   Choose where your week is made.

   Settings › Where the week is made

   OpsBrio is where every company starts: you build the week on Schedule and press Publish. Cortex draft plans it in Amazon’s Scheduling and publishes it here — press Plan in Cortex, publish here. Cortex plans and publishes it there — press Follow Cortex. Either Cortex answer reads this week and next every half hour, which needs version 1.0.9 or later of the extension; its popup shows the version. The Where the week is made guide follows each answer to the board.

4. 4

   If OpsBrio makes your week, send us your schedule.

   OpsBrio support

   Your standing schedule — each driver’s usual days and wave — or the next few weeks, from your spreadsheet or old system. We bring it in and tell you when it is on your schedule. A standing schedule becomes your permanent schedule and every later week is generated from it; a few weeks alone get you started, and the week after them is typed by hand.

5. 5

   Check your vans’ seats.

   Fleet › Seats

   Each van has a 1st, 2nd and 3rd call, and empty seats fill themselves: each night a driver with no seat takes the empty seat on the van they drive, behind whoever is seated — from Amazon’s vehicle checks, from the first sync. Seats shows each van’s week and suggests changes to the seats you set; nothing moves until you press Move. To seat somebody yourself, open the van and Save the bench. When the day is built, each driver lands in their seated van, and anyone without one is lent a free van.

Read your rules before the week closes

Each starts on a sensible value, so nothing breaks while you read them — but the first week is judged by them. All on Settings:

Bonus & hours

The weekly bonus is off until the Owner saves it. The hours guarantee and how a route is priced live here too.

Ranking & standing

What a return, a write-up and a rescue cost the rank. It runs on standard rules until you change them.

Hours rules

The limits the desk is warned at — 12 hours a day and 60 in seven to start.

Extra shifts & days off · The desk’s day

Each station’s contingency and its extra-shift and day-off offers, and the desk’s deadlines through the day.

Payroll app

The app your drivers clock in and out of. Named, their Home asks them to after check-in and check-out; blank, it asks nothing.

Breaks · Uniform on the DA card · DVIC timer

On, with standard values, under Discipline & safety.

When somebody leaves

Ops team › Members › the person › Offboard

Offboarding switches their access off and bans the sign-in in the same press, which ends any session already open — including one on a phone in somebody’s pocket. Their name and everything they did stays, because the history has to remain answerable. There is a Bring back for the person who returns, and the screen tells you in words if either half did not land rather than reporting success over a job half done.

For a driver, do it from their profile in People instead: that one press also clears their future schedule days and their future board rows, gives their van seat back, and moves whoever was second call on that van up a place.