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
You have a template that captures one of your recurring work patterns, with the duration and the requirement values included. You then create a request from it that arrives pre-filled and correct.
Before you begin
- The Editor or Admin role.
- A criteria vocabulary that is worth bundling. Match requests to the right resources builds one.
- A genuinely recurring pattern. Templates pay off through repetition. A one-off does not need one.
Step 1 — Identify the pattern
A good template candidate has a shared duration and a shared requirement set. For example:
weekly line maintenance — 4 hours, needs Crane, or operator training — 1 day, needs
Projector, capacity ≥ 12.
Write down the duration and the criteria values before you open any dialog.
Step 2 — Create the template
- Open Settings → Templates and select Add Template.
- In Create Request Template, fill in these fields:
- Name — say what it produces, for example Line Maintenance (4h).
- Description — when to use it.
- Minimal Duration — the number and the unit (Hours, Days, and so on). A placement shorter than this raises a Below Minimum Duration conflict later. It is a floor, not a suggestion.
- Criteria — select each criterion and set its value. These become the requirement values of the requests you create from the template.
- Select Create Template.
Step 3 — Create a request from it
Create a new request and use the template. The duration and the requirements arrive pre-filled, so intake becomes: name it, place it, done.
Check the Requirements section of the request once, to confirm that the values came through as you intended.
Step 4 — Maintain the library
- A template edit affects future requests only. Existing requests keep their values. You can therefore refine a template continuously and safely.
- A deletion is also not retroactive. “This action cannot be undone.” refers to the template.
- Keep the list curated. Use one template per real pattern, and name it by what it produces. As the list grows, search finds them for you.
Distribute templates
Templates travel with Export/Import, as CSV or JSON. See Import and export.
They also ride inside presets, next to criteria and groups. A standard template library can therefore ship to every workspace you run.