100% QuebecGetting Started
Clients 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.
A shift is always planned on a project, and a project always belongs to a client. That chain is not a filing convenience: it is what decides the decree applied, the geofencing radius accepted, the pre-ticked premiums, and the line the hours will be billed on.
The sections that follow are the zones of those two screens. Read the ones that concern you: the last, on what prevents a deletion, is worth the detour even if you have nothing to delete today.
- The chain
- Client › project › shift › hours
- What a project decides
- Decree, geofencing, premiums, budget
- Deletion
- Trash first, permanent if never used
Landmark 01
The client list
A client is a billable entity: the building, the school board, the hotel chain. It is the level above projects, and the only one carrying an address book and a login account.
Two tabs, and the second counts as much as the first. “Active” lists what is in use; “Trash” keeps what was deleted, restorable at any time. A record never disappears with one click.
Search covers the name and the contact person: handy when you remember who you call, not what the building is called.
Landmark 02
A client record
Five tabs. “Information” carries the identity, the category and the internal notes. “Account” opens the client's access to their own dashboard, with their username and password. “Team” lists the supervisors and workers attached to them. “Notes” and “Documents” round out the file.
The field to notice is elsewhere: “Decree”. It reads “Inherited from the organisation” by default, and it is the middle link of a cascade most users discover too late.
The decree cascade, top to bottom
A shift may impose its decree. Failing that, the project's applies. Failing that, the client's. Failing that, the organisation's. The first level that explicitly declares a decree wins: which is why a client under a particular agreement is set once, here, rather than project by project.
Landmark 03
The project list
A project is a contract, a site, a mandate: the place where the work happens. The list carries four useful columns: the name, the client it belongs to, the address, and the status.
Three shortcuts at the top. “See on the map” places every project on a map. “Import” and “Export” bring the list in or out in bulk: a first filling is rarely done by hand.
Landmark 04
Identity, address and geofencing
The client is required, and the app says so bluntly: a project always belongs to a client. The name is worth making precise (“Carrefour Lachine) washrooms (day)” stands apart from “Carrefour Lachine: common areas” on a schedule.
The address can be taken from the client's book or entered custom, with its latitude and longitude. It is what serves as the centre of the geofence: the radius within which a punch counts as made on site.
A radius of 0 m disables the check. That is the shipped setting, and it is deliberate: switching on a position constraint unknowingly would refuse legitimate punches from day one.
Landmark 05
The project's pay regime
“Project decree” reads “Inherited (client or organisation)” by default: the project takes its place in the cascade without imposing anything. Filling it in here overrides the client and the organisation, for every shift on the project.
The note under the field says exactly how far it reaches: “Applies to every shift on this project, unless manually overridden on the schedule.”
Two neighbouring settings serve certain sectors only. The CCQ sub-sector picks the residential grid and overtime regime. The mining-sector mandate with accommodation pushes the consecutive-day uplift threshold from the 7th to the 15th day, as the security guards' decree provides.
Landmark 06
The budget envelope
A ceiling in hours or dollars, and the person to warn before it is blown. It is the guardrail of a fixed-price mandate.
Nothing is blocked when the ceiling is reached: you are warned, you are not stopped. The distinction matters: a site does not halt because a budget was exceeded.
The site's standing premiums
Lower in the same panel, standing premiums are pre-ticked on every shift planned on this project. A site classed “work at height” or “confined space” pays them to everyone, all the time: declaring them here avoids adding them by hand on every shift, and forgetting them.
Landmark 07
A project record, month by month
Four counters, framed on a month: the employees attached to the client, those who actually worked, the hours paid, and the pre-payroll amount that follows.
The arrows change month. It is the view you open when a client asks what their building cost in July.
Landmark 08
The same payroll, split two ways
The month breaks down two ways side by side: by employee, and by job class. Both totals are identical: it is the same sum, cut differently.
One answers “who”, the other answers “at what rate”. The breakdown by class is the one you take into a discussion with a client: it says how many hours were worked in class A, B or C without naming anyone.
Landmark 09
Finishing a project
A finished project leaves schedule creation: no shift can be planned on it any more. It stays readable, with all its history of hours and amounts.
That is the right way to close a completed mandate. Deletion serves something else: the next section.
Landmark 10
The trash, and what refuses to go
Deleting a client or a project sends it to the trash. Nothing is lost: the record stays restorable, and a project whose client is also in the trash asks you to restore the client first.
Permanent deletion is only offered if the record is referenced nowhere. Shifts happened on this project, hours were declared on it, projects still belong to this client: in those cases the app refuses and says which.
It is not excessive caution. Erasing a project on which hours were paid would make those hours unexplainable: in an inspection as in your own history.
What to remember
A client can see their own dashboard
The “Account” tab of a client record opens read access for them: they follow the progress of their projects without seeing your rates or your other clients. Leaving the password empty during an edit does not change it.
The client category serves the construction sector
It is optional and classifies projects. If it is of no use to you, empty its values in Settings › Reference data: the field then disappears from the records.
Why the attachment matters for payroll
The client and the project follow every timesheet all the way to the exports: pre-payroll, the pay run and the monthly CPEEP report all carry them. A misattached project therefore does not show up on the schedule: it shows up on the declaration.
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.
LireUnderstanding and following your decrees
Where the rules that decide your payroll live, why they are read-only, and how a rate increase applies without rewriting the payrolls already done.
LireGenerating a pre-payroll export
Assemble the columns your payroll software expects, check what goes into the file, and understand what a preview does not freeze.
LireCan't find what you're looking for?
Our team can answer your technical questions and support your rollout.
