What to use when

Tiro Pro has several ways to put AI to work on your documents, and the right one depends on the job in front of you. This page starts from the job. Each entry names the feature that fits, what it takes in and gives back, and when it is the wrong choice. If you are still unsure, ask the agent in a discussion: describe what you are trying to do and it will suggest where to start.

Start from the job

Ask questions about a document, or a set of documents

Use a discussion. Attach the documents you want the agent to consult, ask in your own words, and carry on from the answer; the agent remembers the earlier turns. A discussion is private to you and is kept for as long as you want it. See About discussions and Use discussions.

It is the wrong choice when you want the same questions answered the same way across many documents, or by the whole team. Write the questions down instead, as an extraction schema or a dynamic workflow.

Draft or change a Word document

Use a discussion. Attach the Word document and ask for the change; the agent drafts it as tracked changes in the Drafts panel, and nothing in your library changes until you save the draft as the document's newest version. The agent can also write a new Word document from scratch. See About discussions.

It is the wrong choice for a document your team produces again and again from the same set of questions. That is a template.

Check a contract against your team's standard positions

Use a contract review. Point it at a contract and one of your team's playbooks — its library of standard positions, one issue at a time — and it returns a deviation table, an issue analysis, and a marked-up Word document for you to edit and approve. Choose Analysis only when you want the findings without the drafting. See About contract review and Start a contract review.

It needs a playbook. If your team has not written down its positions yet, start with Manage playbooks.

Pull the same facts out of many documents

Use an extraction. An extraction schema is a reusable list of the pieces of information you want from a contract — a notice period, an annual rent, the parties — and a run returns an answer for each item, linked to the clause it came from, in a table you read in Activity. You can write the schema by hand or have an agent draft it from a description or from example documents. See About extractions and Your first extraction.

It is the wrong choice when what you want back is prose analysis rather than a set of fields. That is a dynamic workflow.

Do a job of your own, in your own words, again and again

Use a dynamic workflow. You describe the job once, in plain English — what to read, what to check, what the answer should cover — and run it against any documents whenever you need it. Runs happen in the background and their output arrives in Activity. See About dynamic workflows and Build a dynamic workflow.

It is the wrong choice for a one-off question, which a discussion answers on the spot, and for a fixed list of facts, which an extraction returns in a table.

Produce a document from a set of answers

Use a template. A template carries its own questionnaire; you answer the questions and Tiro Pro assembles the finished Word document from your answers, with a live preview beside the form. One template can produce several documents from one set of answers. See About templates and Generate a document from a template.

Prepare a board record

Use flying minutes. Choose the source documents that need board approval and your team's board-record template; Tiro Pro drafts the narrative, key details, and resolutions for each matter, and you review and edit them beside a live preview before generating the record. See About flying minutes and Run a flying minutes session.

Understand how a set of documents fits together

File the documents into a matter: a collection you have declared to mean "these documents belong to one evolving story". Tiro Pro then works out what each document is, how the documents relate, and what the set amounts to, and keeps that current as the matter changes. The results show in the documents table, the details panel, and the Document navigator, and the agent in a discussion can draw on them. See About contextualisation and Contextualise documents.

Have it happen without anyone starting it

Use a policy: a standing rule over your team's documents — for every document matching the rule, do this — that puts an agent to work, or makes a mechanical change, whenever a document matches. Policies are still in development and not yet available; see About policies for how they will work.

Common combinations

The features are designed to be used together. These are the sequences teams reach for most often.

A matter, then a discussion. File a deal's documents into a matter and let contextualisation link them (Contextualise documents). Then select them on the Documents page and choose Send to discussion (Work with the documents table): the agent starts with the documents attached and can look up how they relate as it answers.

A review, then the key terms. Start a contract review of the new draft against your playbook (Start a contract review), and run your key-terms extraction schema against the same document (Extract information from contracts). Both run in the background; the review appears on its dashboard and the extraction's results in Activity.

The documents table, then a workflow. Select documents on the Documents page and choose Send to workflow to run a dynamic workflow or an extraction schema on the selection, together or one run per document (Work with the documents table).

A discussion that runs a workflow. In a discussion, ask the agent to find and run one of your team's saved dynamic workflows or extraction schemas. It proposes which documents to use and starts the work in the background; the results appear in Activity and you can discuss them in the same thread (About discussions).

A template, then flying minutes. A flying minutes session lays its drafting into your team's board-record template, so the record comes out in your format (About flying minutes).

A workflow, then a policy. Once policies are available, a workflow you have built can be dispatched by a standing rule whenever a matching document arrives (About policies).

Ask the agent

If you are not sure which of these fits, open a discussion, or Quick Chat from any page, and describe what you are trying to do. The agent knows this documentation and can suggest where to start, explain how to set the feature up, and walk you through the steps one at a time. It describes the app but does not operate it for you: it will tell you which page to open and which control to select, and you take it from there. See Use discussions.

If the job you describe is one for dynamic workflows, the agent can also write them: on the Workflows page, under Dynamic, choose Create with AI and describe the job there. See Create workflows with the agent.