A rules engine, not another chain of if statements
RuleVerdict is the subscription layer in front of a dedicated overtime rules engine — a guided rule editor and one calculation API, instead of per-client overtime logic spread across your codebase.
Overtime logic has a way of ending up hardcoded — a chain of if
statements for one client's daily threshold, another branch for a different state's
rest-hours rule, a special case for the one contract with a short-turnaround clause.
It works, until the next contract needs a rule the code was never written to express,
and someone has to go find every place that logic lives and change it correctly,
under deadline, without breaking the clients already relying on it.
RuleVerdict is the subscription layer in front of a dedicated overtime rules engine — a guided rule editor your team (or your client's team) can use to define daily/weekly thresholds, rest-hours and short-turnaround detection, holiday and shift-differential premiums, and rounding conventions — with grouped AND/OR conditions, hour-range matching, and custom fields for whatever your contract needs — per contract, without touching your codebase. Every change is drafted, tested against real time entries, and published as its own immutable, versioned record — so "what rules applied on this date" is always a real, auditable answer, not a guess.
Once a rule is published, your product calls one API — /v1/evaluate/ — and
gets back correct, reconciled regular and overtime hours. The same engine your rule editor
tested against is the one computing the real answer, every time.