What we are building next

Until now DocuTract has done one job very well: you build a template once, upload the scans, and a finished document comes back with a source recorded for every value. That job stays exactly as it is. What changes over the next few releases is everything around it, because that is where the time actually goes.

We asked ourselves a simple question: after a document is generated, what does a person still do by hand? The answers turned into the seven features below. We will ship them one at a time, each with a post like this one and a new section in the help centre.

1. Collecting documents from the client

Today you upload the scans yourself. Soon you will be able to send a client a one-off link instead: they open it in a browser, drop in their documents, and the files land in your workspace already attached to the right case. No account needed on their side, no photos arriving by three different messengers. The link expires, can be revoked, and accepts only the formats we can actually read.

2. Cases: one set of scans, several documents

A single deal rarely needs one document. A lease needs the lease itself, an acceptance act, and often an invoice, all filled from the same handful of scans. A case groups them: you upload the documents once, and every template in the case reads the same verified values. Fix a date in one place and it is right everywhere.

3. Cross checks between documents

When two scans disagree, that is usually the moment a mistake would slip through. The name on the extract does not match the name on the certificate, the amount in the statement contradicts the terms sheet, a date falls outside the period. Instead of hoping someone notices, DocuTract will compare the values across documents in a case and show the conflicts before you generate anything.

4. A directory of parties

The same landlord, the same company, the same bank details, typed again for every new deal. A parties directory stores them once: you pick a party and its fields fill in from the card, while the scans still fill everything that is specific to this case. Every generated document quietly keeps the directory up to date.

5. Conditional blocks and template versions

Real contracts are not fixed text. A clause appears only when there is a deposit; a paragraph about pets belongs in some leases and not others. Conditional blocks let a template include a section based on the data, instead of forcing you to keep five near-identical templates. And because templates change, each one will keep its version history, so a document generated last month can always be explained.

6. Connecting DocuTract to your own systems

Some of you already have a CRM, a portal, or a script that knows when a document is needed. A public API, webhooks that fire when a document is ready, and exports of the extracted values will let DocuTract sit inside that flow rather than beside it. Sending the finished document for signature belongs in the same release.

7. Batch generation

The same template, thirty different sets of data: thirty employment contracts, thirty notices, thirty certificates. Batch generation takes a table of values or a folder of cases and produces the whole stack in one run, with a clear report of what succeeded and what needs a human.

How this will arrive

Each feature is a separate release. When one ships, you will find:

• a post here explaining what it does and how it looks in the interface,
• a new section in the help centre with the step by step,
• and the feature itself, live in your workspace.

Nothing in the list changes how the core works or what you already pay for. If one of these seven matters to you more than the others, tell us on the contact page and it moves up the queue.