CT · 3 rules · reviewed 2026-07
Connecticut's scheduling-relevant rule is its meal period, and the detail that matters is placement rather than duration: the 30 minutes must fall after the first two hours of work and before the last two. A break scheduled at the end of a shift does not satisfy it.
This is a reference, not legal advice. Every rule below links to its primary source — a statute, an ordinance, or the enforcing agency — so you can read the law rather than a summary of a summary. Consult counsel before relying on any of it.
All 3 rules below apply regardless of industry. Most US predictive-scheduling law is municipal, so where a rule comes from a city ordinance its name says so — a company can easily have one location covered and two not.
No person may be required to work 7.5 or more consecutive hours without at least 30 consecutive minutes for a meal, and it must be given after the first 2 hours of work and before the last 2 hours. Placement is part of the requirement, not a courtesy.
In Weekwright: Break periods are stored with their own start and end times against the shift, so check_meal_break_compliance can see WHERE in the shift the break fell, not just that one existed. A break punched in the last two hours is a finding rather than a pass.
The requirement does not apply to an employer who instead provides 30 or more total minutes of paid rest or meal periods within each 7.5-hour work period. Several short paid breaks can substitute for one unpaid 30-minute block.
In Weekwright: Breaks carry a paid/unpaid flag, so the total paid break minutes inside a shift is a number you can actually produce from the punch data — which is what you would need to show you qualify for this alternative.
Connecticut has no daily overtime and no statewide predictive-scheduling law. Non-exempt employees earn 1.5x beyond 40 hours in a workweek, and rest periods count toward that weekly calculation.
In Weekwright: MAX_HOURS_PER_WEEK at 40 with WARNING severity gives you the visibility without blocking legitimate overtime, and the payroll export uses your own configured threshold rather than assuming 40 — which matters if a union agreement sets it lower.
Read the law itself. These are the statutes, ordinances and agencies the rules above are taken from.
The same statutes read for one vertical, with the scheduling patterns that vertical actually runs.
Again, because it matters: this is not legal advice. It is a reading aid over primary sources, maintained by a software company rather than a law firm. It surfaces obvious gaps so you can act on them — it does not tell you whether a specific ordinance applies to your specific business. Consult counsel for that. Found something out of date? hello@weekwright.com — a correction to a primary source is welcome from anyone, customer or not.
Weekwright enforces the baseline for where each shift happens, before you publish. Free for a single location, up to 20 employees.
We use cookies to see which pages get read, where people give up, and whether an ad click ended in a signup. Nothing loads until you choose, and none of it is personalised advertising. What we store