The document checklist
Every engagement is a list of documents you are asking for. Here is how to shape that list before and after you send it.
Open an engagement and the middle of the page is a list. One row per document. That list is the whole conversation you are having with your client, so it is worth getting right.
Shaping the list
Add a row for anything the template missed. Remove rows that do not apply to this client. Reword a row if your client will not recognise the official name for it, because they read this exact text.
Write rows the way your client thinks, not the way the CRA does. Your December bank statement gets a faster response than the form number.
Required and optional
Rows marked Required are what Vylan chases. An engagement is not finished while a required row is empty. Optional rows are asked for once and then left alone.
Changing the list after you send
You can add and remove rows on a live engagement. The client's page updates, and Vylan folds the change into its follow-ups rather than sending a separate announcement about it.
Removing a row your client already uploaded to removes that request. Their file is not silently deleted, but the row stops being part of the job. If you only meant to accept it, approve it instead.
When a client says a row does not apply
Clients can mark a row Not applicable themselves. It stops being a hole in the checklist and Vylan stops chasing it, and you can see every row they did that to. See how your client uploads documents.