Creating and uploading a template

Owners and adminsUpdated 22 Oct 2026

Build a template from a built-in one or from your own Word document, then import it.

#What you'll need

  • Microsoft Word, or another editor that saves .docx files.
  • Basic familiarity with Jinja, or a colleague who has it.
  • A role of owner or admin. Other members can see templates but not import them.

#Getting started

Pick one of two approaches:

  • Start from a built-in template and change it to your taste.
  • Convert your existing Word template into a Sourcemint template.

Either way, download the built-in template from Templates → DOCX templates and keep it open as a reference. It already handles the common cases, such as hiding a section when it is empty, and it shows how to write loops and conditions.

#Converting your own template

  1. Find the information you want filled in automatically, such as the summary.
  2. Replace the fixed text with a tag from the variables reference, for example {{ summary }}.
  3. Save the file as .docx.

#Repeating and hiding sections

Wrap a block in a loop to repeat it for every entry, and in a condition to show it only when there is something to show:

Experience with a condition
{% if experience %}
{% for exp in experience %}
{{ exp.company }}  {{ exp.from }} – {{ exp.to }}
{% endfor %}
{% endif %}

To repeat a table row for every entry, put {%tr for item in items %} alone in the row above it and {%tr endfor %} alone in the row below it. The row between them repeats.

#Importing the template

  1. Open Templates → DOCX templates and choose Import template.
  2. On the File step, drop your .docx file or choose Choose file.
  3. On the Check step, wait for Sourcemint to validate the file and render a preview.
  4. On the Name step, give the template a descriptive name, such as Outbound US, and save it.

The file can be up to 100 MB. Imported templates appear under Your templates.

#What the check verifies

  • It is a valid .docx file that contains at least one tag.
  • Every {{, {% and {# is closed.
  • It renders with a sample profile.

A file that fails is not saved. Fix the problems the check lists and import the file again.

#Fixing template errors

The check shows each problem with the text it found. The most common ones are:

  • A tag is not closed. A tag that opens with {{ needs }}, and one that opens with {% needs %}. Add the missing end.
  • Invalid syntax. The message names what Jinja did not expect. A loop needs its {% endfor %} and a condition needs its {% endif %}, and a misspelled tag name such as endloop is reported.
  • A field refers to data that does not exist. This happens when you read a part of something that is not there, for example {{ exp.company }} outside its {% for exp in experience %} loop.
  • The file contains no tags. Add at least one tag, such as {{ first_name }}.

#Preview and default

Each template in Your templates has actions to preview it, download its original file, rename it and delete it. A preview renders the template with a fictional sample profile. Choose the organization's default template in the card at the top of the page. It is the one marked Default when someone downloads a profile.