Turn a long document into traceable facts, risks, and actions

A useful analysis begins by defining what the reader must decide and what output is needed. This guide turns a supplied document into an actionable summary, with locatable citations and a clear separation between facts, risks, and inferences.

When to use it and when not to

Use it for proposals, internal policies, reports, manuals, meeting minutes, or drafts that you can provide to the assistant. Do not use it to conceal obligations, replace professional review, or make your own decisions about contracts, tax, employment, health, or regulated compliance. Contracts and regulated decisions require qualified review. Consider a business audit only when analysis is recurring, shared by a team, involves meaningful volume or spend, contains sensitive data, or removes a material bottleneck. Otherwise, reuse this guide or the general Quest assistant.

Input and output worksheet

Define the input first:

• Input objective: what question must the analysis answer? __________________
• Document and version: ______________________________
• Audience and expected decision: ____________________
• Priority sections: _________________________________
• Data that must be redacted: ________________________

Define the output:

• Executive summary in 3 to 5 points.
• Facts with page or section citations.
• Risks, severity, and possible impact.
• Internal or cross-document contradictions.
• Inferences, always labeled.
• Open questions and missing data.
• Actions, owner, and suggested date.

Workflow

1. Confirm authorization to process the document and remove unnecessary data.
2. Identify version, date, language, pages, and included appendices.
3. Formulate an analysis question answerable from the supplied content.
4. Ask for an initial outline of sections, definitions, obligations, figures, and exceptions.
5. Extract facts literally and add the page, section, or paragraph.
6. Search for conditions, deadlines, renewals, dependencies, exclusions, and ambiguous metrics.
7. Compare definitions, figures, and obligations to detect contradictions.
8. Separate explicit risks from inferences. Explain the reasoning for each inference.
9. Turn open questions into specific information or review requests.
10. Draft prioritized actions and validate the result against the original document.
11. Flag everything requiring legal, regulatory, technical, or financial review.

Short before and after example

Before, a supplier note says: “The service renews automatically and may be canceled with prior notice.” It is ambiguous because duration, notice period, and channel are missing.

After, the analysis records: “Fact: automatic renewal; source: section 4, page 2. Fact: cancellation with prior notice is available; period and channel are not stated. Risk: unwanted renewal, medium severity. Open question: confirm notice days and cutoff date. Action: request written clarification before signing.” No legal conclusion is presented.

Copyable final artifact: redacted risk map

# Document risk map

Document and version:
Analysis date:
Objective:
Scope and pages reviewed:

## Executive summary
1.
2.
3.

## Cited facts
- [Fact] | page/section: | quote or data:
- [Fact] | page/section: | quote or data:

## Risks
| Risk | Evidence and location | Severity | Possible impact | Proposed control | Owner |
|---|---|---|---|---|---|
| | | low/medium/high | | | |

## Contradictions
- [Conflicting elements] | locations: | clarification needed:

## Inferences
- [Inference] | supporting facts: | confidence:

## Open questions
- [Question] | information required | owner | date:

## Actions
- [Action] | priority | owner | suggested date

## Qualified review needed
[legal, regulatory, technical, financial, or other]

Failure and safety checks

Work from a copy and retain the original. Verify that citations point to the correct page or section, including appendices. Do not invent text when a PDF is scanned or incomplete: mark extraction as uncertain and request a legible copy. Check that tables have not lost columns, dates retain their format, and “must,” “may,” and “should” are not swapped. Redact names, identifiers, account details, signatures, and personal data before sharing the map. If versions differ, analyze them separately and record which one is current. A summary does not prove compliance or remove the need for professional review.

As a restrained next step, give the map to the responsible person and reuse the template for the next document. Request a business audit only when repetition, collaboration, significant volume or spend, sensitive data, or a material blockage is present.