Skip to main content

Rejecting a requisition

When and how to reject a requisition, and what happens after rejection

Written by Austin Brummer

When to reject

Reject a requisition during approval when it should not be approved. The action is available only when your access and the requisition state allow it. For an already approved requirement that is no longer needed, use cancellation where available. Typical rejection reasons include:

  • Incorrect role, trade, or site

  • Wrong dates, shift pattern, or quantity

  • Missing or incorrect rates, cost code, or PO details

  • Budget, headcount, or project-policy issues

  • Duplicate of an existing requisition

  • Request that should be revised before approval


​

Step through rejection

Follow these steps to reject a requisition:

  1. Open the requisition, select Actions at the top right, then Reject requisition. The label follows your company's preferred name for requisitions.

  2. Choose a rejection reason from the list. Project users see project rejection reasons.

  3. Add comments where useful, or where the selected reason (for example Other) requires them.

  4. Select Submit to record the rejection.


​

Choosing a rejection reason

A reason is always required, and is stored against the requisition. Things to be aware of:

  • Reasons help the requestor understand what to change.

  • Reasons are used in activity history and reporting.

  • Selecting Other usually requires comments so the requestor has enough context.


​

Comments

Use comments to explain what needs to change or why the requisition cannot be approved. Comments are saved with the rejection activity and included in the rejection communication to the requestor.


​

What happens after rejection

When a requisition is rejected, the system:

  • Marks the requisition as rejected and stores the rejected date.

  • Sets the project status to rejected.

  • Removes any pending scheduled agency releases.

  • Records a rejection activity entry with the reason and comments.

  • Notifies the requestor by email and in-app notification.


​

What the requestor sees

The requestor is notified that the requisition was not approved. The rejection reason and comments are included in the rejection email and in the requisition activity history.


​

What agencies see

Project rejection and agency rejection are separate actions:

  • If a requisition is rejected before approval and agency notification, agencies do not receive it as an active fulfilment request.

  • If an agency rejects a requisition after receiving it, only that agency's response is marked as rejected — the requisition itself is not rejected for everyone.

Did this answer your question?