TrmTrk Docs

Appearance

Features/Exporting Results

Exporting Results ​

Analysis is only useful if you can hand it off. The Export button on the Analysis Matrix produces a file that mirrors the matrix you see — same rows, same active columns, same values, overrides and all.

Two Formats, Same Content ​

Pick either from the Export dropdown:

  • CSV — universal, smaller, plaintext.
  • XLSX — column widths and light formatting preserved, opens natively in Excel.

Content is identical across the two. The choice is about what the downstream reader needs.

What Each Row Contains ​

One row per contract in the project. Each row carries:

  • The extracted value for every active template field (one column each)
  • Document type — MSA, SOW, Lease, Amendment, etc.
  • Upload date
  • Analysis status — complete, error, analyzing
  • Override flag — per-field indicator distinguishing AI-extracted from human-modified values

The override flag is the important one. Downstream spreadsheets and pipelines can filter to "only rows a human touched" or "only rows still on the AI's original extraction" — the audit trail survives the export.

When to Export ​

The typical workflow:

  1. Upload the full contract stack.
  2. Run analysis.
  3. Filter the matrix to amber-flagged cells and work the review queue.
  4. Override or validate as you go.
  5. Export.

The export is the handoff artifact — the thing that goes to the deal memo, the counterparty workspace, the VDR index, or the partner reviewing the diligence output.

Where Exports Live ​

The file downloads to your machine immediately. It's also persisted in the project — every past export is listed on the Project Overview, with timestamp and the user who ran it.

That means you can re-download an older snapshot without re-running anything, and you can diff yesterday's CSV against today's to see exactly what changed between review passes.

XLSX vs CSV ​

  • Pick CSV if the file is feeding a pipeline, a Python notebook, a BI tool, or a model. Fewer surprises, no format quirks.
  • Pick XLSX if a human is going to open it and work with it. Column widths stay readable, headers stay distinct from data.

If in doubt, XLSX — it's the default for a reason.

TIP

Export after every major review pass. Exports are project snapshots — easy to diff later if you want to see what changed between runs, and a useful checkpoint to share with a teammate mid-review without granting them project access.

→ For more detail, see The Analysis Matrix. → For more detail, see Running AI Analysis.