Almost every field on the engagement details page arrives prefilled. Those defaults come from your practice management system through mappings your firm agreed on during implementation — which is why two firms running Aiwyn can see different behavior from the same screen.
What is mapped
| Default | Comes from |
|---|---|
| Primary contact | The contact category or type your firm nominated. Contacts marked Engagement contact or Primary contact are typical choices. |
| Billing contact | Either a nominated billing category, or a firm-wide rule that it always matches the primary contact. |
| Engagement partner | The client's designated client partner. |
| Engagement manager | The client's designated client manager. |
| Reachable clients and contacts | Client group structure. |
| Available projects | Client projects for the selected fiscal year. |
| Full-date placeholders | The client's fiscal year end month and day, combined with the fiscal year you select. |
| Engagement name | A default name structure your firm chose, built from variables. |
Letter wording is driven by the same data
On a dynamic letter template, the practice management system decides more than the defaults on the details page. Each block or snippet in the template can hold several variants, and each variant has an expression that tests the engagement's data: client type, client state, project name and project type, service line, price, and any custom fields your firm mapped during implementation. Aiwyn shows the variant whose condition is met and hides the others.
| Wording that varies | Typically driven by |
|---|---|
| Individual, trust or entity paragraphs on a tax letter | Client type |
| Corporation versus S-corporation wording | Project name (for example contains "1120" but not "1120S") |
| A bookkeeping clause | A project custom field on any project on the letter |
| Audit scope, supplemental schedules, non-attest services | Custom fields created in the practice management system for the purpose; standard fields rarely carry these distinctions |
| A fee table versus a plain list of services | Whether the projects on the letter have a price |
This is why a template built for one firm cannot simply be copied to another: the variants depend on which fields that firm's system actually populates.
Why the defaults are only defaults
Every one of them can be changed on the letter in front of you. The mapping is a starting position, not a rule.
It is right most of the time, which is what makes batch creation viable at all — you can generate 500 letters and expect the majority to be correctly addressed.
When a default looks wrong
If a default is consistently wrong for one client, the fix is usually in your practice management system rather than in Aiwyn (unless your firm is on Aiwyn Practice). A primary contact that keeps defaulting to the wrong person means that person carries the mapped category on the client record.
If a default is consistently wrong across all clients, the mapping itself may need revisiting. Contact Aiwyn Support.
The same logic applies to the letter's wording. If a block or snippet shows the wrong variant for one client, the client type, project name, or custom field it tests is wrong or empty in your practice management system. Correct the record there; a draft letter reflects the corrected data within a few minutes, without being recreated. If every client shows the wrong variant, the expression on the block or the field mapping needs attention, which is a job for your engagement admin rather than for the letter editor.
A missing default stops the letter
Aiwyn cannot send a letter without a primary contact and a billing contact who each have an email address.
In batch creation, clients missing that data appear under Engagements with errors with the gaps highlighted in red. The batch will not proceed until you either fill them in or remove the client.
Related
- Engagement details field reference
- Contact Data Mapping and Management Guide
- Batch create engagement letters from existing projects