Skip to main content
In Zuper, administrators can configure job card templates by defining categories, layouts, and content formatting options. The templates can be customized based on business needs, providing flexibility in format, orientation, border settings, and text styling. This guide explains how to create, edit, and manage job card templates in Zuper.
Navigation: Settings -> Modules -> Jobs -> Job Card Templates
To configure job card templates, follow these steps:
  • Select the “Settings” module from the left navigation menu.
  • Click “Modules” and select “Jobs” to open the Job Settings page.
  • Choose Job Card Templates.
Job2 Pn
  • The job card templates listing page will appear, displaying all existing templates.

​
Creating a new job card template

To create a new job card template:
  • On the job card templates listing page, click + New Template.
Job3 Pn
  • A new job card template dialog box will appear.
  • Fill in the following details:
    1. Template Name (Mandatory): Enter a unique name for the job card template.
    2. Job Category (Mandatory): Select the relevant job category from the dropdown menu.
    3. Template Description (Mandatory): Provide a brief description of the template.
    4. Format (Mandatory): Choose the document size from the available options:
      • A3
      • A4
      • A5
      • Letter
      • Legal
      • Tabloid
    5. Orientation (Mandatory): Select either Landscape or Portrait.
    6. Border Settings (Mandatory): Define the margins for the job card layout:
      • Top Border (e.g., 10mm)
      • Right Border (e.g., 10mm)
      • Bottom Border (e.g., 10mm)
      • Left Border (e.g., 10mm)
    7. Click Proceed to move to the template editor.
Editing a job card template’s content Once the template is created, you can customize the content using the Template Editor. Template editor customization options The Template Editor offers various formatting tools and components to help you design and structure your job card layout with ease. Text formatting options Basic text formatting options such as font size, font styling (bold, italic, underline, strikethrough), headers, and bullet/numbered lists are available to help you format your content effectively. Job57 Pn Additional formatting options
  1. Table: Add tables to organize and display information in a structured manner.
  2. Field Components – Easily search for and insert default system fields like:
    • Work Order Number
    • Job Priority
    • Job Description
    • Customer Email
    • Assigned to FE and more.
Once you have customized the template, click Save to successfully create your Job Card Template. Job6 Pn
Note: The Template Editor also includes a Code Mode. Switching to code mode allows you to create and edit templates directly using HTML for greater customization.Job58 Pn

​
Editing a job card template

To modify an existing job card template:
  • Navigate to the job card templates listing page.
  • Click the pencil icon next to the specific template.
Job7 Pn
  • The template editor will open.
  • Make the necessary changes.
  • Click Save to update the template.

​
Deleting a job card template

If a job card template is no longer needed, follow these steps to delete it:
  • Navigate to the job card templates listing page.
  • Click the delete icon next to the template you want to remove.
Job8 Pn
  • A confirmation dialog box will appear.
  • Click Delete to permanently remove the job card template.

​
Using dynamic variables in job card templates

Navigation: Settings → Document Templates → Job Card Templates
Job card templates in Zuper use dynamic variables to pull live data from a job directly into your document. When Zuper generates a job card, every placeholder in your template is replaced with real values — the customer name, the technician’s checklist answers, the job status, and more. You do not need a technical background to use these patterns. Each one follows the same logic: wrap the data you want in the correct set of tags, and Zuper fills in the rest when the document renders. Think of each pattern as a reusable building block. Copy it into your template, adjust the field names to match your setup, and combine patterns to build more complex layouts. This article is a reference companion to the Job Card Templates feature. For steps on creating or editing a template, see Configuring Job Card Templates.
Every dynamic variable expression sits between double curly braces: {{ }}. Expressions that open a block — such as a loop or a condition — also need a closing tag. For example, {{#each checklist}} opens a loop and {{/each}} closes it. A missing closing tag is one of the most common causes of a template not rendering correctly.
Before you start Two building blocks appear throughout every pattern in this article.
  • A field is any piece of job data you want to display — for example, {{job_title}} or {{customer.customer_first_name}}.
  • A helper is a built-in function that lets you loop through a list, compare values, split text, or format a date before it renders.
An array is a list of items that Zuper stores together — for example, all the checklist questions on a job, or all the assets linked to a work order. When a pattern in this article refers to an array, think of it as a collection you can loop through, one item at a time.
Helper quick reference Use this table as a fast lookup while you build your template.

​
Patterns

Use this pattern when you want to display the answer to a specific checklist question — for example, a pre-work photo or a remarks field. Loop through all checklist items with {{#each checklist}}, then use {{#stringEqStrict question 'Your Question Name'}} to target the exact question you want. Add one block per question you need to display.Key fields: checklist, question, answer
Example 1 — Display a photo answerUse this example when your checklist question captures one or more photos. Zuper stores photo answers as a comma-separated list of image links, so the template splits that list and renders each image individually.
Replace 'Pre-Work Photo' with the exact name of your photo question. Question names are case-sensitive — the capitalization must match what appears in your checklist exactly.
Example 2 — Display a text remarks answerUse this example when your checklist question captures a free-text response. Zuper stores multi-line text answers with a line break between each entry, so the template splits on that break and wraps each line in its own paragraph.
Replace 'Misc. Remarks' with the exact name of your text question. To display answers for additional questions, copy this block and update the question name for each one.
Use this pattern when you want to display a specific answer from an inspection form — for example, the shingle type recorded during a roof inspection, or the condition noted during an equipment check. Zuper stores inspection answers inside each service task or asset on the job. This pattern finds the answer by its field name and displays it in your document.Inspection forms can be attached to a job in two ways — through a service task, or directly through an asset. The code you use depends on where the inspection form lives.Key fields: service_tasks / assets, label, value
Service task versionWhat each line does:
Replace "JOB WALK FORM" with your task title exactly as it appears in Zuper — including capitalization. Replace the label string to pull any field by its name.
Asset versionWhat each line does:
The asset version does not need a title match step. Every asset on the job is checked automatically, and the inspection form attached to each one is read in turn. This pattern prints values from every asset inspection form associated with the job. If the job has multiple assets, each with its own inspection form, the document displays a result for each one. Review your output after generating the document to confirm the results are as expected.
Use this pattern to display a color-coded visual for each field in an asset inspection form. The template loops through the inspection data and matches each result value to a styled badge.Key fields: asset_inspection_submission_uid.data, label, value
Define .badge-pass, .badge-fail, and .badge-na in your template’s CSS section to apply colors to each result badge. Copy the example below into your template’s CSS section to get started. Adjust the colors to match your brand.
The colors above are suggestions. Replace the background-color and color values with your own hex codes to match your company’s style. The padding, border-radius, and font-weight values control the badge’s shape and size — leave these unchanged to start, then adjust as needed.
Use this pattern to show or hide sections of your template based on the job’s current status. Zuper tracks every status a job passes through, but your document only needs to reflect where the job is right now. The {{#eachLastInstance}} helper handles this — it returns only the most recent status entry so the right section renders every time.Key fields: job_status, status_name
Always use {{#eachLastInstance job_status "status_name"}} instead of {{#each job_status}}. Plain {{#each}} renders your content once for every status transition the job has ever had, not just the current one.
Add more {{#stringEq status_name "..."}} blocks for any custom statuses in your workflow.
Use this pattern when you want every checklist item to appear automatically as a two-column row — question on the left, answer on the right — without listing question names individually.Key fields: checklist, question, answer, type
Example 1 — Display a specific checklist answer as textUse this when you want to show the answer to one specific checklist question as plain text in your document. In this example, the question is “Work completed notes.”
This displays one row — the question on the left, the text answer on the right. All other checklist items are skipped.
Example 2 — Display a specific checklist answer as an imageUse this when the answer to a checklist question is a photo captured by the field executive. In this example, the question is “Site photo.”
This displays one row — the question on the left, the photo on the right. Replace "Site photo" with the exact question text from your checklist.
Use these examples when you need a single specific checklist item. To display all checklist items at once, use the full dynamic loop in Pattern 5 above.
Use these placeholders to display the most commonly used job, customer, and organization fields anywhere in your template.Job detailsCustomerAddressAssigned technicianOrganization
Every placeholder above is optional. Wrap any placeholder in {{#if field}}...{{/if}} before adding it to your template. This prevents empty gaps in your document when a field has no value on a particular job.
Use formatDateWithTimeZone to display any date field in a readable format. Always pass timezone as the third argument so dates display in the customer’s local time zone.Syntax: {{formatDateWithTimeZone field "FORMAT" timezone}}
timezone is a job-level field that Zuper populates automatically. Omitting it causes dates to display in UTC instead of the customer’s local time zone.
Use this pattern to display job-level custom fields. You can display a single field by its name, display all fields of a specific type, or display fields that belong to a specific group.Key fields: custom_fields, label, value, type, group_name
Example 1 — Display a specific custom field by nameUse this example when you want to display one specific custom field — for example, the invoice amount paid on a job. The template finds the field by matching its exact label and displays its value.
Replace "Invoice amount paid" with the exact label of your custom field as it appears in Zuper — including capitalization.
Example 2 — Display all fields of a specific typeUse this example when you want to display all custom fields of a given type — for example, all time fields or all multi-line text fields. The template loops through every custom field and renders each one that matches the type you specify.
Add a {{#stringEqStrict type "..."}} block for each custom field type you use. Types you do not include produce no output and do not cause errors.
Example 3 — Display fields from a specific group by labelUse this example when your custom fields are organized into groups in Zuper — for example, a group called “Payment Details” that contains fields like “Invoice amount paid” and “Payment method.” The template finds the group by name, then looks up the specific field you want by its label.
Replace "Payment Details" with your group name exactly as it appears in Zuper. Replace "Invoice amount paid" and "Payment method" with the exact labels of the fields you want to display from that group. Add one {{#stringEqStrict label "..."}} block for each additional field you need.
Think of a nested loop like a folder inside a folder. The job is the outer folder. The checklist is the inner folder. When you are working inside the inner folder, Zuper can only see what is in that folder — not what is in the outer one.Use ../ before a field name to step out one level and pull in fields from the job level — for example, the job title or work order number.
A missing ../ is one of the most common reasons a field renders blank inside a loop. If a field is showing as empty and you are inside a {{#each}} block, check whether it needs a ../ prefix.

​
FAQs

The most likely causes are that the field has no value on that job, or the field is inside a loop and needs a ../ prefix to reach the parent scope. Wrap the field in {{#if field}}...{{/if}} to confirm whether it has a value. If you are inside a {{#each}} block, add ../ before the field name and test again. If the issue continues, contact Support.
Check for two things. First, confirm you are using {{#eachLastInstance job_status "status_name"}} and not {{#each job_status}}. Plain {{#each}} repeats the section for every status the job has ever had. {{#eachLastInstance}} shows only the current one. Second, confirm your {{#stringEq status_name "..."}} filter is present and the status name matches exactly what appears in Zuper — including capitalization. A missing or mismatched filter causes the section to show nothing or display the wrong content.
{{#stringEq}} performs a loose match and is not case-sensitive. Use it for status name comparisons such as “Completed” or “Scheduled.” {{#stringEqStrict}} performs an exact, case-sensitive match. Use it when matching question names, inspection labels, or result values such as “Pass,” “Fail,” or “N/A.”
Yes. The most common combination is nesting Pattern 1 (checklist loop) or Pattern 2 (inspection results) inside a Pattern 4 job status block. This lets you show checklist photos only when a job reaches a specific status, for example.
Use {{formatDateWithTimeZone field "FORMAT" timezone}}. Always include timezone as the third argument — it is a job-level field that Zuper populates automatically. Omitting it causes dates to display in UTC instead of the customer’s local zone. See Pattern 7 for format token examples.