Fieldwork Five

A written, fixed-scope process

Know what ships.

Before production begins, the scope, inputs, approval points, and handoff are written down. Here are three working examples of what that looks like.

These are process samples, not client deliverables or case studies. A project’s final scope is confirmed in writing with the client. The five-business-day production period starts after scope approval, Stage 1 payment, required materials, and a named approver are confirmed; client feedback, funding, and DNS timing also affect the schedule.

Artifact 01 / Scope

Sample written scope

A compact view of the deliverables and boundaries that are confirmed before work starts.

OutcomeA focused website with a clear path for mobile visitors to call or request an estimate.
PagesUp to five core pages: home, one primary service, one service area, about, and contact. One may be replaced by written agreement.
IncludedOne estimate-request workflow, mobile-first implementation, client-approved copy refinement, metadata, semantic headings, sitemap, appropriate business schema, verified phone and form destination, deployment support, two consolidated revision rounds, recorded handoff, and final project files.
Not includedAdditional pages, new integrations, brand identity from zero, paid advertising, ongoing SEO, photography, bulk migration, hosting fees, or guarantees of rankings, traffic, leads, or revenue.
Price & stagesFixed project price: USD 2,400. Stage 1: USD 1,200 for approved page plan, working copy, and responsive prototype. Stage 2: USD 1,200 for production implementation, QA, launch support, and final file transfer.

Payment is handled through the mutually confirmed settlement workflow. The final platform terms and fees are reviewed before acceptance.

Artifact 02 / Before launch

Launch readiness checklist

Items confirmed with the client before production and launch. The client supplies accurate information and identifies who owns technical access.

  • Public business name, verified phone number, and tested form or CRM destination.
  • Approved service descriptions, service-area list, hours, and any emergency terms.
  • License, certification, warranty, and financing claims verified and approved for publication.
  • Logo, licensed photos, testimonials, and written confirmation that supplied materials may be published.
  • Privacy policy and other legal notices supplied by the client.
  • Agreed page plan, named approver, and one representative to consolidate feedback.
  • Domain registrar, DNS change owner, hosting owner, analytics owner, and Search Console owner identified.
  • Existing URLs that should be preserved identified for a redirect map; credentials are not stored in the project brief.
  • Two revision rounds, change-request boundaries, schedule dependencies, and no-guarantee terms understood.

Missing materials, access, consolidated feedback, or stage funding move the delivery date. Client-controlled DNS or registrar delays are outside the five production days.

Artifact 03 / Acceptance

Handoff & acceptance checklist

Acceptance is recorded at each stage against the agreed result. This checklist is a sample of the confirmation points, not a substitute for the final settlement-platform agreement.

Stage 1 — plan and prototype

  • Page plan matches the written scope.
  • Working copy reflects information approved by the client.
  • Responsive prototype presents the agreed page structure and mobile layout.
  • Client records acceptance and any required in-scope corrections before Stage 2 preparation.

Stage 2 — production and handoff

  • Production site is checked against the approved scope.
  • Main phone and estimate-request paths are tested.
  • Launch support and recorded operating walkthrough are provided.
  • Final project files or ownership access are transferred.
  • Client records acceptance and any in-scope defects for the fourteen-day correction window.

The correction window covers defects in the delivered scope. New pages, integrations, and major direction changes require a written change request.