Heat Rules Worker Heat Safety Beta — under active development, not production-ready. Verify every result against the governing standard.
On this page

← Back to the calculator · All standards

Odisha Labour & ESI Department Seasonal Midday Outdoor-Work Restriction — Stop-Work / Banned-Hours Rule

Odisha's Labour & ESI Department is reported to issue an annual seasonal restriction on outdoor work between 11:00 and 15:00 from 1 April to 15 June, with a carve-out for essential services alongside cool-water, shade and ORS provision. THE PRIMARY ORDER HAS NEVER BEEN LOCATED. Every value rests on Odisha news reporting of a departmental communication; no memo or letter number is cited by any source. A later project scan reached the department's own site and judged the circular an advisory with no numeric temperature trigger and no cited statutory basis, concluding that Odisha should have no engine at all. This engine therefore encodes no temperature trigger, claims no statutory force, never asserts stop-work, and never enters the work/rest composite.

Browse all standards → · Evaluate every standard at once in the calculator →

Governing metric
Date and time of day only. There is NO temperature or WBGT trigger — the reported instrument is a calendar and clock restriction, not a heat-measurement rule.
Authority
Labour & Employees' State Insurance (ESI) Department, Government of Odisha
Jurisdiction
Odisha India
Legal status
Source Needs Verification
Rule type
Stop Work Rule
Standard ID
HGC-132

Check a reading against this rule

This rule has no numeric trigger the calculator evaluates — it states duties and control measures rather than a threshold a reading can be checked against. Its measures are listed below.

Governing formula

No standalone formula is published for this standard; see programmable logic and parameters below.

Stop-work / banned hours

ParameterValue
seasonStartMonth4
seasonStartDay1
seasonEndMonth6
seasonEndDay15
restrictionStartHour11
restrictionEndHour15

These are the 2026 instance as REPORTED BY NEWS OUTLETS, not read from an order. They must be re-verified every season, and the underlying instrument must be located before this engine is relied on at all. No temperature threshold appears here because none was ever reported — the instrument is a calendar and clock restriction.

The reported essential-services carve-out is NOT encoded: no source described its scope precisely enough to gate on, and guessing at an exemption would be worse than omitting it, since an unencoded exemption makes the engine more conservative rather than less.

Programmable logic

Exempt when outdoor is explicitly false. Outside the reported 1 April – 15 June window, reports that the seasonal period does not apply. Inside it, reports whether the supplied shift or time falls within the reported 11:00–15:00 restriction window. Crucially it sets `restricted`, NOT `stopWork`: stopWork is pinned false in every branch.

Asserting a stop-work obligation would claim more than press reporting of an advisory can support, and a stop-work assertion is exactly the kind of output that changes someone's working day. Structurally this mirrors kerala_labour_heat_order — same country, same department type, same seasonal-window-plus-daily-window shape — but Kerala's rests on a Government Order under the Minimum Wages Act and is classified regulation/verified, where this rests on press reporting alone and is classified source_needs_verification/unverified.

Inputs

Required inputs: date

Optional inputs: outdoor, shiftStart, shiftEnd, time

Sources

Update history