Review Bypass Requests
Approve or deny technician requests to skip wizard requirements.
Before you start
- •Sign in to the Hub with access to this workspace.
You will finish with
- •You can explain what Review Bypass Requests is for and choose the correct next action.
Safety and data checks
- • A bypass weakens a workflow control; never approve merely to make a job appear complete.
Complete the task
- 1Navigate
Open Review Bypass Requests
Use the Hub navigation to open Review Bypass Requests. Do not begin from a bookmarked record until you can identify this workspace in the normal menu.
Expected resultReview Bypass Requests is open and its page heading is visible.
- 2Review
Understand what belongs here
Bypass Requests allows controlled exceptions when a technician cannot complete a non-critical wizard requirement. Use this distinction to avoid creating the same work in a neighbouring workspace.
- 3Verify
Read the current state first
Read the work order, step, requirement, technician reason, evidence, customer impact, and prior bypass history. Read the customer, owner, date, and status before opening or changing a record.
- 4Review
Choose the correct action
Approve only with an adequate reason and safe alternative, or deny with specific instructions for completion. Open the specific record and confirm its history before saving, sending, assigning, or completing anything.
- 5Verify
Confirm the safe stopping point
A bypass weakens a workflow control; never approve merely to make a job appear complete. This orientation ends before any irreversible or customer-facing submission.
A bypass weakens a workflow control; never approve merely to make a job appear complete.Expected resultYou know what must be verified before the final action.
If something does not look right
The page or action is not visible.
Confirm your role and Navigation & Access settings, then ask a Super Admin if the feature is disabled.