These worksheets help you make a decision before opening another tool. Fill them out in your own notes and adapt the scope to your project. The blank fields are intentional: they are places for your requirements, evidence, and owners—not facts a tool should invent.
Use the website brief first, then the AI prompt or tool scorecard when those choices become relevant. Return to the launch checklist after the site is implemented and review the published pages rather than only the design canvas.
Website project brief
Define the people, purpose, content, and boundaries before choosing a tool.
WEBSITE PROJECT BRIEF — LowCodeWeb.com
Project name:
Audience:
The visitor's main task:
The one action the first release must support:
Pages and their distinct purposes:
Approved facts, copy, and images:
Missing information and its owner:
Visual direction and accessibility needs:
Included in this release:
Explicitly out of scope:
Person responsible for updates:
Acceptance checks:
- Every navigation and contact destination works.
- Real content fits narrow and wide layouts.
- Keyboard navigation and visible focus work.
- Metadata matches the visible page.
- The maintainer can make a routine update.
Decision date:
Open questions before launch:
AI web design prompt
Keep the task bounded and require real evidence rather than plausible-sounding claims.
AI WEB DESIGN PROMPT — LowCodeWeb.com
Create a page outline using only the approved material below.
Audience:
Primary visitor task:
Required pages or sections:
Approved facts and content:
Visual direction:
Constraints:
- Do not invent statistics, reviews, awards, or credentials.
- Do not add account, form, or service controls without an implementation plan.
- Keep essential information in readable text.
- Design a logical mobile reading order and keyboard-accessible navigation.
- Raise missing information as questions rather than filling gaps.
First return a content outline and list of assumptions.
After review, work on one component at a time.
Preserve approved facts and existing destinations during revisions.
Acceptance checks:
What a successful result looks like:
What must remain unchanged:
Tool evaluation scorecard
Compare the same job in each candidate, and keep unknowns visible.
TOOL EVALUATION SCORECARD — LowCodeWeb.com
Tool and edition:
Documentation checked on:
Evaluator:
Small project used for the test:
Fictional test data:
For each requirement, record one status:
DEMONSTRATED / PARTLY DEMONSTRATED / NOT DEMONSTRATED / NOT REQUIRED
1. Main workflow:
2. One awkward edge case:
3. Roles and access boundaries:
4. Routine content or logic change:
5. Mobile and keyboard behavior:
6. Error handling and recovery:
7. Export and ownership:
8. Current plan, capacity, and integration terms:
Evidence for each status:
Mandatory requirements still unresolved:
Ongoing owner and maintenance needs:
Decision and reasons:
Known limitations:
What would trigger a new evaluation:
Website launch checklist
Review the actual visitor journey, then hand over a site someone can maintain.
WEBSITE LAUNCH CHECKLIST — LowCodeWeb.com
[ ] CONTENT: Confirm facts, names, contact details, and image permissions.
[ ] JOURNEYS: Follow every menu item, call to action, and footer destination.
[ ] MOBILE: Check narrow, medium, wide, portrait, and landscape layouts.
[ ] ACCESS: Test keyboard navigation, focus, zoom, and reduced motion.
[ ] ASSETS: Confirm every image, stylesheet, script, and download is present.
[ ] METADATA: Review unique titles, descriptions, canonical URLs, and structured data.
[ ] DISCOVERY: Validate sitemap, robots file, RSS, and direct interior-page access.
[ ] HANDOVER: Record ownership, publishing steps, backups, and open issues.
Page types tested:
Browsers and viewport widths:
Issues and reproduction steps:
Outstanding decisions:
Release owner:
Review date:
Keep a decision record alongside the template.
A useful project note records what you decided, what evidence supports it, and what remains unknown. Update it when requirements change. It is more valuable than a long list of tool features with no connection to the work you need done.
Learn the evaluation method ↗