Skip to main content

Requisition default rules

How priority rules set requisition defaults for selected agencies

Written by Austin Brummer

Create and prioritise rules

Authorised hiring-side users manage Default rules from Company Config under Requisitions. Create a named rule, select at least one agency, then choose a default field and its value. Use Add default to configure another field in the same rule. New rules are active by default.

Drag rules into priority order. Priority 1 is evaluated first, and lower rules are ignored as soon as an active rule matches. Deactivate a rule to retain its configuration without applying it. A rule already used by a requisition can be deactivated but cannot be deleted.


​

How the agency condition matches

A rule containing Agency A and Agency B matches when either agency is selected on the requisition.

An agency match applies the resulting action to the whole requisition. If Agency A and Agency B are selected and Agency A causes the rule to match, Agency B receives the same resulting requirements.


​

Available actions

  • Assignment basis — choose Auto assign to create assignments automatically for qualifying candidates submitted by agencies, or Manual assign so the hiring team creates assignments after review.

  • Remove competency requirements — replaces the inherited company or project matrix with no competency requirements for this requisition.


​

Review and submission

The request form initially selects the rule's assignment basis and updates the displayed competency requirements when agency selections cause a rule to match. The user can change Auto assign or Manual assign for the requisition before submission. When agency selections change, the matching rule is evaluated again; if no rule matches, the assignment basis returns to the applicable project or company default. The review step names the applied rule.

When the winning rule removes competency requirements, they cannot be manually amended while the rule continues to match.

The server evaluates the current active rules again when the requisition is submitted, applies the winning rule, records the actions in activity, and stores an audit snapshot. Later edits to the rule do not rewrite an existing requisition.


​

For agencies

Requisition default rules are configured by the hiring company. Agencies see the requirements resulting from the matched rule on requisitions sent to them.

Auto assign creates an assignment when an agency submits a qualifying candidate. Manual assign leaves the hiring team to review the candidate and create the assignment.

Because a matched rule applies to the whole requisition, every selected agency receives the same assignment basis and competency requirements.


​

Continuing agency competency exemptions

For hirers and agencies, the first active rule matching the hiring company and the actual supplying agency is checked during worker submission, assignment competency previews, trade changes and confirmation. If that rule removes competency requirements, the agency is exempt from the matrix even where an existing pending or cloned assignment has saved requirements or uses an older requisition. No individual assignment override is needed. Confirmation records the exemption rule in assignment activity.

This continuing exemption is specific to the hiring company and supplying agency. The original requisition default still applies to the whole requisition when it is raised. Existing requisition and assignment overrides are retained; they are not rewritten by the continuing check. Deactivating or changing the rule removes the continuing exemption, but an existing saved override with no requirements continues to apply.

Agencies do not configure these rules. Other worker, document, pricing, allowance and permission checks continue to apply, and assignment-basis defaults are unchanged.

Did this answer your question?