CANADIAN WEBSITE PROJECT BRIEF
Branding Tatva | Updated 11 November 2026

Copy this plain text worksheet into your own document. Complete the fields you
can answer and mark the rest "to agree". Use it to compare proposals for the
same work. Website implementation receives its own scope and CAD quote.

Keep passwords, API keys, customer records and health information out of this
brief. Describe information categories and account owners only. Arrange access
through provider invitations after responsibilities have been agreed.

1. BUSINESS AND CUSTOMER
Business name and current website:
Services customers should understand:
Priority customers and provinces or territories served:
Main customer action, such as enquiry, booking or quotation request:
What makes that action difficult on the current site:

2. PAGE SCOPE
Pages to keep:
Pages to rewrite, add or retire:
Important existing URLs and the traffic or enquiries they support:
Documents, images or other downloads that need to move:
Who supplies and approves each page:

3. LANGUAGES AND REVIEW
English pages required:
French or other language versions required:
Named writer, translator and reviewer for each language:
How paired pages, forms and later updates will stay aligned:
Questions for Quebec counsel or another appointed adviser:

4. PLATFORM AND ACCOUNT OWNERSHIP
Current CMS and preferred editing tasks:
Domain, DNS, hosting and CMS account owners:
Booking, payment, CRM or email integrations to retain:
Existing licences, renewal dates and export restrictions:
Who receives administrator access and training at handover:

5. HOSTING, DATA AND ACCESSIBILITY
Required hosting or data location, if any, and who confirms it:
Information categories collected by forms and where they go:
Owner of privacy wording, consent decisions and retention requirements:
Accessibility target and important customer journeys to assess:
Named reviewer, agreed testing scope and retesting responsibility:
Support needed from users or specialist assessors:

6. MIGRATION AND SEARCH CONTINUITY
List old URLs beside their intended new destinations before launch.
Record which pages remain at the same address and who checks redirects.

Owner of the URL inventory and redirect map:
Owner of canonical, sitemap and indexing checks:
Search Console access owner and baseline reporting dates:
Launch fallback plan and the person authorised to activate it:

7. BUDGET AND CANADIAN REVIEW WINDOWS
Website budget or range in CAD:
One time project fee to confirm:
Recurring hosting, licences and support costs to confirm:
Tax treatment and payment provider charges to confirm:
Target launch date and business reason:
Canadian time zone and preferred meeting hours:
Named approver and expected feedback turnaround:

8. ACCEPTANCE CHECKS
Agree the evidence and owner for each check in the proposal.
Examples to adapt to the actual project:

A customer can complete the agreed enquiry or booking journey on the selected
phone and desktop browsers, with errors explained and delivery verified.

An editor can update an agreed service page using their own CMS account.

The agreed English and French pages, navigation and forms are reviewed by the
named language reviewers before publication.

Important old URLs reach the agreed destinations. Public pages carry the
intended canonical and indexing settings; the staging site stays protected.

The agreed accessibility assessment is completed, issues are assigned and
corrections are retested. Record any remaining limitations and their owners.

Project specific acceptance checks:
Copy the record below for each check. Use separate records when the page,
language or receiving team changes. Keep the agreed result beside the
observation so the approver can see what still needs attention.

Check reference and customer task:
Page URL and language:
Device and browser used:
Expected result agreed in the proposal:
Evidence required:
Tester and test date:
Observed result and receiving team confirmation where relevant:
Evidence location using sample details:
Status: pending / passed / failed / accepted with follow up
Issue, fix owner and target date:
Retest date, reviewer and evidence:
Acceptance owner:
Acceptance decision and date:

Issues agreed to block launch:
Remaining issues accepted by, fix owner and due date:
Final launch decision, approver and date:

9. HANDOVER AND SUPPORT
Files, account invitations and documentation to receive:
Training attendees and recording requirements:
Maintenance, backups and support responsibilities:
Support period, response expectations and exclusions:
How additional work is estimated and approved:

10. SUMMARY FOR AN ENQUIRY
Current website:
Main customer problem:
Provinces or territories served:
Required pages and languages:
Budget in CAD and target date:
Approver and Canadian review window:
Decisions still to agree:

Paste this short summary into the website enquiry form:
https://brandingtatva.com/contact?service=website-redesign&market=canada#write

Website scope:
https://brandingtatva.com/website-redesign

Canadian service and delivery details:
https://brandingtatva.com/brand-strategy-canada

FURTHER READING
Website launch acceptance checklist for Canadian businesses
https://brandingtatva.com/insights/website-launch-acceptance-checklist-canada

Google Search Central: site moves and URL migration
https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

W3C WAI: accessibility planning and responsibilities
https://www.w3.org/WAI/planning/

This is an original project planning worksheet. Your appointed advisers confirm
legal and regulatory requirements. Translation and specialist assessment need
an agreed scope. The signed proposal governs deliverables, fees and dates.