Every field on the Engagement details page. Aiwyn prefills most of them from your practice management system, and all of them can be changed before the letter is sent.
Client details
| Field | Required | Default | Notes |
|---|---|---|---|
| Primary client | Yes | — | The client the letter is directed to. Shown first on a single engagement; on a batch it appears once the drafts are generated. After the first save it can only be changed to another client in the same client group. On a renewal it cannot be changed at all. |
| Primary contact | Yes | Set at implementation from contact category or type in your practice management system | Must have an email address. Must sign. Choose from contacts of the primary client, of clients in its client group, or of any other client added to the letter. |
| Billing contact | Yes | Either the client's designated billing contact, or the same as the primary contact — a firm-wide choice made at implementation | Must have an email address. Responsible for the payment method and any prepayment. Does not sign unless also added as an additional signatory. |
| Address on letter | Yes | — | The primary contact's address or the client address, both as they come from your practice management system. |
Payment
| Field | Required | Default | Notes |
|---|---|---|---|
| Prompt for payment method | Yes |
The default Payment Prompt on a new engagement letter depends on three firm-level settings, checked in order: -If the firm doesn’t have the Payments module turned on, the Payment Prompt is set to None and locked. Hovering over it shows a note explaining it can’t be changed because payments aren’t enabled. -If Payments is on but the firm has chosen not to collect payment information through engagement letters, the Payment Prompt defaults to None. -If the firm does collect payment information but hasn’t made it mandatory, the Payment Prompt defaults to Optional, meaning clients can add a payment method when signing but aren’t required to. -If the firm collects payment information and has made it mandatory, the Payment Prompt defaults to Required, meaning clients must add a payment method to complete signing. -In every case, the default can still be changed on an individual engagement letter unless Payments is off entirely. |
Required, optional, or not prompted. Overridden if any project on the letter carries a prepayment. See Payment prompt options. |
Firm details
| Field | Required | Default | Notes |
|---|---|---|---|
| Engagement partner | Yes | The client's designated client partner | The letter's author. Receives the executed notification with the signed PDF attached. Can be any active staff member. |
| Engagement manager | Yes | The client's designated client manager |
The sender of the client email — their address appears as the From. Receives the executed notification with the signed PDF attached. Can be any active staff member. |
| Collaborators | No | None |
Any number of additional staff. Receive the executed notification with the signed PDF attached. Can be any active staff member. Multiple collaborators are possible. |
Engagement details
| Field | Required | Default | Notes |
|---|---|---|---|
| Letter template | Yes | — | Built and maintained by your firm's engagement admins. Must be chosen before you can proceed. |
| Fiscal year | Yes | Current year | Selectable four years back and four years forward. Available as a placeholder, and combines with the client's fiscal year end to build full-date placeholders. |
| Engagement name | Yes | Your firm's default name structure, set at implementation | Appears throughout the client and firm portals. Editable per letter or per batch. Built from variables — see Engagement placeholder variables. |
| Start date | Yes | On acceptance | A fixed past or future date, or On acceptance. Start date placeholders populate only when the date is fixed. See Choosing an engagement start date. |
| Renewal date | No | None | Includes the engagement in the monthly renewal reminder to partners and managers. Not required in order to renew. |
Fields that also decide the letter's wording
On a dynamic letter template, several of the values above are tested by block variants as well as merged into the letter. Changing them on the details page can therefore add or remove whole paragraphs, not just change a merged value.
| Field | Effect on a dynamic letter |
|---|---|
| Primary client | Supplies the client type, state and client custom fields that variants commonly test. A trust and an individual get different paragraphs from the same template. |
| Letter template | Decides which blocks, snippets and variants the letter is built from. The template cannot be changed after the first save; to use a different template, create a new engagement. |
| Fiscal year | Merged as a placeholder. |
| Engagement partner | Merged as the partner placeholder; a variant can also test the partner, for example to show their unique signature (image). |
| Start date | Merged only when fixed; a variant testing the start date has nothing to evaluate while it is On acceptance. |
| Projects, prices and prepayments (Scope of services tab) | Project name, service line, price and prepayment are the most common variant conditions after client type. Adding a project or saving a price can change the letter's shape. |
Engagement details stay editable until the engagement is executed. See What you can edit at each status.