Plainview Web

From open questions to a useful brief

Website Project Brief & Page Planner

Plan the goals, pages, content and launch decisions for a website. Export an editable project plan, a readable brief and a page inventory to share with your builder.

A clearer starting point

Give the website a purpose. Give each page a job.

Start with what you know and leave undecided details blank. Your work stays in this tab. Download JSON before leaving; there is no autosave.

1. Shape the project

Go to pages ↓

Use names or roles for responsibilities. Keep passwords, secret keys and private customer information out of this plan.

Project and decisions
A working name is enough. 0/160 characters.
Optional address or a note that this is a new site. This tool does not visit it. 0/160 characters.
Name a person or role responsible for final approval. 0/160 characters.
Who contributes, who resolves conflicting feedback, and who approves changes to scope, cost or timing? 0/2,000 characters.
Audience and outcome
Who needs the website, and what situation brings them here? 0/2,000 characters.
Their main questions or tasks, informed by actual inquiries or research. 0/2,000 characters.
For example, compare services and send a useful inquiry. 0/2,000 characters.
Describe what you hope to improve and how it could be observed. Avoid treating a desired result as a guarantee. 0/2,000 characters.
Features and content
Describe inputs, expected results, connected systems, follow-up owner and failure behavior. 0/2,000 characters.
List copy, images, logos and factual material; include location, permission status, supplier and due date. 0/2,000 characters.
What should be editable, by whom, and how often? 0/2,000 characters.
Record approximate quantities, existing downloads, redirects to plan, and email or other services that must keep working. 0/2,000 characters.
Identify review responsibilities, devices, languages, personal data, storage and retention decisions. Do not include private customer data. 0/2,000 characters.
Keep first-launch essentials separate from possible later work. 0/2,000 characters.
Budget, schedule and launch
State the range or limit, currency, what it covers and spending approver. This planner does not calculate a quote. 0/2,000 characters.
Consider domain, hosting, software and care; identify who approves spending. 0/2,000 characters.
Give a target date or window, its reason, and whether it can move. 0/2,000 characters.
For each dependency, note its owner, needed-by date, what it blocks and current status. 0/2,000 characters.
Record observable checks, such as an agreed test inquiry reaching the right inbox, and who approves launch. 0/2,000 characters.
List the question, person responsible, needed-by date and decision when known. 0/2,000 characters.
Accounts and handoff
For domain, hosting, email, CMS and integrations: provider, account owner, access status, invitation task and renewal owner. Never enter passwords, recovery codes or secret keys. 0/2,000 characters.
List source files, editable assets, licenses, instructions, content updates, recovery and support responsibilities to agree. 0/2,000 characters.
Optional date, change, approver and effect on scope, budget or timing. 0/2,000 characters.

2. Plan the pages

1/30 pages

Add the page's job, intended next step and content owner. For an existing site, record whether to keep, revise, merge or remove each page. Paths are planning text and are never requested.

0/160 characters.
For example, /services. This is not a URL checker. 0/500 characters.
Which question or task does this page help with? 0/2,000 characters.
0/2,000 characters.
Who supplies and approves the content? 0/160 characters.
Include source material, missing approvals, needed-by dates or a merge/redirect destination to discuss. 0/2,000 characters.

Save an editable copy

3. Save and share the plan

JSON reopens the complete plan here. Markdown is the readable brief. CSV contains only the page inventory. Empty entries are allowed so you can save work in progress.

Downloads are not encrypted. Review their contents before sharing. This planner does not submit an inquiry, build a site or determine an agreed price or scope.

How to use the result

Bring a clearer plan to the project conversation.

Describe the audience, main action, features, content, budget, launch dependencies and account responsibilities. Give each page a purpose, next step, content owner and readiness status. Record unknowns openly rather than guessing.

Save the JSON file to continue later, share the Markdown brief with a builder, or use the CSV page list for content coordination. Import accepts only this tool's version 1 JSON format. A checked import, new plan or fictional example replaces the current work only after confirmation.

Processing stays in this browser tab. The tool does not upload or save your plan, use browser storage, visit entered addresses or transfer details to a contact form. Closing or refreshing the page loses unsaved work. Keep passwords, recovery codes, secret keys and private customer information out of the brief.

Limits: 30 pages, 256 KiB (262,144 bytes) for UTF-8 JSON imports and saved plans, 160 characters for short project/page labels, 500 for page addresses and 2,000 for each planning note. CSV formula mitigation adds an apostrophe to potentially active cells; JSON retains the original text. The plan is a starting point for scope discussions, not a quote or a verified readiness score.

Website project preparation guide · Form & Intake Planner · Content Brief Generator

Website planning, design and development · How these tools work