Structuring templates in Amicus: Best practices

A strong Template makes every Proposal faster and every Agreement cleaner. The aim is simple: write Terms and Conditions that read naturally while using Roles and Details for the blanks you fill in during negotiation. Done well, you gain clarity in authoring, speed in negotiation, and integrity across Agreements.

Title

The Title is the most visible label in lists; make it clear, specific, and recognizable. Prefer names that tell a busy reader exactly what the Template is for (for example, “Master Services Agreement (North America)” rather than a generic “MSA”). Avoid dates or client names in the Title—those belong in Details or the Case.

Roles

Roles are the named Parties to your agreement. Label them cleanly—use “Provider,” “Customer,” “Licensor,” or “Distributor,” not technical prefixes or placeholders. Keep role names stable across Templates when feasible so your team can reuse Terms without rewrites. Once a Role is defined, do not redundantly repeat the Party’s actual name inside the Terms. Refer to the Role label once and rely on associating Parties to Roles in the Case to bind the correct Party.

A stable set of Role labels also reduces noise in negotiation. The counterparty sees the same Roles across Proposals, and you avoid brittle search-and-replace edits that introduce errors.

Details

Details are fields you set at Proposal time; Terms are more fixed in the Template. Use Details to hold values you expect to change between deals while keeping the governing language steady. This enables quick counterproposals—adjust the Detail and keep the Template intact.

Choose Details when one or more apply:

• The value is likely to be negotiated (e.g., Fee, Payment Period, Service Description).
• The same Terms apply to more than one object (e.g., multiple jurisdictions, delivery locations).
• The value appears multiple times in the Terms; referencing one Detail prevents drift.

Do not make a Detail when:

• The item is not negotiable in your work (bake it into the Terms).
• The text is too long or narrative to fit a clean label (draft it once in the Terms).

Be strategic: each added Detail increases flexibility but also maintenance. Favor Details that unlock quick, safe edits without rewriting clauses.

Terms

Write the Terms as natural prose that references Role and Detail labels. Avoid technical prefixes and avoid building Party names or values into the Template that belong in Details. Do not redundantly repeat Party names or Detail values inside the Terms; refer to the labels once.

Think in a simple contract adaptation of subject–verb–object: Role–Terms–Details. The Role (subject) takes or receives an action; the Terms express the obligation; the Details supply the fields or modifiers you will fill in. Terms should be readable on their own, with labels sliding in smoothly.

Contrast:

Bad:  ROLE_PROVIDER shall deliver services to ROLE_CUSTOMER (Acme Corp). The fee is $10,000 USD (DETAIL_FEE). ROLE_CUSTOMER (Acme Corp) must pay within fifteen (15) days.

Good: Provider will deliver the Service Description for the Fee. Customer will pay within the Payment Period after receipt of invoice.

In the good version, Role labels (“Provider,” “Customer”) and Detail labels (“Service Description,” “Fee,” “Payment Period”) appear once and hold the values you will enter in the Proposal.

• Do not add a signature section; signatures are managed in‑app.
• Do not add dates or times for Proposal or signature events; Amicus tracks these automatically.

Field types

Pick field types that fit the value: text, number, yes/no, or date. Text can describe anything, but field types protect your Template. Numbers keep currency and quantities in the right format and prevent wrong entries. Dates prevent impossible timelines. Yes/no fields guard against ambiguous toggles. Appropriate field types reduce errors if a counterparty—or you—enter something wrong during negotiation.

Name Details so they read well in a sentence. “Payment Period” is clearer than “DaysToPay.” Avoid technical casing and prefixes; labels should read as plain English. If a Detail recurs, reuse the same label rather than variants. This keeps Terms concise and prevents silent drift when you update one location and miss another.

Finally, review the Template holistically. Ask whether a new reader can understand the Terms on first pass, whether each Detail is necessary and set to the right field type, and whether the Roles support reuse across similar Templates. Small investments in structure yield compound benefits: clearer authorship, faster counterproposals, and more consistent Agreements.

Clarity and Integrity are the point: write once with stable Roles and Details using the right field types, and let the Terms do the quiet work across every Proposal you send.