A plumbing job approval should identify the work and commitment being authorized. A broad “approved” flag can become misleading when the caller changes the property, timing, or scope before dispatch.
Define who can approve attendance, charges, service-area exceptions, and scope changes. These may be different people. Keep the approval record separate from the remote job-creation or scheduling result.
Bind approval to reviewed facts
Record request identifier and version, approver, timestamp, decision, permitted scope, and expiry where appropriate. Present the property, reported issue, caller role, proposed timing, fee context, and unresolved questions to the reviewer.
If material facts change, mark the relevant approval stale. An approval for routine attendance at one rental property does not automatically cover a commercial site after hours.
Work through a fictional managed-property request
A property manager approves a daytime assessment at Unit 2. Before booking, the tenant changes the requested site to another building and asks for tonight. The original approval remains in the history but cannot authorize the changed request under the company's policy.
The workflow requests a new decision and preserves the pending state. It does not silently carry the earlier fee and attendance authorization into a different commitment.
| Approval condition | Required behavior |
|---|---|
| Request unchanged | Execute only approved scope |
| Property changes | Reevaluate affected approval |
| Fee exception requested | Authorized financial decision route |
| Approval rejected | Reason and next owner retained |
| Execution times out | Uncertain action, not assumed dispatch |
Separate permission from completion
An authorized request can still fail to create a job. Store approval, attempted operation, remote identifier, and final status independently. Staff should distinguish approved-but-pending from confirmed attendance.
Explicit approval adds coordination work. Routine requests can use preapproved policy where appropriate, while consequential exceptions remain human-reviewed. Record the policy version for those automated decisions so the outcome remains explainable.
Prevent repeated approval events from triggering duplicate creation. Reconciliation is required when a previous execution outcome is unknown. Review dispatcher approval records for the general versioning boundary.
Questions about plumbing approvals
Is a notification read receipt approval?
No. Define the explicit decision action that grants the intended authority.
Can approval be verbal?
Yes if the approved process records the authorized person, request version, decision, and scope with adequate evidence.
What should the caller hear while waiting?
Explain that authorization or dispatch confirmation is pending and state the approved follow-up route. Do not describe a planned visit as accepted before the required decisions and execution succeed.