Template Designer

Templates define the content and instructions that REV23 uses to guide a customer through signing a form. A Template is the blueprint used to present information to the customer and collect their signature. Once completed, the signed result becomes a Form.

Templates are made up of several key concepts: steps, fields, messages, sections, blocks, and a set of additional settings.

Steps are the virtual pages a customer moves through as they progress through a template in Kiosk (iOS) or Web Sign (browser).

For example, the Identification step prompts the customer to provide a photo ID scan, ID number, and expiration date.

Fields are the individual values displayed and collected within a step. For example, ID Number and Expiration Date are fields, as well as Middle Name, Address, etc.

Steps and their available fields are predefined by REV23, but you can customize their visibility and whether they are required where appropriate.

A block is content you want the customer to interact with, such as:

• Text they must read (a paragraph)
• A statement they must agree to (a checkbox, initials)
• A question they must answer (a date, time, text, etc.)

A section is a group of related blocks. Sections are used to visually organize content and separate related ideas.

Note

Blocks appear on the Disclaimers step near the end of the signing flow.

Depending on your needs, a template can be very simple (a single section with one paragraph block) or more complex, with multiple sections and a longer questionnaire. The structure is entirely up to you.

The outline of a template design looks like this:

Sections
└─ Section 1 (At least one section is required per template)
   └─ Block 1 (At least one block is required per section)
   └─ Block 2
   └─ Block 3
└─ Section 2
   └─ Block 1
   └─ Block 2

Let’s look at a practical example:

- Start Message
    "Welcome to Pawnee Tattoo! Please fill out this form..."

Sections
└─ Disclaimers
   └─ Paragraph: "By filling out this form you are agreeing to the following..."
   └─ Yes/No: Are you pregnant or breast-feeding?
   └─ Yes/No: Are you allergic to latex?
   └─ Time: When did you last eat?
└─ Additional Release
   └─ Initials: Photo consent
   └─ Initials: I verified spelling of tattoo if applicable
└─ Parent/Guardian Section
   └─ Document: Scan a copy of the birth certificate

- Finish Message
    "Thank you! Please hand the device back to studio staff and we will begin your service shortly!"

Revisions

Each template can have multiple revisions, but only one revision is active at a time. The active revision is the version customers see when they sign a release form.

How revisions work

When you edit a template that has already been used to sign forms, REV23 protects the integrity of those signed documents. Instead of modifying the active revision, a new draft revision is created with your changes. The active revision remains unchanged until you explicitly activate the new one.

If the template has not been used yet (no signed forms), your changes are saved directly to the current revision.

Activating a revision

Draft revisions are not used during signing until you activate them. When you are ready for customers to see the updated template:

1. Open the Revision History from the template designer.
2. Find the draft revision you want to go live.
3. Click Activate and confirm.

The previous active revision becomes inactive but is preserved in the revision history. You can switch back to any previous revision at any time.

Revision history

The revision history shows all revisions for a template, including:

• Which revision is currently active.
• How many forms have been signed with each revision.
• When each revision was created.

You can view, activate, or export any revision from this list. This gives you a complete audit trail of how your template has evolved over time.

Safe to edit

You cannot break a live form by editing a template. Changes are saved as a draft revision that is not used until you explicitly activate it. Previously signed forms remain tied to the revision they were signed with, so historical records are never affected by your changes.

Settings

The Settings tab contains three cards: Age Requirements, Web Sign, and Print Settings.

Age Requirements

You can define customer age rules for completing a form directly within the template. Two settings control this behavior:

• Required Age The age a customer must be to complete the form without a parent or guardian.

  • In most cases, this is 18.

• Minimum Age The minimum age a customer must be to complete the form with a parent or guardian present.

  • If left blank: The service is not offered to minors at all, even with a parent or guardian present.
    • Example: If you do not tattoo minors under any circumstances, leave this blank.
  • If set: Specifies the youngest age allowed with a parent or guardian.
    • Example: If you pierce minors but require them to be at least 8 years old, set this to 8.
    • If there is no minimum age, set this to 0.

Web Sign

These settings control whether and how the template is available through Web Sign.

• Enable web signing When enabled, customers can fill out this template from a browser using your studio’s Web Sign URL.

• Allow guardian web signing When enabled, guardians can co-sign remotely from a separate device when a minor requires a guardian.

• Redirect URL If specified, the Continue button at the end of signing redirects the customer to this URL. If blank, the Studio URL is used instead. If no studio URL exists, the Continue button is hidden.

Print Settings

• Paper Size The paper size used when generating the document.

  • Letter (8.5 x 11)
  • Legal (8.5 x 14)
  • A4

• Print studio logo If enabled, your studio logo (as configured in Studio settings) is printed in the document header.

• Print medical conditions If enabled, the medical conditions table is included on the generated document. This is different from the Medical Conditions step visibility.

  • Compact format — Uses a condensed layout for the medical conditions table.

• Print supplies used If enabled, supplies tracked in the session (needles, ink, jewelry, etc.) are printed on the generated document.

Messages

Each template includes three designated messages: Start, Guardian, and Finish. These messages are shown to the customer during the signing flow only — they do not appear on the generated release form.

• Start Message — Appears as the first step. Use it to welcome the customer and provide instructions (e.g. “Please lay your ID flat on a dark surface. Do not hold it with your hands.”).
• Guardian Message — Appears after the Start Message, but only when a guardian is required.
• Finish Message — Appears after the form is completed. Typically used to thank the customer and explain what to do next.

You can define separate messages for REV23 Cloud (iOS) and Web Sign experiences. For example, “Please hand the iPad back to your artist” would not make sense on a web form. See Kiosk & Web Sign for more on the differences between the two experiences.

Steps and Fields

Steps are the pages a customer moves through during the signing flow. Fields are the individual values within a step. Both are predefined by REV23 Cloud, but you can customize their visibility and requirements through the template settings.

Visibility and Requirement Rules

Steps and fields share the same visibility and requirement options:

Visible / Required Controls whether the step or field is shown, and whether it can be skipped or left blank.

Guardian Visible / Guardian Required Optionally overrides visibility or requirement when the customer is a minor. When checked, the guardian-specific rule applies. When unchecked, it falls back to the primary setting.

Error Message Optionally customize the message shown when a customer tries to continue without completing a required step or field. If not set, REV23 displays a built-in default.

Step Visibility Priority

A step’s visibility always takes precedence over its fields:

• If a step is hidden, none of its fields are shown.
• If a step has no visible fields, the app automatically hides the step.

Continue Previous Service

The Continue Previous Service step (ServiceSession.IncompleteServices) controls whether returning customers with incomplete services are prompted to continue a previous service or start a new one. See Continue Existing Service for how this step appears in the signing flow.

• Visible (default) — The prompt is shown, and the customer can choose to continue an existing service or start fresh.
• Hidden — The prompt is skipped entirely. The customer always starts a new service.

This step also supports Guardian Visible, so you can configure different behavior for minors.

Note

The prompt is only skipped when all templates mapped to service types in the selected category hide this step. If any template in the category leaves it visible, the prompt still appears. This ensures backwards-compatible behavior across mixed template configurations.

Cloud Rules

Some rules are enforced by REV23 Cloud and cannot be overridden by template settings:

• The Customer Picture step is always hidden for customers under 18.
• If the Medical Conditions step is visible, the Required setting has no effect (it is always required).
• If no Sources or Medical Conditions are configured in Settings, those steps are hidden.
• Guardian Signature is only shown when a guardian is required. Whether it appears is controlled by the Guardian Signature field visibility in the template. It is enabled by default in all default templates.
• Provider Signature is always hidden on Web Sign.

Sections

A section is a logical grouping of blocks. Each section has options that control layout in the signing flow and in the generated PDF.

• Title — Shown during signing and printed as a section header on the document.
• Break Page — If checked, this section begins on a new page in the generated document.
• Parent/Guardian Section — If checked, this section only appears when a guardian is required. See Guardian Behavior.

Blocks

Blocks are the actual content of a form — text the customer reads or questions they answer.

Block Type	Purpose
Paragraph	A block of text to read.
Initials Entry	The customer’s typed initials. In a Parent/Guardian Section, requires the guardian’s initials instead.
Text Entry	A short, single-line text response.
Multi-Line Entry	A longer text response.
Select Entry	A dropdown/popup to choose from predefined values. You must add items to the list.
Yes/No Entry	A yes or no question with optional answer enforcement.
Yes/No & Text Entry	A yes or no question with a text field for details. Also supports the Answer setting.
Date/Time Entry	A date and time value.
Date Entry	A date-only value.
Time Entry	A time-only value.
Photo Upload	Upload a photo (camera on iOS, file upload on web). Included directly on the generated document.
Document Upload	Upload or scan a document (document scanner on iOS with auto-crop/straighten, file upload on web). Included as a link on the generated document.

All blocks (except Paragraph) share these common options:

• Required — A value must be provided before the customer can continue.
• Provider Review — The block and its response will be highlighted for the provider when reviewing the form before starting the session.

Initials Entry

A block that requests the customer’s initials. For example, “John Doe” must enter JD.

If placed in a Parent/Guardian Section, the guardian’s initials are required instead.

Select Entry

A dropdown or popup that allows the customer to choose from a list of predefined values. You must add items to the list before the block can be used.

Yes/No Entry

A yes or no question with an additional Answer setting that enforces a specific response:

• Any — The customer can answer Yes or No (default).
• Yes — The customer must answer Yes to continue.
• No — The customer must answer No to continue.

For example, “Are you currently pregnant or breast-feeding?” with Answer set to No will prevent the customer from proceeding if they answer Yes.

The Answer setting is independent of Required. Required controls whether the customer must make a selection at all; Answer controls which selection is accepted.

Template Mappings

After creating your template, you must map it to a Service Type so REV23 Cloud knows which template to use for each service.

See Template Mappings for more information.

Tokens

You can insert tokens into messages and blocks to use dynamic data from your studio. Tokens are wrapped in double curly braces {{ }} and are replaced immediately before the form is shown to the customer. This is especially useful in multi-studio environments.

For example, a Start Message written as:

Welcome to {{studio.name}}!

Please fill out the form and ask your artist if you have any questions!

Will display as:

Welcome to Pawnee Tattoo!

Please fill out the form and ask your artist if you have any questions!

Name	Token
Studio Name	studio.name
Studio Short Name	studio.shortname
Studio Address	studio.address
Studio Phone Number	studio.phonenumber
Studio Email	studio.email
Studio URL	studio.url

Note

Tokens are based on studio data only. You cannot use tokens based on information the customer provides.

Guardian Behavior Summary

A guardian is required when the customer does not meet the Required Age but does meet the Minimum Age defined in the template’s age requirements. If the customer does not meet the Minimum Age, service types mapped to the template are not visible at all.

When a guardian is required, REV23 Cloud automatically adjusts the flow:

• A Guardian Details step is injected (not configurable).
• Steps and fields with Guardian Visible or Guardian Required settings apply their minor-specific rules. See Visibility and Requirement Rules.
• Sections marked as Parent/Guardian Section are shown (hidden for adults).
• Initials blocks in a Parent/Guardian Section require the guardian’s initials instead of the customer’s.

Markdown

Markdown is a simple way to format text using plain characters. You can use Markdown in template messages and block text to add emphasis, structure, and readability to your release forms without needing any design tools.

Here are the most common formatting examples:

What you type	What the customer sees
**Bold text**	Bold text
_Italic text_	Italic text
**_Bold and italic_**	Bold and italic
# Heading	A large heading
## Smaller Heading	A smaller heading
- Item one	A bulleted list
1. First item	A numbered list
> Important note	A blockquote (indented text)

Unsupported elements

For security and consistency, some Markdown features are intentionally disabled in templates:

Element	Supported
Emphasis, bold, italic	Yes
Paragraphs	Yes
Headings	Yes
Blockquotes	Yes
Lists and nested lists	Yes
Code formatting	Yes
Links	No
Images	No
HTML	No

Learn more about Markdown at: https://commonmark.org/help/