Resources

# Case Studies

An honest account of where this sits, rather than a page of invented projects.

Published case studies are still being assembled. Describing a client network publicly requires their permission, and project photography has to be captured during the work. This page explains what a Strilla case study will contain and what you can evaluate in the meantime.

## Why this page has no case studies on it yet

Two things are required before a specific project can be published. The client has to agree to their network being described publicly, and photography has to have been captured during construction rather than reconstructed afterward.

Both are straightforward to arrange going forward and neither can be manufactured retrospectively. Publishing a project without permission, or writing a plausible sounding case study that describes no actual job, would contradict the standards this company claims to hold everywhere else on this site.

## Why client permission is not a formality

An ISP's network topology, capacity and build sequence are commercially sensitive. A municipality's infrastructure detail can be a security consideration. Publishing that because it makes good marketing is a poor way to treat a client relationship.

Contractors who publish detailed client work without asking are demonstrating something about how they handle client information generally, and it is worth noticing.

## What a Strilla case study will contain

The purpose of a case study is to demonstrate a standard, not to impress. Each will cover the same ground so they can be compared against each other and against other contractors' work.

- Client type, named only where permission is given
- The objective and the constraints that shaped the approach
- Scope of work and which services were involved
- Field conditions encountered, including the ones that went wrong
- How those conditions were handled and what it cost in time
- Photographs of the work and of the completed restoration
- What the closeout package contained

## What to evaluate instead, right now

Case studies are a weaker evaluation tool than they appear. They are self selected, professionally written and impossible to verify. Every contractor's case studies describe projects that went well.

Process and standards are more informative because they are falsifiable claims you can hold a contractor to. The closeout standards page states exactly what a complete package contains. The process pages state what happens at each stage. The capability overview states what is self performed rather than subcontracted, including what is not.

References are the strongest signal, and those are provided directly on request.

## How will a Strilla case study be checked?

Every published case study will carry enough detail for a reader to test it. Where the client agrees, the client will be named and a contact offered. Photographs will be keyed to location and taken during construction. The closeout contents will be listed item by item, so you can compare them with your own requirements.

Where a client prefers not to be named, the case study will say so plainly and describe the client by type only. It will not invent a substitute name or blur the line between a real job and an illustration.

## How should you read any contractor's case study?

Read it as a sample chosen by the author, because that is what it is. The useful question is not whether the project went well. It is whether the write up tells you anything you could check or hold the contractor to on your own job.

- Does it describe at least one field condition that went wrong and how it was handled?
- Does it state the restoration standard and show the finished surface?
- Does it say what the closeout package contained, not only that one was delivered?
- Are the photographs clearly from that job, or could they be stock images?
- Is a reference offered, or is the client unnamed with no way to confirm the story?
- Does it say which work was self performed and which was subcontracted?

## Published case studies

None are published yet. When a client agrees to publication and the project was photographed during construction, its case study will appear here in the format described above.

Until then, the process pages, the closeout standards and references supplied on request are the most reliable way to judge how a Strilla project is run.

## Key takeaways

- Strilla Communications Company does not publish a client's project details without that client's permission.
- A case study is a sample chosen by its author, so the useful test is whether it contains detail you can check.
- Every Strilla case study will list its closeout contents and use photographs taken during the project.
- References supplied on request are a stronger evaluation signal than any published case study.

## Key terms

**Case study**: A written account of a specific completed project, covering the objective, constraints, scope, field conditions, how problems were handled and what was delivered. It is useful to a buyer only when the details can be checked through a named client, a reference or project records.

**Reference check**: A direct conversation with a past client about how a contractor performed. Unlike a published account, the buyer chooses the questions, such as how field changes were communicated, whether restoration was finished before demobilization and whether the closeout arrived complete.

**Closeout package**: The documentary record delivered when construction finishes: as-built drawings or route data, bore logs, photographs keyed to location, test records, structure locations, reconciled footage and material, permit closure and warranty terms. Its contents are the most concrete evidence of how a job was run.

*How contractor evaluation sources compare*

| Source | Who controls it | Can you verify it? | What it tells you |
| --- | --- | --- | --- |
| Published case study | The contractor | Only if a client is named or a reference offered | How the contractor wants to be seen |
| Reference call | The past client | Yes, you ask the questions | How the contractor behaved under real conditions |
| Written process and standards | The contractor | Yes, against your own project as it runs | What you can hold the contractor to |
| Sample closeout contents list | The contractor | Yes, at your own closeout | Whether documentation is a deliverable or an afterthought |
| Daily reports on your project | Shared | Yes, every day | Whether communication matches what was promised |

*What a closeout package contains*

## What this means for your project

Choosing a contractor on the strength of a polished case study shifts risk onto your project, because the story was written to reassure and cannot be tested. Choosing on standards you can enforce, such as a defined closeout package and daily reporting, keeps the risk visible and gives you a contract basis for raising it.

For a project manager, the practical step is to write the evaluation criteria into the scope. Ask every bidder for the same things: a reference on similar work, their closeout contents list and a sample daily report format. Comparing like with like is fairer to the bidders and far more informative for you.

## Related reading

- [Closeout and documentation standardsExactly what a complete closeout package should contain.](https://strillacommunications.com/resources/closeout-and-documentation-standards)
- [Full capabilities overviewWhat Strilla performs with its own crews, stated plainly.](https://strillacommunications.com/services/full-capabilities-overview)
- [Questions to ask before hiring a fiber teamQuestions that reveal more than any case study.](https://strillacommunications.com/blog/questions-to-ask-before-hiring-a-fiber-construction-team)
- [Our processThe five stages every Strilla project follows.](https://strillacommunications.com/about/our-process)
- [Work examplesThe kinds of work Strilla takes on, described without client detail.](https://strillacommunications.com/projects/work-examples)
- [Testimonials policyHow client feedback will be shown once it can be published genuinely.](https://strillacommunications.com/about/testimonials)

## Frequently Asked Questions

**Why do you not have case studies published?**: Because publishing a client's network detail requires their permission, and project photography has to be captured during the work rather than reconstructed later. Both are being arranged going forward. Writing a plausible case study describing no actual project would contradict the standards claimed everywhere else on this site.

**Can you provide references instead?**: Yes. References are provided directly on request and are a considerably stronger signal than a published case study, because you can ask your own questions rather than read a self selected account. Contact us and describe the kind of project you are evaluating so the references offered are relevant to it.

**What should I evaluate if there are no case studies to read?**: Process and standards, because they are falsifiable claims you can hold a contractor to. The closeout standards page states exactly what a complete package should contain. The capability overview states what is self performed and what is not. Both are more useful than a case study describing a project that went well.

**When will case studies be published here?**: When a client agrees to publication and photography from that project exists. No date is promised, because both depend on things that cannot be rushed or manufactured. Each case study will be added to this page as it is ready, using the same structure so they can be compared with each other and with other contractors' work.

**What makes a contractor case study trustworthy?**: Detail you can check. A trustworthy case study names the client or offers a reference, shows photographs taken on that job, describes at least one problem and how it was handled, states the restoration standard, and lists what the closeout package contained. A polished story with none of those is marketing, however well written it is.

**Will case studies use stock photography?**: No. A case study exists to show a real job, so it will use photographs taken during that project. Stock imagery used elsewhere on this site is representative only and is disclosed as such on the notices page. Mixing the two inside a case study would defeat the purpose of publishing one at all.

**Can you share project examples privately?**: Ask, and describe the kind of work you are evaluating. Anything shared about a client's network still needs that client's agreement, whether it is published or sent privately. References are the most common route, because a reference can answer your questions directly and decide for themselves what to say about their own project.

---
Source: https://strillacommunications.com/resources/case-studies