How to Write Construction Case Studies That Win Work

Most construction firms are better than their websites suggest. They finish a difficult job, hand it over, and move straight on to the next one. What made the project go well (the problem they solved, the call they made when the site fought back, the client who would happily vouch for them) never gets written down.

That is a waste. Apart from the building itself, a good case study is often the only lasting thing a multi-million-pound contract leaves behind. It is also one of the few pieces of marketing a cautious construction buyer will actually read.

For more than nine years I was a reporter for Building, AJ, BD and other trade titles, asking contractors, architects and engineers how they solved problems on real projects. Those conversations produced the best articles, and the same approach produces the most convincing case studies. This guide sets out how to do it: which projects to choose, what to ask, how to structure the write-up, and how to get it working in bids, on your website and on LinkedIn.

It applies whether you are a main contractor, a specialist subcontractor, a building products manufacturer or a construction tech company.

What a construction case study is actually for

A case study has one job: to help a buyer answer the question “Can this firm do it again, for us?”

Everything else follows from that. Done properly, case studies:

show clients you can meet their needs, manage their risks and bring projects in on time and on budget
put the people in your business, and how they handle problems, front and centre
give bid writers ready-made evidence to drop into tenders and pre-qualification questionnaires
help everyone from the board to the sales team explain what the company does well
give you something genuinely useful to publish on your website, send to the trade press and post on LinkedIn

Write for the bid first, then the website

Most construction case studies are written for the website. The ones that win work are written for the bid. They are different documents:

A website case study…	A bid-ready case study…
leads with the building	leads with the problem the client walked in with
says “we’re proud to have delivered”	says what changed, with a number attached
quotes no one	lives or dies on the client’s own words
is written once and frozen	includes the results that landed six months after handover
is about how good you are	is about whether you can do it again, for them
sits in a marketing folder	is formatted and findable at 9pm the night before submission

Write the full, bid-ready version first. Then cut it down for the website. One interview, two jobs done.

Why most construction case studies fall flat

Here is a typical example:

“In early 2007, Bob’s Builders completed the construction of two new high-specification three-storey office blocks at Whizzo Business Park in Macclesfield. Over 28 weeks, we took possession of this £1.4m scheme after the erection of the structural steel frames of the two units, completing the external envelope, mechanical and electrical installations and core area fit-out, as well as associated external works and landscaping.”

Is this really all that can be grown from a £1.4m, six-month project? It is a list of features with a start date, a budget and a duration. Nothing in it tells a prospective client how Bob’s Builders works, what went wrong, how the team dealt with it, or whether the client was happy.

The same pattern turns up on LinkedIn every day: “Proud to have installed 400m² of [product] at [landmark].” A photo of the finished elevation, a supplier tag, job done. Other installers nod. The main contractors and clients who award the next job scroll straight past, because the post answers a question they weren’t asking.

Buyers don’t really care what you fixed to the wall. They care why, and how you coped when things got difficult.

Step 1: Choose the right project (and the right customer)

Most firms default to their biggest client, or whoever said yes first. Both can work, but three things are worth weighing up.

Best challenge. The project with a real, specific problem that the team solved. “They improved efficiency” persuades nobody. “They caught a 20% overrun everyone else had missed” makes a reader lean in. Pick the customer with a story, not just a result.
Most relatable. Not your flashiest client, but your most representative one. A cautious buyer reads a case study asking one thing: would this work for a company like mine? A customer who looks like your next prospect (same size, same kind of project) answers that better than a famous name.
Most willing. The client who will give you half an hour, talk freely and put their name to it. A perfect project you can’t publish is worthless.

If you can get all three in one project, you have your next case study. Usually you have to trade. When I do, I drop “best challenge” before “most willing” every time: a genuinely willing client is the rarest of the three, and the story dies without one.

Cover every sector you claim

One of the most common, and most damaging, mistakes is listing a sector you can’t back up. If your website says you work in healthcare, education or rail, a buyer from that sector will look for examples. An empty or thin category drains their confidence fast. Make sure every sector and service you list has at least a couple of case studies behind it.

Step 2: Get the story from the people who were there

Treat this with the respect it deserves. Arrange a face-to-face (or video) conversation with the project team soon after handover, before they scatter to other jobs. Don’t let anyone “send you something by email”: you will get a list of materials and dates.

Explain why you’re doing it and how it helps win new work. Reassure the team, especially anyone nervous about upsetting the client, that they will see the draft before it goes anywhere.

Before the interview, write down the things clients typically worry about on this kind of project. For example:

Can the contractor stay within budget?
Will they help me create something my boss will like?
I have to cut energy bills. Is this the right team?
How on earth do we fit everyone in?
This site is a nightmare, and the neighbours are going to complain.

Then find out exactly how each worry was dealt with on this job. Useful questions include:

What did the client walk in worried about?
What was the hardest part of the job, and why?
What went wrong, or nearly did? What did you do about it?
What decision would someone outside the team not understand without an explanation?
What can we measure? Time saved, cost saved, defects avoided, waste recycled, energy performance?
Who on the client side would be willing to comment?

Ask follow-up questions until you understand the nitty-gritty, and check anything that doesn’t add up. Don’t worry about looking stupid. You’ll look sillier if you get it wrong in print.

Step 3: Structure it like a story, not a spec sheet

A case study that sells follows the same basic shape as a good news feature. Here is the structure I use.

1. A headline with one idea

Every news story has one main idea, the one the headline announces. Do the same. Find the single most interesting thing about the project and build the case study around it. “Piling through made ground without a single settlement claim” beats “New office development, Macclesfield.”

2. The client’s problem

Open with what the client needed and what was at stake, in their terms rather than yours. This is what a buyer in the same position will recognise.

3. The constraints

Budget, programme, a tight site, live operations, planning conditions, the neighbours. Constraints are what make the solution interesting.

4. What you did, and why

This is where most case studies list materials and methods. Add one thing: the reason. A simple test is to bolt a “why” onto every “what”:

“We used a hidden-fix rainscreen because the client wanted crisp shadow lines with no visible fixings, and we specified A2 non-combustible even though the budget didn’t force us to.”
“We went with a piled raft because the made ground would have swallowed a standard footing, so we traded upfront cost for zero settlement risk.”
“We fitted a single-ply membrane because the roof carries PV and plant, and it had to take foot traffic and penetrations without leaking in year five.”

Notice what the “why” smuggles in every time: the constraint, the trade-off, and the thing the client was really worried about. It turns a specification into evidence that you were thinking about their problem, not just doing your bit.

5. The problems you overcame

Highlighting problems might sound like marketing madness, but these are challenges your team beat. Talking about them openly sets you apart and gives you a story, and people remember stories. Typical examples:

a supplier or subcontractor that went bust, or materials that couldn’t be sourced
sudden value engineering after a price rise
a deadline that moved
ecology on site that had to be protected or relocated
a detail nobody drew, or a wall that was out of true

Real problems are usually more unpredictable than any list, which is why you have to ask the team.

6. Results, with numbers

What changed for the client? Handover date against programme, cost against budget, defects, energy performance, safety record, waste diverted from landfill. If results arrived after handover (lower bills, fewer complaints, a second contract), go back and add them. A case study can be updated.

7. A client quote

A comment from the client makes the whole thing trustworthy. In effect, you have one client speaking to another about you. Always check the quote, and the finished copy, with the client before publishing. Many will also be glad to use it on their own website, which doubles its reach.

8. A data box for the technical readers

Tell a good story, but keep the technical reviewers happy too. Put the hard facts in a separate box so they can find them quickly:

client, location and sector
contract type and value
programme and key phase lengths
construction method and main systems
project team
notable numbers (waste recycled, carbon, energy rating, safety)

Step 4: Photos – fix a real one, never fake a good one

The photos that come back from site are often poor: blurry, grey sky, a skip in the corner, somebody’s thumb. It matters less than you think, and some of the fixes work better than a glossy hero shot.

Crop into the hard part. Instead of the whole building, small and tidy, show the one junction, connection or awkward detail that was the real challenge. The case study is about the problem you solved, so the image should show it.
Put the render next to the reality. The design model or BIM render alongside the built photo tells a story on its own: here’s what we set out to make, here’s what we made.
Sometimes, skip the photo. A before-and-after, a simple diagram of the fix, or one big number on a plain background can persuade more than a picture.

One firm rule: never use AI to generate a “photo” of built work. A case study’s whole value is that it’s true, and a buyer who spots one faked image stops believing your numbers too.

Case studies for specialists and subcontractors

On high-end projects, the glass, steel and joinery are what people photograph. They are usually fitted by a specialist team brought in by someone else, and that team often solves the hardest problems on the job. Yet when the project appears in a glossy magazine, the architect or interior designer gets the credit and the fitter gets paid and leaves.

If you’re a specialist, your best work is probably sitting in someone else’s portfolio. Photos with no story don’t do much. A proper write-up in your own name, or even a caption saying what was hard and how you solved it, does. You don’t need a marketing department, just the job written up properly by someone who understands what you do.

Case studies for construction tech companies

Tech moves at sprint pace. Construction moves at the speed of getting it right, because you can’t undo a steel frame. That doesn’t mean the industry is closed to new tools. It is open to a clear argument, as long as the benefits are obvious and the evidence is there.

Contractors, site managers and quantity surveyors are practical people. They want to know three things: What does it do? Who else uses it? What happens if it goes wrong? Many have been let down by shiny software before.

Customer stories answer the second question better than anything else you can publish. To make them work:

lead with the site problem, not the platform
use the buyer’s language, not your product team’s
choose customers who look like your next prospect
show what happened on a real project, with numbers
put the technical detail in its own section for the people who want it

You might be proudest of the tech. For a construction buyer, it’s often the least interesting part of the story.

Step 5: Make every case study work harder

Writing the case study is half the job. The other half is making sure it gets used.

Tag and store them so bid teams can find them

Once you have a handful of case studies, you’ll find they are hard to locate in a hurry, usually when someone is putting a tender together and asking for “a green office project in the North East”. Tag each one by sector, contract type, value, construction method, year, location, project team and special features. A simple shared folder or spreadsheet is enough.

Publish on your website

Give each case study its own page, with a clear title that describes the project and the problem. Link to it from the relevant service and sector pages. Each page is another chance to appear in search for the kinds of projects you want more of.

Pitch it to the trade press

An interesting project is a good way into the building press. Approach one editor at a time, starting with your first choice, and lead with the one idea that makes the project newsworthy.

Turn it into LinkedIn posts

One case study can produce several posts: the problem, the decision and the reason for it, the result, the client’s quote, a detail photo. Each one should include the “why”, not just the “what”.

Use it in proposals

Drop the relevant case studies into bids and capability statements. A short, well-chosen case study that matches the client’s project often does more than pages of company history.

Construction case study checklist

Is there one clear idea that could be a headline?
Does it open with the client’s problem, not the building?
Are the constraints explained?
Does every key decision come with a reason?
Is at least one problem and its solution described?
Are there measurable results?
Is there a client quote, and has the client approved the copy?
Is there a data box with the technical facts?
Do the images show the hard part of the job, and are they genuine?
Is it tagged so the bid team can find it?

Frequently asked questions

How long should a construction case study be?

For a website, 400 to 800 words plus a data box usually works. For a bid, follow the word limit, but keep a fuller master version you can cut from. The structure matters more than the length.

How many case studies do we need?

Enough to cover every sector and service you claim, with at least two examples each. A small library of strong, relevant case studies beats a long list of thin ones.

Do we need the client’s permission?

Yes, if you name them or quote them. Most clients are happy to agree, especially if they get to review the copy and can use it themselves. If a client says no, you can often still publish an anonymised version.

When should we write the case study?

Interview the team as soon as possible after handover, while details are fresh. Then go back after six months to add results from occupation.

Should we write them ourselves or use a specialist?

Either can work. The hard part is the interviewing: asking the right questions, pushing past “it went well”, and turning technical detail into a story a buyer will read. That’s where a writer with construction knowledge earns their fee.

Want your projects written up properly?

Takooba turns completed projects and happy customers into case studies that win the next job, for contractors, specialists, building products manufacturers and construction tech companies. See how it works or get in touch.

Michael Willoughby