Handing a matter to your own drafting software

Take a client’s instructions off the platform, draft in the software your firm already uses, and bring the finished will back.

Last reviewed

Before you can ask

A copy of a client’s instructions leaving TheWILL.ai is the one step in the professional workflow that cannot be undone, so four things have to be true before a copy can be prepared. The egress pane on the matter states the reason when a request is blocked, and asks you to accept the addendum before your first copy.

  • Your professional profile is verified.
  • The client has signed your engagement letter for this matter. Instructions do not travel before signature.
  • Your firm has accepted the data-sharing addendum. It is accepted once for the firm, not per matter, from the egress pane before your first copy (asking a client needs no addendum), and it is what records that your firm becomes a controller of any copy it takes.
  • You are engaged at full or review access on the matter. A client who has chosen you but not yet engaged you is not covered.

Screenshot, for illustration only

The Use your own drafting software pane on a client's matter, listing what would be sent and the button to request the client's consentThe Use your own drafting software pane on a client's matter, listing what would be sent and the button to request the client's consent
The Use your own drafting software pane on a client's matter, listing what would be sent and the button to request the client's consentThe Use your own drafting software pane on a client's matter, listing what would be sent and the button to request the client's consent
The Use your own drafting software pane on a matter before your firm’s first copy, asking you to accept the data-sharing addendum.

Why the addendum is separate

The engagement letter is between you and your client. The addendum is between your firm and us, and it covers the copies your firm holds outside the platform. Neither substitutes for the other, and a matter cannot be exported until both are in place.

Asking the client

You ask from the "Use your own drafting software" pane on the matter. The pane itemises, section by section, exactly what would be sent before you ask, so you can tell the client accurately what you are asking for.

  1. Open the matter and select Request consent on the egress pane.
  2. The request appears for the client on the Professional Access page of their account, with the same section-by-section list you saw.
  3. The client picks how long the permission lasts from the periods the consent form offers.
  4. The client ticks an acknowledgement that a copy already taken cannot be recalled. Nothing is prepared until they do.
  5. The pane opens, and you can collect the pack by file or by API for as long as the permission runs.

The permission ends by itself at the end of the period the client chose. The client can also withdraw it at any point from the same page without telling you first. Withdrawn and expired permissions stay on their list, so they keep a record of every permission they gave.

What is in the pack

The pack carries the client’s instructions, not a will drafted for them, and it carries only the sections your current access already opens. Each section arrives with a line describing what it is, so a pack read out of context is still self-describing.

Will instructions

The drafting instructions the client entered, step by step, in their own words where they wrote prose. This is the section your drafting software is for.

The client’s case summary

What the client told us about their situation when they chose you.

Assets, guardianship nominations and business succession

The client’s tracked assets, who they have nominated to care for their children, dependants and pets, and their business succession arrangements, each at the level of detail your current access opens and no further.

Documents the client has shared

Titles, categories and dates only. File content is never in the pack. Fetch a document through the platform when you need to see it.

What never leaves, and how you can tell

Some records never leave the platform under any consent, whatever your access: consultation recordings, their transcripts and AI summaries, vulnerability assessments, identity-verification records and documents, and health and other special-category answers. Beyond that, a section you do not have access to is simply absent. Every pack carries a manifest naming every section included, every section excluded and the reason, so you can show a client or a regulator what you were and were not sent.

For a section the pack leaves out, the exclusion reason is deliberately the same whether it was closed to you or simply empty. Splitting the two would tell you something about the client’s affairs that the pack itself withholds.

Collecting the data

There are two lanes and they carry the same content. Which one suits you depends on whether your drafting software can call an API.

By file

Select Download pack on the egress pane. You may be asked for your password first, and the list of copies already taken is behind the same prompt. You get a single archive per matter containing four files:

  • brief.json, the machine-readable instructions on the published schema.
  • brief.pdf, the same content laid out to read, with a provenance footer naming the matter and the date on every page.
  • instructions.csv, flat, for firms that will only ever retype.
  • manifest.json, naming every section included, every section excluded and why, and the consent it was taken under.

The download link is signed and lasts only a few minutes, so use it straight away rather than pasting it into a case-management note. You can ask for a fresh link while the archive is still held. The archive itself is kept for a few days, then deleted on a schedule, and no link works after that. The manifest record of what you were sent outlives the file, so "what did we receive" is still answerable afterwards.

The file lane is the weaker one

A file on your own disk cannot be revoked, cannot be re-scoped and goes stale silently. If the client changes their instructions the next day, your copy does not change with them. Re-download before you draft, and treat an old pack as out of date rather than as the record.

By API

If your software can call an API, the matter-brief API is the better lane, because the consent is checked on every single fetch rather than once at download. When a client withdraws, the very next call stops returning the brief. The endpoints, the field tables, the response schema and the versioning policy are documented in the matter-brief API guide, which is public so you can hand it to your own developer or software vendor.

Keys belong to a person, not to a firm, so the engaged professional signs in and mints one from their own developer hub. The egress pane gives you a copyable snippet already carrying this matter’s identifier. The worked example below is the same one the API guide carries, imported rather than copied so the two cannot drift:

# 1. Mint a key with the pro:read scope (or pro:matters:read) on your API keys page, then
#    put it in a file curl reads, NOT on the command line. Every process's argv
#    is readable by other users on the same host, so a key passed with -H leaks
#    to anyone who can run ps.
umask 077; TW_CFG=$(mktemp); trap 'rm -f "$TW_CFG"' EXIT INT TERM HUP
printf 'header = "Authorization: Bearer %s"\n' "$TW_KEY" > "$TW_CFG"

# 2. List the matters you may pull a brief for (no client data in this response)
curl -s --config "$TW_CFG" \
     https://api.thewill.ai/api/v1/pro/ext/matters/

# 3. Fetch one brief. Use an id whose brief_available was true.
curl -s --config "$TW_CFG" \
     https://api.thewill.ai/api/v1/pro/ext/matters/MATTER_ID/brief/

# 4. A lapsed or revoked grant answers 404, not 403. Handle it as "not available
#    now" and re-read brief_available, rather than treating it as a hard error.
curl -s -o /dev/null -w '%{http_code}\n' --config "$TW_CFG" \
     https://api.thewill.ai/api/v1/pro/ext/matters/MATTER_ID/brief/

The list endpoint carries no client data at all, only which matters currently have a brief available, so it is safe to poll. The brief endpoint is the one that carries client data and it is the one behind the consent check.

Drafting in your own software

Nothing about this step is ours. You draft in the software your firm already uses, against the instructions in the pack, applying your own house style, your own precedent bank and your own checking.

Two practical points are worth building into your process. Pin the schema version your integration reads, so a later addition to the brief cannot silently change what your software maps. And keep the manifest with the matter file: it is the record of what you were sent, and it is the thing that answers a later question about scope without anyone having to reconstruct it.

Bringing the finished document back

All three routes are first class. None of them is a fallback, and all three land in the same place, so the client’s record, the audit trail and the storage are identical whichever you use.

  1. Upload the finished document. A PDF or Word file of the executed or engrossed will, read by the platform extraction step.
  2. Upload structured data. JSON on the same published schema you were sent, or CSV on the importer vocabulary, if your software can emit it.
  3. Draft here instead. If you used our wizard for this matter, nothing extra is needed and the return is already recorded.

Where the pack you were sent carried will instructions, the return is compared against it field by field, and you are shown every field that changed, was dropped or was added before the matter completes. That check exists because we know exactly what we sent you, so the comparison is against a known reference rather than a guess. You confirm the differences, and re-editing after you confirm asks you again.

How the platform reads an uploaded document

Extraction runs on our own infrastructure by default and never sends a document to an outside AI service without the client’s explicit, recorded consent for that document. If our own extraction is unavailable, the upload waits and you retry. It does not quietly go elsewhere.

When consent lapses mid-matter

Consent can end mid-matter in three ways: the period the client chose runs out, the client withdraws it, or the engagement itself ends. What happens next is the same in all three cases.

  • The API stops returning the brief on the next call, with the uniform 404 described below. There is no grace period.
  • Any signed download link stops working, and no new pack can be minted.
  • A copy you already downloaded is still on your disk. We cannot recall it, and we do not pretend to.
  • You can still return the finished will. A return is you giving us data, not us giving you more, so it is accepted whether or not the consent is still live.

If you still need the instructions, ask again from the pane rather than working from a stale pack. A fresh consent is a fresh decision for the client to make, and a fresh pack reflects any changes they have made since.

Troubleshooting

The pane will not let you ask, or will not let you download

The pane always states the reason rather than showing a dead button. Find the sentence you were shown.

What you are shownWhat to do
This client has no TheWILL.ai account, so there is nobody to ask for permission to copy this matter into your own software.The client record is not linked to an account, so there is no one who can give consent. Nothing can be requested for this client until they have an account linked to the record.
A copy can only be prepared while you are actively working with this professional on this matter.The matter is not at an access level that allows a copy to leave the platform. Only a full or review engagement does. Complete the engagement, or ask the client to confirm the instruction, and the pane reopens.
This professional’s engagement letter has to be signed before a copy of your information can be prepared for their own software.Send the engagement letter and wait for the client to sign it. Nothing about the matter leaves the platform before signature, because that is what the client was promised.
A copy that has already been taken cannot be recalled, so we need you to confirm you understand that before we can allow one.The client opened the consent form but has not ticked the acknowledgement. Ask them to finish it. You cannot tick it for them.
Choose how long this permission should last.The client has not picked a duration. They choose from the periods the consent form offers, and the permission ends by itself at the end of whichever they choose.
A copy can only be prepared once this professional’s practice has accepted our data-sharing addendum.Your firm has not accepted the data-sharing addendum. Accept it once for the firm from the egress pane. Asking the client and the client consenting do not need it, but nothing can be collected until it is in place.
This professional is based in [country], so we need you to agree to your information being sent there before we can allow a copy.Your practice is outside the countries the UK treats as adequate, so the copy is a restricted transfer and the client has to agree to it separately on the consent form. The sentence names your country where this page shows [country]. Ask the client to complete that step. You cannot agree on their behalf.
A copy of your information can only be prepared while a current consent for this matter is in place.There is no live consent for this matter: it was never given, it has expired, it was withdrawn, or it belongs to a different matter. Ask again from the pane. The same sentence covers all four on purpose, so that a request cannot be used to work out which of them is true.
A copy of your information cannot be prepared right now. Please contact support.The matter holds something that may never leave the platform and the pack could not be built safely around it. Contact support with the matter reference and do not retry.

The API returned an error

The response schema for each status is in the matter-brief API guide. What follows is what to do about each.

StatusWhat to do
401 The key is missing, malformed, revoked or expired. Send it as an Authorization: Bearer header and mint a replacement from the developer hub. Retrying the same key will not help.
403 The key authenticated but is not allowed here: it lacks the pro:read scope, or the account does not hold API access on its plan. Fix the key or the plan. This is not a transient error.
404 Treat this as "no data available now" and re-check the matter list. It means the matter is not yours, does not exist, or the consent has lapsed or been revoked, and those cases are deliberately indistinguishable so that a leaked key cannot map which matters exist.
429 You have exceeded a request cap. Two apply independently: your plan’s API rate limit, and a separate cap of 30 per hour on matter briefs, shared between API fetches and file downloads. Back off and retry after the window rather than spinning.

What your firm takes on

These are stated here rather than left in the addendum, because they are the part of this workflow that a fee earner meets in practice. They are a description of the position, not advice on it. Your firm’s own compliance adviser is the right person to tell you what your obligations require of you.

  • Your firm becomes a controller of the copy it takes. From the moment the pack lands on your systems, your firm decides what happens to it, and your own retention, security and subject-access processes apply to it.
  • The pack names people who never dealt with us. Executors, beneficiaries and guardians are in it because the client named them. Article 14 of the UK GDPR places an information duty on a controller who obtains personal data from someone other than the person it is about, and that duty may fall on your firm in respect of those people. What it requires of your firm in practice is a question for your own compliance adviser.
  • We cannot recall the copy and we do not police it. Once a pack has been downloaded, revoking the client’s consent closes our lanes; it does not reach into your systems. There is no automated control on our side that can undo a download, and we would rather say so plainly than imply otherwise.
  • The client can see the permission they gave you. It stays on their Professional Access page with its dates and state, including after it has been withdrawn or has ended, so a question about scope has a shared answer.

TheWILL.ai tells the client the same thing

The consent form the client signs says, in the same words, that a copy already taken cannot be recalled. Neither side of this workflow is being told a softer version of it.

Related

Can’t find what you’re looking for?

Our support team is here to help. Contact us and we’ll get back to you as soon as possible.

Contact us

We use cookies to improve your experience. See our Cookie policy (opens in a new tab) for details.