How to connect projects, prospects and payments without multiplying files

A property sale should not be split into three separate stories

In many teams, unit inventory lives in a sales grid, prospect conversations in another file, and due dates in a table kept by administration or finance. Each file may be correct on its own. The problem appears the moment you try to reconcile them.

A salesperson can offer a unit without seeing that an option was just placed on it. Management can count a reservation without knowing the next due date. Finance can receive a payment without immediately finding the project, the unit and the record it belongs to. The lost time does not come only from data entry: it comes from hunting for the right context.

The guiding principle: every important piece of information must have a clear source, then stay connected to the record throughout the whole sales journey.

1. Start with a reliable project–unit foundation

The project and the unit form the shared reference. Before organising the sales pipeline, you have to stabilise the information the whole team uses: unit identifier, building or phase, property type, floor area, price, status and available documents.

Every significant change must leave a trace. A price change, an option or a reservation should not simply overwrite an old value without context. A readable history lets you understand who made the change, when it happened and which record triggered it.

• Use a unique, stable unit identifier.
• Define a short list of statuses everyone understands.
• Attach plans, prices and characteristics to the same unit.
• Avoid local copies of the sales grid.

2. Move the prospect forward without losing their context

A useful prospect record is more than a name and a phone number. It should hold the source of the enquiry, the need, the budget, the projects considered, the viewings, the notes and the next action. When a colleague picks up the file, they should understand the situation without reconstructing the conversation.

The link between prospect and unit can evolve. At first, the prospect is interested in a property type or a project. Then a viewing or an option narrows the choice. The system must preserve that path without turning every step into an isolated new row.

• Assign an owner and a next action to every active record.
• Record viewings, calls and notes in a shared timeline.
• Connect interest to a project before a specific unit is chosen.
• Measure movement between stages rather than raw contact volume.

3. Place the payment in the continuity of the sale

Financial tracking becomes simpler when the payment schedule is generated from the reservation or sale record. Every deposit, instalment and collection then keeps its link to the buyer, the unit and the project. Finance no longer has to interpret a free-text reference to understand where a transaction came from.

This continuity also lets you separate what is planned, what has fallen due and what has actually been collected. Management can read a collection rate or an outstanding balance without confusing a sales commitment with cash actually received.

• Generate a payment schedule attached to the sales record.
• Keep issue, due and payment dates.
• Distinguish paid, pending and overdue.
• Match every payment to the right record before consolidating indicators.

Putting the continuous thread in place without blocking the team

There is no need to migrate every archive on day one. Start with one active project, clean up the unit grid, import the prospects that are still open, then bring over the relevant reservations and payment schedules. This reduced scope lets you test the rules against real cases.

After a few weeks, check the gaps: units without a reliable status, prospects without a next action, reservations without a payment schedule, or payments with nothing attached. These exceptions show where to improve the process before extending the method to other projects.

A good rollout does not try to reproduce every old file. It keeps the useful information and simplifies the handovers between teams.