Rejecting sends an application back to be corrected with the approver’s reason recorded. The entered data is kept, so only the problem needs fixing before it’s resubmitted.

This guide covers:

• Recording the rejection decision and comments at any step
• Notifying whoever submitted it — the worker, or their employer admin
• Correcting the flagged problem while the rest of the application stays intact
• Resubmitting so the approval sequence runs again

Reject with a clear reason and the fix is targeted, not a fresh start.

💡 Power User Insight: Every decision — approve, reject, re-approve — is kept as append-only history. If an earlier step is rejected after a later one was approved, the later approval isn’t wiped; it’s marked as needing re-approval.