Contracts and Documents: Findable When It Matters

Contracts and Documents: Findable When It Matters

Across the last four parts we brought three daily cycles under control: unit status, the money cycle from due date to renewal, and the maintenance cycle from report to close. Each of them produces paper. A contract, an annex, a receipt, a photo, a record, a report. That paper is the silent layer nobody thinks about until the moment everybody needs it at once.

And that moment always arrives in the same shape: a tenant leaves and claims the full deposit, or says the crack in the marble was there before they moved in, or denies receiving a third key, or claims a payment they say they made in cash. Remembering does not help here. Finding does. And the gap between an office that produces its document in a minute and one that searches for three days is not a tidiness gap — it is an entirely different negotiating position.

Why a document goes missing while still being stored

Most offices do not actually lose their documents; they lose the ability to reach them. The reason is that files get stored under a person or a date rather than under the unit they belong to. These are the five most common places where a stored document becomes unfindable:

• The folder named after an employee. A folder on a laptop or a personal inbox, organised by its owner's own logic. When they leave, the folder stays and its map goes with them, and searching it takes longer than searching the drawer.
• The file inside a conversation. The contract or receipt was sent on WhatsApp and stayed there. A chat is not an archive: searching it depends on remembering who sent it and roughly when, and the first phone change wipes half of it.
• The paper with no copy. The signed original sits in exactly one file. Any fire, leak or office move means a permanent loss with nothing to fall back on.
• The document with a meaningless name. Files called WhatsApp Image or Scan 47, all saved in one place. They exist in theory and are unfindable in practice.
• Multiple versions with no authoritative one. Three copies of the same contract — one before amendment, one after, and one nobody can place. When the two sides disagree you discover you cannot say which one was actually signed.

What all five share is that the filing was designed for the convenience of whoever stored it, not for the need of whoever will search two years later. And whoever searches two years later may not be you.

The unit file: the only rule you need

The rule is simple enough to sound trivial: every document is stored against the unit first, then against the contract or request inside it. Not the tenant, not the employee, not the year. The reason is that the unit is the only fixed element in the equation. Tenants change above it, staff change around it, years pass — and the unit stays with its accumulated history.

When that unit file is opened, it should answer the question in full without a single phone call. What deserves to live in it:

• The contract and its annexes. The final signed version, plus any later annex changing a term, an amount or an obligation. The annex is stored attached to the contract rather than beside it, because a contract without its annex is a misleading document.
• The parties' details. What you need for statutory registration and for contact, per what the regulator requires — while remembering that this is personal data governed by the Personal Data Protection Law, collected and kept only for the purpose it was gathered for.
• The handover record with photos. The most important document in the whole file and the most neglected. Unit condition on handover day, meter readings, key count, a list of appliances or furnishings, signed by both sides — with dated photos of every room.
• The payment ledger and receipts. Every amount that fell due, every amount posted, and its supporting document. This is what we built in part three; here we store its trace rather than its promise.
• Maintenance requests and their reports. The unit's reports, before and after photos, and costs. This is the output of part four, and here it becomes the technical history of the asset.
• Correspondence that carries effect. The renewal notice, the arrears notice, an agreed extension, any waiver. Correspondence that creates an obligation is kept; passing chat is not.

Notice that four of these six are natural outputs of the earlier parts. You are not starting a new activity called archiving — you are storing, in the right place, what your operation already produces every day.

What a dispute actually needs

People store a great deal and lack the few things that settle matters. Recurring residential and commercial lease disputes tend to revolve around four questions, and each has exactly one document that answers it:

• What did we agree? Answered by the signed contract with its approved annexes. A lease registered through the Ejar network carries a documentary status different from a page signed privately between two parties.
• In what condition was it received and returned? Answered by the handover record with dated photos and its matching move-out record. Without those two, every deposit discussion ends in personal judgement.
• Did they pay? Answered by the posting document linked to the contract, not a message saying the transfer is done. Where a tax invoice is required, it performs this role formally as detailed by the Zakat, Tax and Customs Authority.
• Did they report it and did we respond? Answered by the maintenance request log with its dates, and by renewal and arrears notices with their send dates.

Here is a test you can run today: pick a contract that ended a year ago and try to gather those four items about it in five minutes. If you succeed, your filing is sound. If you need to call someone, you are relying on a person's memory rather than a record — and that is the entire problem in one sentence.

Storage, privacy and retention

A good archive is not the biggest archive. Keeping everything forever is not diligence but exposure, because every personal document you hold is an obligation to protect it. Three practical considerations govern this:

First, tenants' personal documents in the Kingdom fall under the Personal Data Protection Law overseen by the Saudi Data and AI Authority, whose core principle is that data is collected for a specified purpose, not used for another, and not kept once the need for it ends. In practice that means ID photos have no place in a WhatsApp group or on a personal device, and access is limited to those who need it for their work.

Second, documents with financial and tax effect have statutory retention periods. Check the invoice and record-keeping requirements published by the Zakat, Tax and Customs Authority and apply what they state to your case, rather than relying on a general assumption.

Third, a backup is part of storage rather than an addition to it. One file on one device is not an archive no matter how tidy it is. The simplest rule is that every important document has a copy in a physically different place, and that you verify from time to time that the copy actually opens rather than merely exists.

The Origami view

Real estate and hotels is one of our specialisation sectors, and we treat a document as part of the unit's record rather than as a file uploaded somewhere on the side. The practical difference is that once a document is linked to its unit, contract and request, it becomes findable from the natural starting point — the unit that has the problem — instead of from trying to remember the name of whoever filed it.

The order we recommend: make storing a step inside the process rather than a task afterwards, so that signing a contract or closing a maintenance request is not complete until its document is attached; then standardise naming; then set who can see what; then backups and retention periods. We apply this order in real estate and hotels projects because archiving detached from the daily process becomes a deferred task within weeks, and then an incomplete archive that offers false reassurance.

What you can do this week

• Pick five units only and build each a complete file with the six document types above. Five units is enough to reveal what you are genuinely missing.
• Standardise naming with one rule that starts with the unit number, then the document type, then the date. The rule itself matters far less than it being singular and written down.
• Audit handover records for your live contracts and count how many have no record or no photos. That is your direct risk list at the end of every one of those contracts.
• Move identity documents out of chats and personal devices into one access-limited place, and delete the scattered copies.
• Try restoring one backup and confirm it opens. A backup that has never been tested is not a backup.

Coming next

Now that each unit has a file its owner can reach when it matters, the next part turns to one document with its own regulatory requirements: e-invoicing for rent and brokerage. What changes at the moment of collection rather than in the accounting department, how to handle brokerage commission, administrative fees and credit notes, and where to verify a requirement with the authority instead of relying on hearsay.

Sources

• Real Estate General Authority — regulation of the Saudi real estate sector and its platforms and services.
• Ejar Network — registration of lease contracts and the data of their parties and terms.
• Saudi Data and AI Authority — the Personal Data Protection Law and controls on collecting and retaining data.
• Zakat, Tax and Customs Authority — invoice and record-keeping requirements.
• Ministry of Municipal and Rural Affairs and Housing — policies governing the municipal and housing sectors.
• Ministry of Tourism — regulation and licensing of tourist accommodation facilities in the Kingdom.