HR Policy Packages for Cybersecurity companies
What this looks like in your business
A security firm's policies are read by more people than most firms realise: staff, clients running their own supplier checks, and auditors asking how conduct is controlled. Yet the rules on night shifts, call-outs, confidentiality and learning time may be a mix of old emails and chat messages. A policy package gives the owner a drafted, consistent set, with the same structure, an employee FAQ, a workflow and forms for each policy. GullyHR drafts it after a short call, the owner makes the management choices, and the firm's own legal adviser reviews everything before it is issued to staff.
Where unwritten rules cause trouble here
In a security firm, the rules that matter most are the ones least likely to be written. Who may carry client data on a laptop, what a tester must do on finding something outside the agreed scope, when a monitoring analyst may swap a night shift, how much rest follows a long incident, and what happens when an employee posts about client work online. These are conduct questions that a client or auditor can ask on any day. When they are answered by whichever director is asked, staff hear different things and a dispute has nothing to rest on. A copied policy pack from another sector adds confusion. It talks of dress codes and canteen hours, and says nothing about on-call cover, rest after incidents or the use of personal devices on a client network. Two documents can contradict each other, for example a leave policy that promises time off and a rota that never allows it. The package exists to give every rule one home, in one voice. One home for each rule means the answer is the same on every shift.
Choosing which policies to draft first
GullyHR starts with a short call and a read of whatever your firm already holds: offer letters, any old handbook, confidentiality terms and the rota. It then proposes a package size. Starter has five policies, Core eleven and Complete thirty, and the choice depends on what the firm can actually put into practice. For a security firm the likely first five are conduct and confidentiality, working hours and shift cover, leave and rest after incidents, learning and development time, and exit and return of material. Larger packages add areas such as remote work, use of devices, grievance and discipline. Every policy follows one section structure, with an employee FAQ, a workflow naming who approves what, and the forms staff need. Before drafting, GullyHR asks the owner to settle management choices that only the firm can make: how much rest after an incident, whether learning hours are protected, and who approves a swap of shifts. Nothing is drafted in the abstract: each policy is shaped around a real shift, role or record in your firm.
A rest-after-incident policy in practice
Picture a firm of about twenty-five people with an incident response team and a monitoring floor. After a long engagement, two responders work through a weekend and one takes the Monday off because he asks, while another is not told he can. The owner wants one rule. On the call, GullyHR asks what the firm will actually grant. The owner decides on rest in proportion to hours worked beyond the normal week, approved by the incident lead and recorded by whoever keeps attendance. GullyHR drafts the policy with the same sections as every other: purpose, who it covers, the rule, the workflow, the employee FAQ and a short request form. It checks the draft against the leave policy and finds a clash, because leave rules treat unrecorded time off as unauthorised. The two documents are aligned. The draft then goes to the firm's legal adviser before issue. The owner chooses the rest rule and approves the final text. The owner also decides whether learning hours count as work time, and that choice goes into the learning policy beside it.
Owners, review and what stays with the owner
A policy is only as good as the person who maintains it. GullyHR assigns each policy a named owner in your firm: the head of monitoring for shift cover, the incident lead for rest after call-outs, the owner or director for conduct, confidentiality and discipline, and delivery managers for project leave and learning time. Each policy is dated and has a review point recorded, so it does not drift away from what the firm does. Staff receive the final set with a short explanation, and acknowledgements are kept in the staff register next to the signed confidentiality terms. GullyHR drafts and aligns the documents. It does not give legal advice, and the drafts go to your own legal adviser before issue, because local rules differ. What stays with the owner is every choice inside the policies, such as how much rest, which behaviour leads to a warning, and when an exception applies. A package can grow with the firm, adding policies as new teams or services arrive. Reading it once a year, with the policy owners, keeps it honest.