SOP — Post-sales handoff
Purpose: coordinate work after approval or contract start without implying automation of underlying records.
| Field | Standard |
|---|---|
| Trigger | Customer approved or contract work begins. |
| Responsible role | Post-sales coordinator/assigned staff. |
| Required information | Customer, application, contract, lead/reservation context, assignee, outstanding documents. |
| Steps in platform | Start checklist; set agreement/document/payment-setup/collections-handoff states; create tasks; update timeline and blockers. |
| Expected status changes | Checklist not started/in progress/blocked/completed/cancelled; task states updated. |
| Required documents | Agreements, signed documents, payment setup evidence as required. |
| Financial checks | Payment setup readiness does not create/verify payment. |
| Follow-up deadline | Task due dates and handoff target per policy. |
| Escalation conditions | Blocked agreement/documents, missing payment setup, unclear collections ownership. |
| Completion criteria | Required readiness states verified and tasks resolved or owned. |
| Audit/accountability evidence | Checklist/task/activity history and Audit Trail. |
| Common mistakes | Marking complete before documents or handoff are verified. |
Media: Diagram, screenshot, checklist.