Compliance
Checking local permissions before a mission in Mauritania
Confirm applicable conditions with competent contacts instead of assuming one permission regime fits every site.
1. Define the activity.
Describe the location in Mauritania, task, dates, people and proposed equipment precisely. Distinguish site entry, performing the work and any intended data collection. This preparation does not presume a particular legal requirement applies. This general guidance does not replace qualified legal advice, formal risk assessment or confirmation of actual conditions by competent authorities and site managers. Record uncertainties openly so the mission is not planned around unverified assumptions about local permissions.
2. Identify contacts.
With the client, establish the operator, owner or site manager and other competent contacts for the proposed activity. Ask who confirms access conditions and who approves the work itself. Arrangements may differ by location and task; do not automatically carry conditions over from a previous mission. Verify contact details and assign an internal owner to centralize correspondence and decisions. An introduction from a client is not itself confirmation of every applicable condition.
3. Confirm conditions.
Request documented confirmation of permissions, restrictions or steps that actually apply to the proposed scope. Clarify the people covered, validity period, authorized areas and limits of the agreement. Do not invent a universal form, deadline or permit requirement. If a response remains ambiguous, ask the competent contact to clarify and keep the issue open before scheduling the affected work. Record the source and date of confirmation so the team can verify its relevance.
4. Check sensitive activities.
If the mission includes photography, surveys, connected devices or particular equipment, explicitly ask which conditions apply. Do not interpret site entry as implied permission to record or transmit everything. Confirm confidentiality restrictions with the client and operator before collecting information. When doubt remains unresolved, suspend the affected activity pending confirmation, without trying to bypass a limitation through another device. Share verified restrictions with all people handling recordings or mission data.
5. Prepare the file.
Gather relevant confirmations, contacts and site instructions in a file accessible to mission leads. Check consistency between the agreed scope and the actual planned task. Limit copies of personal data to justified needs and use approved storage methods. Brief the team on authorized areas and activities, confirmed restrictions and the contact for changed local requests. Make essential instructions available offline when connectivity is uncertain without distributing unnecessary sensitive information.
6. Reconfirm and archive.
Before departure and on arrival, verify that documented conditions remain valid and contacts expect the team. Have competent people revalidate significant changes to dates, personnel or scope. Suspend affected work when confirmation is missing rather than relying on an earlier informal understanding. After the mission, archive decisions and deviations under organizational rules to support review without claiming to guarantee future compliance. Treat each new mission as requiring its own applicability check.
7. Build an evidence checklist.
Have competent authorities and qualified local contacts determine actual requirements. For land access, port or site entry, filming, drones and proposed radio frequencies, record activity, area, approving authority, applicable written approval, restrictions and expiry. Verify the issuer has authority over that activity; client consent does not automatically cover every regulator or operator. Retain references, correspondence and approval evidence accessible to authorized team members. Confirm recording, flight and transmission limits before use. Do not invent universal permit names or assume one approval covers all activities. Missing evidence or a changed scope requires clarification before the affected activity proceeds.