Eastern · Call centers
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.
Last updated 2026-07. Statute citations linked inline. Not legal advice — consult counsel for compliance audits.
Rules that affect your schedule
Each rule includes the statute reference and how Weekwright helps you stay compliant. We focus on rules that affect the schedule itself — not every wage-and-hour topic.
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.
How Weekwright helps
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.
How Weekwright helps
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.
How Weekwright helps
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.
Citations link to the primary statute, ordinance, or agency page so you can verify against the original. This is research guidance, not legal advice — consult counsel for compliance audits.
Pricing
Compliance rules apply per location, so a chain operating in Connecticut and elsewhere runs each rule set independently.
For your first scheduled week.
The agent writes your week.
Core plus the answers.
For multi-location operators.
Common questions
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. The most relevant rules for call centers are: Meal period on shifts of 7.5 hours or more, The 30-minutes-of-paid-breaks alternative, Overtime follows the weekly federal baseline.
Weekwright ships with a configurable compliance rules engine. Connecticut-relevant rules (rest periods, consecutive-day limits, daily overtime caps) are checked at every shift create, move, and publish. The audit log captures every change for predictability-pay calculations and labor-board responses.
We track changes to the major scheduling-related laws (predictive scheduling ordinances, sick leave, daily overtime). Compliance rule defaults can be updated org-wide; we don't push silent changes — labor law is sensitive enough that we surface the diff first.
Weekwright is multi-jurisdiction friendly. Each location pins its IANA timezone and its own set of compliance rules — a chain operating in Connecticut and another state runs both rule sets independently, on the same dashboard.
Free for up to 10 employees. No credit card required.