ODT forensics

OpenDocument Text — .odt — is the LibreOffice / OpenOffice native format and the OOXML's open-standards alternative. Structurally similar to DOCX: a ZIP archive with content.xml, styles.xml, meta.xml, and supporting parts.

LibreOffice/OpenOffice are common authoring tools for students who don't have access to a paid Word license, plus institutions that adopt FOSS toolchains by default.

Signals available on ODT

Metadata — meta.xml contains Creator, InitialCreator, Created, ModificationDate, EditingDuration, EditingCycles (LibreOffice's name for revision count). The field set is close to DOCX-equivalent.
Edit history — tracked changes ("recorded changes" in LibreOffice terminology), comments, hidden text. Same forensics-relevant residue as DOCX.
Paste detection — formatting-run inventory, language-tag flips, edit-time vs. word-count ratio.
Font / encoding — full font fallback chains. LibreOffice tends to write longer fallback chains than Word, so the default fallback inventory looks different.
AI signals — every linguistic detector runs.
Structural — ZIP-entry sequence is distinctive (LibreOffice writes parts in a different order than Word writes its DOCX). Cross-format conversion fingerprints surface here.

Common false-positive paths

DOCX-saved-as-ODT or ODT-saved-as-DOCX workflows leave conversion fingerprints that look unusual against the format-claimed editor.
LibreOffice fallback chains can trip the font-encoding detector if it's been calibrated only against Word output — Autotend Forensics calibrates against both, but be aware.

What's distinctive about ODT review

ODT carries most of the same authorship signals as DOCX, sometimes more (LibreOffice records a few fields Word doesn't, like EditingCycles vs. Revision). The reviewing patterns are the same; the field names differ.

If a student submits ODT when DOCX was an option, that's not itself suspicious — it usually just means they're a LibreOffice user.

What to expect

A typical authored ODT scan surfaces a similar volume of signals to the equivalent DOCX. Pair the inspector view (which shows both DOCX and ODT field names with cross-reference) with the document scorecard.