Portability

Portability

Portability is the ability for evidence to remain useful outside one platform, vendor, account, device, repository, storage location, or internal system.

A record may be available today but trapped tomorrow. Access can change. Export formats can change. Accounts can close. Platforms can remove data. Vendors can fail. Systems can be migrated. Devices can be lost. Internal tools can be retired. Permissions can expire.

The purpose of this guide is to help users preserve evidence so it can still be understood, recovered, and checked when the original environment is no longer available or no longer trusted.

Quick Read

• Portability helps evidence survive outside the system where it was created or stored.
• Strong portability keeps source material, context, identifiers, receipts, exports, and verification routes connected.
• Portability does not automatically prove truth, ownership, authorship, legality, originality, or independent verification.

What this means

Portability is the independence of an evidence record from a single environment.

It does not mean every record must be public or moved everywhere. It means important evidence should not depend entirely on one account, platform, device, vendor, application, or internal system.

For a creator, portability may mean keeping original project files, exports, drafts, publication records, and evidence notes outside a single creative platform. For a business, it may mean preserving decisions, approvals, contracts, logs, receipts, and supporting documents outside one SaaS account. For a researcher, it may mean keeping datasets, analysis notes, permissions, and contribution records in durable formats. For an organisation, it may mean making sure evidence can survive migrations, staff changes, supplier changes, platform failures, and retention changes.

Portability answers a practical question:

Can the evidence still be used if the original system is gone, inaccessible, disputed, or no longer enough?

Why it matters

Many digital records are platform-dependent.

A platform may show an upload date, but not export the full history. A cloud service may hold files, but not preserve context. A messaging app may contain approvals, but not reliably export attachments. A design tool may hold version history, but not keep it forever. A repository may show changes, but access may depend on one account. A social platform may show publication, but not creation. An internal tool may hold logs, but those logs may rotate or vanish.

This creates captive evidence risk.

Evidence becomes weak when the only meaningful proof sits inside a system controlled by someone else or by a system that may not be available later.

Portability reduces this risk by keeping evidence usable beyond the environment that created it.

What strong portability should include

A stronger portability position usually includes:

• The portable evidence material — source files, exports, records, datasets, messages, receipts, approvals, logs, or supporting documents.
• The original environment — the platform, account, device, vendor, application, workspace, repository, or system where the record was created or stored.
• Exportable copies — usable copies or exports in formats likely to remain accessible.
• Source preservation — original files or source materials kept where possible.
• Context preservation — notes explaining what the record is, where it came from, and what it supports.
• Identifier preservation — filenames, hashes, IDs, timestamps, receipt references, URLs, account names, version numbers, or repository references.
• Custody context — how portable copies were created, stored, and protected.
• Verification route — how the record can be checked outside the original environment.
• Recovery route — how the evidence can be found later.
• Privacy controls — what should be restricted when evidence is exported or shared.
• Claim boundaries — what the portable evidence supports and what it does not support.

Portability should preserve meaning, not just files.

Common weak points

Portability is usually weak when:

• evidence exists only inside one platform
• records cannot be exported clearly
• exports lose metadata, attachments, comments, version history, or timestamps
• screenshots are used instead of source records
• evidence depends on one account owner
• files are kept only in a device folder with no context
• platform URLs are saved without preserving the underlying material
• version history is assumed to remain available forever
• receipts are not stored with the related source material
• internal logs are not exported before expiry
• migrated systems lose old context
• private material is exported without access controls
• the portable copy cannot be verified later
• the claim relies on information left behind in the original system

These weaknesses often appear only when access is lost.

How to apply this yourself

For each important record, create a portability note.

Ask:

• Where does this evidence currently live?
• What system, platform, device, account, vendor, or repository controls it?
• What would happen if access disappeared?
• Can the source material be exported or preserved?
• What metadata, timestamps, comments, approvals, versions, or attachments might be lost during export?
• What context must travel with the record?
• What identifiers should be preserved?
• Where will portable copies be stored?
• Who is responsible for keeping them recoverable?
• How can the portable evidence be checked later?
• What private material must be protected?
• What does the portable evidence not prove?

Then preserve the source material, export, evidence note, and related identifiers together.

Do not assume that a platform record will remain available, complete, or accepted later.

What this does not prove

Portability does not automatically prove:

• ownership
• authorship
• copyright
• permission
• legality
• originality
• authenticity
• accuracy
• completeness
• absence of alteration
• absence of dispute
• that an export is complete
• that the evidence has been independently verified
• that EviWrite has preserved, verified, or backed the record

Portability helps evidence remain usable beyond one environment. It does not decide what the evidence proves.

Framework-aligned claim boundary

A person or organisation may use this guide as part of EviWrite Framework alignment if they apply the guidance honestly and avoid implying EviWrite involvement.

Acceptable wording may include:

“We use the EviWrite Framework to improve evidence portability for important records.”

It must not be used to imply:

• EviWrite has exported or preserved the evidence
• EviWrite has verified the portable record
• EviWrite has approved the portability process
• the record is EviWrite-backed
• the record is EviWrite-certified
• the record carries the controlled ⓔ mark
• EviWrite has endorsed the organisation’s evidence portability controls

Framework-aligned means public guidance was followed.

EviWrite-backed means the record was created through EviWrite or an authorised evidencing channel.

Related checklist

Use the Portability Checklist to check whether source materials, exports, identifiers, context, receipts, storage locations, recovery routes, and verification routes remain usable outside one platform or system.