A performance development plan is a written agreement between a manager and an employee that sets specific goals, the support needed to reach them and the dates those goals will be reviewed. For a security team it turns a vague “improve your patrols” conversation into a documented plan the guard has seen, understood and formally accepted. That accepted record is what protects both sides when performance is later disputed.
Security operations run on shift work, spread across sites, with supervisors who rarely sit in the same room as the guards they manage. Development conversations happen verbally at a gatehouse and are forgotten by the next roster. A performance development plan fixes that gap by putting the goal, the timeline and the acknowledgement in one place.
Why a performance development plan matters for security staff
Guarding is measured on consistency: patrols completed, checkpoints scanned, handovers logged, incidents reported correctly. When a guard falls short, most teams either ignore it or jump straight to disciplinary action. A performance development plan is the missing middle step. It gives the guard a fair, recorded chance to improve before anything escalates.
It matters for three reasons. It creates accountability, because the guard has accepted a specific goal rather than a general complaint. It creates a paper trail, so if the same issue recurs the escalation is defensible. And it supports retention, because good guards stay where they can see a path to a supervisor or site-lead role rather than being managed only by punishment.
Without a documented plan, the common failure is disagreement about what was ever agreed. The guard says no target was set; the supervisor says it was discussed. Neither can prove it. A plan the guard has formally accepted removes that argument entirely.
How a performance development plan works
A good plan follows a simple loop: agree the goal, record the guard’s acknowledgement, set a review date, then review against the same written target. The strength of the process is that nothing depends on memory.
In AVES the Performance Development Plan module holds the plan as a formal record and requires the employee to accept or decline it. That accept or decline response is the part paper forms never capture. When a guard accepts, you have proof they saw and agreed the goal. When a guard declines, you have an early signal that a conversation is needed before the review period even starts, not after it has failed.
Because the plan lives in the same system as the guard’s operational records, the review is grounded in evidence rather than impression. Patrol completion, shift handover submissions and incident reports already sit in the platform, so a supervisor reviews the plan against what actually happened on shift instead of relying on a gut feeling about the guard.
What to include in a performance development plan
Keep it short enough that a guard reads it on a phone at the start of a shift. Every plan should cover:
- The specific goal. Not “be more reliable” but “complete all scheduled patrol checkpoints on every shift” or “submit the shift handover before leaving the post”.
- The current gap. A plain statement of where performance stands today, so the target is measured against a known starting point.
- The support offered. Retraining, a mentor, a refresher on the app, or a revised checklist. A plan that only lists demands and no support is a warning, not a development plan.
- The review date. A fixed date when manager and guard sit down against the same written goal.
- The acknowledgement. The guard’s formal accept or decline, with the name, date and time recorded automatically.
That acknowledgement is the difference between a plan and a note. Everything above it is intention; the accept or decline is the evidence.
Common mistakes to avoid
The most frequent error is writing goals a guard cannot control. Tying a plan to “reduce site incidents” punishes the guard for events outside their influence. Tie it instead to the behaviours they own: patrols scanned, handovers logged, reports filed correctly.
The second mistake is no acknowledgement step. A plan the employee never formally accepted is worth little if performance is later challenged, because there is no proof the guard ever agreed to it. Always capture the accept or decline.
The third is setting a plan and never returning to it. A review date that passes unactioned tells the guard the plan was never serious, and every future plan carries less weight. If you set a date, hold the review.
The fourth is confusing development with discipline. A performance development plan is a chance to improve. A disciplinary or show-cause notice is a separate, later step for when improvement has not happened. Keeping the two distinct keeps the development plan constructive and keeps your escalation defensible.
Frequently asked questions
What is a performance development plan?
A written agreement between a manager and an employee that sets specific goals, the support to reach them and a review date, with the employee’s formal acknowledgement recorded. For security staff it converts a verbal coaching chat into a documented, accepted plan.
How is a performance development plan different from a performance improvement plan?
A development plan is generally forward-looking and can apply to any guard growing toward a target, including strong performers. A performance improvement plan is usually the more formal, remedial step when performance is already below standard. In practice the structure, of goal, support, review and acknowledgement, is much the same.
Who should sign off a performance development plan?
The supervisor or site lead who set the goal and the employee it applies to. The employee’s accept or decline is the essential record; a plan without the employee’s acknowledgement is incomplete.
How often should a performance development plan be reviewed?
Set an explicit review date when the plan is created, commonly 30 to 90 days out depending on the goal. The key is that the review happens against the same written target the guard accepted.
Can a performance development plan lead to disciplinary action?
It can, if the agreed goal is not met after fair support and a proper review. Kept separate and documented, the development plan becomes the evidence that the guard was given a fair chance before any escalation.
Set fair, trackable development plans for your guards
AVES holds each performance development plan as a formal record with a built-in accept or decline step, and reviews it against the patrol, handover and reporting data your guards already generate, so every plan is fair, tracked and defensible.
Book a 30-minute demo and we will show you the actual Performance Development Plan screen, including how the accept or decline acknowledgement is captured: book a demo.
See how security teams put this into practice on our Instagram.
Prefer to explore first? Start a free trial and set up your first development plan today.