Document transfer

How it works

Editable documents carry change history and comments. A PDF export freezes them. Say which you are sending. Macro-enabled files trip mail filters. The transfer is ordinary binary. The business check is version: the filename date must match the bytes you hashed.

A 4 MB contract in DOCX goes by mail. The client's policy strips macros and the file still opens. A 35 MB scan bundle bounces. They switch to a link. Track-changes in the DOCX are still on. The client reads internal notes. A PDF export would have avoided that. The transfer was not the leak. The format choice was.

How it differs

Document transfer is not document collaboration. A shared editor keeps one live object. A transfer hands off a copy.

Auto-save names like Contract-final-v7-final collide. Put the hash or a timestamp in the delivery note.

Cloud links that require the recipient to have the same suite are a share, not a transfer, until they download.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For document transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive document transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.