The coordinator tells the site team that the application has been sent. A week later the project manager needs the reference, but the only record on file is an email attachment marked final. A finished drawing, a submission receipt and an issued permit answer different questions. Give each its own place in the handover.

Build a receipt record

Ask the submitting party for the application reference, submission date, project location, record of the submitted drawing revision and the contact responsible for follow-up. Store the receipt or acknowledgement with the project record. Share the reference with authorised colleagues; a handover does not require sharing account passwords.

What a receipt can tell the site team

Consider a coordinator who holds a submission acknowledgement for revision B and an unsigned revision C from the designer. The receipt can help locate the application. By itself it does not establish that revision C was submitted, that a decision has been made or that work may start. Ask the applicant to confirm the current record through the official channel.

Give the next action an owner

State who checks for correspondence, who obtains technical answers and who issues any subsequent decision to the site team. Keep the receipt when the outcome arrives, but file the issued documents separately. This leaves a clear record of both the request and the authority’s response.

Related guide: RTA ROWPS Application Service: Defining Support Scope and Client Handover. For authority information, see the Dubai RTA right-of-way utilisation service.

Contact us today and let us handle your RTA ROWPS application.

Share This Story, Choose Your Platform!

Leave A Comment