Insights:Website Development Acceptance Standards: Item-by-Item Checklist Before Launch
Four Dimensions
| Dimension | Checklist Content |
|---|---|
| Functionality | Page list, forms, admin panel |
| Content | Copy, images, links |
| Technical | Performance, compatibility, security |
| Operations | Statistics, SEO config, editability |
Functionality Acceptance
- Page list matches the contract; verify quantity and URLs.
- All forms submit successfully with success/failure notifications.
- Admin panel supports adding, editing, and deleting content.
- Role-based permissions are functional (at least admin and editor).
Content Acceptance
- No placeholder text in copy (e.g., "This is an introduction").
- Images include alt text.
- No broken internal links (spot-check 10).
- Contact info and addresses are accurate.
Technical Acceptance
- Page load times are acceptable on main pages.
- Mobile display is normal.
- HTTPS is active with no mixed-content warnings.
- Error pages (404) are configured.
Operations Acceptance
- Analytics code is installed.
- Sitemap is accessible.
- Page titles and descriptions are filled in.
- Admin panel can view form submissions.
Common Issues
- PAGES built that aren't in the contract checklist.
- Admin allows text edits but not image replacements.
- Internal links point to non-existent pages.
- Horizontal scrolling on mobile devices.
Acceptance Process Recommendations
- Developer conducts self-inspection and submits a checklist.
- The client inspects each item against the checklist.
- Issue classification: blocking (must resolve before launch) / deferrable.
- Launch only after all blocking items are fixed.
Scope Boundaries
Acceptance criteria are based on corporate showcase sites. Functional sites (member accounts, orders, payments) require additional business-rule checks and reconciliation verification.
Related articles: