Workflows

The three signature workflows

Explicitly set by the operator, never computed. Signature type is an editorial decision — not a heuristic.

Why three workflows?

Tactical activities welcome a mixed audience: adults, minors, families. Forcing everyone into the same flow produces shaky signatures. Tacticat separates the cases and equips each with the right level of friction.

ADULT

ADULT — Each adult signs for themselves

The simple case, frictionless.

For offers reserved for adults (16+ or 18+ depending on your framework).

  • No account required for the participant.
  • The name confirmed at signature time prevails, regardless of the booker’s spelling.
  • The link closes automatically once the signature count reaches the reserved number.
FLOW
  1. 1

    ADULT — Each adult signs for themselves

  2. 2

    Name selection from list

    Tolerant search. E.g. "Lea's friend" → confirms their real full name when signing.

  3. 3

    Majority declaration

    No account required for the participant. No date of birth (GDPR).

  4. 4

    Reading the T&Cs / conditions

  5. 5

    Email (optional)

    Strongly recommended, not required.

  6. 6

    SIGNATURE

    Handwritten stroke (canvas) OR checkbox + full name entry.

  7. 7

    Signature saved

    Declared identity · UTC timestamp · IP + user-agent · document version · signature data · email if provided · active status · X/Y counter incremented.

  8. 8

    Immediate confirmation

    The link closes automatically once the signature count reaches the reserved number.

MINOR

MINOR — The parent signs for every child

The complex case, properly equipped.

For children’s offers (birthdays, schools, groups).

  • The parent doesn’t need a Tacticat account.
  • The child’s spot stays in “awaiting parent” status — it counts in the headcount (not squattable) but isn’t confirmed.
  • A minor never signs themselves.
FLOW
  1. 1

    MINOR — The parent signs for every child

  2. 2

    Booking created with minor participants

  3. 3

    System generates a secure sub-link per child

  4. 4

    Email sent to the legal guardian

  5. 5

    Child recap

    First name + Last name · Date of birth · Slot (site, date, time).

  6. 6

    Parental declaration

    ☐ "I certify that I am the legal guardian of this child".

  7. 7

    Reading the T&Cs / conditions

  8. 8

    Parent signature

    Handwritten stroke (canvas) OR checkbox + full name entry.

  9. 9

    Signature saved

    Child identity + birthdate · declared identity of the legal guardian · UTC timestamp + IP + user-agent · document version · signature data · active status.

  10. 10

    Confirmation

    A minor never signs themselves.

The fallback chain, configurable per operator

  1. 1Remote parental sublink — normal path
  2. 2On-site signature — if the parent is there on D-day
  3. 3Paper form — last resort only

The order and activation of each link is configured from your back-office, depending on your insurer.

MIXED

MIXED — Both workflows in parallel

For family outings, mixed groups, mixed hen/stag parties.

The system generates two independent workflows from a single booking. The organizer classifies each participant as adult or child at booking time — that’s the only place this choice exists. The two workflows then progress independently.

MIXED booking
Submitted
ADULTS
↘
Flow ADULT
Group link
CHILDREN
↙
Flow MINOR
Parental sublinks

Parent-organizer case

When the parent books for their own children, the parental flow is short-circuited.

Single global attestation, then for each child, immediate signature from the parent. An exception exists: if a child is not yours, they automatically switch to the third-party MINOR flow, and the global attestation does not cover them.

See how it’s configured on the operator side

The signature type is set when creating the offer — one checkbox, three options.

Learn more