Website handoff planner

What does the client need to control after website handoff?

Separate permission to edit, receipt of a site and a working copy. Start with what you already have and the limited arrangement the client actually wants.

Status choices stay in this tab’s page history for Back navigation. No names, domains, keys, documents or account details are requested or sent. This planner does not operate an account or perform a transfer.

Share editing while the current owner keeps the site
Delegated editing under an agreed continuing arrangement. Does not mean site receipt, control of the builder account, domain ownership or independent subscription services.
Receive the site in the client's own Carrd account
Carrd site-transfer workflow to an existing or separately created recipient account. The entire sender account, login credentials, domain registration and legal rights are not transferred by this definition.
Use an independently hosted copy
Plan a separately operated working site and its dependencies. Source files or a WordPress content export alone do not establish this outcome.

Your reported scope and checks

Which site are you planning for?

What must the client control?

undefined

Has the current owner confirmed sharing access for this job?

Has the sender confirmed access to Carrd site transfer?

Are the actual site permissions sufficient for this job?

Is the recipient account active?

Have the exact site features been confirmed for the recipient?

Is a receiving site slot available?

What has happened with shared editing access?

What has happened with the site-transfer request?

Has the client agreed to this control model?

What plugin-service arrangement has been checked?

Has a representative check worked for this scope?

What kind of copy has been prepared?

Is a custom domain in scope?

Must the platform contact form keep working?

Must another form keep working?

Are paid WordPress plugins in scope?

Site access

A not-needed answer requires a valid reason and not-applicable owner/check. Site access is required for every selected job; no paid plugins does not remove hosting or core-update responsibilities.

Is this required for the agreed scope?Who is the operational owner?What is the reported check result?If not needed, why?

Domain and DNS

A not-needed answer requires a valid reason and not-applicable owner/check. Site access is required for every selected job; no paid plugins does not remove hosting or core-update responsibilities.

Is this required for the agreed scope?Who is the operational owner?What is the reported check result?If not needed, why?

Form delivery

A not-needed answer requires a valid reason and not-applicable owner/check. Site access is required for every selected job; no paid plugins does not remove hosting or core-update responsibilities.

Is this required for the agreed scope?Who is the operational owner?What is the reported check result?If not needed, why?

Renewals and updates

A not-needed answer requires a valid reason and not-applicable owner/check. Site access is required for every selected job; no paid plugins does not remove hosting or core-update responsibilities.

Is this required for the agreed scope?Who is the operational owner?What is the reported check result?If not needed, why?

First choose the control the client needs

Unknown is useful. Name the goal before comparing product requirements. A login, a download and reported acceptance answer different questions.

Choose the platform and the limited control needed.
Name the operational owner and the evidence for each relevant dependency.
Keep an adequate existing or managed arrangement when it meets the job.

Four fictional worked decisions

A shared editor is not receipt of a site

A client wants to edit text while the existing owner continues operating a Carrd site. Ask whether permitted sharing is adequate and have the client check access. Do not select a recipient upgrade merely for editing. Receiving the site in the client’s own account is a different goal: account activity, needed features, a free site slot and recipient acceptance are separate checks.

Pending is still waiting

Suppose the sender and recipient report suitable accounts, features and a free slot. A pending site-transfer request is still waiting. Reported acceptance still needs acknowledgement and a relevant functional check. This planner does not send, accept or complete the request.

A downloaded file is not a working form

A client requires a contact form in a separately hosted copy. A source ZIP alone does not confirm inquiry delivery. Check a representative inquiry; a failed required function takes priority over a positive account or copy status. If no form is needed, explicitly change the agreed scope and recheck the remaining dependencies. Keep a working existing site where adequate.

A WordPress role and a subkey leave other dependencies

A client reports administration access and an appropriate domain-subkey arrangement, but nobody has confirmed renewal responsibility. Keep that question open. A content export alone is not a configured working site, and a subkey does not establish independent subscription ownership or future services. No primary key is requested.

These are buyer-reported checks for final confirmation, not a completed transfer, ownership certificate, legal-rights finding, compatibility test or security guarantee.

Use the existing Carrd website guide, Crocoblock guide or website and database recovery guide for the next relevant check. No new purchase is established by this planner.

Documentation observed and what remains unconfirmed

Public documentation observed November 2, 2026; not a hands-on site, account or product test. Current scope-specific product requirements remain unconfirmed in this planner. Site receipt does not transfer an entire sender account, domain registration, contractual rights or every external service. A configured WordPress role or reported domain subkey does not establish independent subscription control.