The scene
The first request is only the first version.
Someone contacts you looking for a two-bedroom apartment in a specific area. After a phone call it turns out the daily commute matters more than the neighborhood. At the first viewing their sense of the space shifts. Then the budget narrows, or an option opens up that didn’t exist before.
These aren’t contradictions to fix: they are details that make the request truer. The problem starts when each change overwrites the previous one without leaving a trace. A property ruled out yesterday can become relevant again, but nobody remembers why it was ruled out in the first place.
Four layers
Separate what stays from what moves.
The record shouldn’t become an endless list. It should help you work out what to propose and which question to ask next.
The method
Update the request without rewriting the history.
After each contact, change only what you have really learned. If an area doesn’t work because of the commute, record the reason. If the budget is still uncertain, leave it as an open question instead of turning it into a made-up number. If a viewing shifts a priority, link that evidence to the criterion that moved.
That way the next shortlist doesn’t start from isolated filters. It starts from a sharper understanding of the person. A colleague, or you tomorrow, can read the path without rebuilding it from messages, notes and appointments.
With Avanlio
Person, request, properties and viewings stay on the same thread.
Avanlio is built so the request doesn’t live in a note separate from the properties you’ve considered and the conversations that made it evolve. You can keep the current criteria, viewings, open decisions and the next thing to do close together. Assist can suggest an update from the sources you choose, but changes nothing without clear confirmation.
The benefit isn’t guessing what the client wants. It’s keeping enough context to ask the right question and propose the next step more precisely.
If the relationship has only just begun, also read what to keep after the first property call. Or see how Avanlio works for independent real estate agents.
Questions
Short answers.
How do you keep track of a property request that keeps changing?
By separating what stays (the stable reason) from what moves (criteria, observed signals) and updating only what you have really learned after each contact.
Why keep the reason for a change?
Because a property ruled out yesterday can become relevant again, and without the reason for the first choice nobody remembers why.
What should the next check contain?
A question, a proposal or a viewing that confirms the hypothesis instead of adding noise.