AAG PROJECT BRIEF CHECKLIST
Version 1.0 | 13 October 2026 | Anglo Ascot Group

Use this worksheet to prepare a useful first conversation. It is not a quote,
contract, compliance certification or substitute for a project-specific scope.
Do not include passwords, customer personal data or confidential credentials.

1. THE PROBLEM
What is difficult today? Give one real task, without identifying customers.
Who is affected? What happens when the task goes wrong?
What would a useful improvement look like in ordinary language?

2. THE PEOPLE
Who uses the public website? Who works in the internal system?
Who can approve the scope, content and release?
Who needs to see information, change it, approve it or export it?

3. THE CURRENT TOOLS
What website, spreadsheet, application or provider is already involved?
What should be retained? What access is available to the business?
What restrictions, renewal dates or external dependencies matter?

4. THE FIRST RELEASE
List the essential pages or tasks. Mark everything else as a later idea.
Describe the main journey from entry to completion.
Name one unsuccessful action that the design needs to handle well.

5. CONTENT AND RIGHTS
Who supplies and approves services, prices, opening hours and descriptions?
Who owns the logo, photographs, illustrations and other supplied material?
What publication permission or licence applies? Keep the record.
What information must stay private?

6. DATA AND PROVIDERS
What information is actually needed and why?
Who can access it? How long does the business need to keep it?
Which hosting, mail, payment or other providers are involved?
Who is responsible for the relevant provider and processing agreements?

7. ACCEPTANCE
What should a person be able to do before the work is accepted?
What should happen if a submission fails or information is incomplete?
Which devices, roles and external connections are relevant to the checks?
Who records the result and decides whether the release is ready?

8. RELEASE AND HANDOVER
Who controls the domain, hosting, accounts and billing?
Who maintains content, availability and customer promises after launch?
What documentation and access are needed for routine operation?
What is the recovery route? What support is expressly included?

9. PRACTICAL CONSTRAINTS
Is there a target date and a reason for it?
What budget range is available? Which decisions are still open?
What can be reduced if the first release needs to stay focused?

NEXT STEP
Send a short, non-sensitive summary at https://angloascotgroup.com/contact
or email contact@angloascotgroup.com.