Design handoff: what should you receive, and what still needs development?
Separate designs, prototypes, and working functionality, and agree formats, source files, behavior notes, and implementation responsibilities.
A design handoff should explain the proposal to you and let the next implementer continue. Attractive screens alone may leave mobile layouts, errors, and responsibility for actual functionality unclear.
First distinguish website development that includes design from a standalone product design engagement. Their scope and deliverables can differ.
Agree the level of design
A wireframe mainly explains structure and content. A high-fidelity interface presents an appearance closer to the intended result. A clickable prototype demonstrates agreed paths. They support different decisions without necessarily delivering a working application.
| Deliverable | What you should be able to confirm |
|---|---|
| Pages and flows | Included pages, languages, tasks, and exclusions |
| Designs and preview | How to open them and which version is under approval |
| Shared rules and states | Applicable mobile, long-content, waiting, and failure behavior |
| Source and assets | Agreed editable files, images, and usage permissions |
| Remaining implementation | Simulated functions and services still to connect or build |
| Responsibility and acceptance | Who answers questions, implements, and checks completion |
A small website does not automatically need an extensive component library. Notes should explain the agreed work, especially behavior that appearance cannot communicate.
Separate prototypes from real functions
A prototype might display “Appointment confirmed” after a click without checking availability, saving data, or sending notifications. Record separately what it demonstrates and what will be implemented.
Real inquiries need receipt checks; real bookings need confirmation in the relevant system. Visual approval does not establish production functionality. See the form guide and acceptance guide .
How SiteMonk delivers
Website design and development includes website design, with pages and functions agreed for the project. Standalone product and UX design has a separate scope for flows, interfaces, and design detail, billed for actual hours.
SiteMonk delivers HTML/CSS designs and browser prototypes, with source, annotations, and acceptance notes according to the agreed scope. We do not provide Figma files. Developing a working product requires a separate scope.
You confirm business content, reviewers, and approval feedback. The team records assumptions and unresolved items. Have one contact consolidate feedback and distinguish corrections from new requests. See the website design process for the stages.