Continuity schedule

What this worksheet records

A continuity schedule plans how permitted work remains usable when a relationship, account or service changes. Identify each accepted obligation and its actual provider, then list the records, artwork and other inputs needed to continue it. Ownership, access and transfer permission are different questions; do not assume that possessing a copy means it can be redistributed. Keep the source versions and authorised contact route beside the obligation rather than depending on a departing person's informal memory.

Complete and review it

Review the schedule before an agency, supplier or software relationship ends. Test whether permitted exports are complete and usable, and identify dependencies that still need an agreed handover. Access revocation should prevent unauthorised future retrieval while preserving the records needed for legitimate continuing fulfilment. An expired licence or account must be interpreted under its actual terms; obtain appropriate advice instead of assuming expiry automatically cancels an accepted contract or authorises new work. Record the resulting decision and any remaining limitation.

Field definitions

• continuity_id: A stable identifier for this continuity, used to connect related rows without merging unrelated records.
• relationship_reference: The actual attributable source for relationship reference; a reference is not evidence that a decision was authenticated or its content verified.
• accepted_obligation: The specific accepted duty and responsible party retained under the actual agreement.
• provider_legal_entity: The actual party for provider legal entity, with its responsibility or rights source identified; do not substitute the platform brand.
• permitted_record_owner: The named person or agreed role responsible for permitted record owner; confirm its real scope rather than assuming authority from a typed name.
• required_asset_or_file: The actual required asset or file relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• source_version: The exact source version used for this row; retain earlier versions and revisit affected decisions after a change.
• access_end_date: The actual access end date, with date format or period meaning explicit; distinguish requested, planned, confirmed and observed values.
• transfer_permission: The actual permission to transfer the specified records or files, separate from possessing a copy.
• continuing_contact: The actual continuing contact relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• backup_reference: The actual attributable source for backup reference; a reference is not evidence that a decision was authenticated or its content verified.
• tested_action: The actual tested action relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• unresolved_dependency: The specific unanswered unresolved dependency that needs an owned response before the relevant next gate can close.
• decision_owner: The named person or agreed role responsible for decision owner; confirm its real scope rather than assuming authority from a typed name.

Prepare a deliberate export

Continuity records can reveal contracts, permissions and recovery locations. Share only the authorised transition package, excluding credentials and unrelated clients. The worksheet does not transfer legal obligations or guarantee that another provider will accept the work.

Take it to the next job

• Separate data ownership, access permission and continuing obligations.
• Test the permitted handover before ending the relationship.
• Keep unresolved transfer and licence terms for attributable review.