Turn your firm's trusted Word templates into Filevine DocGen — in minutes, not weeks.
- Hours → minutes. Manual coding that takes hours of find-and-replace runs in seconds per document.
- No more broken merge fields. Codes are matched to your project's real Field List, not guessed.
- Complex coding available. Captions, ordinal dates, per-party pronouns and uppercase formatting are handled automatically.
- Nothing slips through. Unknowns are flagged in yellow so a human confirms the last 1%.
Learn how Filevine DocGen works
Use our practical guides to build a template, format dynamic values, and avoid common Word and DocGen problems.
Request access
NuvoDraft is invite-only right now. Leave your email and we'll set you up. Already approved? .
Set up Filevine DocGen for your firm
Drop your existing Word templates, answer a few questions, and we'll produce Filevine-ready versions with anything unknown flagged in yellow for your review.
Welcome to NuvoDraft
What's your firm's name? We save it with your account, so you only set this once.
1 · Your documents
Drop in the Word documents you want to turn into ready-to-use Filevine templates (.doc or .docx). Two kinds work:
- Documents that already have merge fields from other software — codes like
«code»,<<code>>, or[code]. - Plain letters or templates with case details typed in — you'll highlight each spot you want Filevine to fill.
First time? Click here for best practices
No merge codes from other software? You can still convert a plain document that has real case data typed into it. Wherever you want Filevine to fill in data, highlight that spot and label it with the field name or the information you need. The clearer the label, the better we can match it to a Filevine field. For example:
- Today's date — for the date the document is generated, type a placeholder like
Date: today's dateand highlight it (don't leave it blank). - Date of incident — write
Date of LossorDate of Incidentwhere the accident date belongs, then highlight it. - Client or party name — label it
Plaintiff Name,Defendant Name, orClient Nameso we know which person fills there, then highlight. - Page count — where you want something like
Page X of Yor a total page count, type the placeholder and highlight it.
On the next step you'll pick which highlight color marks these fill-from-Filevine spots — anything in that color gets treated like a merge field.
Drag & drop documents here
or
2 · Merge fields we found
We scanned every common way merge fields can be written. Below is what turned up — uncheck any group if those aren't really fields to fill (for example, [Exhibit A] citations that look like merge fields but aren't).
| Pattern | Found | Sample codes |
|---|
See all 0 codes found
If something doesn't look right, click here to learn more
Open one of your documents in Word. Find a line that has a merge field and paste a few words of context here, including the brackets around the code. We'll try to detect the pattern automatically — and if we can't, we'll save your example so we can add support for it.
3 · Filevine merge field list
Upload your project's Filevine DocGen Field List PDF — the list of every merge field available in your Filevine project. We use it to auto-map the fields we just found, and save it to your firm profile so you only upload it once. When you come back, it's already loaded — drop a new PDF only when your Filevine fields change, and we'll show you what changed before saving.
Using a collection section? Collection sections (repeating lists like witnesses, providers, or damages) have their own merge fields that don't appear in a standard project Field List. If this template will live on a collection section's DocGen button, generate the Field List from that collection section so those fields are included — or add a PDF that has them.
- Open the Filevine project for this firm.
- Click Menu → Advanced → DocGen Setup.
- Choose the project type, then click the section that has the DocGen button you're building this template for.
- Click the Field List button on that DocGen button.
- Filevine renders the PDF with every available merge field — save it and drop it below.
Don't have one yet? Ask the firm's Filevine administrator — every project has one.
Drag & drop the Field List PDF
or
4 · Map fields to Filevine codes
Auto-matched fields from your Field List are shown in green. For anything left, paste the Filevine code or pick highlight text (highlight for manual review), remove old brackets, or skip.
Find a code fast. This list can get long. To jump to a specific field or word anywhere on the page, use your browser's find-on-page: press Ctrl + F on Windows, or ⌘ Cmd + F on a Mac, then type what you're looking for. (Each mapping row also has its own search box for picking the Filevine code.)
How Filevine codes are built. Every Filevine merge code is the section name followed by the field name, joined by a dot. For example {{client.email1}} is the Client section's Email field, and {{casesummary.paralegal.name}} is the Case Summary → Paralegal section's Name field. So when you're hunting for a code, think of the section first — whose data is it (client, defendant, paralegal, case summary)? — then the field. That's exactly how they're named in your Field List.
Pronouns (his/her, he/she). When a document has a pronoun placeholder, that row asks whose pronoun it is — pick the party (client, defendant, …) and the grammatical form. We insert a Word IF field that fills the right pronoun from that party's gender in Filevine. The gender field is set once under Account → Document preferences. This supports Filevine's standard Male/Female values; if a party's gender is blank or something else, a neutral pronoun (they/their) is used. Prefer to fill a pronoun by hand? Switch that row to highlight text.
No contact cards or repeated field-names turned up in this batch — nothing to group here. Continue to review your matches.
No auto-matches yet — that's fine, you'll map fields on the next screen.
Nothing left to decide — every field is grouped or matched. 🎉
5 · Firm-wide rules
A couple of optional firm-wide settings — both are saved with the profile so you only set them once.
What are the org / letterhead fields, and where does Filevine fill them from?
The letterhead codes in this step — {{orgName}}, {{orgAddress1Line1}}, {{orgPhone1}}, {{orgFax1}} — pull your firm's own contact information from Filevine's organization record. Using them means your letterhead always shows the current firm name, address, and phone, maintained in one place instead of retyped into every template.
Where to enter or update your firm info in Filevine: an Org Admin opens Main Menu → Setup → Org, where the organization's name, address, and phone are managed (fax and text numbers have a dedicated Org Phone Numbers advanced tool). If these are blank in Filevine, the generated letterhead will be blank too — so fill them in there first.
Editing org details usually requires Org Admin permissions. If you can't see or edit them, ask your firm's Filevine administrator.
Firm letterhead — verbatim text → Filevine codes
If any of your documents have your firm's address/phone hard-coded (instead of as a merge field), paste the exact text once. We'll swap it for {{orgName}}, {{orgAddress1Line1}}, etc. so Filevine pulls the live values.
| Exact text in your docs | → Filevine code | |
|---|---|---|
6 · Confirm and generate
Last check before we generate the Filevine-ready files.
7 · Done — download & review
If you need to re-upload a corrected source document or adjust your field mappings, return to Step 1 and re-run the conversion — your firm profile keeps your Field List and confirmed mappings, so a re-run is quick.
NuvoDraft is free while we're in beta — re-run as many times as you need.