Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Technology Buying Guides 6 min read

Website redesign vendor checklist: a working template

A working website redesign vendor checklist covering scope, capability, technical due diligence, security, contract and launch.

E
EncryptTechBD · 0 comments
Team meeting around a table with laptops
Photo: Direct Media / StockSnap

A website redesign replaces an asset that already earns revenue, ranks in search and holds customer history. The vendor checklist should therefore test protection as well as design taste. A beautiful proposal can still hide a weak migration plan, an untested accessibility claim or a contract that leaves you without the source files. Use this document as a scoring sheet and a gate record, not as a vague set of questions.

How to score the checklist

Score each item zero, one or two: zero for absent, one for claimed without evidence, two for evidenced and reviewed. Assign an owner for each section and record the evidence link. Review the checklist at shortlist, before contract signature and again at the launch gate. Set a minimum score for the technical, security and handover sections before considering the design score. A vendor that excels at visual concepts but fails the launch gate is not a safe choice for a business-critical site.

Section A: Business case and scope

  • Goals and baseline metrics. Owner: marketing lead. Evidence: current traffic, conversion, search and support measures.
  • Audience and priority tasks. Owner: product owner. Evidence: research notes or analytics review.
  • Page inventory and content owner. Owner: content lead. Evidence: list with keep, rewrite, merge or retire decisions.
  • Success criteria and acceptance method. Owner: project sponsor. Evidence: signed definition of done.
  • Budget envelope and contingency. Owner: finance. Evidence: approved range and change-control rule.
  • Decision owner and escalation route. Owner: project sponsor. Evidence: named roles and meeting cadence.

Section B: Vendor evidence

  • Comparable projects. Owner: procurement. Evidence: three references with outcomes, not just screenshots.
  • Named team and subcontractors. Owner: vendor. Evidence: roles, hours and confirmation of who does the work.
  • Platform and migration experience. Owner: technical lead. Evidence: a case with redirects, content and data migration.
  • Accessibility testing. Owner: design lead. Evidence: a recent audit and how issues were fixed.
  • Performance budgets. Owner: technical lead. Evidence: before-and-after Core Web Vitals evidence.
  • Support after launch. Owner: operations lead. Evidence: service description, response times and named contact.

Section C: Technical due diligence

  • Platform and hosting rationale. Owner: technical lead. Evidence: written trade-off against two alternatives.
  • Environments and deployment. Owner: developer. Evidence: staging, production and rollback process.
  • Backup and restore. Owner: infrastructure lead. Evidence: restore test, not just a backup schedule.
  • DNS, TLS and redirect ownership. Owner: technical lead. Evidence: access list and cutover plan.
  • URL preservation and redirect map. Owner: SEO lead. Evidence: exported URL list mapped to destinations.
  • Structured data and analytics. Owner: marketing lead. Evidence: tag plan, consent rules and event definitions.
  • Data migration. Owner: content or CRM lead. Evidence: field mapping and reconciliation report.

Section D: Content, search and accessibility

  • Content audit completed. Owner: content lead. Evidence: inventory with decisions and owners.
  • Metadata and headings reviewed. Owner: SEO lead. Evidence: template rules and sample pages.
  • Internal links checked. Owner: content lead. Evidence: broken-link report before launch.
  • Images have alternative text. Owner: content lead. Evidence: accessibility check on a sample.
  • Bangla and English handled consistently. Owner: content lead. Evidence: language switch, fonts and line-length review.
  • WCAG 2.2 AA target agreed. Owner: design lead. Evidence: audit against the standard, not a vendor claim.
  • Search, 404 and legal pages. Owner: product owner. Evidence: tested journeys and approved copy.

Section E: Security and data handling

  • Security standard agreed. Owner: security lead. Evidence: OWASP ASVS level and test scope in the contract.
  • Dependency and patch policy. Owner: developer. Evidence: update cadence and vulnerability process.
  • Admin access and multi-factor authentication. Owner: security lead. Evidence: role matrix and enforcement screenshot.
  • Vulnerability disclosure route. Owner: vendor. Evidence: published contact and response process.
  • Data processing agreement. Owner: legal. Evidence: signed terms covering personal data and retention.
  • Cookie consent and tracking. Owner: marketing lead. Evidence: consent behaviour tested before launch.

Section F: Contract, handover and exit

  • Scope and change control. Owner: procurement. Evidence: deliverables, assumptions and change pricing rules.
  • Intellectual property. Owner: legal. Evidence: assignment of design, code and content to your organisation.
  • Repository and source files. Owner: technical lead. Evidence: access before final payment, not after.
  • Documentation and training. Owner: vendor. Evidence: admin guide, editor training and recorded session.
  • Warranty and support. Owner: procurement. Evidence: defect period, response times and exclusions.
  • Exit and transition. Owner: legal. Evidence: data export, domain transfer and reasonable assistance clause.

Section G: Launch gate

  • User acceptance testing signed. Owner: product owner. Evidence: test log with pass and fail results.
  • Accessibility audit complete. Owner: design lead. Evidence: issues closed or accepted with an owner.
  • Performance tested on mobile. Owner: technical lead. Evidence: Core Web Vitals report on real devices.
  • Redirects and search checks passed. Owner: SEO lead. Evidence: crawl comparison before and after.
  • Rollback and DNS plan ready. Owner: technical lead. Evidence: named decision maker and tested restore.
  • Monitoring and support active. Owner: operations lead. Evidence: uptime checks, error tracking and on-call contact.

Sign-off and red flags

Record the section scores, the evidence links and the date of the decision. Do not sign the launch gate with open critical issues. Red flags include a vendor who will not share the repository, a migration plan that ignores existing URLs, an accessibility claim with no audit, a performance promise with no mobile test, and a contract that treats support as a separate negotiation after launch. A vendor who resists evidence is telling you how the project will be run.

Using the result

Compare vendors on the evidence they provide, not on the polish of the presentation. If two are close, ask each to walk through a failed project and explain what they changed. The answer reveals more about delivery than another concept board. Keep the completed checklist with the contract so that the promises made during selection become the standard used at handover.

A redesign also changes the platform, content and operating routine. Our custom software team handles the build and migration with the launch gate built in. The pricing page explains how work is scoped, and the website malware prevention checklist covers maintenance after launch.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes