Guides related to Matter Record
Help Guides provide in-depth explanations of key features, with step-by-step detail, to help you get the most from your automation.
Understanding Matter Record
Smarter Drafter Matter Record allows previously entered data for a matter to be reused in subsequent submissions, reducing the need to rekey information. This reduces the need for rekeying information saving time and improving consistency.
Section Aliases and Field Aliases Help Guide
Aliases are alternate references for sections or fields that standardise how data is labelled, stored, and reused across forms. Section aliases are mandatory and automatically generated, while field aliases are optional and applied only to reusable data, using consistent naming conventions to avoid duplication and support effective data sharing. Organisations should regularly review, edit, replace, or delete aliases as needed, and when combined with roles, aliases ensure data is accurately identified and shared across documents.
Creating and Assigning Record Types Help Guide
Record types are labels that group related data, such as purchaser, vendor, or property details, and work alongside section and field aliases to enable accurate data sharing across documents. They are created and assigned during form building, using consistent naming conventions, and can be applied, adjusted, bulk-assigned, or unassigned as needed, with regular reviews recommended to prevent duplication. When generating documents, record types allow data to be reused from contacts or previous submissions, ensuring consistency and reducing re-entry of information.
Form Set-Up Help Guide
Data sharing stores information entered during document generation so it can be reused in future documents, with section aliases, field aliases, and roles creating the data pathways. When forms are set up correctly, answers are retained against the matter and can populate into later documents, reducing re-entry and maintaining consistency. Builders should apply descriptive aliases, assign roles only where useful, and follow a checklist to ensure sections and fields are properly structured, with contact and user mapping applied.