Follow the job from permission to paperwork
These are candidate workflows, not a promise of autonomous dispatch or faster payment. If a consistent form and checklist solve the problem, start there.
Keep access and spending authority separate
Identify the reporter, access contact, owner or tenant, spending approver and billing recipient. Preserve the purchase order (PO), not-to-exceed (NTE) amount, after-hours rules and the exact approved scope. An old email or a person opening the door is not new approval.
- Extra work exceeds the NTE limit.
- A tenant reports the problem but the owner pays.
- A signed service record confirms completion, not additional charges.
Prepare the crew’s brief without guessing urgency
Bring reported symptoms, affected area, business impact, approved site history and access logistics together. Flag missing information and route urgency to dispatch. Do not invent an arrival time, diagnose a hazard from a photo or give improvised repair instructions.
A customer should not have to repeat the same story to every person. Dispatch still owns priority, crew suitability and commitments. Shared buildings and shutdowns affecting other tenants need explicit human coordination.
Make completed work ready for billing review
Compare authorized scope with technician-verified labor, materials, approved changes and required photos. Prepare a customer summary and invoice-ready packet; assign missing items to their owner. Keep the correct building and PO attached.
Technicians verify facts and the office approves charges and invoice release. A note about extra work is not customer authorization. Measure first-pass completeness and completion-to-ready-to-bill time separately from actual payment timing.
Check who actually owns recurring work
Backflow, pump, drain and water-heater programs need verified asset records, qualified providers, access and applicable requirements. Do not invent intervals or passing test results.
Fairfax County describes certified testing and reporting responsibilities. Las Vegas Valley Water District maintains, tests and replaces covered devices through its program. These local examples are not interchangeable. Verify the utility, device and responsibility before offering private testing.
Make leak evidence useful, not dramatic
With authorized meter data, prepare anomalies for professional investigation and compare occupancy or seasonal changes. A shared meter or unusual use is not proof of a leak. After verified repair, use measured volume and the customer’s actual applicable water/wastewater tariff to explain savings.
EPA’s leak-detection guide uses illustrative engineering and historical rate assumptions, not a current local quote. No AI-controlled shutoff or guaranteed savings. CDC water-management guidance supports professionally governed documentation, not automated health certification.
Buy a cleaner handoff, not a bigger software stack
Measure review-adjusted office minutes, repeat calls, authorization gaps and rejected closeouts. Capacity is not cash saved unless a real cost falls or valuable work is actually enabled. Earlier invoice readiness does not change the customer’s payment terms by itself.
Use existing forms and service-platform rules first. If custom work is warranted, price integrations, account-rule setup, monitoring and handover explicitly. Test wrong POs, missing approvals, disputes and failed integrations before release.
Define a disputed-job path before connecting accounting. If authorization is unclear, the closeout can organize the evidence without treating a technician’s note or a completion signature as permission for extra charges. Keep the original record, identify the responsible reviewer and pause the affected customer document. A clean-looking packet is not a reason to conceal an unresolved commercial disagreement.
