SOP — Approved application to customer
Purpose: verify and take ownership of the customer record created/linked after approval.
| Field | Standard |
|---|---|
| Trigger | Application is Approved. |
| Responsible role | Operations/Admin. |
| Required information | Customer identity/contact, approved application, lot, lead, reservation, owner. |
| Steps in platform | Open customer; verify linked application and contact details; review lot/contract context; assign next owner; start post-sales when ready. |
| Expected status changes | Customer exists/links from approval; post-sales begins only when staff starts it. |
| Required documents | Approved application and required onboarding evidence. |
| Financial checks | Confirm no payment is inferred from approval. |
| Follow-up deadline | First customer/contract action per approved policy. |
| Escalation conditions | Customer mismatch, missing link, wrong lot, conflicting reservation. |
| Completion criteria | Customer ownership and next action are documented. |
| Audit/accountability evidence | Customer history, linked application, Audit Trail. |
| Common mistakes | Assuming a contract or payment setup was created automatically. |
Media: Screenshot, checklist, fictional scenario.