Before a request becomes active
What needs to be ready, what can follow later, and how to keep work moving.
Ready before production
- A clear goal, audience, deliverable, and intended use.
- The agreed scope: pages, formats, dimensions, variants, and required outputs.
- Approved content and usable source assets for the work being produced.
- The printer template, platform requirements, or access needed for that stage.
- A priority, deadline, and one person who can approve the work.
What can follow later
Inputs for later stages can arrive later if we agree that sequence. For example, a launch domain may not be needed for wireframes, but it is needed before launch. Minor refinements can happen after a direction is reviewed. Missing core content, dimensions, or approval are not minor details.
If you are not ready yet
We can begin with discovery, a content outline, a wireframe, or an audit instead of pretending a production request is ready. Agree what can be explored using assumptions and what needs final information. Placeholder work may need revision when the real inputs arrive.
Use the checklist on each offering
Every individual offering has a short checklist tailored to its production needs. Tick it as a personal planning aid. It does not submit files, approve the request, or start the delivery estimate; we confirm readiness together. Checklist ticks reset when the page reloads.