Chapter
I — Preliminary
Rule 1 — Short title and commencement
Rule-by-rule operational analysis with Code, Form, evidence, authority and State-jurisdiction controls.
Rule identity
Part/sector
General
Control family
Statutory implementation control
Linked Code sections
Section 1, Section 2
Forms
No direct Annexure VII form identified
Source review
2026-07-17
Rule-level operational analysis
The exact Gazette wording controls. The following map converts Rule 1 into an implementation sequence and highlights the records needed to demonstrate compliance.
- Requirement 1. Identify the covered establishment, worker category, appropriate Government and sector-specific overlay.
- Requirement 2. Break the provision into trigger, actor, action, timing, evidence and consequence before configuring the process.
- Requirement 3. Read the corresponding Central Rule, prescribed form, Schedule and notified authority together.
- Requirement 4. Create a named control owner and maker-checker evidence trail.
- Requirement 5. Recheck later Central orders, State rules and technical standards before relying on a threshold or procedure.
Sub-rule review protocol
Who acts
Identify the employer, occupier, manager, contractor, worker, medical officer, Inspector-cum-Facilitator or other authority named in each sub-rule.
When
Record the triggering event and calculate every hour/day/month period from documentary evidence.
How
Use the portal, prescribed Form, written notice, examination, committee or technical control stated in the Rule.
Exception/proviso
Do not generalise an exception. Record why its facts and jurisdiction are satisfied.
Decision evidence
Keep the maker, reviewer, competent authority, date, acknowledgement and corrected version.
Later instrument
Check general/special orders, authority notifications, standards and State rules before reliance.
Code and Form concordance
Evidence and audit file
- coverage memo
- legal crosswalk
- process/control document
- transaction evidence
- approval and acknowledgement
- exception/escalation record
Failure consequence and cure
A generic policy without transaction-level evidence will not prove compliance with the provision.
Where the Rule uses a portal, form or notified authority, a locally created substitute is not automatically equivalent. Cure should preserve the original due date and explain any late correction.
Worked implementation scenario
A covered establishment converts “Short title and commencement” into a control with a named owner, trigger, deadline, prescribed evidence, reviewer and escalation path. A sample transaction is tested before the policy is treated as operational.
Rule-specific QA questions
Has the exact Gazette text been checked?
Yes for source structure and title; users must still read the complete Rule and sub-rules before applying it to facts.
Is this a State-rule page?
No. It covers the 2026 Central Rules. State-specific implementation belongs in a separately sourced State overlay.
Can another existing Finin2min article own this rule?
No. This URL is the canonical legal repository for Rule 1. Articles and hubs should link here without reproducing the full rule analysis.