Change Control — Closing Appointment
The closing case is a moving object
A land-registry application is not frozen when submitted. The office may request a correction, a party may change representative, an identity document may be renewed, the property record may change, a fee notice may be replaced or the transaction may be routed differently. Change control keeps the file aligned with the live official case. It prevents a team from preparing, paying or appearing on the basis of an earlier version after the facts or official instructions have moved.
Create a baseline at submission
Record the application channel, office, case/reference number, submission date, parties, representation, registered property identifiers, transaction type and the document set actually submitted. Preserve the original acknowledgement or system record. This is the baseline against which later changes are compared. Do not use a generic “appointment folder” containing mixed screenshots; each item should show its source, date and relationship to the case.
Capture changes at field level
When something changes, record the old and new value: representative A to B, passport X to Y, parcel identifier, independent unit, office, application reference, fee amount, missing-document request, intended transaction type or scheduled procedural step. Explain who initiated the change and why. Attach the official or primary evidence. A field-level log is important because “case updated” does not tell a reviewer whether the update was harmless contact information or a change that affects legal authority or the subject property.
Classify what the change reopens
Identity changes reopen identity checks; a new representative reopens authority and powers; a property identifier change reopens title, contract and valuation matching; a new title entry reopens risk and payment gates; a changed office or application reference reopens routing and fee instructions; a changed date reopens validity of time-sensitive documents. Write these dependent checks in the change record. A new case version cannot inherit every old approval automatically.
Follow the current WebTapu/Alo 181 process
TKGM’s current notice should guide how the application is tracked. Since the former e-Randevu route was ended, a change log should preserve current WebTapu/Alo 181 or office-specific communications rather than old e-Randevu assumptions. If the office returns the application or creates a new reference, do not continue under the obsolete reference. Keep both references linked so the history can be reconstructed while the active file points to the current case.
Revalidate money instructions after material change
A schedule change alone does not necessarily change the purchase price, but it can make an earlier payment approval stale. Any change in seller, representative, beneficiary, property, encumbrance status or contract milestone should reopen the payment gate. Fee amounts and official payment references should also be refreshed if the case changed. Never transfer because “payment was already approved yesterday” when the information supporting that approval has changed.
Freeze a final closing package
Before the parties execute the transaction, create a final package with the current case message, identities, representation evidence, property match, required documents, fee instructions and open-exception status. Mark it with time and version. If a change occurs after the freeze, reopen control and issue a new package rather than editing the old one silently. The document or data actually used in the official act should match the final package or have a recorded explanation for any system-generated difference.
Preserve old states for audit
Do not delete returned applications, replaced messages or previous versions. Mark them inactive or superseded and keep the reason. This is especially useful if a later dispute asks why a transaction was delayed, why a different representative appeared, or why amounts and dates changed. The active file should be simple, but the historical trail should remain complete.
Closing standard
A change is controlled only when it is identified, evidenced, assessed for impact, approved where necessary, propagated to dependent checks, and reflected in the final official case. The purpose is not to resist legitimate corrections. It is to ensure that every decision—attendance, signing, fee payment, purchase-price release and registration—uses the same current set of facts.
