Copyable client message
Hi [client name], before we start the redesign, we need one complete request package so we can plan the site without chasing missing files later.
Please send the current website URL, goals for the redesign, required pages, approved copy, logo/source brand files, image assets, CMS access, hosting access, domain access, analytics access, and the person who gives final approval.
If anything is not ready yet, note who owns it and when it will be available.
Request checklist
| Section | Ask for |
|---|---|
| Project context | Redesign goals, current site problems, launch deadline, target audience |
| Site structure | Current URL, pages to keep, pages to remove, new pages, sitemap notes |
| Content | Page copy, service descriptions, team bios, testimonials, case studies |
| Brand assets | Logo source files, brand guidelines, fonts, colors, photography |
| Access | CMS, hosting, domain registrar, analytics, Search Console |
| Approval | Final decision maker, review steps, legal or stakeholder constraints |
Common mistakes
- Asking for “all content” without naming the pages.
- Accepting a low-resolution logo screenshot as a source file.
- Waiting until development to request hosting or domain access.
- Not identifying the final approver before the first review round.
Portal upgrade
A static request is fine for one-off work. A Kicklayer portal makes the same request trackable: clients see each missing item, agencies can reject unusable uploads, and the finished package is easier to export.
Client-ready request
A version you can paste into an email, Slack thread, or Kicklayer portal.
Hi [client name], before we start the redesign, please send one complete package with the current site URL, redesign goals, required pages, approved copy, brand source files, images, CMS access, hosting access, domain access, analytics access, and the final approver. If an item is not ready, please note who owns it and when it will be available.
How to structure the request
Break the ask into fields a client can answer cleanly, rather than a single vague upload request.
Redesign goals
Required text
Ask what needs to change, what must stay, and which business outcome matters most.
Page list
Required text
Collect the sitemap, pages to keep, pages to remove, and new pages that need copy.
Brand files
Required file
Request source logo files, brand guidelines, fonts, colors, photography, and illustration files.
Site access
Required access
Separate CMS, hosting, registrar, analytics, and Search Console access into their own fields.
Approval owner
Required approval
Name the person who can approve structure, copy, design, launch timing, and legal review.
Client request breakdown
These are the asks that make the request specific enough for the client to complete without a follow-up loop.
Project context
What is the main goal of the redesign?
This keeps design decisions tied to a measurable outcome instead of taste alone.
Content
Which pages need new copy, existing copy, or client review?
Redesign delays often start when page ownership is vague.
Assets
Send logos in SVG, AI, EPS, or high-resolution transparent PNG format.
A screenshot or compressed social avatar is rarely usable in production.
Access
Provide CMS, hosting, domain, analytics, and Search Console access separately.
Separate requests make missing permissions easier to spot.
Launch
Confirm fixed dates, blackout windows, and final approval stakeholders.
Launch constraints should be visible before design or development starts.
Make the request easier to complete
Small wording choices change whether a client sends useful material or another incomplete reply.
Do
- Name every required page instead of asking for all website content.
- Ask for source files and acceptable alternatives in the same field.
- Collect access before development begins, even if it will not be used until launch.
- Confirm who can approve final copy, design, DNS changes, and launch timing.
Avoid
- Accept a logo screenshot as the final logo asset.
- Bury access requests in a general project kickoff email.
- Let multiple stakeholders send conflicting page lists in separate threads.
- Wait until the week of launch to ask for domain registrar access.
When the checklist becomes a portal
The same request becomes more reliable when every field has an owner, a status, and a place to submit it.
Clients see each missing item in one place instead of hunting through emails.
Your team can reject unusable logos, incomplete copy, or missing access details.
The finished package can be exported when the redesign is ready to begin.
Practical questions
What should a website redesign request include?
At minimum, collect goals, current site problems, page list, approved copy, brand files, images, CMS access, hosting access, domain access, analytics access, and final approval ownership.
Should access details be sent by email?
It is better to use a controlled portal or password manager invite. If you must use email, ask for named user invitations instead of shared owner passwords.
When should the client send content?
Ask for required content before design or development starts. If some content is not ready, collect the owner and due date so the gap is explicit.