Validate - Scoping & Estimation (Internal)

Never client-facing. The unit each step is sized in, its S/M/L/XL bands, and the role mix - one section per step, in step order. Hours per step per tier are in the effort model; the tier model and prices in productisation.md. Bands and tiers are defined in depth.md.

5.1 Content Population & Migration

Lines: migration scripts ~4–6 hrs per source × content type · manual population ~0.25 hrs per item (calibration observed ~0.2; cushion kept) · both from the Cornerstone's migration tiers and content volumes. See the effort model.

Role mix: engineer writes and runs scripts; mid populates manually; lead engineer owns the migration report.

5.2 Content QA & Beta Release

Lines: content QA scales with volume (sampled - see the effort model); the beta pass itself is near-fixed (~8 hrs: full-site review, reports, release).

Role mix: mid runs the QA sweep; lead engineer signs the beta release and owns both reports.

5.3 User Acceptance Testing

Line: see the effort model - the cycle allowance and the extra-cycle rule live there; sold at the sales moment, confirmed in the Cornerstone. Extra cycles are priced variations (£2,500 each) or the Momentum route.

Role mix: lead engineer triages and owns fixes; PM runs the log and the windows; mid implements amends.

5.4 Acceptance & Final Content

Near-fixed: acceptance session, punch-list routing, freeze coordination ~4–6 hrs; the script re-run ~1–2 hrs per source (priced in the population lines).

Role mix: PM runs acceptance and the routes; engineer runs the re-run; the lead signs the handoff to Launch.