Hiring clients can now send a submitted requirement back to a contractor for resubmission. This new ‘Send back to contractor’ action gives reviewers a way to request corrections on a submission without rejecting the requirement entirely — and lets contractors update and resubmit their work directly from the contractor portal.
1. About Send Back to Contractor
When a contractor submits a requirement that isn’t quite right — maybe the wrong document was uploaded, a field was filled out incorrectly, or a certificate is outdated — hiring clients can now send it back to the contractor for resubmission, rather than approving or rejecting it outright.
Sending a requirement back:
- Changes the requirement’s status from ‘Awaiting Approval’ back to ‘Pending Submission’
- Notifies the contractor that a resubmission is needed, along with the reason
- Allows the contractor to update their submission and submit again
- Returns the requirement to its original approval workflow once resubmitted
This action is available at every step of a multi-step approval workflow, so any approver can request a resubmission — not just the first reviewer.
2. Sending a Requirement Back to a Contractor
To send a submitted requirement back to a contractor for resubmission:
- Navigate to the requirement in Contractor Management
- Open the submitted requirement to review the contractor’s submission
- Click More Actions
- Select Send back to contractor
- Enter a brief reason for the resubmission request — this will be visible to the contractor so they understand what needs to be corrected
- Click Send Back to confirm
The requirement’s status will update to ‘Pending Submission’, and the contractor will be notified that a resubmission is required.
3. What the Contractor Sees
When a requirement is sent back, the contractor sees the following changes in their contractor portal:
- Task returns to To Do — The task that was previously ‘Pending Approval’ will move back to ‘To Do’, prompting action
- Resubmission request details — The contractor will see who requested the resubmission, the date it was sent back, and the reason provided
- Edit and resubmit — The contractor can update their submission (replace documents, correct fields, etc.) and submit again
4. After the Contractor Resubmits
Once the contractor submits their updated requirement:
- The requirement’s status returns to ‘Awaiting Approval’
- The requirement re-enters the approval workflow at the step where it was sent back
- The original reviewer (or any approver at that step) can now review the updated submission and approve, deny, or send it back again if needed
If approved, the workflow continues to the next step. Subsequent approvers in a multi-step workflow can also send the requirement back to the contractor at their step if needed.
5. Tips for Using Send Back to Contractor
- Be specific in the reason — The clearer the explanation, the faster the contractor can correct and resubmit
- Use it for small corrections — Send Back is ideal for fixable issues like incorrect uploads or missing fields; use Deny for submissions that fundamentally don’t meet requirements
- Available at every approval step — If you’re a later-step approver and spot an issue, you can still send the requirement back to the contractor
- Status changes are visible to everyone — Anyone reviewing this requirement can see that it was sent back, by whom, and why — supporting a clear audit trail
6. Important Considerations
- Sending a requirement back does not skip approval steps — once resubmitted, the requirement returns to the step where it was sent back, not the beginning of the workflow
- Contractors must take action to resubmit; the requirement will remain in ‘Pending Submission’ status until they do
- This action is available only for requirements currently in ‘Awaiting Approval’ status