The 5-Role Access Model: Who Should See and Edit the Schedule

Why "Everyone Can Edit" Breaks Down
The spreadsheet lived on a shared drive. Anyone with the link could open it, and anyone who opened it could type over whatever was already there. On a Tuesday in March, a site superintendent needed a mini excavator for a Thursday trench job, so he typed his crew's name into Thursday's column. Twenty minutes later, the equipment manager — working from a different tab, unaware of the edit — assigned the same machine to a second site for the same day, because his copy of the sheet hadn't refreshed. Neither person did anything wrong. The tool let two people make a legitimate decision about the same asset at the same time, and it had no way to tell either of them the other had already moved.
This is not a training problem. It's a structural one. When every person who touches the schedule has the same level of access — open the file, type anywhere, save — there is no mechanism to prevent two people from committing to the same resource. The fix isn't a stricter spreadsheet or a stern email about "checking before you edit." It's separating who can ask for equipment from who can approve the ask from who can permanently assign it — and making sure only one of those steps actually locks the calendar.
That separation is what a role-based access model does. Below is how to structure it for a fleet of owned and leased equipment running across multiple active sites, and what each role should — and shouldn't — be able to touch.
The 5-Role Access Model Explained
Equipment scheduling role based access works best when it maps to five distinct functions rather than five job titles — a single person can hold more than one role, especially in a smaller operation, but the functions themselves need to stay separate in the system:
- Admin — owns the account, manages user access, configures equipment and sites, and can override any assignment. Typically the equipment manager, operations manager, or owner in a smaller shop.
- Equipment Manager — the primary scheduler. Reviews incoming requests, resolves conflicts, assigns machines to sites, and reassigns equipment when priorities shift.
- Site/Project Manager — requests equipment for their job site, sees the schedule for their own projects, and can flag a problem (a no-show, a breakdown) but does not have blanket edit rights across every site.
- Operator — sees their own assignments (where to report, what machine, what site) and can see conflicts that affect them directly, but does not assign equipment to themselves or others.
- Operations Director / Executive — view-only across the entire fleet and every site, for utilization and planning visibility, without day-to-day scheduling responsibility.
The pattern underneath all five: requesting equipment, approving a request, and committing an assignment to the calendar are three separate actions, and only one role — the Equipment Manager, sometimes with Admin override — should be able to do the third one. Everyone else requests, views, or flags. This is the single change that prevents the Tuesday-in-March problem, because a request sitting in a queue doesn't block a calendar slot the way a direct edit does. Two site managers can both request the same excavator for Thursday; the system (or the equipment manager reviewing it) catches the overlap before either request becomes a confirmed assignment.
Request vs. Approve vs. Edit: Where the Line Sits
It helps to think of these as three distinct permission levels rather than a ladder from "less trusted" to "more trusted":
- Request-only access lets a site or project manager say "I need a skid steer at Site B starting the 14th" without touching anyone else's assignment. It's the correct default for anyone who needs equipment but doesn't own the scheduling decision.
- Approve/assign access belongs to whoever resolves competing requests — checking what's available, what's already committed, and what makes sense operationally. This is where a deterministic conflict check matters most: before a request becomes a locked assignment, the system should run an overlap check across the equipment's date range and flag it if another assignment already exists for that window.
- View-only access serves anyone who needs to see the fleet picture without needing to act on it — an operations director reviewing utilization across eight sites, for instance, has no reason to carry edit rights, and giving them edit rights anyway just adds another person who could unknowingly create a conflict.
A detailed walkthrough of how a site manager should submit and track a request, and how an equipment manager should triage the resulting queue, is worth reading in full if you're setting this up for the first time — see the breakdowns on how equipment managers run the scheduling workflow and how site managers should submit equipment requests.
The question isn't "who do we trust?" It's "who needs to commit a resource, and who just needs to ask for one?" Collapsing that distinction is what turns a shared calendar into a liability.
What Each Role Should (and Shouldn't) See
Visibility matters as much as edit rights. A role-based model that gives everyone edit access to everything is the obvious failure mode, but a model that hides too much information from the people who need it creates a quieter version of the same problem — requests get made blind, without knowing what's already committed.
- Admin and Equipment Manager need full fleet visibility: every asset, every site, every assignment, past and upcoming.
- Site/Project Manager needs visibility into their own site's confirmed assignments and, ideally, a general sense of fleet-wide availability so they're not requesting a machine that's obviously already committed elsewhere — without needing edit rights to every other site's schedule.
- Operator needs their own upcoming assignments and any certification or qualification requirements tied to the equipment they're assigned to — not the full administrative view.
- Operations Director needs the aggregate picture — utilization across the fleet, how often requests turn into conflicts, which sites are under- or over-equipped — without needing to act on any single assignment. That's a different kind of access than the Equipment Manager's, and worth reading about separately: see what fleet-wide visibility should look like for an operations director.
Getting this balance right is less about restricting people and more about matching what someone sees to what they're actually responsible for deciding.
How the Approval Workflow Actually Resolves Conflicts
The mechanism that makes this model work is a request/approve workflow, not a single shared document. A site manager submits a request for a date range and an asset type or specific machine. That request sits in a queue, visible to the Equipment Manager, until it's approved, declined, or modified. Only approval converts the request into a locked calendar assignment — and at that point, a conflict check runs automatically across the equipment's date range (and, where operator scheduling is in use, across the assigned operator's date range as well) before the assignment is allowed to save. If another assignment already occupies that window, the system flags it before it becomes a second commitment on top of the first, rather than after.
That sequencing — request, review, conflict check, commit — is the actual fix for the 7am double-booking scenario. It doesn't rely on everyone remembering to refresh their spreadsheet tab. For the full mechanics of how a request moves from submission to approval, see the equipment request approval workflow in detail.
Setting This Up Without Creating a Bottleneck
The most common objection to a role-based model is that it will slow things down — that funneling every request through one Equipment Manager creates a queue where there used to be instant (if chaotic) access. In practice, the opposite tends to be true once it's running: a brief, clear request takes less time to submit than a scramble to confirm an assignment manually did or didn't already happen, and an Equipment Manager reviewing a queue of three or four pending requests at the start of the day resolves conflicts in minutes instead of discovering them in person, on-site, after a crew has already shown up.
Starting with five roles doesn't mean assigning five different people. A ten-person operation might have one person holding Admin and Equipment Manager functions, with site superintendents as requesters and an owner checking in with view-only access. What matters is that the functions stay separate in the system even when the people don't — because the moment someone with request-only intent accidentally gets edit rights "just to make things easier," the whole point of the model erodes.
For a broader map of how these roles connect to the rest of the scheduling process — from first request to final assignment — the equipment scheduling resource hub is a useful starting point. If you're ready to see how a role-based access model and a built-in conflict check work together on a live schedule, EquipmentScheduler's plans include a trial period long enough to run it against a real week of requests.


