Validity and deadline control for a preliminary real-estate sale contract
A preliminary sale arrangement in Turkey should be reviewed first for what legal instrument it actually is, not for the label used by a salesperson. A reservation form, ordinary private promise, notarial promise to sell and a real-estate sale contract executed under legally permitted procedures can have different legal effects. Before tracking deadlines, identify the document type, the parties, the property, the form in which it was executed and whether the parties expect an annotation in the land register. The Turkish Code of Obligations, Notary Law and TKGM practice provide the legal framework; the file should not assume that every “preliminary contract” creates the same enforceable right.
Confirm parties and authority before calculating time
The buyer and seller named in the document must match the legal persons who are supposed to perform. Check identity, corporate authority, powers of attorney and, for a developer sale, the entity that actually owns or is authorised to dispose of the registered property. A deadline cannot be evaluated intelligently if the person required to transfer title lacks authority. If representation documents have an expiry, a joint-signature requirement or a transaction-specific limit, place those dates in the same control sheet as the contract milestones. Changes in party identity or representation should trigger an amendment or renewed verification rather than being handled by informal email alone.
Identify the property with registered data
The contract should be tied to cadastral identifiers or to a demonstrable chain leading to the future independent unit. Record province, district, neighbourhood, block, parcel, project building and unit details, and compare them with the current title status. If the project is still under construction and the unit description may change, preserve the approved plan or allocation evidence explaining the mapping. A validity review should flag a contract whose subject cannot be reliably matched to the registered asset, because even a perfectly drafted payment calendar does not cure uncertainty about which property must ultimately be transferred.
Build a deadline table from the contract itself
Extract every date that creates a right, duty or consequence: reservation expiry, deposit due date, instalments, document-delivery dates, construction milestones, notice periods, final payment, title-transfer target and any long-stop date. For each event, record who must act, what evidence proves performance and what the contract says happens after delay. Distinguish a calendar date from a period calculated after notice, completion or another trigger. If a deadline is extended, retain the original term and the signed extension so the chronology remains auditable. Do not silently overwrite old dates in the database.
Control conditions that must exist before payment
Some payments should depend on conditions such as authority confirmation, building or title status, bank release, delivery of specified documents or satisfaction of a contractual milestone. The control file should state whether each condition is documentary, technical or legal and who is authorised to confirm it. If a large payment is due before the condition can reasonably be verified, the risk should be escalated before funds are transferred. A deadline review is therefore not merely a reminder calendar; it is a test of whether the payment sequence, evidence sequence and title-transfer sequence are logically aligned.
Track notices, amendments and land-register annotation
If the agreement contemplates a formal notice, termination right, penalty, extension or annotation of a promise in the land register, preserve the required form and timing. An informal message may not satisfy a contractual or statutory notice requirement. Where a notarial promise to sell is annotated, retain the application and registry result and review the current legal effect with official guidance rather than relying on marketing statements. Amendments should identify the clause changed, the new date or obligation and the authorised signatures. Multiple unsigned schedules create ambiguity and should not be treated as operative simply because a payment team used them.
Revalidate before the final title-transfer date
Long-running preliminary contracts can outlive passports, powers of attorney, corporate signatories, valuations, permits or other evidence that was current at signing. Shortly before final transfer, recheck the items that must still be valid and compare the latest title record with the property promised in the contract. Confirm outstanding payments, fees and documents through official channels. If construction, subdivision or condominium registration changed identifiers, reconcile the change formally. The closing decision should be based on current evidence, not on the fact that a contract was valid when originally signed.
Close the contract file with a complete chronology
When title transfers, keep the executed contract, amendments, notices, payment evidence, milestone confirmations, any land-register annotation and the final title result together. If the deal terminates, preserve the termination basis, refund or settlement evidence and any release rather than simply marking the file “cancelled.” A future reviewer should be able to reconstruct the life of the agreement from signature through performance or termination. That chronology is the best protection against disputes over missed deadlines, unofficial extensions, conditions that were never satisfied or payments made after the legal basis for the preliminary arrangement had changed.