UNFINISHED WEBSITE TAKEOVER WORKSHEET
Branding Tatva | Prepared 30 October 2026

Use this record before commissioning someone to complete an unfinished website.
Confirm the brief, available work, authorised access and unresolved dependencies
before deciding between completion, repair and migration. A working preview
alone leaves those decisions open.

This original planning worksheet is free and requires no account or email
address. Complete a copy in your own controlled workspace. Mark missing evidence
UNCONFIRMED rather than guessing. Keep passwords, recovery codes, API keys,
private repository links, access tokens and customer records out of this
worksheet and the enquiry form. Share only public URLs and redacted examples
that your business has permission to share.

01. RECORD THE CURRENT SITUATION

Business and person approving this review:
Public website URL safe to share:
Date observed and platform, where known:
Original business outcome and priority customer journey:
Intended launch date and reason for that date:
What already works:
What prevents launch:
Original scope available to the authorised reviewer: YES / NO / UNCONFIRMED
Previous acceptance decisions and outstanding questions:

Separate your observation from an explanation of its cause. For example,
"the booking button opens a blank page" is an observation; a technical cause
requires investigation. Avoid assigning blame in the working brief.

02. CONFIRM CONTROL AND PERMISSION

For each item below record: business owner | access status | permission to
inspect or change | evidence date | person resolving any gap.

Domain registration and DNS:
Hosting and deployment project:
CMS and editing access:
Source repository and build instructions:
Design files, approved copy, images and fonts:
Analytics and Search Console properties:
Forms, booking, payments and other connected services:
Backups and the person responsible for restoration:

Record status rather than credentials. Access to an account and permission to
reuse its contents are separate questions. Confirm the agreed handover and
licence position with the responsible party; disputed rights need qualified
review before reuse. Request secure invitations only after scope and authority
are agreed. Leave existing access controls in place during the enquiry.

03. INVENTORY THE WORK THAT CAN BE REVIEWED

Use one row per page, template, integration or content group:
Item | intended job | current state | evidence | remaining work | owner

Suggested states: OBSERVED WORKING / NEEDS REVIEW / MISSING / UNCONFIRMED.

Include mobile layouts, service pages, forms and confirmation messages, language
versions, downloads, CMS editing and required integrations. Identify which
source version corresponds to the preview. Separate approved work from concepts
and incomplete work. A page count alone leaves templates, writing and connected
services unresolved.

04. EXPOSE DEPENDENCIES BEFORE SETTING DATES

Pending content and approval owner:
Translation or language review and owner:
Third party licences, renewals and account holder:
Required vendor access or cooperation:
Hosting or data location requirements supplied by the business:
Specialist accessibility, privacy or security review required:
Business review windows and decision maker availability:
Items whose feasibility remains UNCONFIRMED:

Keep completion work separate from replacement features. Ask the reviewer to
explain what can be retained, repaired, replaced or deferred, with the evidence
and unresolved dependencies behind each recommendation. Implementation and
schedule are confirmed after the takeover review.

05. PRESERVE THE WORKING SITE AND SEARCH RECORD

Existing live site that must remain available:
Current URL and content inventory owner:
Available search and enquiry baseline, period and limitations:
Proposed URL changes, relevant destinations and review owner:
Staging review arrangements and approved access:
Backup and restoration evidence to request from the technical owner:
Release approver, rollback decision owner and support contact:

For a move that changes URLs, Google's guidance covers preparation, URL mapping,
redirects and monitoring. Search visibility can fluctuate during a move. [1]
Use the migration worksheet after deciding that migration belongs in the scope:
https://brandingtatva.com/resources/website-migration-launch-worksheet.txt

Record preview restrictions separately from production indexing checks. Google's
noindex guidance concerns search indexing; treat access to confidential staging
content as a separate access control decision. [2]

06. DEFINE ACCEPTANCE AND HANDOVER

For each agreed requirement record: expected result | review method | evidence
location in your private workspace | reviewer | unresolved issue | retest date.

Include the agreed mobile and keyboard journeys, content approval, editing,
forms and destination receipt, integrations and any specialist review. Arrange
test data and recipients before testing; use an agreed test environment for
payments or other actions that could create real transactions. A successful
page response and a completed customer journey are different observations.

Decide who approves release and who handles remaining issues. Record account
ownership, agreed source and content handover, licences, training and continuing
support. A launch checklist is separate from measured enquiries or revenue.

07. ADD YOUR COUNTRY AND DELIVERY CONTEXT

Choose the relevant market and include your actual locations, languages, time
zone, review owners and preferred quotation currency. These are briefing prompts,
rather than assertions about local law or a local studio office.

Canada: provinces served, French or other language scope and hosting requirements.
https://brandingtatva.com/contact?service=website-redesign&market=canada#write

Australia: states served, time zone, content approval and launch support window.
https://brandingtatva.com/contact?service=website-redesign&market=australia#write

UAE: emirates served, Arabic and English page scope and the language reviewer.
https://brandingtatva.com/contact?service=website-redesign&market=uae#write

UK: service scope, content approval and accessibility review responsibilities.
https://brandingtatva.com/contact?service=website-redesign&market=uk#write

USA: states served, time zones, integrations and the account handover owner.
https://brandingtatva.com/contact?service=website-redesign&market=usa#write

India: required languages, mobile enquiries and content and account owners.
https://brandingtatva.com/contact?service=website-redesign&market=india#write

08. PREPARE A SAFE ENQUIRY SUMMARY

Public URL:
The customer journey that needs to work:
Three observed gaps:
Accounts and source availability, as status only:
Country, time zone and review owner:
Preferred launch date and any fixed dependency:
Budget range and currency, shared privately:
Main question for the takeover review:

Bring this short summary rather than the complete private working record.
Branding Tatva delivers remotely from India. Suman Sharma leads strategy,
website messaging and client coordination. The written proposal identifies the
assigned team, review scope, feasibility decisions, implementation boundaries
and private commercial terms. Specialist assurance receives explicit scope.
A completed worksheet is preparation, rather than a project acceptance, legal
opinion, security assessment or promise of completion or search rankings.

Review the website service and its takeover answer:
https://brandingtatva.com/website-redesign

Choose another planning resource:
https://brandingtatva.com/resources#choose-a-resource

SOURCE NOTES

The questions and working structure are original Branding Tatva guidance.
The sources below support the specific search planning notes in section 05.
They establish neither approval of this worksheet nor a result for your project.
Reviewed 30 October 2026.

[1] Google Search Central: Site moves with URL changes.
https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

[2] Google Search Central: Block Search indexing with noindex.
https://developers.google.com/search/docs/crawling-indexing/block-indexing