The drafting library

The library is what documents are drafted from. It is maintained by admins and by members granted author documents (on the Users page, or on the invitation). Everyone else starts documents from the Drafting page, which offers only the document types and templates they may use. Open it with Drafting library on the Drafting page. Five tabs: Blocks, Document types, Fields, Templates and Selection tests.

A good order for a new library: the fields first, then the document type with its sections, then the blocks, then a template for the documents produced the same way every time.

Fields

A field is one question a document asks, defined once and merged by its key (testator.full_name) in every block that needs it.

• Each field has a kind: text, long text, date, whole number, number, money, yes / no, one of a list, several from a list, person, people, address or image. One of a list and several from a list take their options, one per line.
• Optional rules: shortest and longest, lowest and highest, a required format, fewest and most.
• The document types a field belongs to; none means every type.
• Give this field a default answer fills it in for every new document from then on: a firm's address, a standard notice period. With Members may change it off, the answer is fixed and shows read-only on the form. Changing a default changes future documents only, and the change is recorded. The Fields tab marks these with Default and Fixed chips.
• An image field holds a picture (a logo, a seal) uploaded rather than typed: PNG or JPEG, up to 1 MB and 2000 pixels each way, with a printed width in millimetres. Its default is uploaded on the field with Choose an image.
• Save and add another saves the field and keeps the editor open on a blank one, for entering several in a row.

A field's key can't change, and the field can't be deleted, while a published block merges it. The tab has a search and filters for the kind, the document type and whether a default is set.

Document types

A document type names a kind of document, a will, a lease, with:

• Its sections, the headings in order, and the clause numbering: throughout the document, within each section, or none. Numbered within each section, Number the section headings prints a section's number in its heading: "3. Letting and rent" over clauses 3.1 and 3.2. Section heading size sets how large the section headings print, from heading 1 (the size of the document's title) to heading 4; a schedule's parts print one size smaller. Switch New page on for a section to start it on a fresh page in the PDF and Word exports: each schedule, say.
• Blocks every document of this type includes, the mandatory blocks.
• The groups the form asks its questions under, and a document title pattern with merge fields.
• Guidance for the AI when it proposes blocks for the type.
• A header and a footer, printed on every page of an export and written like a block; page.number and page.count print the page number, and the header can be left off the first page.
• Two switches: mark the text as a draft until reviewed, and require a review before export.
• Who may review: admins, the Owner, roles or people. Only they can mark a document of the type reviewed, and its owner asks them with Request review. Leave it empty and anyone who can see a document may mark it reviewed.

Who can use restricts the type to specific people and roles; admins and document authors always pass, and a restricted type's blocks and fields are hidden from everyone else. Archive stops new documents without deleting anything; Delete is refused while blocks or fields are tagged to the type.

Blocks

A building block is a piece of text, a clause or a paragraph, with merge fields, conditions and repeats, written in Markdown. Each block has a key (how other blocks refer to it), a title, a description and a use when note. The description and the note are what the AI reads when it proposes blocks, so write them for a colleague who has never seen the block.

• Revisions. A block is created as a draft. Publish makes the draft the revision documents use; editing a published block opens a new draft beside it, and publishing that draft archives the old one. Discard draft drops a draft and keeps the published revision. A block can be saved with errors but not published; the Errors chip on the list says which drafts are blocked. A document keeps the revision it was planned with until its owner chooses to update.
• Document types and where it sits. Add the document types the block belongs to. For each, choose the section it sits under and its order within the section, so one block can sit under different headings in different types. A block with no type can be saved but not published, and no document offers it.
• Requires names blocks that must be in the document with this one; Conflicts with names blocks that can't be. Blocks in the same variant group are alternatives: a plan takes at most one.
• Include when is a test over the answers: a yes / no question compares with `true` or `false`, a number with the number in backticks, text with text in single quotes. A save tidies the plain cases and lists anything it can't read. The form asks the questions the test reads. With Add it automatically when the condition holds on, the block joins the plan by itself once the answers make the test true; off, the test only removes a chosen block when it fails.
• Defines and Uses the terms record defined terms, so a block that uses one brings in the block that defines it.
• Delete is refused while another block requires or conflicts with it, or a document type lists it as mandatory.

The block editor

• Details sits above the text and can be collapsed once filled in. Add the block's document types first: a field that belongs to a type is offered only once that type is added. Number this block as a clause is on by default; off, the text appears as it is, with no number, for a heading, a recital or an address.
• Text is the block's language in a code editor: Markdown for the words, merge fields, conditions and repeats between double braces. A new line in the text is a new line in the document, and a blank line starts a new paragraph. {{ page_break }} on a line of its own starts a new page in the PDF and Word exports, and text between ::: middle and ::: (or top or bottom) prints on a page of its own: a front sheet, say. Insert a field offers the fields the block may use; Import from Liquid converts the core of a Liquid template and reports the tags it can't. The full language is the block language reference, also open from Reference under the editor.
• The text is checked as you type: the status line counts errors and warnings, the list under the editor explains each with a position to jump to and, where mechanical, a one-click fix. Errors block publishing, never saving.
• Preview shows the block with sample answers. Fields this block uses lists the keys read from the text, each with an Optional switch; an optional field left empty prints its label in brackets unless a condition guards it.
• AI drafting (the lightbulb on the Text card) asks the AI to improve the text you have typed, with an optional instruction such as make it mutual, or to write a clause from a description. It knows the language and the fields of the block's types, merges only those fields and never invents one; a fact with no field is left in square brackets for you. The proposal shows as the changes against your text, with the check's findings and the AI's notes, and nothing changes until you choose Use this text.
• The same AI drafting button sits beside the Use when note and the Guidance for the person drafting in the block's details. It improves what you have written, with an optional instruction, or writes a new note from the block: its text, fields and condition, its document types and the blocks around it, so a use when note can say when to choose this block rather than its alternatives. Nothing changes until you choose Use this text.
• Save draft, Publish and + New block sit together; a new block from a block with unsaved changes asks first.

Templates

A template fixes a recipe, a document type and the blocks a document always starts with, so a member picks it under New draft → Use a template and goes straight to the form, and an integration can produce the same document through the API. It is a recipe, never a snapshot: the blocks are resolved to their published revisions each time it is used.

• The editor ticks the recipe from the type's published blocks and checks it as you tick: the plan the rules would build, the questions the form would ask, and anything that stops the template being used. A recipe the rules block can't be saved.
• Who can use restricts a template like a document type; a member sees it only when they can use both it and its type. Require a review before export makes every document from the template wait for a person's attestation, whatever its type says.
• The card shows Fields changed since last use when a republished block asks different questions now, and Needs attention when a block lost its published revision or the rules now block the recipe. Archive hides a template from members and the API; Delete removes it, and documents already made from it keep their plan.

Selection tests

A selection test measures how well the AI picks blocks for a document type: a brief written the way a member would write it, the blocks a right answer must pick and the ones it must not. Run sends the brief through the same selection Ask the AI uses and scores the result, precision (how many of its picks were wanted) and recall (how many of the wanted blocks it found); a test passes when nothing expected is missing and nothing forbidden was picked. Blocks the type always includes count as picked, and are saved as expected too, so if one later stops being mandatory and the AI leaves it out, the test fails.

Run the tests after changing a block's description or use when note, or after adding a block that overlaps an existing one; Run all runs every test in turn. A failing card lists what was missing and what was picked but forbidden; the fix is usually a sharper use when note, or the type's guidance for the AI. Each run is one model call on your workspace's allowance.

Export and import a document type

Export on a document type's card downloads it with everything it stands on — the fields assigned to it and every shared field its blocks use, its published blocks, its templates and its selection tests — as one portable bundle that carries no names or ids from your workspace. Import a library brings a bundle into any workspace: the document type arrives restricted to you, every block arrives as a draft to review and publish, and any templates it carries say they need attention until the blocks are published.

A field key the workspace already holds is never renamed for you. Before anything is written the import lists each such key beside the field you have — the same, the same kind with a different label, options or rules, or a different kind altogether — and you choose: use the existing field (it joins the imported document type) or create a new field under a key you type, which the imported blocks then merge instead. A field of a different kind can only be created anew. Nothing is imported until every clash is answered.

The bundle is plain JSON. Build a library import file describes it in full, with its schema, for writing or changing one yourself.

Limits and notes

• Your workspace's plan may limit how many document types and templates the library holds; the tabs show the counts where a limit applies, and the + New button is disabled at the limit. Contact support to raise it.
• Names, text, descriptions and answers are encrypted at rest with your workspace's key, like every other document in the workspace.
• The library and its documents are part of the workspace export.

Related: produce a document, the member's side.