Booking approvals

The approval chain

Every project has an approval chain, and every submitted booking runs through it in order. The built-in chain is Sales person → Team head → Booking approver → CRM → Accounts. The Sales person level is the rep's own submit and is approved automatically; the Team head is whoever the rep reports to; the other three are named people on the project. A company can rename levels, add its own (for example Sales Support or a director's sign-off) and remove the first two; the Booking approver, CRM and Accounts levels are always present and keep their order.

The chain is shown on the booking's Overview tab under Approval chain, one card per level with the approver's name, the status, any remarks, and a checklist of what still blocks that level.

Approving or rejecting

1. Open the booking (from Bookings › Pending approval or the notification) and read the form, the Cost & brokerage tab and the Documents tab.
2. On your level's card click Decide. The button is disabled until the checklist above it is clear.
3. Choose Approve or Reject, add Remarks (optional, kept on the booking) and click Submit decision.

• Levels decide in order: a level cannot approve while an earlier one is pending.
• CRM cannot approve until the Booking Form, Id Proof and Address Proof are uploaded and verified, and the applicant has an address.
• Accounts cannot approve while the booking has receipts that are still on verification.
• The last level is also blocked while the client has an open lead clash; the site head settles the clash first.
• A partner booking is refused at every level if the brokerage is missing (and not waived), or the firm's RERA number is not valid for the project's authority.
• A rejection sets the status to Rejected. The unit stays with the booking; the rep sees Revise and resubmit and the same chain runs again on the corrected form.
• Self-approval is allowed (a head who is also the rep), and is written to the audit log.

Revisions, notify and reassign

• The Revisions tab keeps Review rounds (every submit, approval and send-back with its remarks) and Changes made in review (each field changed on the form while it was in review, before and after, and where approval picked up again).
• Notify sends the approver a reminder.
• Reassign (admins and project managers) moves a pending step to another person, with a reason. The previous approver loses the booking; the new one is told.
• The header shows Edit for the rep while the booking is a draft or rejected, and for heads and approvers at any time before approval.

Setting the chain for a project

1. Go to Real estate › Projects and click the Approval chain action on the project's row.
2. Rename a level, use the arrows to reorder, the bin to remove a non-core level, or Add a level for a custom one and name the person who decides it. Levels tagged From the rep and From the reporting tree need no name.
3. Pick the Booking Approver, CRM and Accounts people, then click Publish as version N.