100% QuebecAn open shift is a shift published with nobody on it. Eligible employees see it in the mobile app and claim it; you decide, or the app decides for you. When a claim is accepted, the schedule is created automatically.
It answers a last-minute drop-out as well as a long-planned surge. The difference between the two comes down to two settings (the assignment mode and the deadline) and that is where this article insists.
- Who sees the posting
- Employees assignable to the site
- Who decides
- You, or first come first served
- Effect of an acceptance
- The schedule is created at once
Before you start
- An existing client and site: a posting always attaches to a project.
- Employees assignable to that site: without them, nobody will see the posting.
- 1
Open the open shifts
“Open shifts”, in the Planning & team section. Three tabs, answering three different questions.
“Open” lists what is still waiting for a taker. “Filled and cancelled” keeps the history of what was assigned or withdrawn. “Swaps” is a separate thread: employees propose to swap a shift among themselves, from the mobile app.
1 what is waiting · 2 what is settled · 3 the swaps proposed by employees. - 2
Choose a shift or a block
The first decision in the dialog, and it changes the rest: publish ONE shift, or a whole schedule.
A block gathers several shifts assigned TOGETHER to the same person: a week, a rotation. Nobody can take half of it. That is what you publish for a vacation replacement; the single shift serves the hole of one evening.
The block is indivisible: whoever gets it gets all its shifts. - 3
Describe the posting
The client and the site are required: that attachment determines who is assignable, and therefore who will see the posting.
The required class is copied onto every shift, and stays editable shift by shift. The title is optional: without it, the site name is displayed, which is enough most of the time.
The instructions serve what does not fit in a schedule: report to the foreman, boots required, access code.
1 the client · 2 the site · 3 the required class, carried onto every shift. - 4
Place the shifts
Each shift carries its date, its start, its end, its class and its breaks: two hours maximum per break. “Add a shift” stacks more into the same posting.
For a whole week, the generator avoids repetitive typing: tick the days, give a start, an end and a break, and it replaces the shifts with one per ticked day.
Two rules are checked as you type. Two shifts cannot overlap. And two shifts less than two hours apart are refused: that case is a break inside one shift, not two shifts.
The shift being entered, on the right. At the bottom, the posting summary: “1 shift · 8 h 30 · 1 spot”. - 5
Spots and assignment mode
The number of spots says how many people can get this posting: from 1 to 50. Three spots is a posting that fills in three goes.
The mode decides who rules. “With approval” collects the claims and lets you choose. “Automatic assignment” accepts the first claim outright, without you.
Automatic suits the urgent replacement, when speed matters. Approval suits the case where the person matters: seniority, skill, balance of hours.
1 the number of spots · 2 you decide · 3 first come first served. On automatic, the schedule is created without you
The first claim is accepted outright and the schedule appears immediately. There is no confirmation screen, no grace period: if the person claiming does not suit you, you will have to undo the schedule afterwards. Choose this mode knowingly.
- 6
Restrict eligibility
Two filters, both optional. “Allowed classes” limits the posting to certain job classes. “Specific employees” reserves it for named people.
Left empty (the normal case) every employee assignable to the site sees the posting. The sentence under the fields says so in plain words, and it is the right way to publish most of the time: the more people see it, the faster it fills.
“Empty = every employee assignable to the site.” - 7
Set the claim deadline
Past that date and time, the posting expires: nobody can claim it any more. By default, the deadline is the start of the first shift: which leaves claiming open to the last minute.
Bringing it forward serves when you need time between the assignment and the shift: warning a foreman, arranging access, ordering equipment.
Left empty, the deadline aligns with the start of the first shift. - 8
Publish
“Publish” notifies every eligible employee in the mobile app right away. It is the button that writes, and there is no draft: a published posting is visible.
A summary reminds you before clicking how many shifts and how many spots the posting holds.
Nothing is sent before that click; “Cancel” closes the dialog with no trace. - 9
Follow and decide
Each posting shows as a card: its type, its status, its assignment mode, the site, the dates, and the count of spots filled.
At the bottom, the state of the claims. “No claim” when nobody has asked; otherwise the number, including those pending. “View / Decide” opens the list of claims, each with the date of the request and an optional note.
Approving creates the person's schedule. Refusing lets you attach a word: optional, but that is what tells a refusal apart from silence.
This posting has no title: the site name takes its place, as announced at step 3. Cancelling a posting does not undo what is assigned
“Cancel the posting” refuses the claims still pending, but the schedules already assigned stay in place. That is consistent: the person committed, and their shift is planned. To remove it, you go through the schedule itself.
- 10
Swaps between colleagues
The third tab is not about your postings: it is employees proposing to swap a shift among themselves, from the mobile app.
One particular case is worth knowing: when a shift is released by someone, the card carries the mention “Replacement · requested by X”. Approving a claim then creates the replacement's schedule AND removes the shift from the original person, in a single operation.
Empty thread here: swaps are born in the mobile app, not in the back office.
What to remember
Open shifts also appear in the schedule
The schedule grid carries an “Open shifts” row and a monthly badge counting the postings still open. You therefore do not have to watch this screen to know there are holes left.
An expired posting is not a cancelled posting
“Expired” means the deadline passed with no taker; “Cancelled” means you withdrew it. Both end up in the “Filled and cancelled” tab, and the distinction matters when you are looking for why a shift was never covered.
The required class is not eligibility
The required class is the one the shift will be paid under; the allowed classes decide who may claim it. They often coincide, but not always: you can open a class B shift to employees of classes A and B.
Go further
Building an employee's schedule
Placing a shift on a site: who, where, when, with which breaks, and reading the total paid hours before saving, not after.
LireClients and projects
The frame everything else hangs on: what a project is for, what it decides for the hours worked on it, and why some records refuse to disappear.
LireApproving a week of timesheets
Review punched hours against the planned schedule, understand what the decree adds, and approve: knowing what approval locks in.
LireCan't find what you're looking for?
Our team can answer your technical questions and support your rollout.
