Collective agreements in SKLA — CCT inside Validate
Collective rules as product parameters: they may tighten limits, not break the constitutional ceiling — in the same publish flow.
SKLA treats collective agreements (CCT) as operational governance — not a PDF filed away in HR. Active parameters feed the Rule Engine when teams Validate and Publish.
In every country the idea is the same: law and tenant agreements constrain the schedule decision. In Brazil, CCT fills what the labor code leaves open; with EC 141/2026, it may tighten the cap, not raise it above the constitutional limit.
Hierarchy in the product
- Constitution / law for the operation’s legal profile
- Registered collective agreement (restricts)
- SKLA baseline (fallback)
What usually goes in CCT
Daily/weekly hours (restrict only), inter-shift rest, facilities rules, optional monthly weekly-rest compensation flag.
Why it exists in SKLA
Without parameters in the system, the agreement lives in someone’s head. With CCT on the tenant/unit, the same Validate that checks coverage also applies hours and rest — and respects the constitution when a clause is incompatible.
Read next
The real agreement and the law prevail; SKLA executes what is configured.