Skip to main content

Applications

Applications is the internal review workspace for buyer applications submitted through the public form or entered by authorized staff. It brings together the applicant's information, preferred lot, intended use, payment preference, acknowledgements, review notes, linked lead, availability context, and decision status.

An application is a request for consideration. Submission does not reserve a lot, confirm financing, create a payment, or guarantee approval.

Application statuses​

The core application statuses are:

  • Pending Review — the application has not received a final authorized decision.
  • Approved — an authorized human reviewer has recorded approval according to the business process.
  • Declined — an authorized human reviewer has recorded that the application will not proceed under the reviewed conditions.

Exact labels and permissions should be confirmed in the live environment before training is finalized.

What to review​

Before making a decision, review:

Applicant identity and contact information​

  • full name;
  • phone and email;
  • address or other required identity information;
  • whether contact details match the linked lead; and
  • any possible duplicate context.

Lot and project context​

  • preferred project and lot;
  • current lot status;
  • active reservation context;
  • whether the lot became unavailable after submission; and
  • whether an alternative lot discussion is required.

Purchase and payment context​

  • intended use;
  • payment option or installment preference;
  • deposit or financing information requested by the form;
  • required acknowledgements; and
  • information that still needs verification by Finance or management.

Supporting notes and completeness​

  • applicant notes;
  • staff review notes;
  • missing required information;
  • inconsistencies between fields; and
  • linked lead activities that explain the buyer's current position.
  1. Open the application and confirm the applicant identity.
  2. Review the linked lead and latest activities.
  3. Check the Possible Duplicate indicator and compare records where necessary.
  4. Open the preferred lot and confirm status and reservation context.
  5. Review completeness and required acknowledgements.
  6. Review payment-option context without treating it as financial approval.
  7. Read any AI review or smart insight as advisory information only.
  8. Record factual review notes.
  9. Obtain any required business, legal, finance, or management confirmation.
  10. Record the authorized human decision.
  11. Notify or assign the next responsible staff member according to the business process.
  12. Confirm that the linked lead, customer, reservation, and follow-up work reflect the decision appropriately.

AI application review​

Where enabled, the platform may generate an application review or highlight information needing attention. This is intended to help the human reviewer notice missing, inconsistent, or high-priority information.

AI review does not:

  • approve or decline the application;
  • verify the applicant's identity;
  • confirm that a lot is available;
  • confirm payment ability or financial truth;
  • replace legal or business-policy review; or
  • update the final application status by itself.

The reviewer should compare every material statement with the application and linked records.

Possible Duplicate indicators​

A possible duplicate may be identified through normalized email, phone, or buyer name plus preferred lot. Reviewers should:

  1. open the related records;
  2. compare identity and submission context;
  3. determine whether the person submitted twice, submitted an update, or is a different buyer;
  4. avoid deleting or merging records without an approved process;
  5. continue the correct application review; and
  6. document the decision about how parallel records will be handled.

The duplicate indicator does not automatically block submission or lead creation.

When the preferred lot is unavailable​

Do not approve the application against an unavailable lot without an approved resolution.

  1. Verify the lot's current status and reservation context.
  2. Review when the application was submitted and what the buyer was told.
  3. Notify the assigned sales owner.
  4. Discuss verified alternatives with the buyer.
  5. Record the buyer's decision in the lead activity history.
  6. Update the preferred lot only through the approved process.
  7. Continue, pause, approve, or decline the review according to business policy.

Do not disclose another buyer's personal information when explaining the lot change.

Approval​

Before recording approval, confirm that:

  • the applicant information has been reviewed;
  • the lot or approved alternative is valid for the decision;
  • required information and acknowledgements are present;
  • any required manager or finance review is complete;
  • the reason or review notes are sufficient; and
  • the downstream customer, contract, reservation, and follow-up process is understood.

Approval is a human business decision. The person recording it should be authorized and identifiable in the record history.

Decline​

Before recording a decline:

  • confirm the applicable business reason;
  • avoid vague, discriminatory, or speculative notes;
  • record factual internal context;
  • follow the approved communication process;
  • close or update linked sales work appropriately; and
  • preserve the application history.

A decline should not be used merely to remove an incomplete application from a queue when further information is expected.

Example: incomplete application with duplicate context​

A fictional buyer, Selena Training, submits an application using a different phone format from an earlier inquiry. The system flags a possible duplicate, and the selected lot is Reserved to another buyer.

  1. Staff compare the email, normalized phone, name, and lead history.
  2. The records are confirmed as the same buyer; both records are preserved according to policy.
  3. The preferred lot is checked and confirmed unavailable for a new hold.
  4. Sales contacts Selena with verified alternative lots.
  5. The application remains Pending Review while the buyer selects an alternative and provides missing information.
  6. Review notes explain the duplicate and lot context.
  7. The application is approved or declined only after the authorized review is complete.

Common mistakes​

  • Approving because the application appears complete without checking the lot.
  • Treating AI review as the decision.
  • Declining an application only to remove it from Pending Review.
  • Ignoring duplicate context and creating parallel follow-up work.
  • Changing the preferred lot without recording the buyer's agreement.
  • Treating payment preference as confirmed financing or a recorded payment.
  • Failing to update the linked lead after the decision.
  • Including unnecessary sensitive information in review notes.

Suggested training media​

Screenshot space: Add an application-list screenshot showing status, applicant, preferred lot, submission date, duplicate indicator, and review priority. Annotate the filters used for Pending Review and unavailable-lot exceptions.
Screenshot space: Add an application-detail screenshot showing applicant information, lot context, linked lead, completeness indicators, review notes, AI review panel, and decision controls. Clearly label advisory versus authoritative sections.
Screenshot space: Add a side-by-side duplicate-review example with two fictional submissions and the email, phone, name, preferred lot, and submission dates highlighted.
Diagram space: Add the application decision flow: Submit → Identity/duplicate review → Lot verification → Completeness review → Required human review → Approve, decline, or request information → Downstream customer/contract or closure.
Video space: Record an 8–10 minute application-review walkthrough using the Selena Training scenario. Demonstrate duplicate review, lot verification, missing-information notes, and the point at which an authorized human may make the decision.