Blank requests for web designers and small agencies. Adapt them to your project. A received item still needs review. You may use these drafts in your own work.
Free editable versions: gatherkit.io/gather/templates. Published by Interesting Concepts LLC. This pack contains no client information.
Ask for page copy, imagery and approvals in one organized request.
CONTENT REQUEST — [Project] Pages: [Pages needing content] Coordinator: [Client coordinator] Requested by: [Requested delivery date] Upload location: [Approved upload location] For each page: [ ] Approved page copy with a named owner. [ ] Images with usage permission and useful filenames. [ ] The action visitors should take. [ ] Correct contact details and destinations. [ ] Final approval or the name of the remaining approver. Please flag missing items and their expected dates. A received file still needs review.
Never ask clients to put passwords, payment details or sensitive personal records into a general content checklist.
Open the editable versionGet the decisions that shape a project before building the wrong thing.
KICKOFF BRIEF — [Project] Primary outcome: [Primary outcome] Audience: [Intended audience] Final decision-maker: [Final decision-maker] Main constraint: [Main constraint] Questions to resolve: 1. What should a successful visitor or customer do? 2. What must remain from the current process? 3. Which deliverables are included in the agreement? 4. Who supplies content and who approves it? 5. What could block the schedule? 6. Which decisions are still open, and who owns each?
Keep unconfirmed answers marked open. Silence is not approval.
Open the editable versionCheck that the next person has the files, decisions and responsibilities they need.
HANDOFF — [Project] Receiving owner: [Receiving owner] Approved files: [Approved files location] Open items: [Open items] Next review: [Next review] [ ] Final versions are clearly labeled. [ ] Links and access have been checked by the receiver. [ ] Usage rights and known limitations are documented. [ ] Open items have owners and dates. [ ] Instructions explain the next routine task. [ ] The receiver has confirmed what arrived. Transfer credentials through an approved secure channel separately.
Mark receipt and acceptance separately; they are different decisions.
Open the editable versionCollect the promise, proof and next action needed to write a useful homepage.
HOMEPAGE COPY REQUEST — [Project] Who the homepage is for: [Who the homepage is for] Main service or offer: [Main service or offer] Primary visitor action: [Primary visitor action] Available evidence: [Available evidence] [ ] One sentence explaining who you help and what you do. [ ] The visitor problem, in the customer’s own language. [ ] Three specific services or benefits, with supporting detail. [ ] Evidence for every claim, including permission to publish quotations. [ ] A primary button label and the exact destination it should open. [ ] Hero image choice, crop notes and meaningful image description. [ ] Public contact details, service area and responsible approver. Mark unanswered items as open. Record who approves the final version before using it.
Do not invent awards, testimonials, customer counts or guaranteed results.
Open the editable versionTurn a company history into a credible introduction with facts and a clear point of view.
ABOUT PAGE STORY WORKSHEET — [Project] Why the business began: [Why the business began] Verified milestones: [Verified milestones] Story approver: [Story approver] Approved portraits or archive images: [Approved portraits or archive images] [ ] Founder or team introduction with correct names and roles. [ ] The customer problem that led to the business. [ ] A short timeline containing only checked dates and milestones. [ ] An explanation of how the team works today. [ ] A concrete example that supports each stated value. [ ] Permission to use portraits, team stories and customer names. [ ] A relevant next step, such as viewing services or contacting the team. Mark unanswered items as open. Record who approves the final version before using it.
Avoid manufacturing a dramatic founder story or publishing personal details without permission.
Open the editable versionDefine the deliverables, fit, process and exclusions for one service.
SERVICE PAGE CONTENT BRIEF — [Project] Service name: [Service name] Best-fit customer: [Best-fit customer] What is included: [What is included] How to enquire: [How to enquire] [ ] The problem this service helps solve. [ ] Observable deliverables the customer receives. [ ] What the client must provide before work begins. [ ] Main stages and any timing dependencies. [ ] Exclusions and services quoted separately. [ ] Verified qualifications, relevant work or permitted testimonials. [ ] Pricing basis if the client authorizes publication. [ ] Enquiry route and information needed to assess fit. Mark unanswered items as open. Record who approves the final version before using it.
A website brief cannot change signed scope, contractual obligations or pricing without agreement.
Open the editable versionCollect product facts, variants, imagery and purchase information before building a store page.
PRODUCT PAGE INFORMATION REQUEST — [Project] Product and SKU: [Product and SKU] Available variants: [Available variants] Verified specifications: [Verified specifications] Approved policy links: [Approved policy links] [ ] Correct product name, SKU and variant labels. [ ] Dimensions, materials, compatibility and care instructions. [ ] Current prices and currency approved by the store owner. [ ] Variant-specific images matched to the right product. [ ] Stock or availability source and person maintaining it. [ ] Shipping restrictions and links to approved return information. [ ] Evidence for performance, sustainability or certification claims. [ ] Accessible image descriptions and a clear purchase action. Mark unanswered items as open. Record who approves the final version before using it.
Do not invent certifications or legal policies. Ask the responsible business owner to provide approved policy text.
Open the editable versionGather a usable project story without exaggerating the outcome.
CLIENT CASE STUDY INTERVIEW — [Project] Client name or approved anonymous description: [Client name or approved anonymous description] Starting challenge: [Starting challenge] Work delivered: [Work delivered] Available outcome evidence: [Available outcome evidence] [ ] Permission to name the client and display the work. [ ] Starting situation and the objective agreed before the project. [ ] Constraints that influenced the solution. [ ] Specific work completed and the team’s actual contribution. [ ] Before-and-after images with clear labels and permission. [ ] Outcome evidence, its source and measurement period. [ ] A clear distinction between observed results and client opinion. [ ] Final client review of quotations and attribution. Mark unanswered items as open. Record who approves the final version before using it.
Do not imply sole credit for work done jointly or publish confidential client performance data.
Open the editable versionRequest consistent, approved biographies and portraits from a client’s team.
TEAM BIOGRAPHY COLLECTION — [Project] People included: [People included] Requested biography length: [Requested biography length] Portrait requirements: [Portrait requirements] Final reviewer: [Final reviewer] [ ] Preferred public name, pronouns if voluntarily supplied, and exact role. [ ] Responsibilities relevant to the website audience. [ ] Verified qualifications and dates where relevant. [ ] A brief explanation of the person’s approach to their work. [ ] Optional personal detail chosen by the individual. [ ] Approved portrait with usage permission and credit requirements. [ ] Public professional links the individual wants included. [ ] Approval from each person before the biography goes live. Mark unanswered items as open. Record who approves the final version before using it.
Do not request private home addresses, birth dates or unrelated personal histories.
Open the editable versionCollect real customer questions and assign an owner to each answer.
CUSTOMER FAQ COLLECTION — [Project] Service or product covered: [Service or product covered] Questions customers actually ask: [Questions customers actually ask] Where the questions came from: [Where the questions came from] Answer owner: [Answer owner] [ ] The question in language a customer would use. [ ] A short direct answer before any supporting explanation. [ ] Conditions, exclusions or dependencies affecting the answer. [ ] An approved source for prices, deadlines or policy statements. [ ] A useful link when the answer needs a longer explanation. [ ] An owner and review date for information likely to change. [ ] Removal of duplicate questions and unsupported claims. Mark unanswered items as open. Record who approves the final version before using it.
Do not disguise promotional statements as customer questions or copy another company’s policies.
Open the editable versionRequest the correct logo, font and visual files with usable access and version notes.
BRAND ASSET REQUEST CHECKLIST — [Project] Brand or trading name: [Brand or trading name] Approved asset folder: [Approved asset folder] Brand approver: [Brand approver] Planned uses: [Planned uses] [ ] Primary logo in an appropriate vector format if available. [ ] Light, dark and compact logo variations with usage notes. [ ] Brand color values and approved combinations. [ ] Font names, licensed files or authorized delivery links. [ ] Brand guidelines and the latest version date. [ ] Photography or illustration library with permission notes. [ ] Favicon or small-format mark if approved. [ ] Access tested from the designer’s account, without sharing passwords. Mark unanswered items as open. Record who approves the final version before using it.
A file being downloadable does not prove that the client has rights to use it.
Open the editable versionMatch each image to its page, purpose, crop and permission status.
WEBSITE IMAGE BRIEF — [Project] Page and image placement: [Page and image placement] What the image should communicate: [What the image should communicate] Required shape or crop guidance: [Required shape or crop guidance] Image supplier and approver: [Image supplier and approver] [ ] Source image link and descriptive filename. [ ] Subject or message the image needs to communicate. [ ] Planned placement and required aspect ratio. [ ] Focal point and any details that must remain visible. [ ] Permission, license restrictions and required credit. [ ] Whether recognizable people have approved the intended use. [ ] Useful image description based on the image’s purpose. [ ] Approved replacement if the original cannot be used. Mark unanswered items as open. Record who approves the final version before using it.
Do not treat a generic file name as an accessibility description or assume decorative images need lengthy alternative text.
Open the editable versionDecide which existing pages to keep, rewrite, combine or retire before a redesign.
WEBSITE CONTENT MIGRATION INVENTORY — [Project] Current website: [Current website] Pages in scope: [Pages in scope] Content decision owner: [Content decision owner] Proposed new structure: [Proposed new structure] [ ] Current page URL and page title. [ ] Proposed action: keep, rewrite, combine or retire. [ ] New destination or a clearly marked unresolved decision. [ ] Copy owner and whether source content is still accurate. [ ] Images, downloads and embedded items needing transfer. [ ] Links and forms that must be checked after the move. [ ] Redirect recommendation for the implementation team to review. [ ] Approval and a final published-page check. Mark unanswered items as open. Record who approves the final version before using it.
This worksheet does not crawl a site, configure redirects or guarantee search rankings.
Open the editable versionAsk the responsible person to approve a specific version and identify unresolved items.
WEBSITE CONTENT APPROVAL REQUEST — [Project] Version or review link: [Version or review link] Pages covered: [Pages covered] Authorized approver: [Authorized approver] Requested response date: [Requested response date] [ ] The exact document, page version or review link. [ ] What is ready for approval and what remains open. [ ] The person authorized to make the decision. [ ] Checks for factual accuracy, permissions and public contact details. [ ] One consolidated list of changes with page references. [ ] Explicit approval or requested changes, recorded with the response. [ ] A separate review if the approved content changes later. Mark unanswered items as open. Record who approves the final version before using it.
A request is not evidence of approval. Silence and a checked local box do not create client acceptance.
Open the editable versionPrepare a focused follow-up that names the missing item, owner and next decision.
MISSING WEBSITE CONTENT FOLLOW-UP — [Project] Client contact: [Client contact] Items still needed: [Items still needed] What depends on them: [What depends on them] Requested update date: [Requested update date] [ ] Confirm the items are still missing before sending. [ ] Remove anything already supplied or no longer needed. [ ] Name the format or decision required for each item. [ ] Explain the real dependency without inventing urgency. [ ] Ask for a realistic delivery date if the proposed date is not possible. [ ] Offer a short clarification conversation if the request is unclear. [ ] Review and send this message yourself through your agreed channel. Mark unanswered items as open. Record who approves the final version before using it.
Gather does not send this follow-up automatically. Do not claim that a deadline was agreed if it was only proposed.
Open the editable version