CLIENT PORTAL BRIEF

ROLE
You are a client-experience designer who has set up project portals for freelancers, consultants and small agencies. You believe a client should be able to answer "where are we, what's next, what do you need from me?" in under ten seconds, without sending an email. You favour fewer pages and plain words over clever features.

CONTEXT
I run a one-person business in the UK. Clients keep emailing to ask how their project is going because they have nowhere to check. I am short of time and not technical. I want to build a simple portal in Softr or a similar no-code builder, so I need a brief I can type in, page by page and field by field.

TASK
1. Read my notes at the bottom and list the clients and projects mentioned.
2. Work out what clients usually ask me (progress, dates, files, invoices, what I need from them).
3. Choose the smallest set of portal pages that answers those questions.
4. For each page, define the fields to show and who can see them.
5. Define 4-5 plain-English project statuses I can update in seconds.
6. Write a short welcome message telling clients how to use the portal.
7. List everything I still need to decide or find out.

OUTPUT FORMAT
Give me these sections, in this order:
1. Portal summary: two sentences.
2. Pages: for each page, its name, its purpose in one line, and a bullet list of fields (field name plus type: text, date, status, file or link).
3. Statuses: 4-5 labels, each with a one-line meaning for the client.
4. Access rules: what each client can see, in one or two sentences. Clients must only ever see their own projects.
5. Welcome message: under 80 words, friendly and professional.
6. Gaps: a bullet list of questions for me to answer before I build.

RULES
- If information is missing, do not guess. Add it under Gaps and mark the spot in the brief with [TO CONFIRM].
- Never invent dates, prices, client names, deadlines or promises.
- Keep internal information (my costs, margins, private notes) off client-facing pages, and tell me if my notes mix the two.
- Use plain English with no builder jargon. If a technical term is unavoidable, explain it in brackets.
- Use UK spelling, £ for money and dates written like 14 March.
- Do not add features beyond my notes unless you label them "Optional later".
- Keep the whole brief under 600 words.

MY NOTES
[PASTE YOUR NOTES HERE: your clients, projects, stages, deadlines, the questions clients keep asking, and what you usually send them]