Prevent spreadsheet formulas from executing in research exports — what should the operator record?
A source title or excerpt may begin with characters a spreadsheet interprets as a formula. Opening a research export should not execute that text. Treat source strings as untrusted data and validate the receiving application's actual import behavior, keeping any protective representation separate from the original returned value.
Use a tested export representation for untrusted text without altering the source quotation.
Mark title, excerpt and other externally supplied strings as data fields, including cells whose first nonspace character may trigger formula interpretation. Leading whitespace can affect interpretation in some import paths, so include it in fixtures instead of checking only the first literal character of the raw string.
Name the application and import path checked, withholding unsupported formats rather than promising that one escaping convention is safe in every spreadsheet. A compatibility note should identify tested application behavior without making a universal guarantee across versions, locale settings and import methods that were not exercised.Identify text boundaries
Mark title, excerpt and other externally supplied strings as data fields, including cells whose first nonspace character may trigger formula interpretation. Leading whitespace can affect interpretation in some import paths, so include it in fixtures instead of checking only the first literal character of the raw string.
Choose an approved representation
Use the team's tested text-import or escaping convention for the target application; ordinary CSV quoting alone must not be assumed to prevent formula evaluation. Document whether protection occurs during import or in a derived export field; protective changes must not be quoted downstream as though they were original publisher text.
Build harmless fixtures
Test benign strings beginning with equals, plus, minus and at-sign characters without using network calls, commands or sensitive content. A harmless fixture such as a simple arithmetic-looking string can test interpretation without triggering network access or invoking external programs during the review.
Check round-trip meaning
Confirm the protected representation is not executed and that reviewers can distinguish its protective prefix from the actual source text. If the receiving application strips protective markers on reexport, that downstream artifact needs another check rather than inheriting the first file's safety assessment.
Record compatibility limits
Name the application and import path checked, withholding unsupported formats rather than promising that one escaping convention is safe in every spreadsheet. A compatibility note should identify tested application behavior without making a universal guarantee across versions, locale settings and import methods that were not exercised.
Keep the boundaries clear.
- Use a tested export representation for untrusted text without altering the source quotation.
- Operational record: Identify text boundaries. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.