Quick answer: A security installer case study template that protects the customer has four parts: written permission first, a problem–design–result structure, anonymizing that removes the name, address and anything that reveals the site’s security layout, and a short list of places to use it, such as proposals, your Google Business Profile and your website. Keep every result measured and every product fact traceable to the spec sheet; an anonymous story still has to be exact.
Why get written permission first, even for an anonymous case study?
Leaving out the name does not make the story yours to publish. The customer may still recognize their site, their staff may recognize the incident, and a competitor of theirs may work out who it is from the details. A case study published without agreement can cost you the account and the referrals that came with it. Ask first, in writing, before you draft.
Make the request specific so the customer knows exactly what they are agreeing to:
- Whether the customer may be named, described by industry and region only, or not described at all.
- Which photos may be used: equipment, the rack, the mounting detail, or none.
- Whether any video frame may be shown, and only with faces and plates blurred.
- Where the case study will appear: proposals, your website, your Google Business Profile, social posts, email.
- Whether the customer reviews the final text before it is used, and how long the permission lasts.
- That they can withdraw permission and you will remove the content within a stated time.
Keep the signed or emailed approval in the job folder with the final text. If a quote from the customer is included, it should be their own words, approved by them; advertising rules on testimonials apply (the FTC Endorsement Guides in the US, the Competition Act in Canada), so verify with counsel if you are unsure.
What structure works: problem, design, result?
A case study is a short argument: this was the situation, this is what we designed and why, and this is what changed. Readers are other facility managers and owners deciding whether you understand their kind of site, so the problem section matters most.
- Situation: industry, size and region in general terms; what was happening; what the old system could not do.
- Requirement: what the customer needed, in their language: “identify who enters after hours,” “find incidents faster,” “cover the yard without new trenching.”
- Design: the approach and the reasoning; equipment by category and, where it helps, by full SKU with printed specs.
- Installation: constraints you solved: occupied building, cold weather, long runs, limited pathways, phased work.
- Result: what changed, measured where possible and stated as the customer reports it.
- Support: how the system is maintained, and who the customer calls.
Aim for 400 to 700 words, plus one or two photos. Longer case studies are rarely read to the end; shorter ones rarely prove anything.
How do you anonymize the site and the customer?
Anonymizing is more than deleting the name. A determined reader can identify a site from a combination of small details, so remove or generalize each of them.
| Detail | Remove or generalize to |
|---|---|
| Customer name, logo, brand colors | “A regional self-storage operator” |
| Address, city, intersection | State or province, or “the Midwest,” “Southern Ontario” |
| Exact building count and size | Ranges: “three buildings,” “about 60,000 sq ft (5,600 m²)” |
| Incident specifics, dates, people | “Repeated after-hours break-ins at a rear door” |
| Camera positions, blind spots, recorder location | Never publish; describe coverage in general terms |
| Network details, IP ranges, user names | Never publish |
| Staff names and job titles | “The facility manager” |
The security rule matters as much as the privacy rule: never publish anything that would help someone defeat the system, such as a floor plan with camera positions, the location of the recorder, or the hours when the site is unmonitored. A case study is about your design approach, not a guide to the customer’s defenses.
Which photos and footage can you use?
Installation photos are the safest and often the most convincing: a clean rack, a labeled patch panel, a sealed junction box, a camera on a pole mount. They show workmanship without showing the site. Check each photo for signs, vehicles, license plates, people, reflections and anything that shows the building’s name or location.
Video frames are a different matter. A frame from the recorder shows real people, often in a private or semi-private setting, and is subject to privacy rules: state laws in the US, and provincial laws and PIPEDA in Canada. Use a frame only with the customer’s written permission, only to show image quality, with faces and plates blurred, and never from an incident under investigation. When in doubt, describe the result in words and keep the footage off the page.
How do you keep the results exact?
An anonymous case study is still a public statement about your work and about the products you used. Every claim in it must be true and checkable.
- State results as the customer measured or reported them: “the customer’s incident log shows no forced entries at the rear door in the six months after handover” is checkable; “crime dropped 90%” is not, unless the customer has the numbers.
- Quote product facts only from the spec sheet of the exact SKU, with the full spelling. For example, the CS-I86V I-180 prints an 8MP (4+4) stitched image at 4640×1728 and 98 ft (30 m) white light; the CS-I4SV S-2.8mm prints 0.0001 Lux with PhotonX and 33 ft (10 m) white light.
- Describe features as they were configured on that project: low-light and full-color behavior is stated per SKU on the specification sheet and should be confirmed for the site, and EW availability is confirmed per SKU.
- State warranty exactly if you mention it: CASE cameras and CASE NVRs carry a 6-year warranty. CASE PTZ cameras carry a 3-year warranty. CASE accessories carry unlimited warranty. Hard drives are supported through back-to-back manufacturer warranty.
- Do not imply results the customer did not see, and do not present an illustrative example as a real project.
Security installer case study template
Copy this table into your own document or job folder and fill it in from the job file. The middle column shows an illustrative example, not a real project.
| Section | Illustrative example | Your text |
|---|---|---|
| Headline | Covering a three-building storage site with one stitched view per lot | |
| Situation | A regional self-storage operator in the Midwest; older cameras gave gray night images and left gaps between buildings | |
| Requirement | Color night records of the lots and a faster way to find incidents | |
| Design | A CS-I86V I-180 stitched 180° camera per open lot; a CS-I4SV S-2.8mm at an unlit side gate; a CS-N440 P16H-AI recorder with 40 channels and 16 PoE ports as printed | |
| Installation | Work phased around tenant hours; existing pathways reused | |
| Result | [Measured result from the customer’s own records, approved by the customer] | |
| Support | Twice-yearly visits; warranty and service through the installer | |
| Permission | Industry and region only; equipment photos approved; no footage |
Where should you use the case study?
- Proposals: one relevant case study per proposal, placed after the design section, chosen for the same kind of site. See writing a security camera proposal.
- Google Business Profile: a short post with an approved installation photo and two sentences of the story; the setup is in the Google Business Profile guide.
- Your website: a projects page organized by industry, so a visitor finds a site like theirs.
- Email and referrals: a link in the quarterly customer email or in a reply to a referral introduction; see the referral program guide.
- Bids: as a described reference project where the customer has agreed to be contacted, and only within the limits they approved.
What to tell your customer
“We would like to describe your project as an example of our work, without your name or address and without anything that shows where cameras or the recorder are. You will see the text and any photo before we use it, you decide where it appears, and you can ask us to remove it at any time.”
FAQ
Do I need permission if I do not name the customer?
Yes. Customers, staff and competitors can often recognize a site from details even without a name, and publishing without agreement can cost you the account. Ask in writing before drafting, state exactly what will be described, which photos will be used and where it will appear, and keep the approval in the job folder.
Can I use recorded video in a case study?
Only with the customer’s written permission, only to show image quality, with faces and license plates blurred, and never from an incident under investigation. Video frames show real people and fall under privacy rules: state laws in the US, and provincial laws and PIPEDA in Canada. Installation photos are usually safer and show your workmanship better.
How long should an installer case study be?
About 400 to 700 words with one or two approved photos. That is enough to describe the situation, the requirement, the design reasoning, the installation constraints and a measured result. Longer write-ups are rarely read to the end, and shorter ones rarely prove anything to a facility manager comparing contractors.
What if the customer has no measured results?
Describe the result in the customer’s own words, approved by them, such as what their staff now do differently, and avoid percentages or figures you cannot support. You can also describe what the design made possible, such as color night records or faster searches, as long as each capability matches the spec sheet of the exact model installed.
Where does a case study help most?
Inside proposals, placed after the design section and matched to the same kind of site. It shows the reader you have solved their problem before. It also works on your Google Business Profile, on a projects page organized by industry, and as a link in referral replies, always within the limits the customer approved.
