Storm In-Editor can configure the full formula layer for timesheet templates — overtime tiers, shift-loading, pay rate multipliers, and weekly totals — based on your instructions. The most important thing to get right before prompting is identifying which timesheet pattern your template uses, since each pattern uses completely different formula logic.
Which timesheet type do I have?
There are two fundamental timesheet types:
Type | Row shape | Formula logic | Template types |
Single entry | One row per shift (one worker, one shift) | TIMEVALUE shift boundaries; thresholds applied per row | Daily, Single Entry Weekly, Time Sensitive |
Multi entry | Multiple rows per day (one row per job code or cost code) | SUMIF running daily total across rows with the same date | Multiple Entry Weekly |
Always tell Storm which pattern applies. If you don't, it will make an assumption and flag it — but getting this wrong means the entire overtime logic will be incorrect.
How do I configure Daily Timesheet formulas with Storm?
One row per worker per shift. Overtime thresholds apply to the net hours worked in that row. Suitable when each worker clocks one shift per day.
What Storm needs to configure correctly:
Ordinary hours threshold (e.g. up to 8 hours)
Time-and-a-half threshold (e.g. 8–10 hours)
Double time threshold (e.g. beyond 10 hours)
Whether Saturday and Sunday are treated differently to weekdays
Whether there is a day/night shift window (e.g. 06:30–18:30 based on start time)
Whether to deduct an unpaid break (entered in hours, e.g. 0.5 = 30 minutes)
Storm defaults if not specified: ordinary ≤8h, time-and-a-half 8–10h, double time >10h. These will be flagged as assumptions.
Example prompt:
"Configure the overtime formulas in this timesheet table. The table already has Start Time, Finish Time, and Break columns. Add Ordinary Hours, Time & Half, and Double Time columns. Ordinary applies up to 8 hours on weekday day shifts. Time & Half applies from 8 to 10 hours on weekdays and for the first 2 hours on Saturday. Double Time applies beyond 10 hours, all Sunday, and any night shift. Day shift is 06:30 to 18:30 based on start time. Break is entered in hours and should be deducted from net hours."
How do I configure Single Entry Weekly Timesheet formulas with Storm?
One row per worker per day across the week. Overtime thresholds apply to the weekly total rather than per shift. Suitable when workers clock in once per day and overtime is assessed at the end of the week.
What Storm needs to configure correctly:
Confirm that overtime is based on weekly total hours (not daily)
Ordinary hours cap per week (e.g. up to 38 hours)
Overtime rate band(s) above that threshold
Whether Saturday and Sunday attract different rates
Whether there is an unpaid break per day
Example prompt:
"Add formula columns to this weekly timesheet. The table has one row per day (Monday to Friday) with Start Time and Finish Time columns. Calculate total hours per day using TIMEDIF, deducting 30 minutes for an unpaid break. Add a weekly total column. Calculate overtime based on the weekly total: ordinary up to 38 hours, time and a half from 38 to 50 hours, double time above 50 hours."
How do I configure Multiple Entry Weekly Timesheet formulas with Storm?
Multiple rows per day — one row per job code or cost code. Overtime thresholds apply to the running daily total across all rows with the same date, not per row. A Date column is required for this to work.
What Storm needs to configure correctly:
Confirm this is a multi-entry timesheet (multiple rows per day)
Confirm the table has a Date column (required for running daily total)
Ordinary hours cap per day (e.g. 7 or 8 hours)
OT 1.5× upper band (e.g. 7–9 hours or 8–10 hours per day)
Whether Saturday and Sunday have different rates
Storm defaults if not specified: ordinary ≤7h, OT 1.5× 7–9h, OT 2× above 9h. These will be flagged as assumptions.
Example prompt:
"Configure the overtime formulas in this multi-entry timesheet. The table has a Date column and multiple rows per day — one row per job code. Add Regular Hours, Overtime 1.5×, and Overtime 2× columns that calculate based on the running daily total across all rows with the same date. Ordinary is the first 8 hours per day. OT 1.5× is from 8 to 10 hours per day. OT 2× is anything above 10 hours. Saturday: OT 1.5× for the first 2 hours, then OT 2×. Sunday: all hours at OT 2×."
How do I configure Time Sensitive Timesheet formulas with Storm?
One row per shift, but the pay rate depends on when the shift starts — not just how many hours are worked. A night shift is classified by its start time falling outside the defined day shift window. Suitable when your award applies different rates for day and night shifts.
What Storm needs to configure correctly:
The day shift window (e.g. starts between 06:30 and 18:30)
The rate for night shifts (triggered when start time falls outside the window)
Ordinary and overtime thresholds within the day shift
Saturday and Sunday rates
Example prompt:
"Add shift-loading formulas to this timesheet. The table has Start Time and Finish Time columns. Classify each row as day shift (starting between 06:30 and 18:30) or night shift (starting before 06:30 or at 18:30 or later). Night shift is all double time. For day shifts on weekdays: ordinary up to 8 hours, time and a half from 8 to 10 hours, double time beyond 10 hours. Saturday day shift: time and a half for the first 2 hours, then double time. All Sunday is double time."
Tips for better timesheet results
State your row shape upfront — "one row per shift" or "multiple rows per day per job code." This determines which formula pattern Storm uses and cannot be inferred from column names alone.
Specify whether overtime is daily or weekly — daily and weekly threshold calculations use different logic. Tell Storm explicitly.
Give exact hour thresholds — don't rely on defaults. If your EBA says ordinary is 7.6 hours, say 7.6, not "standard."
Specify Saturday and Sunday separately — many awards treat them differently. If you don't specify, Storm will flag an assumption.
Name your existing columns — if your table already has a "Start" column and a "Finish" column, reference them by name so Storm maps formulas to the right cells.
Use a correction prefix if Storm gets it wrong — say "Correction — " or "Actually, " before describing the fix. This signals Storm to re-evaluate its last output before responding.
Notes
Timesheet formula support is available in all four timesheet template types listed above.
Storm can add or modify formulas in an existing timesheet template, not just ones being built from scratch.
For formula support in other template types (Scoring System, Risk Matrix, Automated Table Summary, Hand Arm Vibration Record), see How to Use Storm to Configure Formulas in AI Templates.
For general instructions on using Storm In-Editor, see How to Edit Dashpivot Templates with Storm in the Template Editor.