Event tagging

Some pay isn't about how long you worked — it's about what happened that day. Working a holiday, handling pyro, wearing a costume that carries a fee: each of these can owe a flat premium, once, because the event occurred. Function TimeTrack handles these through events, and there are two ways an event gets attached to a day:

• Automatically — for holidays, from your contract's holiday calendar.
• Manually — for everything else, by tagging the day yourself.

Both feed the same pricing step: a matching event premium on your contract fires and adds its amount to the week. The difference is only in how the event gets onto the day.

Automatic: holidays worked

Your contract carries a holiday calendar — the specific dates that count as holidays under your agreement. When you log work on a day whose date matches one of those holidays, the app automatically recognizes it as a holiday worked and fires your contract's holiday premium. There is nothing to tag.

This matters because holiday premiums are often awkward to express as a simple multiplier. A common one is one-sixth of your weekly salary, added, for each holiday worked — a flat addition, not a rate bump. The app carries the holiday calendar and the premium value separately, then combines them automatically when a worked day lands on a holiday. You just log the day normally; the premium appears in the priced week.

When a holiday lands on a weekend

Each holiday carries an optional weekend observation rule, because agreements differ on this and the US federal convention is a convention, not a law:

Leave it empty unless your paper says otherwise — an unconfigured holiday keeps behaving exactly as it always has. The contract's holiday form previews the resolved date as you change it.

Manual: tagging events on a day

Non-calendar events — pyro, a costume fee, an extra performance, a load-out premium — don't come from a date, so you tag them yourself on the day they happened.

To tag an event:

1. Open the day editor for the day in the week view.
2. Find the Event tags section.
3. Type the event code — for example PYRO or COSTUME_WORN — and click Tag. Codes are stored in uppercase, and you can add more than one to a day.
4. Remove a tag with the ✕ next to it if you tagged it by mistake.
5. Save the day.

When the week is priced, each tag is matched against your contract's event premiums by its code. If the contract has a premium configured for that code — say a flat per-performance pyro fee, or a costume fee — the premium fires and its amount is added. If nothing on the contract matches the code, the tag simply records that the event happened without changing the pay.

How the premium is calculated

However an event lands on a day — auto-detected holiday or manual tag — the premium it fires is one of two shapes:

• A flat amount per event. For example, a fixed dollar pyro fee owed once per performance. Two performances in a day with pyro means the fee is owed twice.
• A fraction of your weekly salary per event. For example, a holiday-worked premium of one-sixth of the week, added for each qualifying holiday.

Some premiums only start counting past a threshold — for instance "one-sixth of weekly for each performance beyond eight in a week." In that case only the events over the threshold, counted across the whole week, qualify.

Quick reference