In this context it means procedural coordination of a property transfer: checklists, readiness management, and trustee appointment preparation. It is not legal advice.
Yes. Open a file (free) or start transfer (paid) with the basics; missing items can be requested in parallel.
Conveyance.ae is designed for Dubai secondary-market transfers. If your case is outside Dubai, confirm first.
Secondary is resale of an existing property with a title deed. Off-plan is before completion and uses different developer-led processes.
No. Brokerage (finding and negotiating a deal) is separate from transfer coordination.
No. For disputes, fraud concerns, inheritance, or litigation, consult an independent lawyer.
It starts the coordination process for your scenario and prepares you for a successful trustee appointment.
You receive confirmation, your file is opened, and we start the checklist and readiness plan for your scenario.
Use the start transfer flow and select ‘Not sure’ where available; we’ll confirm the scenario.
Developer NOC and bank timelines (when mortgages are involved), plus missing or mismatched documents.
Buyer pays cash; seller has no mortgage discharge required. Still requires documents and (sometimes) NOC readiness.
Seller has a mortgage and needs bank discharge/clearance steps before the transfer can complete.
Buyer is financing with a mortgage and needs bank approval/letters coordinated for completion.
Bands (1–6) are your site’s way to map property value/complexity to a fixed service fee.
If the true transaction value differs materially, we may need to correct the band before completion to align scope.
If the scenario changes (e.g., a mortgage is introduced), we align the correct package before completion.
If your case is non-standard, open a file (free) for an initial readiness review; complex disputes may require legal advice.
No. Government and third-party fees are separate from our service fee.
Our service is purchased by whoever engages us. Fee responsibility between buyer/seller is a deal-term.
Yes. Open a file (free) and proceed to paid service when you’re ready.
Typically IDs for buyer and seller (passport/Emirates ID as applicable), property reference/title deed copy, and deal terms document if available.
Yes. Even small spelling or transliteration differences can trigger verification issues. Fix mismatches early.
Reconcile old/new passport numbers early and ensure all letters/forms reference the correct identity.
Requirements vary by scenario. At minimum, you need accurate title deed/reference details and correct identification.
Company documents and authorised signatory proof are commonly required. Plan additional time for verification.
Similar: trade license and signatory authority proof are commonly required.
Yes. You can start with basics and provide missing items later.
Usually NOC documents, bank letters for mortgages, or identity/name mismatches.
It’s commonly used in secondary sales to record terms. Requirements vary; ensure deal terms are clear regardless of format.
We handle submissions according to the Privacy Policy and do not request card details over chat.
In some scenarios you may need to show readiness; exact requirements depend on deal structure and bank involvement.
Open a file and we’ll identify alternatives or confirm whether the item is mandatory for your scenario.
Often yes (passport, representation documents). Plan attestation/translation time if POA is used.
Not always, but commonly used when a party cannot attend. Confirm scenario requirements before relying on POA.
Usually not. Fix mismatches before booking the appointment to avoid failure.
Acceptance rules vary. Confirm with the trustee process for your appointment.
The full set of documents for buyer, seller, and transaction readiness. A complete pack reduces delays.
Create one checklist, reconcile names early, and request missing items in parallel.
Yes. Use the checklists and messaging templates in this playbook.
Yes. Open a file (free) and we’ll confirm a readiness plan.
A document the developer may require confirming no objection to transfer under its records and conditions.
No. Requirements vary by developer/property. Confirm for your unit.
Varies by developer. Treat it as a likely critical-path item.
Outstanding charges, missing documents, and developer backlog are common causes.
Usually it is better to confirm NOC readiness first to avoid failed appointments.
Get the delay reason in writing, clear missing items, escalate through the developer process, and run other steps in parallel.
Often yes, but charges vary. Confirm directly with the developer.
Often yes. Clearance can be required for NOC issuance.
Depends on developer rules and deal terms; confirm with the developer process.
Some NOCs have validity periods. Confirm issuance and validity before booking appointments.
If refusal is disputed, legal advice may be appropriate.
It is typically issued by the developer, not the government.
Some developers provide digital confirmations; acceptance depends on the process.
NOC, receipts, clearance confirmations, and all related communications.
Often yes. Parallel processing is a key speed strategy.
A discharge/clearance process is usually required before transfer can complete cleanly.
Often yes for clean transfer, but exact mechanics depend on bank and process.
Letter types vary by bank. Confirm exactly which letters are required for your scenario and when.
Bank processing time, missing documents, and mismatched bank records are common causes.
Often yes; parallel processing reduces idle time.
Bank approval/valuation and required letters become part of the critical path. Align appointment timing accordingly.
No. Mortgage brokerage is separate. We coordinate transfer readiness.
A bank’s initial eligibility confirmation for the buyer. It helps timeline planning but may be conditional.
It can. Banks may require valuation, which adds scheduling and processing steps.
Yes. You can open a file and progress other readiness steps in parallel.
Obtain written status, escalate through the bank channel, and avoid booking trustee appointments prematurely.
Same principle: obtain written status, keep documentation complete, and book appointment once conditions are met.
Deal-dependent. Clarify in writing.
Deal structures vary; handle carefully and document clearly. Confirm what is required by bank/trustee.
Yes. One checklist and one coordinator reduces missed items.
Appointment booked before bank letters/clearance are actually ready.
Requirements vary by bank and structure; expect additional corporate documentation.
Possible but bank requirements vary; plan early and confirm eligibility.
Sometimes. Confirm payment instruments and timing for your scenario.
No. Bank processing timelines are outside our control.
Confirm the bank’s required proof/letters accepted for the transfer process.
Do not assume. Once steps are taken, coordinate carefully; consult the bank.
It changes the scenario. Align package and readiness steps before proceeding.
It changes the scenario; adjust readiness plan and avoid premature appointment booking.
Often yes (bank fees, valuation). Confirm with the bank.
At a DLD authorised trustee centre.
Identity verification, document review, fee payment through approved channels, and execution of the transfer steps in the system.
Often yes, unless an approved representation method is used; confirm your scenario.
If key documents are missing or details cannot be verified, the appointment may be paused or rescheduled.
Don’t book until NOC/bank letters are ready and the document pack is consistent.
Arrive early to allow identity checks and any minor corrections.
Requirements vary. Confirm what the trustee process requires and what is acceptable.
Some remote verification mechanisms exist in some processes, but confirm what applies to your scenario.
Yes, but it is avoidable friction; aim for readiness before booking.
Missing NOC, missing bank letters, or identity mismatches.
Some operational differences exist; confirm your appointment instructions.
Use official lists and choose based on location and appointment availability; follow the official process.
It depends on your scenario. Confirm the expected fees and payment instruments in advance.
Some documents are issued electronically depending on service; confirm what you should receive.
The appointment may fail unless representation is valid and accepted.
Representation or remote verification may be needed; plan early.
Same. Plan representation method early.
Do not proceed. Renew and align identities before attempting transfer.
Update the file and ensure the correct band/package and fee readiness.
Minor clarifications sometimes, but do not rely on on-the-day fixes for missing documents.
No. Our service fee is separate from government and third-party fees.
Yes, that is the purpose of online checkout on Conveyance.ae.
No. Never share card details over chat.
Official services list different payment methods depending on service; confirm what applies to your transaction and trustee process.
Yes. Fees depend on the transaction type and service outputs.
Small line items that appear in some official service fee schedules.
A fee charged by a service partner (e.g., a trustee provider) depending on service type and thresholds.
Often third-party fees depend on the third party’s rules; treat them as potentially non- refundable once incurred.
Try again or use another card. If you were charged but didn’t receive confirmation, contact support with your payment reference.
Yes. After payment you receive confirmation/receipt of the service purchase.
If VAT applies, it should be itemised clearly at checkout.
Refer to the published Refund Policy; eligibility depends on work stage and costs incurred.
Use the official checkout only. Do not pay via links sent by unknown numbers. Verify the domain and receipt.
If you plan instalments, open a file (free) and request options; avoid creating friction on critical path.
Online checkout is the designed payment route. If you need alternatives, contact support.
Third-party fees are paid to the relevant party at the relevant stage; bundling depends on process.
We coordinate readiness to reduce risk; third-party timelines and decisions are outside our control.
Refer to the refund policy and document what stage you reached; disputes may require legal advice.
Often yes with early planning. Representation methods such as POA may be used depending on the scenario.
Acceptance is scenario-specific and can be strict. Confirm requirements before relying on it.
Often yes depending on issuing country and use case. Confirm required attestation/translation steps early.
Only if representation is valid and accepted (often via POA). Do not assume informal
representation is accepted.
It varies. Build time into your plan for attestation and verification.
It depends on the process and scenario. Confirm what is accepted for your transfer.
Non-residents often use passport for identity; exact requirements vary.
They can. Clear communication channels and early planning help.
Assuming a representation method will be accepted without confirming requirements.
Open a file and confirm scenario requirements, including whether POA/remote verification is needed.
Sometimes. Confirm your scenario requirements early.
We do not provide legal drafting. For POA drafting, consult a lawyer.
Often POA scope matters. A lawyer can advise on drafting appropriate scope.
The file may need alternative representation or a different process; it can cause delays.
Some remote verification mechanisms exist in some processes; confirm applicability for your transaction.
You should complete post-transfer housekeeping: update utilities, developer/community access, and billing accounts.
Many outcomes are issued electronically depending on service; confirm what you should receive as proof of completion.
Keys/possession are deal terms and practical handover; clarify early and plan handover steps.
Not always. Confirm the update path with the developer/community manager.
Your outcome documents, receipts, and the full communication record.
Update contact details with relevant providers to ensure correct billing.
Plan a handover and account update to avoid service interruption.
Coordinate access and community requirements early.
Often yes, for access updates and billing accounts.
Access and billing account updates. A checklist prevents it.
Most commonly: NOC pending, bank letters pending, or document mismatch discovered late.
We can coordinate and escalate through the developer process, but developer processing time is outside our control.
We can help ensure documents are complete and follow up, but bank processing time is outside our control.
That becomes a dispute and may require legal advice.
Same. Document everything and seek advice if it becomes a dispute.
Reschedule, but first ensure readiness to avoid repeat failure.
Usually no. Focus on readiness and book once the file is genuinely ready.
Yes, if a mismatch or missing item is discovered at verification. A strong checklist reduces the chance.
The steps that determine earliest completion, often NOC and bank steps.
When NOC/bank letters (if applicable) are confirmed and the document pack is consistent.
Update the file and ensure the correct band/package and fee readiness.
Renew and update the file before proceeding.
Plan representation early; do not assume it can be fixed last minute.
Provide them promptly and ask for written confirmation of next steps and timeline.
Provide promptly and ask for written confirmation of timeline and required letters.
Yes. Document what is pending and resume when ready.
Urgency should trigger stricter readiness discipline, not rushing. Identify critical path and run parallel steps.
No. We coordinate readiness and reduce preventable delays; third-party timelines are outside our control.
Document stage reached; refer to refund policy; disputes may require legal advice.
No. This is procedural coordination and informational guidance.
When there is a dispute, suspected fraud, inheritance/estate issues, court orders, or complex corporate structures.
No.
We can provide procedural templates and checklists, but legal drafting should be done by a qualified lawyer if needed.
That is legal advice. Consult a lawyer.
No. Authorities verify documents and may reject them if requirements are not met.
No. We coordinate; developer decisions and processing time are outside our control.
No.
Check the domain is conveyance.ae and use the on-site checkout. Avoid paying via random links.
Do not pay or share data. Contact support via the website contact details.
Payment processing is handled by the payment provider; do not share card details via chat.
We collect only what is necessary for service and handle it according to the Privacy Policy.
Use the official upload methods and avoid sending sensitive data to unknown contacts.
Last-minute payment instruction changes and urgency pressure.
We do procedural consistency checks. Authorities/banks perform their own verification.
Use a single file record and keep digital backups.
Refer to the Privacy Policy and contact support for your request.
Yes. Publish it clearly and refer clients to it before purchase.
Eligibility depends on how much work has been completed and any third-party costs incurred.
If work has not begun, refunds may be possible subject to payment processor costs; refer to the policy.
Refunds may be partial or not available depending on completed steps; refer to the policy.
Third-party fees may not be refundable; confirm with the third party and the policy.
Contact support with your file number and request cancellation in writing.
Contact support promptly; we align correct scope before completion.
Document what stage you reached; refer to the policy; disputes may require legal advice.
If applicable, disclose clearly in the policy.
Depends on payment processor timelines; set expectations in the policy.