Consent Kit

Get started

Ask for consent

Org Templates

Security

How do Org templates work?

Org Templates are a bit of a conceptual leap from more traditional consent forms.

As part of our research, we got to look at different consent forms across many industries. What was particularly interesting was how consent forms varied within a single organisation, from project to project.

We started to notice patterns:

Org template lifecycle

Define your org template, generate a form, ask for consent

  1. Define your Org Template to generate consent forms
  2. Each time an event is created, we use your template to generate a context specific consent form
  3. When you ask for consent, we attach the appropriate signature mechanism (email,in person or paper), create a unique instance of the form for each participant, and automatically setup your audit trail

Template components

Org templates are made up of three main components: Sections, Liquid (objects and tags) and Placeholders.

Sections

Sections are the building blocks of your template. Consent Kit has the following sections:

Content sections enables you add headers, text, Placeholders, Liquid objects and Liquid tags into your template.

Content Section

Question sets enable you to ask more granular questions of your participants. They will be converted to checkboxes before being sent to the participant. You can add and remove questions by clicking the Add (5) or Remove (6) buttons.

Content Section

You can add or remove Sections (7) from the top right corner of any existing section.

You cannot delete the following sections:

Placeholders

For the parts of the form which can’t be re-used, we use Placeholders to prompt the person creating the form to fill in more information, specific to the project.

Placeholders can be added to any text in a Content section. To add a Placeholder, select the text you want to turn into a Placeholder (1) and click on the Placeholder button (2).

Adding a placeholder to a consent template

Liquid

We use an open source templating engine called Liquid to populate your consent templates with dynamic content.

At a very basic level, Liquid is made up of things called Objects and Tags.

Objects can be used to populate a consent form with information about the researcher (name, email), the project (name, client) or the organisation (name).

Tags can be used to add conditional logic to your templates, eg: If this is true, then use this content, else, use this content. This is particularly useful for populating parts of the form depending on the type of research method being used.

It might seem a little daunting at first, but it’s pretty straightforward once you understand some basic principles. Check out What is liquid for more information on how it works.