Applicants & parking
Who owns the booked unit (the primary applicant and the co-applicants with their ownership shares) and which parking slots came with the booking.
Applicants & parking
This tab lists everyone who will own the unit and the share each holds, and the parking slots that were allocated with the booking. Use it to add a co-applicant after booking, correct a relationship or share, or take a co-applicant off.
Where to find it
Open a booking and choose the Applicants & parking tab. It is the second tab and is always shown to anyone who can view the booking (the View permission on Bookings).
What you see
Applicants card
The subtitle reads "The primary applicant holds <x>%; co-applicants share the rest." The primary applicant's share is worked out as 100% minus everything the co-applicants hold.
- The first row is the primary applicant (the opportunity's contact) with a Primary badge, "phone · email · PAN …" underneath, and their share on the right.
- Each co-applicant follows, in the order they were added: name, relationship, "phone · email", their share (or "—" when none was entered), and the edit and remove icons.
Parking slots card
Each parking slot allocated with the booking, as "<parking slot no> <parking area>" with its status badge. When there are none it reads "No parking slots allocated with this booking."
The note under the list explains: "Parking slots are allocated when booking and released on cancellation; manage the project's parking slots from its Parking tab." The link opens the project's Parking tab. Parking can't be changed on this screen.
KYC & documents card
One block per applicant with their residential status (Resident, NRI, OCI, Foreign National), PAN, masked Aadhaar, date of birth and passport, and the document checklist built from the KYC document types lookup: Document, Status (Pending / Received / Verified / Rejected, a dropdown with the Edit permission), Received, Verified. The badge counts "N of M received". Build checklist (later Refresh checklist) adds the rows each applicant is expected to provide: NRI rows join only for non-resident applicants, Company rows only for a company buyer. Edit KYC (the Edit permission on Contacts) opens the applicant's KYC form: Aadhaar is 12 digits and shown masked once saved. The plus icon asks one applicant for another document type; only a Pending row can be removed. Scanned copies go under the Documents tab.
What you can do
All three actions need the Edit permission on Bookings and an Active booking. In the default roles that is the Administrator, the Sales Manager and Legal & Documentation. On a cancelled booking, or without the permission, the button and icons aren't shown.
Add co-applicant
Opens the panel "Add co-applicant".
- Contact: pick an existing contact, or enter a new one (a first name and a phone number at least). The choice between the two needs the View permission on Contacts; without it you can only enter a new contact. Validation messages: "Pick a contact", "First name is required", "Enter a phone number (at least 5 digits)".
- Relationship (placeholder "e.g. Spouse"; up to 50 characters).
- Share (%, 0 to 100).
Confirm with Add co-applicant (or Cancel to close without saving). A toast reads "<name> added as co-applicant." A new contact is created with the customer contact type. Refusals appear in a banner at the top of the panel.
What the app refuses:
- Shares that go past 100% in total: "Co-applicant shares add up to <n>%, more than 100%".
- The primary applicant added again as a co-applicant: the message shows as "The primary owner cannot also be a co-owner."
- The same contact twice on one booking: "That conflicts with existing data."
Edit a co-applicant
The pencil icon (label "Edit <name>") opens a panel titled with the co-applicant's name. Only Relationship and Share can change; the contact itself can't be swapped. Save changes stays greyed out until you change something. A toast reads "<name> updated." The 100% rule applies here too.
Remove a co-applicant
The trash icon (label "Remove <name>") asks "Remove co-applicant?" with "<name> will no longer be a co-applicant on <booking no>. The contact record is kept." Confirm with Remove. A toast reads "<name> removed."
Things to know
- Shares are ownership, not payment. They record who owns what part of the unit for the agreement; demands and receipts are raised on the booking as a whole, not split by applicant.
- The primary applicant can't be changed here. The primary is the contact on the opportunity, so the booking always belongs to the person the deal was made with. To book in a different name, cancel and book again from a fresh opportunity.
- The primary applicant's share is whatever is left. You never type it; it is 100% minus the co-applicants' shares, so adding a 50% co-applicant leaves the primary with 50%.
- Parking follows the estimate. Parking slots were chosen on the estimate before booking, so this tab only shows them. They are released automatically when the booking is cancelled.
- Allottee purchases (a landowner or tenant buying their allotted unit) may already carry co-applicants: when the booking was made with none, the allottee's co-owners were copied in with their shares.
- Two messages use the tenant wording of the rehab side: "The primary owner cannot also be a co-owner." and "The 'Tenant' contact type is not configured. Ask an administrator to add it under Lookups." On a booking the second one means the customer contact type is missing from your organization's lookups; ask an administrator to add it.
Related
Related
- Booking overviewScreen
A booking's home page: the applicant and unit, parking, dates, money summary, termsheet status and possession, with the buttons to edit the booking, see its history, jump to the opportunity or cancel it.
- Book <unit> for <name> (booking wizard)Screen
The three-step wizard that turns an approved estimate into a booking: review exactly what was approved, add co-applicants and their shares, set the booking date and book the unit.
- Termsheet & scheduleScreen
The buyer's termsheet: the agreed charges and the installment schedule with GST, the TDS the buyer deducts and what is payable to the developer, plus the actions to issue, accept, sign, reopen or regenerate it and to re-date an installment.
- Cancel bookingScreen
The four-step wizard that cancels a booking: it shows the demands and receipts that will be reversed, suggests the forfeiture and charges from the rule in force, sets the refund and posts everything in one go, releasing the unit and parking and marking the opportunity lost.
- ParkingScreen
Set up the project's parking areas (basement, podium, stilt) and their numbered parking slots, see who holds each parking slot, and allocate parking slots to society members.
- ContactsScreen
The master list of every person your organization deals with, with a panel to add, edit, deactivate or delete a contact and see who changed the record.
- LookupsScreen
The dropdown lists every form draws on: contact types, lead sources, activity types, company types, bank account purposes, parking types, amenities, unit types and unit configurations.
- Greyed-out buttonsScreen
Why a button is grey and can't be clicked, where to read the reason, and why some buttons are missing altogether.
- Booking: agreed total, applicants and sharesConcept
A booking is the closed deal on one unit for one opportunity, made from the current Approved estimate: it fixes the agreed total, numbers itself by financial year, books the unit and parking, and names the primary applicant and the co-applicants with their ownership shares.
- Allottee purchasesConcept
How an allottee buys the units their offer allots: one purchase per allotted unit, priced only on the area beyond their entitlement, through the same estimate, payment plan, approval and booking chain as any buyer, with the unit staying Allotted throughout.
- Book a unitHow-to
Turn an approved estimate into a booking: review what was approved, add the co-applicants and their shares, set the booking date and book, then record the agreement details and any co-applicant who joins later.
- Parking areas and parking slotsConcept
A parking area (basement, podium, stilt) holds numbered parking slots that are inventory like units: held by a sent estimate, booked with the unit, or allocated to an allottee from the project.