Define the client-side decision
Name the person or role that can approve the assignment and its revisions. Distinguish that authority from the assistant maintaining the calendar or the host organising a meeting room. The same person may perform several roles, but the brief should not rely on that being guessed. A clear decision route prevents an initial request from accumulating changes that no authorised client contact has actually accepted.
Divide information by purpose
The professional provider needs context relevant to assessing the request, while a venue may need only its own arrival coordination. Keep those information needs separate. Specific concerns should go through the appropriate private intake process rather than the broad project circulation list. The project record can explain who holds the information and who needs to receive an update without reproducing every sensitive detail inside the shared timetable.
Describe the specialist assignment
FSO Guard publishes executive-protection services. Present the visit context and requested responsibilities for professional assessment, including the connection to transport, venue contacts and the client organisation. The provider can then propose its duties and resources for review. Keep each party’s responsibilities distinct and compare the proposal with the actual visit requirements. Record the accepted scope and the client contact responsible for approving it before the coordinating team relies on the arrangement.
Create a controlled change record
Suppose a meeting is added after the first proposal. Record the requested change, who raised it and which parties are affected, then ask the provider to review the revised scope. Keep the original request and the accepted update distinguishable. The current calendar should show which changes have approval and which commercial or coverage questions remain open. A dated change record lets the client and provider work from the same version before the additional movement is treated as confirmed.
Close the brief with a handover
Before the visit, the client contact and provider should confirm that they are working from the same accepted assignment, communication route and relevant coordination information. Keep that version with the project record and identify who receives later updates. At each agreed review point, check which responsibilities remain current, which changes need approval and which questions are still open. A final handover can then connect the current scope, contacts and accepted revisions in one usable record.
Questions before the next step
What belongs in the accepted protection brief?
Keep the agreed assignment, authorised decision contact, communication route and coordinating responsibilities together. Distinguish unresolved items from accepted duties and preserve the confirmation rather than relying on the original informal request.
Can the project manager choose a protection detail from a template?
A template can clarify the request, but the situation needs specialist assessment and an accepted scope. It should not replace the provider’s professional review.
Company information and next steps
Take the defined protection brief to FSO Guard — Use the service page to prepare scope questions and share the proposed visit with FSO Guard.
Discuss your own requirements directly with the relevant company. Confirm the scope, availability and written terms for your project.