| Content & documents | The amount of usable content, outdated pages, scans, PDFs, languages and department review needed. | Who inventories, rewrites, converts and approves material? Which records should be archived, with whose approval? |
| Design & CMS | Template variety, editing roles, approval workflows, search and reuse of existing systems. | Which resident tasks and staff actions must each template support? What can the agency maintain itself? |
| Accessibility testing | The templates, documents and interactive features in the test scope, plus remediation and retesting. | What standards, manual checks, test evidence and acceptance criteria does your agency require? |
| Integrations | Vendor access, API support, authentication, data mapping, error handling and ongoing dependencies. | Is a labeled link sufficient, or is a supported integration required? Who owns the connected systems? |
| Training & support | Number of editors, departments, sessions, documentation and support arrangements. | What is included at handoff? Which updates and support requests will staff handle, and which need assistance? |
| Launch & migration | URL changes, staging reviews, content freeze, validation and coordination with existing providers. | Who approves launch, checks redirects and handles the transition? What rollback and handoff steps are required? |