Client Intake / Project Brief Questionnaire (UK)
Use this client intake questionnaire to collect the key details you need before starting a freelance or small business project (scope, goals, content, timeline, budget, and approvals).
Disclaimer: This template is for general information only and is not legal advice.
CLIENT INTAKE / PROJECT BRIEF QUESTIONNAIRE (UK)
Client name/company: [ ]
Contact person: [ ]
Email: [ ]
Phone: [ ]
Project name: [ ]
Date: [DD/MM/YYYY]
Preferred communication: [Email/WhatsApp/Teams]
Time zone: [UK/Other]
1) ABOUT YOUR BUSINESS
• What does your business do?
• Who is your target audience/customer?
• What are your top 3 competitors (if any)?
2) PROJECT GOALS
• What are you trying to achieve with this project?
• How will you measure success? (e.g., enquiries, bookings, sales)
3) SCOPE & REQUIREMENTS
• What do you need delivered? (list deliverables)
• Any features/requirements that are essential?
• Any features that are nice-to-have?
4) CONTENT & ASSETS
• Do you have your logo, brand colours, and fonts?
• Do you have text/content ready? If not, who will write it?
• Do you have images/videos? If not, should we source stock images?
5) BRAND & STYLE (OPTIONAL)
• Share 2–3 websites/designs you like (links) and why you like them.
• Any designs you dislike (links) and why?
6) TECHNICAL DETAILS (IF RELEVANT)
• Domain name (if already owned):
• Hosting/provider (if any):
• Access details available? (WordPress/hosting/email accounts)
• Integrations needed (e.g., payments, booking, email marketing):
7) TIMELINE & BUDGET
• Desired start date: _______ Desired launch date: _______
• Is this deadline fixed or flexible?
• Budget range (optional): £__________
8) APPROVALS & DECISION MAKERS
• Who will approve the work and provide feedback?
• How quickly can feedback be provided? (e.g., within 48 hours)
9) PAYMENT & INVOICING (OPTIONAL)
• Who should invoices be addressed to?
• Preferred payment method (bank transfer/card):
10) NOTES
[ ]
This one is gold for freelancers/small businesses because it helps you collect requirements before you start (and reduces “scope creep”).
