# Bracen page-family briefs

**Version:** 1.0
**Status:** Canonical route-composition contract.

Every public route belongs to one family. Families share identity, foundations and component rules but may vary composition according to their customer job. A new route does not create a ninth style unless none of these jobs fits.

## 1. Brand and market home

**Routes:** `/`, `/nz`, future `/au`
**Job:** Explain Bracen, make the promise clear and route the visitor to the right next decision.

Required: market context, one H1/value proposition, decision router, evidence/research moment, useful internal discovery, builder path and one closing action. `/` stays global; `/nz` owns local cost, consent, guide and builder pathways. `Find my next step` is primary and the online estimate secondary. The H1 does not need the brand name when the wordmark/eyebrow supplies identity.

Hero imagery must be real and attributable. If a suitable image is unavailable, use a strong type-led composition rather than generic foreign property imagery.

## 2. Editorial guide and comparison

**Routes:** `/nz/guides`, `/nz/guides/[slug]`, `/nz/master-build-guarantee`, `/nz/best-*`
**Job:** Answer a defined question, earn trust and move the reader to one useful next step.

Required: answer-first opening, author/reviewed date, contents for long pages, readable 68ch body, sources/method, limitations, related questions and one contextual CTA. Use coloured backgrounds only for evidence, caution or a single key takeaway.

Comparison variant: criteria and disclosure above the ranking, visible and structured-data order aligned, restrained sand treatment for number one only, paid placement unnumbered and separate. Include short cost/licensing/consent context that links to the canonical deep guide. Do not show a `client share` or similar internal/commercial percentage unless it is explicitly meaningful to the homeowner and methodologically defensible.

## 3. Service and location discovery

**Routes:** `/nz/[service]`, `/nz/[service]/[region]`, `/nz/builders-in/[region]`
**Job:** Own builder-discovery intent while helping the homeowner understand fit and coverage quality.

Required: query-matched H1, concise service/location context, visible result count and evidence boundary, image-led horizontal builder rows, clear sparse/empty states, related services/regions and contextual links to costs, consent and guides. Coverage state must remain visible and index/noindex rules must not be disguised by styling.

## 4. Builder profile

**Route:** `/nz/builders/[slug]`
**Job:** Help a homeowner assess one company without overstating verification.

Required: identity, region/services, source status and dates near the top, explicit unknowns, governed projects/images, review provenance, credentials in neutral language, service areas, related builders and one relevant enquiry. Support rich, sparse, claimed, unclaimed, rated, unrated and unavailable states. Never expose private data or let payment imply approval.

Profile implementation: `src/app/nz/builders/[slug]/page.tsx` and `profile.module.css`.
Use a full-width photographic hero with white identity text and an 80% black overlay, followed by a
compact directory-facts strip, in-page section links and a framed single-builder enquiry. The
profile body uses white. This route treatment follows Cameron's explicit 23 October 2026 direction.
Use an explicitly stored cover when available; otherwise use the existing Bracen NZ framing image
with a visible illustrative-image credit. Scraped social images do not become covers automatically.
Record-update dates must not be labelled as verification dates.

## 5. Cost guide and calculator

**Routes:** `/nz/cost-guides`, `/nz/[service]/cost`, `/estimate`, `/nz/estimate`, `/au`, `/au/guides/[slug]`, `/au/estimate`, approved future calculators
**Job:** Give an immediate useful range while showing its assumptions and uncertainty.

Required: answer/range in the first viewport, market currency (NZD or AUD, stated), region/date/units, scope qualifiers, method/source, calculator or scenario where governed, limitations, FAQ and next step. A comparison or service page may carry a short answer but the cost guide owns the canonical depth. Preserve calculations, validation, payloads, CRM and analytics during visual work.

## 6. Data report

**Routes:** `/nz/report` and report issues/regions
**Job:** Publish defensible market intelligence that can be cited and shared.

Required: issue/date masthead, findings before commentary, charts/tables with units, source and methodology, limitations, citation/share affordance and related homeowner decision. The report may use its namespaced publication palette/type exception but must retain Bracen identity and interaction accessibility.

## 7. Product and conversion

**Routes:** `/nz/plan-your-project`, `/nz/feasibility`, `/nz/claim`, `/nz/pricing` and their confirmed global equivalents
**Job:** Complete a concrete homeowner or builder task without looking like a generic dashboard.

Required: outcome-first header, clear scope and expectations, one action, progress where multi-step, privacy/lead-use copy, validation, result boundary and success/error states. Preserve all identifiers, query parameters, directory lookup, checkout hooks and event contracts. An incomplete payment path must look unavailable, not live.

## 8. Utility and governance

**Routes:** editorial/about, privacy, terms, methodology, contact, not-found, loading and error
**Job:** Make standards, obligations and recovery actions easy to read.

Required: shared chrome, one-column reading measure, explicit effective/updated date, accountable contact where relevant and one safe recovery action for errors. No marketing-card grid or decorative illustration is required.

## Shared release checks

- One H1 and logical headings.
- Full, partial, empty, loading and error states remain truthful.
- Metadata, canonical, JSON-LD, index rules, redirects, internal links, forms and analytics are preserved unless explicitly changed.
- Evidence uses words and dates, not colour alone; commercial relationships are adjacent to what they affect.
- Every image has a known source, permission basis, alt/caption decision and responsive crop.
- No overflow at 320, 375, 768 or 1280px; keyboard, focus, 44px targets, contrast and reduced motion pass.