A design file communicates visual intent, but it does not always define every detail a WordPress implementer needs. Responsive behavior, reusable page patterns, editor controls, form states, and content variations may exist only in someone’s assumptions. A handoff that makes those details visible reduces rework and helps the agency review the build against the right source.
Identify the approved design version
Link to the source file and name the page, frame, or version that is approved for implementation. If the design is still changing, identify what is stable and what remains pending. Set a process for approving changes after build work begins. This avoids multiple people reviewing different screenshots or outdated exports.
Include the complete set of relevant layouts: desktop, tablet or intermediate widths if they matter, and mobile. Explain how the layout should adapt between the frames. If a component changes behavior at a breakpoint, state the expected interaction rather than relying on visual inference.
Provide final content and assets
Supply final copy or mark placeholders with an owner and due date. Include image files, logos, icons, fonts, and any license or attribution requirements. Tell the implementer how images should crop and whether alternate versions are needed for different layouts. Do not expect a production partner to extract assets from low-resolution screenshots when the original files exist.
For WordPress, note the existing theme, builder, plugins, or custom component rules that the implementation must follow. Confirm whether the partner is working in a staging environment and how changes will be reviewed. Avoid sharing live credentials through a design comment or unsecured message.
Describe the component system
Identify elements that should be reusable: buttons, cards, calls to action, navigation, typography styles, color tokens, and repeated page sections. Explain which components can accept different content and which pages need unique layouts. Reusable patterns help maintain consistency, but forcing every page into one template can obscure important differences.
If the project includes a block editor or page builder, describe what the client should be able to change after launch. Should staff edit text and images only, rearrange sections, create new pages, or manage custom data? The editor experience is part of the deliverable, not an afterthought.
Document interactions and content states
Write down behavior that is not obvious from a static design: menu open/close, hover or focus states, form success and error messages, accordion behavior, tabs, search, and any animation. Include empty states and longer-content examples if they affect layout. Tell the partner how to handle missing optional content and whether headings may wrap differently than shown.
Agree on acceptance criteria
Define how the agency will review the implementation. Criteria might include matching the approved design intent at specified sizes, using the supplied copy and assets, working keyboard navigation, functioning forms, and meeting WordPress editing requirements. Name the test browsers and workflows when they matter. Make criteria observable so both sides can agree on whether they are met.
Review in context
When the first build is ready, review it at multiple widths and test the page in WordPress rather than only comparing static screenshots. Check navigation, links, forms, content overflow, and editor usability. Give one consolidated set of feedback that separates defects from new requests. If the client changes the design, agree how that affects scope before continuing.
Describe behavior the design cannot show
A static design rarely answers every implementation question. Document hover and focus states, mobile navigation, expandable content, form validation, empty states, error messages, and what happens when a heading or image is longer than the sample. Note whether a component repeats and which fields a future editor should be able to change. These details help the agency distinguish intentional behavior from a defect during review. If the design uses a third-party font, icon, stock image, or plugin, identify the license or source and who is responsible for it. Confirm the intended fallbacks in case an asset cannot be used in the production environment.
Related resources
Explore the topic hub and these related guides:
For work involving WordPress, the official WordPress documentation is a useful reference for maintenance responsibilities and recovery planning.