Skip to main content

SOP — Approved application to customer

Purpose: verify and take ownership of the customer record created/linked after approval.

FieldStandard
TriggerApplication is Approved.
Responsible roleOperations/Admin.
Required informationCustomer identity/contact, approved application, lot, lead, reservation, owner.
Steps in platformOpen customer; verify linked application and contact details; review lot/contract context; assign next owner; start post-sales when ready.
Expected status changesCustomer exists/links from approval; post-sales begins only when staff starts it.
Required documentsApproved application and required onboarding evidence.
Financial checksConfirm no payment is inferred from approval.
Follow-up deadlineFirst customer/contract action per approved policy.
Escalation conditionsCustomer mismatch, missing link, wrong lot, conflicting reservation.
Completion criteriaCustomer ownership and next action are documented.
Audit/accountability evidenceCustomer history, linked application, Audit Trail.
Common mistakesAssuming a contract or payment setup was created automatically.
Media: Screenshot, checklist, fictional scenario.