What a project is
A project is the main operational container under a company. It controls which users, sites, agencies, cost codes, rates, finance settings, shift patterns, and configuration rules are available when users raise requisitions, create assignments, and process timesheets.
Where projects are used
Projects appear anywhere work needs to be scoped to a part of the company. Users select a project when creating requisitions, assignments, sites, purchase orders, invoices, rates, timesheets, reports, and exports. The selected project then controls the available sites, agencies, cost codes, approvers, rates, and configuration rules.
Core setup
The Overview tab stores the project's identity and core routing data.
Project name and project number
Company, region, sector, jurisdiction, address, and bank holiday region
Single-site or multi-site setting
Support and finance email addresses
Project dates and phone number
Active or inactive status
Tabs on the project detail page
Overview stores the project identity, company, address, region, sector, dates, status, and contact details.
Users controls project admins, finance users, approvers, and requestors.
Cost Codes controls the cost codes available for project workflows.
Finance controls project-level billing details where parent finance is not inherited.
Agencies controls project-level agency overrides and exclusions.
Shift Pattern controls the default shift pattern used by the project and sites that inherit it.
Config controls project-specific requisition, timesheet, uplift, and WRA settings.
Rates shows project and supplier rates where the user has rate access.
Log shows project activity history for authorised admin users.
Notes stores project-specific notes.
What projects affect
Requisition creation, approval, auto-assign defaults, agency selection, cost code selection, and purchase order validation
Assignment project, site, trade, cost code, rate, and shift context
Timesheet approver eligibility, cost code allocation, timesheet adjustment permissions, and WRA accommodation behaviour
Project-specific finance, agency, rates, uplifts, notes, and activity history
Setup dependencies
A project depends on company setup. Before it can be used fully, the company should have regions, sectors, agencies, shift settings, rate setup, permission templates, and any required approval or WRA configuration in place.
Access and visibility
Project access depends on your role and your relationship to the company or project. Project Admin, Project Finance, Project Approver, and Project Requestor users must be assigned to the project to access it. Company and MSP users are scoped by their company access.
Active and inactive projects
Administrators can mark a project active or inactive from the Overview tab. Inactive projects remain part of the system record, but they should not be used for new operational work unless they are reactivated.
For agencies: how projects affect you
Projects are owned and configured by the hiring company, but they shape almost everything an agency does, so it helps to understand them even though you do not set them up.
You only see projects that your agency is connected to through the hiring company, and project setup itself is managed by the company, not by agencies.
The project decides your rates and markup, which cost codes apply, whether you can adjust timesheets, and how WRA accommodation is handled for your workers.
When you raise requisitions, assignments, timesheets, or billing, the selected project controls the rules and rates that apply.
If a project setting looks wrong for your workers, such as rates or timesheet adjustment, raise it with the hiring company since they control project configuration.