SOP — Lead to reservation
Purpose: create a controlled temporary lot hold with clear expiry and ownership.
| Field | Standard |
|---|---|
| Trigger | Approved operational decision to hold a selected lot. |
| Responsible role | Authorized Staff/Admin under company policy. |
| Required information | Buyer context, lot, owner, expiry, expected deposit, due date, notes. |
| Steps in platform | Verify lot and active reservations; create reservation; link lead/application/customer as applicable; save status and follow-up. |
| Expected status changes | draft/reserved/deposit_pending according to approved rule. |
| Required documents | Reservation terms/evidence only if company policy requires it. |
| Financial checks | Expected deposit is readiness data; ledger payment is separate. |
| Follow-up deadline | Before deposit due or reservation expiry. |
| Escalation conditions | Existing active hold, missing expiry, disputed lot, or payment claim without ledger record. |
| Completion criteria | Reservation has valid owner, dates, status, and next review. |
| Audit/accountability evidence | Reservation activity timeline and supported audit events. |
| Common mistakes | Assuming parcel status changes automatically; using reservation as proof of payment. |
Media: Diagram, screenshot, checklist.