I cannot see the requisition
Visibility depends on your role and where the requisition has been routed. Check that all of the following are in place:
You have permission to view requisitions for the relevant company, project, or labour desk
Your role gives access to the company, project, or supplier scope on the requisition
For agency users, the requisition has been sent or released to your agency
Filters such as status, date range, company, and project are not hiding it
The requisition is not cancelled or rejected and excluded by your current filter
I cannot raise a requisition
Raising a requisition requires permission and a valid configuration. If you cannot raise one, check that:
A company admin has confirmed your role can create requisitions for the selected project
The company and project are active and configured for requisitions
Complete the required fields shown by the form. Work activity, cost code, approvers, hiring managers, and custom fields depend on company configuration and the selected approval route
I cannot find Approve requisition
Open the requisition detail page and select Actions at the top right, then Approve requisition. The label uses your company's preferred name for requisitions. The approval action is not in the Overview tab or a section further down the page.
If the action is missing, ask your hiring company's administrator to check your approval permissions, project approval value limit, the pending stage and any fixed-user assignment, and the requisition status. Agencies do not complete the hiring company's approval.
No approvers are available
The approver list is built from the project approval setup and the current approval stage. If no approvers appear:
The project may have no eligible approvers configured for the stage
Multi-stage approval may not be configured with users for the relevant stage
Approvers may be inactive, unverified, or no longer assigned to the project
Ask an administrator to review the project users and approval configuration
Agencies are missing
Agency availability is controlled by setup and tiering. Common reasons an agency does not appear:
Not connected to the project or company supplier list
Restricted by supplier or labour-desk rules
Inactive at the agency, company, or project level
You do not have permission to amend the supplier list
For agency users viewing the list, a later-tier requisition may not have been released yet; this does not prevent the hiring team selecting later-tier agencies
Rates or pay types are unavailable
Rates depend on the selected trade, project, and company configuration. If they are missing or restricted, check:
The selected trade has rates configured for the project
Pay type and rate type combinations are available for that trade
Rate override settings are allowed for your role
Jurisdiction and company rate configuration cover the requisition
Purchase order validation is not blocking the selection
I cannot amend the supplier list
Supplier list changes need permission and a compatible requisition state. You may be blocked when:
You do not have the requisition.amend.supplier permission
Company or project configuration restricts supplier changes
The requisition status no longer allows supplier list changes
The target agency is inactive, restricted, already attached, or otherwise not eligible
A requisition is not marked as filled
Filled status is calculated differently for each fulfilment mode:
Standard — counted assignments must meet or exceed the requested quantity; start confirmation is not required
Shift-based — every working day in the requisition must have enough assigned coverage
Cancelled assignments are excluded from shift-based coverage; Standard Filled calculation can still count them if they have a completed or ended date
I cannot submit more workers
For manual assign, the submission dialog allows up to 10 workers per agency response, or the requested quantity if higher. For example, a requisition for 3 workers allows 10 per agency response; one for 15 allows 15. This applies when submitting or amending a response and excludes workers whose assignments have been cancelled.
Agencies should reduce their selected workers to the allowed count. Hirers may see more submissions overall because this is a limit per agency response, not a combined limit across agencies. With auto-assign enabled, standard submissions cannot exceed the quantity still unfilled. Shift-based assignments cannot exceed the requirement for any selected date.
A worker cannot be assigned
Assignment can be blocked by permission, status, or eligibility rules. Common reasons include:
You do not have the requisition.assign permission
The requisition is filled, rejected, or cancelled
The agency is restricted or the worker has been rejected
The worker is already assigned to the requisition
Missing availability, right-to-work, ID checks, or competency requirements
Trade or submission criteria rules are not met
Standard — you cannot assign more workers than the remaining required quantity
Shift-based — the worker must have valid assigned dates and daily coverage cannot exceed the required quantity
Purchase order validation is failing
When purchase order validation is enabled, selected agencies must have valid PO coverage for the requisition. If validation fails:
Check that an active purchase order exists for each affected agency
Confirm the PO scope covers the requisition's project, site, and trade
Check that the PO has not expired: the requisition selector checks its end date against today, not the full requisition date range
Validation runs when raising, approving, and sending to agencies
An agency has not received the requisition yet
Tiered scheduling delays notifications to later-tier agencies:
Only Tier 1 agencies and any agencies selected for immediate release are notified straight away
Later-tier agencies stay in scheduled status until their trigger time is reached
Scheduled agencies do not receive emails or in-app notifications until released
An authorised user can use the immediate send action to release an agency early
I cannot amend dates, shift, or rates
Different amendments have different blocking conditions:
Dates and shift pattern — the Actions menu hides these while any assigned worker has no cancellation date; ending an assignment alone does not unlock them
Rates, pay type, and rate type — can be amended from the Value tab until any worker has been assigned. Before all approval stages are complete, including while raising the requisition, Amend Requisition Rates (Before approval) is required. Once fully approved, Amend Requisition Rates (After approval) is required. Agencies see the resulting rates subject to rate access
Actions menu amendments have state restrictions; edit controls in the Overview and Value tabs have their own permission and validation checks
Shift-based coverage does not look right
Shift-based coverage uses specific rules for working days and worker counts:
Coverage is calculated for every date between the start and end dates
Only days that fall on the requisition shift pattern count as working days; non-working days are excluded
Assigned workers are counted from active assigned candidates only; cancelled assignments are excluded, so coverage may drop when assignments are cancelled
Available worker counts come from agency submissions with date availability and exclude workers already assigned
Agency users see the assigned and available worker views filtered to that agency, so their figures can differ from the internal totals
A timesheet approver cannot be selected
Specific timesheet approver selection has eligibility and limit rules:
Only eligible project users appear in the list
A user must be active, verified, and hold the project-level Timesheet Approval permission; project-role users must be assigned to the project, while company admins are loaded from the company
Up to four timesheet approvers can be selected
At least one approver is required when raising or editing the approver list