Import never saves a playbook on its own.
It produces a preview you can edit, drop rows from, and then save through the normal create flow.
Start an import
From the new-playbook page, choose Import from a document.1
Set the contract type
Leave it on Auto-detect from document and Vaquill infers the type from the text, or pick one explicitly if you already know.
2
Give it the contract
Upload file takes Word and PDF files.
Paste text takes the body of a contract pasted directly, which is useful when you only have a fragment or an email attachment you cannot download.
3
Extract
One file or pasted text runs a single extraction.
Two or more files run extraction on each and then consolidate them into one consensus playbook.
The same button does both; the file count decides the mode.
4
Review the preview
Every recognized clause appears as an editable row: preferred position, acceptable range, escalation triggers, and rationale.
Uncheck any row you do not want. Fix anything that reads wrong.
5
Name it and save
The preview seeds the normal playbook form. Add a name, confirm the contract type, and create.
One contract, or many
- A single contract
- Several contracts at once
Best when you have one agreement that genuinely represents your house position, for example the template your team actually sends.Each clause block is classified and summarized into a preferred position, an acceptable range, escalation triggers, a rationale, and, where the clause has typed constraints, the numbers themselves: cap, cure period, payment days, and so on.Repeated clause types are merged rather than duplicated.
What it accepts
Resume a recent import
The new-playbook page lists your recent extractions. Resume reopens one of them in the preview stage, so an interrupted session does not mean re-uploading and re-running the extraction.After the import
An imported playbook is a first draft assembled by a model from your own paper. Two things are worth doing before you rely on it.- Run the structure check. Imports typically arrive with language and no governance, so the score starts low and the findings tell you exactly what is missing.
- Add fallback ladders and sign-off levels to the clauses you actually negotiate. Extraction infers what your contracts say, not how far you were willing to move or who had to approve it.
Limitations
- Clause detection relies on document structure: numbered headings, all-caps headings, or a bold first line. A contract with unusual formatting produces fewer, coarser blocks.
- Very large contracts are analyzed up to a cap. When that happens you get a warning that the analysis was partial, and any missing clauses have to be added by hand.
- Clause classification is model-judged. Near-miss labels are folded onto the standard clause type, and clause types outside the standard vocabulary are kept only up to a small number per document.
- Consolidation across several contracts is model-judged too. Confidence is a coarse measure of how many source files agreed on a clause, not a similarity score on the text.
- Extraction reads the final language of a contract. It does not learn from tracked changes, so it tells you where you landed, not what you pushed for.
- Positions arrive without fallback ladders, walk-away floors, approval levels, or conditional rules. Those are yours to add.
- Nothing is verified against law. An imported position reflects what your contract said, including any mistakes in it.
Related
Building a Playbook
Edit and extend the imported result.
Structure Check
See exactly what an import is missing.
Starter Templates
Start from a curated playbook instead, then import selectively.
Supported File Formats
What Vaquill can read across the product.