Contractor Compliance & Lifecycle Management

Frequently asked questions

Can Iddion RegX track CLRA licence limits per contractor?+

Yes — licence validity and permitted headcount are tracked per contractor per establishment, with alerts before expiry and flags when deployment approaches the licensed cap. Most plants discover they're over cap only when an inspector counts; this makes the headroom visible daily.

What happens when a contractor's licence lapses?+

The contractor is flagged across dashboards and registers immediately, and with gate compliance enabled, their workers can be blocked at entry until the licence is restored — with every denial logged. The alternative is discovering the lapse weeks later, with attendance records already showing unlicensed deployment.

Does it verify contractors' statutory remittances?+

Contractor PF and ESI challan evidence is captured against each cycle and matched to computed liabilities, so gaps surface before they become the principal employer's problem. Under CLRA, contractor defaults can fall back on you — this is where that exposure becomes visible.

Can we compare contractor performance across sites?+

Yes. Scorecards cover attendance reliability, compliance flags, document currency, OT patterns, and incident history per contractor across every site they serve — so procurement sees vendor quality alongside commercial terms rather than after a problem.

Can a blacklisted worker be re-submitted under a different contractor?+

No — that's the point of holding blacklists at the worker-identity level rather than per contractor. A worker blocked for a safety violation or security incident stays blocked across your sites regardless of which contractor presents them next, because the block attaches to their biometric identity.

What documents does the system track per contractor?+

CLRA licence and headcount cap, commercial agreement and validity dates, insurance certificates, PF/ESI registration and challan evidence, work orders and scope, plus site-specific approvals. Expiry alerts run on all of them, so renewals happen before lapses rather than after notices.

How does contractor data connect to worker records?+

Every worker is mapped to their contractor, work order, site, department, and cost centre — so attendance, wages, and compliance records roll up per contractor automatically. When a worker moves between contractors, the history follows the worker while the billing follows the contractor.

What happens at contractor exit or contract closure?+

Workers under that contractor are de-provisioned — gate access revoked, biometric enrollments deactivated — and the compliance record is retained for the statutory period. This closes the gap where departed contractors' workers keep valid gate credentials for months.

Can we onboard a new contractor before their documents are complete?+

You can register them, but deployment can be gated on document completeness — so a contractor without a valid licence or insurance can't move workers onto site. Configurable per site, since some plants allow provisional entry under supervision and others don't.

How does this help during a labour inspection?+

Every field an inspector asks for — licences, registers, headcount against cap, remittance evidence, worker-to-contractor mapping — is current in one system and exportable. The difference is a same-day audit response instead of a three-week reconstruction from emails and folders.

How many contractors can it handle?+

Multi-site plants running dozens of contractors simultaneously are the normal case, with per-contractor and consolidated views across sites. Scale is a configuration matter, not a licensing constraint.