About policies

A policy is a standing rule over your team's documents: "for every document matching X, do Y". You write it once and Tiro Pro applies it from then on, so the work happens without anyone having to start it. Policies sit at the top of the Agents page, in a table the whole team can see, with an owner recorded against each rule.

Two kinds of rule

The two kinds differ in what they do and in how quickly they do it.

An agent policy puts an AI agent to work on the documents the rule applies to. You either describe the job in plain English — extract the execution date and the parties, then summarise the term clauses — or point the rule at an eligible workflow your team has already built. The work runs in the background and produces output you read afterwards.

An automation makes a mechanical change the instant a matching change happens: adding a document to a collection, for example. There is nothing to read and nothing to wait for.

The rule of thumb: an agent policy for work that needs considering, an automation for work that just needs doing. AI work is slow and worth queueing; a change of collection is not.

Both say which documents they apply to in the same way

Whichever kind you choose, you answer the same question — which documents does this rule apply to? — through the same three controls:

• Pinned documents always match, whatever else you set.
• Filters narrow the rest by role, collection, tags, or owner. Each filter can include a value or exclude it, and a document has to pass every filter you have set. The collections and tags come from how your team organises its documents.
• Excluded documents never match, even if you pinned them or a filter would have caught them.

A live preview shows how many documents currently match, and which ones, and it updates as you change the settings. You see the set the rule will act on before you commit to it.

Leaving all three empty is allowed. Such a rule matches nothing, which makes it a convenient way to save a draft you intend to scope later.

What a policy leaves behind

An agent policy's runs land in the Agent runs table at the foot of the Agents page, alongside the runs you dispatch by hand. That is where you follow their progress and read what they produced. Both kinds record when they last fired, in the Policies table's Last activity column.

A rule applies only while it is active, and you can turn it on and off at any time without losing it.