Export formats need a stated use range
Aliases: portable format · re-editability · export types
What it is
Export writes content into a file that must still open after leaving this product: PDF, CSV, Markdown, a proprietary bundle. Picking a format is picking what will still be possible—view only, edit again, keep comments and permissions, open in other software. Stating the use range means writing those abilities and losses at the moment of choice, not a row of extensions. This is not which fields a share will show, and not whether the clipboard flashes “copied.”
Why it happens
Format names are expert labels. Most people hear PDF as “how it prints,” CSV as “opens in a grid,” and have no model for “comments drop out,” “formulas become values,” “only the first sheet.” Finding that out after the download means another export or hand repair. A statement moves the consequence to the choice: people are buying a capability, not tapping an icon. If every format says Recommended, the word dies. If the default is the most familiar and most lossy option (flat PDF), people treat it as a full backup. Export is also used for moves and compliance dumps; a vague range lets “I already exported” hide incomplete data.
Studying it
Give content with comments, multiple sheets, and permissions. Ask for “a backup I can still edit later” and “a copy for someone without an account.” See whether the chosen format matches the job.
Independent variables: whether each format states re-editable / read-only / what is dropped, which format is default, whether the filename encodes the format’s meaning. Dependent variables: task–format mismatch, when missing fields are noticed (now versus after leaving the product), re-export count.
A lab that writes full sentences beside formats is not comparable to a product that shows .pdf. Ask “did you think comments were in the file,” not only satisfaction. Long waits on large files cause early leave; split “never finished” from “wrong format.”
Where it stops holding
A single-format product has no choice; hang one sentence on the button: “downloads a read-only copy, comments not included.” A legally required invoice layout cannot be altered for editability. If license forbids redistributing some objects, hide export or switch it to “this device only,” rather than apologizing after the file exists. A proprietary dump for migration must say it opens only in a like product, or it will be filed as a universal backup.
Applying it
- One ability plus one loss per format: “PDF: fixed layout, not editable, no comments.” “CSV: grid stays editable, no images or permissions.”
- Default by task: backup favors a re-editable bundle, outbound delivery favors a read-only layout. Do not default everything to PDF.
- After completion, echo what was actually written (pages, rows, comments included or not) so gaps are visible now.
- Verify: run “keep a copy I can still change” and “send to someone with no account.” Compare chosen format with what opens afterward. A PDF that prompts “but I still need to edit” means the range was not stated.