Engagement path
A clear sequence for internal security policy development — from first conversation to published documents your teams can acknowledge.
-
Discovery call
We learn which policies exist, which systems matter, and who must approve wording. You leave with a proposed scope note.
-
Document and stakeholder map
Current handbooks, access rules, and incident notes are reviewed against owners and operational reality.
-
Drafting cycles
Policies are written in plain English with tracked revisions. Named owners review before anything reaches the board pack.
-
Approval pack
EXCO or board materials summarise decisions required, residual risks, and the first review date.
-
Publication & briefings
Final versions, acknowledgement forms, and optional staff briefings complete the handover so the suite does not stall after approval.
What you prepare
Share existing policies, recent audit or insurer questions, and a contact list for HR, IT, and operations. If documents are missing, we start from a structured outline rather than inventing controls your teams cannot sustain.