Research · Readiness standard
The Conveyance 20-check transfer-readiness standard
A transfer file should show the evidence behind its next step. This standard sets out 20 checks used to organise identity, records, developer requirements, bank milestones, funds and handover responsibilities.
It is Conveyance’s own preparation method. It is not a government standard, certification, legal opinion or statistical study of Dubai transactions.
The 20 checks at a glance
Conveyance’s own preparation method — evidence, owner, next action and dependency for each check. Not a certification.
- Party identity
- Owners and ownership shares
- Representative authority
- Company signatory evidence
- Registration identifiers
- Unit and record match
- Restrictions or holds
- Sale, gift or assignment route
- Developer requirements
- Service-charge clearance
- NOC usability
- Seller liability and settlement
- Buyer finance conditions
- Lender handoffs
- Funds and amount schedule
- Independently confirmed payees
- Agreed fee allocation
- Originals and attendance
- Document and appointment dates
- Registration output and handover
How to use the standard
For each applicable check, record the evidence, its current status, the person or organisation responsible, the next action and the later step depending on it. Use “confirmed”, “action needed”, “confirmation needed” or “not applicable with a reason”. Do not tick an unknown requirement as complete.
The 20 checks
01.Party identity
- Evidence
- Current identity evidence matches the party taking part.
- Responsible party
- Buyer / seller
- Next action when unresolved
- Confirm the current identification and exact legal names.
- Dependency
- Identity before signing or attendance.
confirmed action needed confirmation needed not applicable (reason)02.Owners and ownership shares
- Evidence
- The current owners and shares match the proposed change.
- Responsible party
- Owner / instructing party
- Next action when unresolved
- Reconcile the current record with the intended ownership.
- Dependency
- Ownership instructions before document preparation.
confirmed action needed confirmation needed not applicable (reason)03.Representative authority
- Evidence
- The required representative authority is identified and accepted for the intended acts.
- Responsible party
- Represented party / adviser
- Next action when unresolved
- Confirm the required scope and acceptance before relying on the representative.
- Dependency
- Authority before signing, bank action or attendance.
confirmed action needed confirmation needed not applicable (reason)04.Company signatory evidence
- Evidence
- Current entity and signatory evidence supports the proposed transaction.
- Responsible party
- Company / authorised signatory
- Next action when unresolved
- Supply the corporate evidence and resolve the signing-authority question.
- Dependency
- Entity readiness before its transaction actions.
confirmed action needed confirmation needed not applicable (reason)05.Registration identifiers
- Evidence
- The relevant current registration record is identified.
- Responsible party
- Owner
- Next action when unresolved
- Obtain the current title or provisional-registration reference.
- Dependency
- Record identification before route confirmation.
confirmed action needed confirmation needed not applicable (reason)06.Unit and record match
- Evidence
- Unit, project and property references agree across the file.
- Responsible party
- Buyer / seller / coordinator
- Next action when unresolved
- List and resolve any conflicting identifiers.
- Dependency
- Correct property before applications or payments.
confirmed action needed confirmation needed not applicable (reason)07.Restrictions or holds
- Evidence
- Known restrictions and the necessary official confirmation are addressed.
- Responsible party
- Owner / relevant authority
- Next action when unresolved
- Identify the restriction and the action required by the responsible organisation.
- Dependency
- Route readiness before appointment.
confirmed action needed confirmation needed not applicable (reason)08.Sale, gift or assignment route
- Evidence
- The proposed basis and property status are clear.
- Responsible party
- Instructing party / coordinator
- Next action when unresolved
- Confirm the actual transaction rather than using a generic transfer label.
- Dependency
- Route before service and charge selection.
confirmed action needed confirmation needed not applicable (reason)09.Developer requirements
- Evidence
- The current application requirements for this property are recorded.
- Responsible party
- Owner / developer
- Next action when unresolved
- Obtain the developer’s transaction-specific requirements.
- Dependency
- Requirements before the developer submission.
confirmed action needed confirmation needed not applicable (reason)10.Service-charge clearance
- Evidence
- The relevant clearance and its evidence are addressed.
- Responsible party
- Owner / responsible account holder
- Next action when unresolved
- Resolve the stated clearance requirement and retain evidence.
- Dependency
- Clearance before a dependent developer output.
confirmed action needed confirmation needed not applicable (reason)11.NOC usability
- Evidence
- The required current NOC matches the intended file and date.
- Responsible party
- Owner / developer
- Next action when unresolved
- Obtain or reconfirm the usable NOC for the transaction.
- Dependency
- NOC before the step that requires it.
confirmed action needed confirmation needed not applicable (reason)12.Seller liability and settlement
- Evidence
- The seller-lender amount, instructions and relevant output are current.
- Responsible party
- Seller / seller’s lender
- Next action when unresolved
- Identify the exact liability, settlement or release item still required.
- Dependency
- Seller-bank milestone before its dependent step.
confirmed action needed confirmation needed not applicable (reason)13.Buyer finance conditions
- Evidence
- The buyer’s lender conditions and contribution requirements are identified.
- Responsible party
- Buyer / buyer’s lender
- Next action when unresolved
- Confirm the outstanding lending and funding conditions.
- Dependency
- Buyer-bank milestone before funding and registration.
confirmed action needed confirmation needed not applicable (reason)14.Lender handoffs
- Evidence
- The sequence and evidence required between bank-related steps are clear.
- Responsible party
- Relevant lenders / coordinator
- Next action when unresolved
- Record each required output and the next step that depends on it.
- Dependency
- Bank sequence before final appointment readiness.
confirmed action needed confirmation needed not applicable (reason)15.Funds and amount schedule
- Evidence
- The required amounts, payers and purposes are itemised.
- Responsible party
- Buyer / seller / lender
- Next action when unresolved
- Prepare the current payment schedule with unresolved amounts shown.
- Dependency
- Amount schedule before instruments are ordered.
confirmed action needed confirmation needed not applicable (reason)16.Independently confirmed payees
- Evidence
- Payment instructions have been confirmed through known contacts.
- Responsible party
- Payer / bank / trustee
- Next action when unresolved
- Independently confirm each payee, amount and accepted method.
- Dependency
- Payment verification before funds are sent.
confirmed action needed confirmation needed not applicable (reason)17.Agreed fee allocation
- Evidence
- The provider, scope, service fee and agreed payer are identifiable.
- Responsible party
- Buyer / seller / appointed providers
- Next action when unresolved
- Clarify the allocation and appointment in the applicable documents.
- Dependency
- Agreement before accepting an unclear fee line.
confirmed action needed confirmation needed not applicable (reason)18.Originals and attendance
- Evidence
- Required people, authority and originals are arranged.
- Responsible party
- Parties / representatives
- Next action when unresolved
- Confirm attendance and original-document requirements.
- Dependency
- People and originals before appointment.
confirmed action needed confirmation needed not applicable (reason)19.Document and appointment dates
- Evidence
- Time-sensitive outputs remain usable together.
- Responsible party
- Parties / coordinator / issuing organisations
- Next action when unresolved
- Reconfirm any document or amount affected by a changed date.
- Dependency
- Date alignment before attendance or settlement.
confirmed action needed confirmation needed not applicable (reason)20.Registration output and handover
- Evidence
- The expected official output and separate handover tasks are clear.
- Responsible party
- Buyer / seller / coordinator
- Next action when unresolved
- Record the expected output, delivery and remaining handover responsibilities.
- Dependency
- Output and handover planning before completion.
confirmed action needed confirmation needed not applicable (reason)Read the standard with the actual transaction instructions
Official organisations, developers and banks set the requirements within their roles. The standard helps organise those requirements; it does not replace them. Identity and records must be checked against the actual transaction, not an illustrative example.
The documents guide, NOC guide, mortgage guide and payment guide provide the relevant context.
Use the companion tools
Run the readiness check to turn your answers into an action list. Print a document checklist to organise the supporting file. Neither tool requires private document uploads.
Share and cite the method
You may refer readers to this page when explaining transfer preparation. Please identify it as Conveyance’s own method and retain the distinction between an illustrative framework and official requirements. Contact the transfer desk for press enquiries or a correction supported by a source.
Source: conveyance.ae · reference
Source: dubailand.gov.ae · reference
Source: dubailand.gov.ae · reference
