The short answer
Identify the issuer, document heading, parties, property and registration references on your own file. Compare those details with the SPA and later amendments. Formats and labels may differ. The checklist below is a reading aid, not an official certificate or a template for creating one.
A field-by-field reading aid
| Look for this information | Compare or ask |
|---|---|
| Document heading and issuing authority | Is it an official registration output, a private SPA, a payment receipt or a developer summary? |
| Registration or certificate reference | Keep its exact label and any associated year. Ask which reference the relevant enquiry needs. |
| Application reference | Use for application follow-up; do not assume it is the issued certificate number. |
| Purchaser or ownership information | Compare the names and any shares shown with the signed contract and approved changes. |
| Project, plot, building and unit | Check which official references correspond to marketing or internal developer labels. |
| Date and version | Establish whether a later amendment or final title deed exists. |
| Area or consideration, where shown | Compare like-for-like units and definitions; ask for explanation of differences. |
Not every file places these details in the same position or contains every item in this table. A missing field should prompt a question about the document type and full file, not an invented replacement value.
Where is my Oqood number?
Start with the field explicitly labelled as the registration, certificate or contract reference on the issued document. Record the label together with its value. If a service asks for a different identifier, ask the developer or DLD to confirm the correct field.
For example, keep “SPA reference”, “application reference” and “certificate reference” as separate rows in your notes. Do not label every number “Oqood number” and then try them interchangeably in an official form.
Is an Initial Contract of Sale the same as Oqood?
You may see “initial contract of sale”, “provisional registration” or “pre-title deed” used when discussing off-plan records. Establish whether the file is the DLD registration output or the private contract signed with the developer.
The word “contract” in a heading is not enough to decide. Identify the issuer and registration evidence. The meaning guide explains the distinction between an SPA and official registration.
What if the area, buyer or unit is different?
Retain the original files. Ask for the relationship between the references to be explained, including any approved amendment or survey basis. An internal unit label can differ from a registered label; that does not make every difference harmless.
For a genuine provisional-record amendment, DLD publishes a developer-side service requiring supporting contractual documents, including the amendment annex and reason. A bank letter can also be relevant to finance. Use the correction-support route to organise the request. Do not edit the PDF and present it as an official correction.
Can I see a sample?
This field map answers what to inspect without imitating an official certificate. Our fictional sample review report is a different document: it demonstrates how Cendale would explain matches, differences and unanswered questions.
An official-looking design, stamp or QR image cannot establish authenticity. Follow the verification guide for the appropriate official enquiry and evidence trail.
Questions people ask
Should a joint buyer always appear exactly as I expect?
Compare the ownership information actually shown with the approved purchase and registration documents. Ask for confirmation if a buyer or share appears absent; do not fill in the gap yourself.
Can I share a sample online to ask for help?
Remove personal identifiers, signatures, reference numbers and machine-readable codes before public sharing. Use an agreed private channel if an adviser needs the full file.