What to Ask Before Signing
a Security Design Contract

Most clients who engage a security consultant do so without asking the questions that would meaningfully protect their interests. The proposal looks credible, the credentials appear sound, the fees seem reasonable, and the contract is signed. It is only later, when specifications prove inadequate, contractors substitute cheaper products, or deliverables fall short, that the gaps become visible.

These gaps are almost always avoidable. They stem from questions that were not asked at the outset. Here are eight questions every client should put to a security or ELV consultant before signing an engagement letter.

1. Are you vendor-independent?

Not "do you consider multiple brands," but: do you receive any financial benefit from any equipment manufacturer, distributor, or installation contractor? If the answer is anything other than a direct no, the conflict of interest is worth understanding in full before proceeding.

2. Who will actually do the work?

Many proposals are won by senior principals and delivered by junior staff. Ask specifically who will author the technical specifications, attend site meetings, review contractor submissions, and witness SAT. Get the names in the contract. If the answer is vague, the delivery risk is real.

3. What deliverables are included, and what are not?

Scope ambiguity is the most common source of disputes in security consultancy. "Design services" can mean anything from a concept report to a full tender package with coordinated drawings, BOQs, and commissioning support. Ask for an explicit deliverables schedule. If it is not in the contract, it is not in scope.

4. Does the scope include construction phase support?

Design quality is only fully realised if the design intent is maintained through construction. Many engagements end at the tender stage, leaving the client without technical representation during the phase when contractor deviations are most likely. Confirm whether review of contractor submissions, RFI responses, and SAT witnessing are included or available as additional services.

5. How do you handle contractor-proposed substitutions?

Contractors will routinely propose product substitutions, often claiming equivalence. A vendor-independent consultant evaluates these on technical merit alone. A vendor-tied consultant may approve substitutions that benefit their commercial relationships. Ask how this process works and who has the final say.

6. What standards and frameworks do you apply?

Security and ELV design should be aligned to recognised international frameworks, whether that is IEC, BS, NFPA, SANS, ICD 705 for SCIF environments, or local regulatory requirements. If a consultant cannot name the standards they work to, the technical rigour of their output is questionable.

7. What does your fee cover if the project scope changes?

Scope growth is normal on construction projects. Understand upfront whether your fee is fixed, capped, or time-based, and what the mechanism is for agreeing additional fees. A clearly agreed variation procedure prevents disputes and keeps the relationship professional when scope inevitably changes.

8. Can you provide references from directly comparable projects?

Not from the same country or sector in general, but from projects of similar type, complexity, and delivery model. A consultant who has worked extensively on commercial refurbishments may not have the specific expertise required for a high-security government facility or a multi-building healthcare campus. The reference check should be specific, not generic.

These eight questions take less than thirty minutes to put and answer. They protect against the most common sources of client dissatisfaction in security and ELV consultancy, and they provide a clear baseline for evaluating whether the consultant you are considering has the independence, capability, and contractual clarity to serve your interests properly.