Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.doc-reviewer.site/llms.txt

Use this file to discover all available pages before exploring further.

After running an evaluation, you can export the results to an Excel file (.xlsx). The export gives you a structured spreadsheet that is easy to share with your team, track in a task manager, or attach to a QA report.

Export results

1

Complete an evaluation

Make sure at least one instruction section in the document has been evaluated. The export option is only available when evaluation results exist.
2

Click Export on the document page

Open the document in the Evaluation page. Click the Export button in the document header. The browser downloads the file immediately — no dialog is shown.
3

Open the downloaded file

The file is saved with the document filename as the base name, for example installation-guide_review.xlsx. Open it in Excel, LibreOffice Calc, or any compatible spreadsheet application.

What the XLS file contains

The exported file has one sheet named Evaluation results. The first row is a header with a blue background. Each subsequent row represents one evaluated instruction section.
ColumnContents
SectionThe instruction section title as it appears in the document tree
PageThe page number in the source document (blank for web-based documents)
RatingThe color rating as a label: Good, Notes, Problems, or Critical
RecommendationsAll LLM recommendations for this section, each prefixed with the criterion name and optionally an example
The Rating column uses cell background colors that match the in-app color scale: green, yellow, orange, or red.
The export includes only sections that have evaluation results. Sections classified as non-instruction, sections toggled off for evaluation, and sections that were skipped due to errors are not included.

Use cases

  • Share results with the team — send the XLS to editors, PMs, or QA engineers who do not have Doc Reviewer installed.
  • Track issues in a task tracker — copy rows from the spreadsheet into your bug tracker or project board to create writing tasks.
  • Include in QA reports — attach the file to a release checklist or documentation audit report as evidence of evaluation coverage.
If you want to compare results across document versions in a spreadsheet, export after each evaluation run and keep the files alongside each other. For in-app version comparison, use snapshots instead — they give you a structured diff view without manual file management.