Save the complete comment and context
Copy the comment, application number if available, platform name and date it appeared. State whether this is an initial application, renewal or completion of an existing request. Avoid sending a fragment such as report alone. Adjacent wording may identify the intended document or why an attachment was not accepted, changing how the file should be handled.
Compare the report details with the premises
Review the name, activity, location, uploaded version and date, and describe changes since preparation. The aim is to identify discrepancies before new work, not make undocumented alterations to an issued file. If correction is necessary, its proper route and verification are established with the party responsible for preparing the document.
Classify the obstacle before pricing
We review whether the comment concerns a missing document, mismatched details, safety works needing completion or a different service route. We do not choose a report type because its name is popular. Immediate and non-immediate describe the applicable route; they do not promise delivery of a report or licence within a fixed number of hours.
- File issue: an unclear version or attachment that does not match the request.
- Data issue: an inconsistent activity, location or business detail.
- Works issue: a gap requiring site review or corrective work.
Prepare evidence addressing the comment
Connect each comment with material explaining its status: a document, recent photograph, works statement or drawing. Do not send many unnamed files; name them so contents and versions are clear. Record unavailable items as gaps so we can identify who provides them and whether a separate service is required.
Approve a connected corrective scope when needed
If a report depends on installation, drawings or a certificate, we explain the sequence before work begins. The quotation identifies each item's deliverable, responsibility and dependencies. This avoids paying for a document only to discover that the fit-out work supporting it was never included in the agreed scope.
Follow closure within the same application
After preparing the correction and appropriate document, review the completion procedure and application status. Keep the submitted version, date and any later comments. Uploading does not prove acceptance. Record separately what was submitted, what awaits review and what the relevant authority has confirmed.
Request a review of your Madinah file
Send the activity, procedure type, comment and available reports, drawings and certificates. We serve requests in Madinah. Visits or on-site work are defined in the quotation after site review. We organise reporting, associated work and licensing follow-up according to your case, with a clear cost proposal before execution.
Questions to help you get started
Should I request an immediate or non-immediate report?
The route depends on activity, application status and displayed requirements. Send your details and the requested wording so we can review the appropriate service.
Can the previous report be amended directly?
The error, document preparer and site changes must be reviewed. We do not alter an issued document outside the correct verification and correction process.
Does uploading the report mean the Civil Defense permit has been issued?
No. Uploading is one application step. Acceptance, completion of requirements and permit issuance are separate statuses.
What if I do not have the earlier report?
Say so and provide the application status and available files. We identify how to complete the information before pricing new work.
You may also find these useful
- Technical-report review
- Immediate technical report
- Non-immediate technical report
- Civil Defense permit
- Review a report comment in Madinah
Guide sources
Current requirements for each activity are checked with the relevant authority when the application is made.
