# Project brief

The document your AI should read before any request about the project.

How to use it: replace each example with your own content, then delete the guidance in italics. Keep the headings: they help your AI find the right passage.

## The goal in one sentence

*What the project must change, for whom, and how you will know it worked.*

Example:

> Rebuild the Atelier Lumen website so quote requests go from 12 to 30 a month by September.

## What is in the project, and what is not

*Two short lists. The second stops your AI suggesting what has already been ruled out.*

Example:

> In the project: home page, service pages, quote form, mobile version.
> Out of the project: blog, online shop, new logo.

## Deliverables and their dates

*One deliverable per line, with its date and who signs it off.*

Example:

> - Site map: 14 March, signed off by the client.
> - Mock-ups: 4 April, signed off by the client.
> - Go-live: 30 May.

## Who does what

*Each person’s role, without surnames. Your AI will know who to point a question to.*

Example:

> - Client relationship: account lead.
> - Copy: writer.
> - Mock-ups: designer.
> - Build: developer.

## Constraints never to forget

*Budget, deadlines, legal obligations, firm client preferences.*

Example:

> Budget capped at €18,000 excl. tax. No stock photos. The site must stay online during the switch.

## Questions still open

*What has not been decided. Add the date you expect an answer.*

Example:

> Should the form ask for a budget? Answer expected on 20 March.