Intake and scope definition

This form captures the business decision, delivery constraints, governance needs, and ownership model required to move a website request through the factory without avoidable rework.

Business outcome

Clarify why the site should exist and how leadership will know it worked.

01 / 04

Experience scope

Define the shape of the experience without turning intake into a full specification.

02 / 04
Expected size *
Google Analytics required *
Integrations with other systems required *
Registration form needed *

Governance and risk

Make privacy requirements and known delivery constraints visible before prototype work starts.

03 / 04
Privacy and cookie consent are included by default.

The factory will add the required consent and privacy controls as part of the governed production path.

Launch path

Give delivery teams enough signal to estimate architecture, environments, release timing, and support needs.

04 / 04
Editorial model *
Select an editorial model to see timing impact.

Static delivery is the fastest path. CMS delivery adds architecture, integration, governance, and editorial workflow decisions.

Expected change rhythm *

Submitting does not deploy anything. It marks the request as ready for Stage 02: prototype direction and scope validation.

Complete the required fields and choices before submitting.