You have chosen the person and now there is a document on your desk. It may be two pages or twenty, and it may have been drafted by the director, by their attorney, or adapted from a consulting template that was never meant for this kind of work. Your instinct is to skim it, check the monthly fee, and sign, because the hard part felt like choosing the person. The agreement is where the engagement either gets the structure it needs or quietly fails to.
This article describes what should be in a fractional security director agreement from the perspective of the executive who has to live with it. I am not an attorney and nothing here is legal advice. Have your counsel review any agreement before you sign, and use this article to make sure counsel is reviewing a document that actually describes the engagement you think you are buying. Most of what goes wrong in these arrangements goes wrong because a question that should have been settled in writing was left to assumption.
Scope: What the Director Owns and What They Do Not
The agreement should say in plain language what the director is responsible for. That usually includes the assessment, the security plan, policy development, oversight of the guard and monitoring vendors, incident response leadership, the testing program, and a regular briefing to leadership. It should also say what the director is not responsible for, because ambiguity here breeds resentment on both sides. Daily guard scheduling, badge processing, and camera maintenance usually belong to a manager or to facilities, and if the agreement is silent, the organization will expect the director to do them and the director will expect otherwise.
Read the scope against the sites and the people it covers. If you have three locations and the agreement mentions one, ask. If you have a subsidiary with its own building, decide now whether it is in or out. Scope creep is the most common source of friction in a fractional relationship, and it is far easier to add a site by amendment than to argue about whether it was ever included.
Time, Availability, and What Happens in an Emergency
A fractional arrangement is built on a time commitment, and the agreement should state it in a way you can measure. That might be a number of days per month, a number of on-site visits, or a set of scheduled activities with the hours implied. Vague language about reasonable availability satisfies nobody. The agreement should also say how the director can be reached, how quickly they will respond to a routine request, and how quickly they will respond to an incident. Those are different numbers and they should be written down separately.
Emergencies deserve their own paragraph. Decide whether incident response is included in the retainer or billed separately, whether there is a cap on emergency hours before additional fees apply, and what happens if the director is unreachable because they are with another client. A good director will have a backup arrangement or a triage rule and will be glad to put it in writing. If the agreement says nothing about emergencies, the first one will be an argument about money at the worst possible time.
Authority and Reporting Line
The agreement should name who the director reports to and what the director is authorized to do without asking. Can the director direct the guard vendor, or only recommend? Can the director revoke a credential, change a post order, or stop a contractor at the door? Can the director talk to any employee, any department head, and the board? A director without authority is a consultant with a longer contract, and the organization will not get the leadership it is paying for. In my experience the reporting line matters as much as the authority, because a director who reports to a mid-level manager cannot make the case for security at the level where budgets are decided.
Write down the briefing cadence too. Monthly to the executive sponsor and quarterly to the board or a committee is a common pattern, but what matters is that it is fixed. A briefing that happens when someone remembers to schedule it stops happening within a year.
Independence and Conflicts of Interest
The agreement should state that the director receives no compensation, referral fee, commission, or other benefit from any vendor, integrator, manufacturer, or service provider they recommend or oversee, and that any existing relationship of that kind is disclosed in writing before the engagement begins. This clause is what makes the director’s vendor advice worth having. Without it you have no way of knowing whether the recommendation to replace the guard company is in your interest or in someone else’s. A director who resists this clause is a director you should not hire.
Consider also whether the agreement should address the director’s other clients. You may not need exclusivity, but you may want to know if the director takes on a direct competitor, and you will certainly want confidentiality that survives the end of the engagement. Your counsel will have views on how to word this, and this is a place to take their advice.
Deliverables, Testing, and Ownership of the Work
List the things you should have in hand at defined points. A written assessment by a stated point in the first quarter, a security plan with owners and costs, written policies on a schedule, a record of what was tested and what was found, and a regular written brief. My doctrine, laid out in Until Tested: Security Is Only Assumed through the P.R.O.O.F. framework, is that a security program is only assumed until it is verified, and the agreement should commit the director to a testing program rather than leaving it to good intentions. Name what will be tested and how often, at least in general terms.
The agreement should also say who owns the documents. Policies, assessments, plans, and post orders written for your organization should belong to your organization and should remain usable after the director leaves. Some directors will want to retain rights to their own frameworks and templates, which is reasonable, but the work product that describes your program should stay with you. Ask counsel to make sure this is clear.
Fees, Term, and How It Ends
A monthly retainer is the usual structure, sometimes with a higher fee for the first quarter to reflect the assessment work, and sometimes with a separate rate for hours beyond the commitment. Whatever the structure, the agreement should be clear about what is included and what is extra, how expenses are handled, and when fees are reviewed. An initial term of a year with renewal is common and gives the director enough time to complete the first cycle of assessment, plan, and testing before either side judges the relationship.
Pay close attention to the exit. The agreement should say how much notice either side gives, what the director hands over on the way out, and how long the confidentiality and conflict provisions last afterward. A clean transition clause, with a written handover of the plan, the open items, the vendor relationships, and the testing record, is the difference between a program that continues and a program that resets to zero. Ask for it, have counsel review it, and do not sign until it is there.
Go Deeper
For the full definition of the role, how it is structured, and how it compares to consultants and full-time hires, start with What Is a Fractional Security Director? The Complete Guide. My book Fractional Security Director covers how the engagement should be structured from the first conversation through the handover, and what each side owes the other along the way.
Commissioner William Epps is a former elected Fire Commissioner, federal law-enforcement supervisor, and firefighter since 2006, with instructor credentials in Hazardous Materials response, Active Shooter preparedness, and Stop the Bleed®. He spent seven years in federal law enforcement in physical security, executive protection, and incident command, and now serves organizations as a Fractional Security Director. He is the author of The Spirit of Saul, The Spirit of Pharaoh, and other practical books on security, leadership, and faith, built around one idea: knowledge should be practical enough to use when it matters.
Leave a Reply