1. Document Automation
  2. Features
  3. Template review
Feature · Template review

Template review

Submit and decide on an identified template version.

OverviewTemplates awaiting review
Document Automation · Template review

Templates awaiting review

Approval conditions

New
Template nameVersion numberRevisionStatusParent
Template 836150380SubmittedMTT-29330
Template 171700460SubmittedMTT-65793
Template 295180610SubmittedMTT-13014
Template 71830440SubmittedMTT-24823
Template 279790550SubmittedMTT-94428
6 of 6 records
Template 836Template versions · TV-82105
Submitted
Version number150
Revision380
ParentMTT-29330
Example screen with sample data

What you can do

Review the version intended for use

The Matter Coordinator prepares a template version for the organization and its parent matter. Its name, version number, revision and clause library help identify what the Supervising Attorney is being asked to review. A draft can change during preparation. Submission marks the point when the reviewer should examine a specific version rather than an evolving working copy.

The attorney decides whether the submitted version is approved or rejected. The decision date and approval date remain with the version. The team should compare the decision with the version that will be used; an approved title does not authorize a later revision with different clauses. The team uses the approved version only after checking that the decided revision still matches the intended content.

How the work is organized

  • Preparation. Keep a draft version linked to its organization and matter.
  • Submission. Identify the revision and clause content being sent for legal review.
  • Decision. Record whether that submitted version was approved or rejected.

What to agree during setup

Agree who prepares templates and who decides their legal acceptability. Define how the team names versions and how it records clause library material so the reviewer can compare the actual content. The Supervising Attorney needs to know whether a new version replaces an earlier approved version for future use, while historic matter evidence remains attached to the earlier decision.

Establish a practical handoff after rejection. The coordinator should prepare a corrected draft and resubmit the exact revision for another decision. Do not treat a decision on one version as a blanket approval for all versions of a template name. If a signing service will use an approved version, its connection and receipt need a separate setup decision.

Check the handoff on an actual case

A coordinator prepares a standard engagement letter for a new matter. The first draft includes a clause that needs clarification. The attorney rejects the submitted revision, and the coordinator prepares a corrected version. The coordinator presents the new revision for a separate decision. The attorney can compare the current submission with the rejected one before approving it.

The team then checks that the version selected for use is the approved revision, not the first draft. A reviewer should be able to find the decision time and the matter that led to the version. The example makes the approval boundary concrete for the coordinator, attorney and any later auditor.

What your team sees

  • Templates awaiting review — Find submitted versions that need a decision.
  • Template version board — Compare draft, submitted and decided versions.

What it keeps track of

Data model
Template versions
Document template revisions submitted for legal review and publishing.
Matters
Legal or contract matters with lifecycle, owner and agreed fee.
Organizations
Firm organizations that own matters, clients and document templates.

Who uses it

Permissions
Matter Coordinator
, Supervising Attorney, Auditor.

Set up Document Automation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started