Templates

What a template holds

Everything the composer can set except the page and the exact time — the offset, the repeat rule, the early warning, the priority, the tag, the folder. Anything a template does not have an opinion about is left to your normal defaults.

That last part matters. A template is not a full reminder with blanks; it is a set of statements, and the ones it does not make fall through to the layer beneath.

Making one

Settings → Organising → Templates. Give it a name that says when you would reach for it — Ticket drop, Invoice chase, Read this weekend — rather than what it contains.

Applying one

Pick it in the composer and the fields fill in. Everything stays editable — a template is a starting point, not a lock, and changing a field after applying one is normal.

Applying a template to an existing reminder changes that reminder only. Editing the template later does not reach back and rewrite reminders you already made from it, which is deliberate: a saved reminder is a decision you made, and a settings change should not silently rewrite your decisions.

Where it sits against other defaults

Four things can have an opinion about a new reminder's fields, and they resolve in one fixed order, strongest first:

1. What you typed on the reminder itself
2. The template you applied
3. A per-site rule matching the page
4. Your global defaults
5. Latr's built-in defaults

So a template beats a site rule. If you apply the Ticket drop template on a site that has its own rule, the template wins on every field it speaks about, and the site rule still supplies the ones it does not.

Templates or per-site rules?

They compose. A site rule can fill the form in the moment you open the composer, and a template can override part of it when this one is different.