An engagement in Aiwyn is five things held together:
- Engagement details — who it is for, who it is from, what it is called, when it starts
- Clients — one primary, optionally more
- Scope of services — the projects it covers, optional
- Engagement letter — the document itself
- Contacts — the people who receive and sign it
Almost everything else in the product is an operation on one of those five.
Details come first and give order to the rest
The engagement details page is the starting point, and that ordering is not arbitrary.
Selecting the primary client determines which contacts, clients and projects you can reach afterwards. Selecting the fiscal year determines which projects appear. Selecting the letter template determines what content — and what locked content — you will be working with.
This is why the details must be saved before the draft opens. The draft screen cannot be built until Aiwyn knows what it is drawing from.
One letter, one primary client
However many clients you add to a letter, exactly one is primary. That client is who the letter is ultimately directed to, and whose contact must sign.
Additional clients extend the letter — their projects can be included, their contacts can be signatories — but they do not change who owns it.
Projects are optional throughout
A perfectly ordinary engagement has no projects at all. Projects exist to carry pricing, prepayments and merge fields about the work, drawn from your practice management system however they are not required if things like pricing and prepayments are not needed for the engagement letter.
Firms whose systems do not use projects lose those features and nothing else.
The letter is generated, not written
Letter content comes from a template built by your firm's engagement admins, assembled from content blocks, with placeholder variables filled from the client, contacts, projects, fiscal year and dates you selected.
A preparer adjusts it within limits the firm sets. This is why so much of what ends up in a letter is decided on the details page rather than in the editor.
On a dynamic letter template the details page decides even more than the placeholders. Each block in the template can hold several variants, and each variant has an expression that tests the engagement's data: the client's type, the names and types of the projects you added, the price you set, custom fields your firm maps from its practice management system. Aiwyn shows the variant whose condition is met and hides the others. Change the client, add a project, set a price, and whole paragraphs can appear or disappear without anyone touching the editor. Blocks can contain other blocks, snippets and variants; a snippet holds a word or phrase that varies inside a sentence and cannot contain a snippet or a block of its own.
The practical consequence is that a letter which reads wrongly is usually an engagement whose data is wrong, not a template that needs editing. See How engagement letter content and type are determined.
Related
- Engagement details field reference
- How clients and contacts expand from the primary client
- Locked sections and who can unlock them