Frequently asked questions

It turns the Word documents your firm already uses into Filevine DocGen-ready templates — whether they're full of merge codes from other software (like «code», <<code>>, [code], or Word MERGEFIELDs) or plain letters with case details typed in. It scans your documents, auto-matches each merge field to a Filevine field from your project's Field List, and lets you confirm or adjust every mapping. Anything it can't match is highlighted yellow for manual review.

We will have guidance throughout the process. If your document is a plain letter with real case data typed into it, you can still convert it. Wherever you want Filevine to fill in data, highlight that spot and label it with the field name or information you need (e.g. Date of Loss, Client Name). On the Merge fields step you pick which highlight color marks these "fill from Filevine" fields, and we map them like merge fields.

The Field List is the list of every merge field available in your Filevine project — we use it to auto-map your merge fields. To get it: in Filevine, open Menu → Advanced → DocGen Setup, drill to the Project Type → Section → Doc Generation button your template is for, and click that button's Field List. Save/export it and upload it on the Field list step. We save it to your firm profile so you only upload it once — drop in a new copy only when your Filevine fields change.

We accept Source templates: .doc and .docx. The Filevine Field List is uploaded as a PDF. Picked the wrong document? On the Documents step, click the × next to any file to remove it.

On the Map fields step, codes we matched confidently appear in green. For anything left, type to search your Field List, paste a Filevine code, or choose flag yellow (highlight for manual review), delete (remove the brackets), or skip. A 💡 button shows alternative suggestions when we have them.

Every Filevine merge code is the section name followed by the field name, joined by a dot — e.g. {{client.email1}} is the Client section's Email field, and {{casesummary.paralegal.name}} is Case Summary → Paralegal's Name. When searching, think of the section first (whose data is it?), then the field. Tip: use your browser's find — Ctrl + F (Windows) / ⌘ Cmd + F (Mac) — to jump around a long list.

It leaves the code highlighted in yellow in the generated template so a person can fill it in manually later. Use it when no Filevine field fits, or when you want a human to decide. Anything still yellow in a generated document needs that human review before the document goes out.

Yes. When you map a date field (including today's date), a format dropdown appears on that row. Choose short (6/7/2026), numeric with leading zeros (06/07/2026), long (June 7, 2026), ordinal (June 7th, 2026 / June the 7th, 2026), or a single component — month name, month number, day, or year. The default is short date. This works on any Filevine date field — birth date, trial date, incident date, etc.

When a placeholder reads today's date, current date, or a letter's dateline, the wizard recognizes it and maps it to Filevine's built-in TODAY code automatically — you don't have to find a field for it. You can also pick Today — document generation date from any row's search box. Filevine fills the generation date from TODAY, and you can apply any of the same date formats to it. Ordinal phrasing like "this 7th day of June, 2026" is generated with the confirmed Filevine workaround (native month/day/year codes plus a small nested field for the st/nd/rd/th suffix).

When a document contains a pronoun like his/her, that mapping row asks whose pronoun it is. You pick the party (client, defendant, etc.) and the grammatical form, and we insert a Word IF field that fills the correct pronoun from that party's gender in Filevine when the document is generated — no manual editing needed.

Which gender field is used? The field is set once under Firm Profile → Document preferences ("Gender field"). We suggest matches from your Field List, and you can type your own if your firm names it differently. It's applied consistently to every party (e.g. the defendant's and the client's gender fields).

Supported values. Pronoun automation supports Filevine's standard Male and Female values. If a party's gender is blank or set to something else, a neutral pronoun (they / their / them) is used. If you'd rather fill a pronoun by hand, switch that row to highlight text and it'll be yellow-flagged in the output instead.

1. Open DocGen Setup — Menu (top-left) → Advanced → DocGen Setup.
2. Drill to the button — Project Type → Section → the specific Doc Generation button. (No button yet? Add a Doc Generation widget to that section in the Customs Editor first.)
3. Upload the template — upload your generated .docx to that button. Optionally check its Field List to confirm the codes.
4. Generate from a real project — open a project of that type (or a sandbox) with representative data and click the button to generate the document.
5. Proofread — confirm fields populated, no leftover codes or yellow placeholders, conditional/date fields correct, formatting intact.
6. Need a fix? Come back, adjust your mappings, download the new template, and re-upload it to the same DocGen button — then test again.

Yes. Return to the Documents step, adjust your mappings or re-upload a corrected source document, and re-run — your firm profile keeps your Field List and confirmed mappings, so a re-run is quick.

Your firm's workspace is private to your account — other firms can't see your documents, Field List, mappings, or generated templates, and NuvoDraft does not publicly share any of them. Files are stored encrypted and transferred over HTTPS.

What's kept, and for how long: uploaded source documents and generated templates stay in your workspace so you can re-run and download them, and are automatically deleted after 90 days. Your recent job history (results and their download links) clears after 30 days. You can also remove any uploaded file yourself on the Documents step.

What your firm profile saves so future batches are faster: your firm name and document preferences, confirmed mappings, and your Filevine Field List. Those stay until you change or delete them — your case documents are never part of the profile.

NuvoDraft processes the documents and Field List you upload in order to run your conversion — they're used to generate your Filevine-ready templates and your job history, and they're stored in your firm's private workspace, isolated to your account. Upload documents only if you're authorized by your firm to use them with NuvoDraft.

No. NuvoDraft is an independent tool for firms that use Filevine DocGen. NuvoDraft is not affiliated with, endorsed by, or operated by Filevine.

No. NuvoDraft never connects to your Filevine account and has no access to it. It creates Filevine-ready Word templates that you download and upload into Filevine yourself — it does not change your Filevine projects, fields, buttons, templates, or account settings.

You may need help from a Filevine administrator to export the right Field List (DocGen Setup access), fill in your firm's org letterhead fields (Org Admin), add a Doc Generation widget to a section, or upload templates to the right DocGen button. NuvoDraft guides the template conversion — your firm controls Filevine permissions.

NuvoDraft is in invite-only beta right now. Request access from the website, and approved users can log in from any page.

Use the Request access form on the homepage (it's also an option in the log-in window), enter your email, and confirm that you agree to receive beta-access emails. If NuvoDraft is a good fit for your firm, you'll receive an invitation email to set up your login.

No. Requesting access asks for your email and your consent to receive beta-access emails — no credit card or payment details are requested at any point right now.

Yes — while NuvoDraft is in invite-only beta, it's free for approved firms. There's no credit card and no charges during the testing period. Paid plans will arrive as NuvoDraft leaves beta, and we'll give beta firms plenty of notice before anything changes.

NuvoDraft is in invite-only beta and free for approved firms while we're testing, so there's nothing to pay right now. We haven't published paid plans yet — when NuvoDraft leaves beta, pricing will be shared, and we'll give beta firms plenty of notice first.

Each document conversion produces a generated Filevine-ready .docx template with your confirmed mappings and yellow review flags on anything that needs human review. While NuvoDraft is in beta you can re-run a document as many times as you need at no charge.

Filevine supports merge docs from many sections, but collection sections are limited. If you want data from a collection section, make sure to add the Doc Generation widget inside that collection section — otherwise Filevine has nowhere to pull that data from.

Tip: collections are custom fields where you can add multiple items. Typically these include medicals, insurances, and expenses, to name a few.

• Renamed or deleted fields. If a Filevine field was renamed or removed after you exported your Field List, the code won't match and the spot comes out blank. Re-export a fresh Field List for that DocGen button and re-map.
• Field List from the wrong button. The Field List is specific to each Project Type → Section → Doc Generation button. Using a list from a different button means codes that don't exist there — pull the list from the exact button this template is for.
• Collection data not pulling. Data from a collection (medicals, insurances, expenses, etc.) is blank when the Doc Generation widget isn't inside that collection section. Add the widget there. (See the limitation above.)
• Leftover yellow placeholders. Anything highlighted yellow in the generated template was never mapped to a Filevine field — go back to the Map fields step and map it, delete it, or fill it in by hand.
• Blank letterhead / org fields. {{orgName}}, {{orgAddress1Line1}}, etc. pull from your firm's Filevine org record. If they're empty, an Org Admin must fill them in under Main Menu → Setup → Org first.
• Wrong or missing pronouns. Per-party pronoun fields resolve from that party's gender field. If the gender isn't set on the contact card, the pronoun renders blank or defaults — set it on the project before generating.