Kit / Case studies

Case study pages

A scope-only page for each cleared client: the decision, what was built, what the business kept and how it connects to today’s offer. No results until a client clears them.

ApprovedOwner: Wes FischerUpdated 13 Oct 2026

01The pattern

Scope, not results. The page shows the decision, what was built, what the business kept and how it connects to today’s offer. Outcome figures, quotes and metrics appear only after written clearance.
One page per cleared case, at /work/<slug>/, built from a content collection. Pages stay draft: true until the client clears them.
Ship gate: no page ships with an open [NEEDS WES] or [NEEDS CLIENT CLEARANCE] chip. The build fails if one remains.
Not in scope stays visible. An empty scope column reads "Not in scope" in mute, never a blank or a dash.

02Anatomy

Case study page · fictional exampleDraft state

Draft: not for publication · client permission unresolved

Work / Case study

Enquiries reach the right site first.

Example Co. wanted new-vehicle enquiries to reach a site with the model in stock. The work built routing rules the sales team now runs.

Client: Example Co.
Engagement: Systems & enquiries
Status: Current client [NEEDS WES]

01 / Scope

Scope of the work

Systems & data	Website & journeys	Campaigns & workflows	Testing & reporting
Enquiry and stock records	Not in scope	Routing into site queues	Reply-time reporting

Scope as published in each case. It describes what the engagement covered, not its results.

02 / Built

What was built

New-vehicle enquiries went to a central team, which passed them to sites by hand.

The work set routing rules on the stock list and site hours, and a held list for anything the rules can’t place.

03 / Kept

What the business kept

Decision logicRouting rules, versioned
Data recordEnquiry and stock tables, defined
WorkflowSite queues and the held list
DocumentationNot in the published scope. [NEEDS CLIENT CLEARANCE]

04 / Today

How it connects to today’s offer

Today this starts as a 30-day proof on one decision.

See what your business keeps

Start with the decision

Bring the decision worth testing.

Book a call

Example Co. is fictional. Forest: the header slash and Book a call. Scope and kept markers are ink, because nothing on a case page is a confirmed handover until the client says so.

03Page order

Head: crumb, H1 (3 to 9 words), standfirst, a meta row (client, engagement, status; sector and timeframe hide when empty), byline.
01 Scope of the work: scope summary, then the one-row scope figure with its fixed caption.
02 What was built: the situation in ink, the work in ink-2, then systems and people if cleared.
03 What the business kept: four fixed rows, logic first. A row with no published support says so in words.
04 How it connects to today’s offer: one text link to what your business keeps.
Close band: "Start with the decision", the close line as the H2, Book a call, and "Back to all work".

04Slots and empty states

Nineteen slots. Required slots fail the build when empty; optional ones hide.

#	Slot	Cap	When empty
1	`title`	3 to 9 words	Required
2	`standfirst`	25 words	Required
3	`client_name`	40 chars, cleared list only	Required; build error if not cleared
4	`sector`	30 chars	Hidden
5	`engagement_type`	4 words, a /work/ label	Required
6	`client_status`	Current or past client	Hidden until confirmed
7	`situation`	50 words	Required
8	`scope_figure`	4 cells, under 8 words each	Missing column shows "Not in scope"
9	`scope_summary`	45 words	Required; names every not-in-scope column
10	`work_included`	80 words	Required
11	`systems_touched`	5 items	Hidden
12	`people_involved`	25 words	Hidden
13	`client_kept`	4 items, 30 words each	All four rows always show
14	`timeframe`	10 words	Hidden
15	`offer_link`	90 words	Required
16	`how_we_work_link`	6 words	Default label and URL
17	`close_line`	30 words	"Bring the decision worth testing."
18	`cta`	Fixed "Book a call"	Lead-in hidden until Wes clears it
19	`byline`	4 words	Hidden

05Colour, type and links

Forest at most three times per viewport: the slash, Book a call (header and close band count once) and nothing else on the page.
Scope and kept markers are ink squares and ink outlines. Never Forest on a case page.
Text links are 600 weight ink with a trailing arrow in the text colour. No underlines.
Flag chips are grey, dashed and mono. They show in draft and preview only.
Curly apostrophes, no dashes, no prices, no client quotes, no storage provider names.

06Source and status

Pattern taken from the finished case study template (Site Dev spec, mockups and checks) in /workspace/ntwrk-review/case-study-template/. That mockup uses a real client and stays internal; this page shows only the fictional example. Permission is not verified for any client, so no case page ships yet.