LFW

Capabilities · Records & continuity

A website another person can pick up and run.

Keep the content, decisions, accounts, and operating record understandable to your next colleague or vendor. Agree the handover while the working relationship is beginning.

LFWHandover packageInteractive sample
START-HERE.md
# Website handover

Sample organization: Meridian Parks Alliance
Status: illustrative package

## Contents
01-accounts.csv    Account ownership
02-url-map.csv     Content destinations
03-operations.md   Operating checklist

## Recipient checks
[ ] Open each file
[ ] Confirm account access
[ ] Find the backup provider
[ ] Review unresolved work

Keep a copy in an organization-owned account.
No credentials are included in this sample.
Your accounts
Named, delegated access
Open formats
Agree available exports
Written handover
Check it with the recipient

Your agreement defines ownership and handover. The inventory and formats follow the systems and services in your engagement.

Engagement details

Three records with different jobs.

What to keep

The work record

Requests, correspondence, reports, and decisions show what changed and why. Agree the available exports and who in your organization can retrieve them.

The public-page archive

Looking Glass captures selected public pages on a regular cadence. It helps answer what a captured page showed at a recorded time. It does not include every page or every date.

The recovery backup

The managed host’s backup is used for restoration. Public-page captures do not contain the complete database, draft content, configuration, or credentials needed to restore a site.

Your retention requirements

Set any required retention period and capture coverage in writing. Archive data may be pruned under the service schedule; there is no guaranteed minimum retention unless your Order Form states one.

Agree the responsibilities before the last day.

  1. At the start

    Put accounts in the right hands

    Keep domain, hosting, and vendor accounts under organizational ownership. Delegate named access and identify an authorized person who can approve changes.

  2. During work

    Maintain the operating record

    Keep requests, reports, code changes, and system notes current. Confirm export formats and access before an urgent transfer makes them necessary.

  3. At handover

    Check the package together

    Reconcile the agreed inventory with the recipient. Confirm access, note any platform or license restrictions, and list open work and the next responsible person.

Read the published handover terms

Acceptance check: the recipient can open the files, obtain the agreed access, and locate the documented recovery procedure. Record unresolved transfers explicitly.

Read the published handover terms

Make continuity part of the engagement.

Bring your current systems and recordkeeping needs. We will identify what can be exported, what requires vendor access, and what belongs in the agreement.

Prefer to write?

Tell us what needs to work better.

Slow, fragile, hard to edit, missing a workflow. Say it plainly, and you'll get a straight answer, not a ticket number.