August - Release Notes
Explore the latest updates to Smarter Drafter, including new features, enhancements, and bug fixes.
5 August 2026
Version 8.0.0
This release introduces Co-Builder Form Agent in beta - a conversational AI agent in the form builder that turns plain-language instructions into sections, fields, logic and calculations, with every change proposed as a plan the builder approves before anything is applied. It also introduces submission naming conventions, letting firms define how submissions and generated files are named once and have it apply automatically on every submission. Other highlights include PDF and/or DOCX selection and static attachments in email automation, section block flexibility improvements, and bug fixes.
What’s new:
Co-Builder Form Agent (Beta)
Building an automation has always started with the heaviest lifting: constructing the entire form by hand, one section, field, property and rule at a time - hours of clicking before a template produces a single document. Co-Builder changes that. Describe what you need in plain language, and Co-Builder does the building, while you stay in control of every decision. Here's how it works:
- Describe it, Co-Builder builds it. Ask for a section, a set of fields, or a common pattern like client details, and Co-Builder proposes the sections to create, the fields to add, and their types, properties and validation. It handles logic, calculations and conditional rules of simple to moderate complexity, sets up options on select fields, imports section blocks you have access to, and can publish the form when you're ready.

Co-Builder in Form Build
- A plan for every change. Nothing is applied to the form without your approval. Every change Co-Builder proposes arrives as a plan with its reasoning visible — you approve, revise or reject it, and you can undo the last applied plan. On approval, the changes stream into the form live. The legal profession runs on showing your work, and Co-Builder is built to that standard.
- Your documents stay deterministic. Co-Builder helps build the automation - it never touches the document engine. Your documents are still generated by the same deterministic, rules-based runtime as today: same inputs, same document, every time.
Help us shape it. This is an early release of Co-Builder, and it will improve week over week. Form Agent is the first of a series of specialised agents we're building across the automation journey, with planning, template coding and QA agents to follow. Every Co-Builder response includes thumbs up/down feedback with an optional issue type and comment.
🔗 Learn more here
Submission naming convention
Law firms have established naming conventions for their submissions and documents - but until now, both were named manually in Smarter Drafter, submission by submission, click by click. Now builders define the convention once, and it applies automatically every time.
In the new Submissions tab under form settings, builders compose a convention from free text, form fields and submission details - form name, matter ID, submitter and recipient details, submission date and more. Set it at the parent form and it cascades to child and intake forms; submissions are named automatically on submit, with the form name as a fallback and drafters still free to edit the name on the review page. Supported across Tests, Form Library, embed forms, API, MCP and iManage.
The same capability extends to the files themselves: define a naming convention on an individual document or email template, and every generated file adopts it automatically - including files saved to iManage.

Setup Submission naming in Form Settings
Other updates:
- Email automation: builders can now choose to attach the PDF and/or DOCX version of generated documents to an email template
- Email automation: a new Additional attachments component lets builders upload static files to an email template, added to the generated .eml as-is
- Section Blocks: New page and Hide heading can now be enabled or disabled on an imported section block section
Bug fixes:
- Record IDs not appearing in submission webhooks