Sector Growth Guide
How Should a Builder Turn a Completed Project Into a Website Case Study?
A practical guide to presenting completed construction work with a clear story, approved evidence and useful routes to the relevant service and area pages.
A useful construction case study explains the customer’s situation, the agreed scope, how the work was approached and what was completed. It combines a concise project story with approved photographs and links to the relevant service and area pages. It should help a prospective customer understand whether the builder has handled work like theirs, without publishing private details or inventing results.
A gallery shows the finish; a case study explains the work
Project photographs are valuable, but a collection of images does not always tell a prospective customer what was involved. A case study adds the context needed to assess relevance: what the customer needed, the condition or constraint at the start, which work was included and how the completed project relates to the service being considered.
The aim is not to turn every project into a long article. It is to make selected work easier to understand and compare. A concise, accurate project story can be more useful than a large gallery with no explanation.
Choose projects that answer a buying question
Start with projects that help future customers evaluate an important decision. A kitchen extension may demonstrate coordination between structural work, glazing and internal finishes. A roof replacement may explain access, weather protection and the sequence of work. A commercial refurbishment may show how the project was organised around an operating site.
Choose a project because it represents a real service or customer concern, not simply because it produced the most dramatic photograph. A balanced project library can cover different services, property types, constraints and operating areas without creating dozens of near-identical pages.
| Case-study element | What to explain | Evidence to consider |
|---|---|---|
| Project overview | Type of property, broad location and main objective | Approved exterior or completed-work image |
| Starting point | The practical problem, condition or requirement | Approved before image, survey note or brief |
| Scope | Work included and important exclusions | Concise service list or plan detail |
| Approach | Key stages, coordination and genuine constraints | Progress images or process explanation |
| Completed work | What was delivered and how it answered the brief | Finished images and approved factual detail |
| Next route | Where a similar customer should continue | Relevant service page and enquiry action |
Turn completed work into useful customer evidence
CitedFirst helps construction businesses connect project proof with the services, locations and questions customers are already exploring.
Explore visibility for buildersCollect the facts before writing
A short project record makes the writing easier and more accurate. Record the broad property or site type, customer objective, services delivered, important constraints, project stages and the approved description of the finished work. Keep dates, budgets, performance figures and client comments out unless they are accurate and cleared for publication.
Ask the people involved in delivery to review technical details. Marketing copy should not silently change a repair into a replacement, a subcontracted element into an in-house service or an estimated result into a measured outcome.
Protect the customer and the property
Permission matters. Agree which images, project details and customer references may be used. A broad description such as “a family home in Greater Manchester” may be appropriate where an exact address would expose unnecessary personal information. Commercial projects may also have confidentiality, security or contractual restrictions.
Check photographs for house numbers, vehicle registrations, security systems, documents, faces and neighbouring properties. Remove embedded location data where appropriate. If permission is limited, the case study can still explain the service and process without naming the customer or revealing the exact site.
Use a simple project-story structure
- Open with the project in one paragraph. State what type of work was completed and the broad context.
- Explain the starting requirement. Describe the practical need or constraint in customer language.
- Define the scope. List the important elements of work without turning the page into a quotation.
- Describe the approach. Explain the stages or decisions that are useful to a future customer.
- Present the completed work. Use factual observations and approved evidence.
- Offer a relevant next step. Link to the matching service and a clear enquiry route.
Plan photographs around the story
Use a clear lead image that shows the completed work. Add only the supporting photographs needed to understand the starting point, process or important details. Descriptive filenames and alternative text can make image purpose clearer, but the wording should describe what is visible rather than force keywords into every image.
Compress images before uploading and choose dimensions appropriate to the layout. Large files can slow the page without adding useful detail. Captions can explain a stage, material or design decision when that context is not obvious from the image alone.
Link the project to services and genuine operating areas
A project page should not become an isolated portfolio item. Link naturally to the service that was delivered, the relevant sector page and, where useful, a genuine location page. The corresponding service page can also link back to one or two representative projects as evidence.
Use area references only when they help explain real delivery. Repeating the same case study under multiple city names creates weak pages and makes it difficult for customers to know where the work actually happened.
Review the page like a prospective customer
Before publishing, check whether someone planning similar work can identify the project type, understand the scope and find the relevant service. Confirm that every claim is supported, permissions are recorded, images display correctly on mobile and contact routes work. A case study should reduce uncertainty, not merely announce that a project was completed.
Frequently asked questions
What is the difference between a construction gallery and a case study?
A gallery primarily displays images. A case study explains the customer’s broad requirement, project scope, approach and completed work so a prospective customer can judge whether the experience is relevant.
Does a builder need the customer’s permission?
Permission should be confirmed before publishing identifiable customer, property, project or testimonial information. The approved scope should cover photographs and the level of location or commercial detail being shared.
Should a construction case study include the project price?
Only when the figure is accurate, current enough to be useful and approved for publication. Costs vary with scope, condition, access, materials and timing, so an unexplained historic figure may mislead future customers.
How many photographs should a project page include?
Use enough approved images to explain the project clearly. A strong completed image plus selected before, progress and detail photographs is usually more useful than a large repetitive gallery.
Should every completed project become a website page?
No. Prioritise projects that answer a useful customer question, represent an important service or add distinct evidence. Similar smaller projects can be grouped rather than published as near-identical pages.
Sources and further reading
Make real work easier to assess
Connect project evidence with the next customer decision
Build a project library that explains relevant work and guides suitable customers towards the service they need.
Request a Free Visibility Plan