Back to Resources
Tutorials5 min read

Getting Started with GenDocX

From uploading files to producing a Word document: describe the task in natural language, check the result, then keep refining.

Getting Started with GenDocX

GenDocX is an AI agent centered on Word documents. You can upload existing documents, templates, and related materials, and describe the task in natural language; the agent processes the files as instructed and provides the generated or revised document. You don’t have to add placeholders to every field by hand, but you should still review the content and layout — especially for contracts, financial documents, and other important files.

Step 1: Open the workspace

After signing up and logging in, open the GenDocX chat workspace. You can describe tasks, add files, and view results in the conversation. Use a separate session for each independent task so materials and requirements from different projects don’t get mixed together.

Step 2: Upload the relevant files

Before you start, gather the files the task needs and explain the role of each one in your instructions:

  • Document to edit: a Word file whose content needs revising, whose layout needs fixing, or that needs further refinement.
  • Template: a Word file to fill in or to take the structure from.
  • Style reference: a file whose headings, fonts, paragraphs, tables, or overall layout you want the new document to follow.
  • Source materials: files that provide names, dates, amounts, facts, or clauses.

Don’t just upload a batch of files without saying what they are for. Point out which file is the template, which is for reference only, and which files are the sources of truth. For the actually uploadable formats and size limits, follow the current product interface.

Step 3: Describe the task clearly

A good instruction usually contains four things: the target file, the changes to make, the requirements that must be followed, and what to do when information is missing.

Prompts you can try

  • “Fill in the equipment purchase agreement using this contract template and the information in the two PDFs. Leave missing fields blank — do not guess.”
  • “Turn this Markdown into a Word document with a clear heading hierarchy and a table of contents.”
  • “Fix the blank pages and tables breaking across pages in this Word file. Preserve the body text as much as possible, and list what you changed.”
  • “Following the layout of this official document, generate a new file from the request content I provided. Use it as a format reference only — don’t copy the original text.”

For key fields such as amounts, dates, and party information, state explicitly which source is authoritative. If sources conflict, ask the agent to list the conflicts first rather than choosing on its own.

Step 4: Check the results

After generation, open the file and check these first:

  • Key data — names, company names, amounts, dates, reference numbers — is correct.
  • No missing fields, duplicated units, wrong substitutions, or content of unknown origin.
  • Tables, images, headers and footers, pagination, and signature/seal areas are as expected.
  • Data from the source files has been transcribed accurately and any calculations are correct.

When you find a problem, point to the specific location and the expected result. For example: “The table on page 3 is split apart — please fix the pagination without changing the table content.” This is much easier to verify than “make the layout better”.

Step 5: Save and deliver

When the result checks out, download the generated Word file. If your workspace currently offers document management or template saving, use those as needed. For important files, keep the original version and save the generated file as a new version so you can trace and compare changes later.

AI generation is not a substitute for review. Before formal use, someone with the appropriate authority should verify important facts, contract terms, and compliance content; signature, seal, and offline-confirmation areas should also go through the real-world process.

Continue reading