# Pascal Documents

Source: https://www.trypascal.io/platform/documents

Every finding, a path back to the source.

Turn documents into facts your team can check. Keep extracted fields and findings linked to the original page, passage, and version.

## Capabilities

### Organize a governed corpus

Bring files into a shared collection with their source, scope, and access requirements. Keep new versions connected to the original document.

### Work with real document structure

Process native and scanned material while retaining pages, sections, tables, figures, and the structure needed to interpret a finding.

### Extract facts with citations

Turn a clause, value, or table into a structured finding that points back to the source page and passage.

### Compare extraction approaches

Try a bounded sample with different strategies or providers. Review result quality before processing a larger collection.

### Make uncertainty reviewable

Keep ambiguous fields and conflicting findings available for human review. Preserve corrections with the evidence behind them.

### Put findings into business work

Use extracted evidence in research, business records, and workflows without stripping away the citations that make it inspectable.

## Connected context

Bring document evidence into business records, agent Tasks, and Dynamic Context packages. Give reviewers in Workrooms the source passage behind a finding or proposed change.

- Source documents, pages, versions, and document sets
- Extracted fields, tables, passages, and citations
- Processing runs, reviews, corrections, and evaluations

## Controls and permissions

An extracted statement still needs the review required by the work. Keep the source version and any corrections attached to the finding. Publishing a finding does not approve an operating change based on it.

## Example

A new bulletin changes the requirements for lithium shipments. Documents keeps the source text beside the finding so Operations and Compliance can check the wording, resolve the outstanding question, and use the accepted evidence in their operating review.

## Workflow

### Read the requirement at its source

- The port bulletin requires current telemetry and shipment-specific Compliance approval before tendering a lithium load.

### Inspect the outstanding finding

- A separate publication-timing finding still needs review. The team can distinguish the extracted statement from an accepted operating change.

### Keep the passage beside the review

- Return to the exact wording and document version. The reviewer has the source needed to judge the finding; no review is submitted in this walkthrough.

## Next steps

Choose a document-heavy process and the findings your team needs to verify. Start with the original files and a clear review responsibility.

- [Contact sales](https://www.trypascal.io/contact)
- [Pascal Work](https://www.trypascal.io/solutions/pascal-work)