Printable implementation checklist
Custom Websites Implementation Readiness Checklist
Custom Websites Implementation Readiness Checklist organizes the decisions that matter for organizations planning a new website, redesign, portal, directory, or online service: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
Custom Websites implementation-path comparison
Compare the smallest responsible paths before treating replacement as the default.
| Path | Best fit | Watch closely |
|---|---|---|
| Repair | The core of business and service website development remains sound | A template cannot support the required workflow |
| Extend | Responsive HTML, CSS, React and modern web stacks has a stable, understood boundary | The current site no longer represents the business |
| Replace | Ownership or architecture prevents a responsible repair | Content and navigation have become confusing |
Before discovery
A template cannot support the required workflow. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as responsive HTML, CSS, React and modern web stacks.
- Name the decision owner
- List systems and vendors
- Collect examples and exact errors
- Confirm who controls access
Before implementation
For Custom Website Development, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Confirm backup and restore path
- Write acceptance checks
- Identify security or privacy constraints
- Document exclusions
Before launch
Frame the first scope around business and service website development and one observable acceptance journey. Treat custom portals, directories and booking systems as a later phase unless the evidence shows it is a true dependency.
- Business and service website development
- Custom portals, directories and booking systems
- CMS and structured content architecture
- Rollback decision point
Before handoff
Repair fits when the core remains sound. Extension fits when the boundary around responsive HTML, CSS, React and modern web stacks is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Current documentation
- Account and domain ownership
- Monitoring responsibility
- Prioritized next steps