Public Demo
You are welcome to explore this solution. Prior to official go-live, you may use it freely — however, your data may be lost in future updates. No guarantees or liability are given. Use at your own discretion.
Intermediate

Speed up intake with request templates

Turn a recurring request pattern into a template with duration and pre-set criteria, then spawn consistent requests from it.

Outcome

A template capturing one of your recurring work patterns — duration and requirement values included — and a request created from it that arrives pre-filled and correct.

Before you begin

  • The Editor or Admin role.
  • A criteria vocabulary worth bundling — Match requests to the right resources builds one.
  • A genuinely recurring pattern. Templates pay off through repetition; a one-off doesn’t need one.

Step 1 — Identify the pattern

Good template candidates share a duration and a requirement set: weekly line maintenance — 4 hours, needs Crane, operator training — 1 day, needs Projector, capacity ≥ 12. Write down the duration and the criteria values before opening any dialog.

Step 2 — Create the template

  1. Open Settings → Templates and choose Add Template.
  2. In Create Request Template:
    • Name — say what it spawns: Line Maintenance (4h).
    • Description — when to use it.
    • Minimal Duration — the number and unit (Hours, Days, …). Placements shorter than this raise a Below Minimum Duration conflict later — it is a floor, not a suggestion.
    • Under Criteria, pick each criterion and set its value — these become the spawned requests’ requirement values.
  3. Create Template.

Step 3 — Spawn a request from it

Create a new request using the template: duration and requirements arrive pre-filled, and intake becomes name it, place it, done. Check the request’s Requirements section once to confirm the values came through as intended.

Step 4 — Maintain the library

  • Template edits affect future requests only — existing ones keep their values. Safe to refine continuously.
  • Deleting is likewise non-retroactive (“This action cannot be undone.” refers to the template).
  • Keep the list curated: one template per real pattern, named by what it produces. Search covers you as it grows.

Distributing templates

Templates travel with Export/Import (CSV/JSON — see Import and export) and ride inside presets alongside criteria and groups — so a standard template library can ship to every workspace you run.