DocuSign Document Generation Not Working? Fix Word Template Merge Fields Not Replacing Values

How I Fixed the Issue of Merge Fields Not Working When Uploading Documents Directly in DocuSign

Recently, I ran into a frustrating issue while working with DocuSign. Whenever I uploaded a Word document directly (for example, a simple file containing {{ name }}), the merge fields refused to update. Everything looked correct, but DocuSign simply didn’t replace the placeholders with actual values.

After investigating, I discovered the real reason: The document wasn’t recognized as a Document Generation–enabled document. And because of that, DocuSign ignored the merge fields entirely.

Once I studied the updated DocuSign document generation workflow, I realized that the way we upload Word files has changed. If you upload a document directly into a template without preparing it correctly, DocuSign will not activate the merge functionality.

To save you the same trouble, here’s the exact method that worked for me.

The Correct Way to Prepare and Upload a Document for DocuSign Document Generation

1. Open Your Document in Microsoft Word (Not Google Docs)

DocuSign’s merge engine only supports Word files that have been prepared using the right tools. Google Docs won’t embed the merge field metadata required for DocGen, so make sure you start with Microsoft Word.

2. Install the “Document Generation Template Assistant” Add-on

DocuSign provides an official Word add-in called Document Generation Template Assistant. Install it from the Microsoft Store inside Word.

This add-on lets you insert merge fields, validate your document, connect your DocuSign account, and prepare the file for Document Generation. Without this tool, your Word document will not be marked as DocGen-enabled.

3. Connect Your DocuSign Account Through the Add-on

After installing the add-on, log in using your DocuSign credentials. This creates a direct link between your Word document and your DocuSign templates, ensuring accurate field mapping and metadata handling.

4. Test and Replace Your Document Inside an Existing DocuSign Template

The Word add-on allows you to replace the existing document inside a DocuSign template with your updated file. This step is important because it keeps the template’s field mappings intact and ensures that the document gets registered as Document Generation Enabled.

Once I replaced the document through the add-in instead of uploading it directly, all my merge fields started working perfectly.

Final Thoughts

This updated workflow made the entire process smoother for me. If your placeholders like {{ name }} aren’t merging, there’s a good chance your document isn’t registered as a DocGen-enabled file.

Using the Document Generation Template Assistant add-on inside Word is the most reliable way to ensure your file is prepared correctly before sending it to DocuSign.

I hope this guide helps you resolve the issue just like it did for me.