A platform should examine the effect of an account restriction before calling it a temporary technical measure. Karnataka’s gig-worker legislation defines termination broadly enough to include materially restricting access, blocking an account and suspension, regardless of duration. A two-day restriction can therefore require a legal assessment even though the worker’s contract remains on the system.
The practical task is to connect the contract, the reason for the proposed restriction, the evidence, the decision process and the worker’s route to challenge it. A risk score or a support ticket alone does not supply that connection. Neither does an independent-contractor clause resolve the State Act’s application.
The Karnataka Platform Based Gig Workers (Social Security and Welfare) Act, 2025 is deemed effective from 30 May 2025. Final State rules were published in November 2025. Platforms assessing a restriction in October 2026 should use that enacted framework and final rules, rather than work from an earlier consultation draft.
Identify the covered activity and the responsible entity
The Act applies to relevant platforms and aggregators operating in Karnataka, with services identified in its Schedule. That Schedule extends beyond ride-hailing and food delivery to categories such as logistics, professional activities, healthcare, travel, hospitality, content and media. Match the actual service to the current Schedule; do not assume a familiar commercial label answers the question.
Identify the entity contracting with the worker, the entity operating the platform and any coordinating enterprise. A group brand is not a substitute for this exercise. Preserve the agreement, worker terms, service description and representative transaction records.
Also establish the Karnataka connection. A worker’s permanent address, the platform’s registered office and the location of services can be different. For someone operating across State borders, maintain a location and engagement history sufficient to assess the relevant activities without assuming that one national contract displaces State requirements.
Review any claimed exemption by its actual instrument, covered entities, conditions and period. An industry association’s description or another platform’s treatment is not an exemption for your business.
Audit the contract before relying on a ground for restriction
The contract should explain the grounds for termination or deactivation comprehensively. The Act also requires transparent terms addressing matters such as payments, deductions, incentives and the right to refuse tasks. Contract changes require advance notice under the statutory framework; a silently replaced web page creates an evidential problem.
Create a version history showing which worker accepted which terms and when a change was communicated. Preserve the language supplied, the delivery channel and the effective date. A screenshot of today’s terms does not prove what a worker received six months ago.
Check whether the alleged conduct falls within an existing ground. “Platform discretion” is a poor substitute for identifying the applicable term and factual reason. If the concern is repeated identity mismatch, distinguish that from customer ratings, alleged fraud or a safety incident. Different facts may need different responses and supporting evidence.
For example, a photograph rejected because of poor lighting does not establish account sharing. The reviewer should examine the underlying evidence and the worker’s explanation before treating the automated label as a proven fact.
Use a decision matrix that describes actual effects
Record what the system will do, not merely the internal name of the button:
| Proposed action | Questions before implementation |
|---|---|
| Stop all new task offers | Does this materially restrict platform access, and on what legal basis? |
| Restrict a service category | What work remains available and why is this scope necessary? |
| Block login | Can the worker still access earnings, notices and the grievance channel? |
| Hold a disputed payment | What contractual and legal basis supports the particular deduction or hold? |
| Permanently deactivate | What ground, evidence, notice and challenge process apply? |
This matrix is a recommended internal control. It does not create a separate exemption for a category described as temporary, limited or protective. The broad statutory definition needs to be applied to the actual effect.
Keep payment decisions distinct from access decisions. If earnings are undisputed, a pending investigation should not automatically erase them from the settlement system. Identify any disputed amount and the reason separately, and communicate deductions through the required payment documentation.
Notice is the ordinary starting point; urgent grounds require precision
Section 14 requires valid written reasons, fourteen days’ prior notice and natural justice for termination or deactivation. Its proviso addresses immediate action where the suspension ground includes bodily harm, while preserving a challenge route.
The final rules also address immediate termination for specified serious criminal matters, material and financial fraud and offences specified by the Board. These provisions should be read together rather than converted into an unrestricted “safety or fraud” exception. For a proposed urgent action, obtain a case-specific assessment of the actual statutory and rule-based ground, the available evidence and any current Board specification.
A bare system flag saying “fraud suspected” is not a completed analysis. Preserve the transactions, explain the suspected conduct and distinguish evidence from inference. Equally, respond promptly to a credible immediate safety concern through the appropriate emergency and protective processes. The decision record should explain why the selected restriction and timing were justified.
The worker-facing communication should identify the decision, reasons, effective time, relevant ground and route for representation. Avoid revealing unnecessary complainant information or creating risks for another person. Fair communication and protection of sensitive evidence need to be designed together.
Automated decisions need an accessible information route
The Act addresses transparency in automated monitoring and decision-making systems. The final rules require a published mechanism for workers to seek relevant information about matters such as fares, earnings and customer feedback, with a response within five working days.
Build a route that a restricted worker can still use. Requiring an active account to appeal a blocked account defeats the operational purpose. Provide a working alternative contact and test it using the same access limitations that an affected worker will face.
A useful explanation identifies the relevant event or data, the rule applied and the available correction process. It should allow a worker to identify a mistaken identity, an incorrect location or an incomplete record. A generic statement that a proprietary algorithm made the decision is unlikely to help resolve the dispute.
Human review should involve someone able to examine and change the result. A support agent who can only repeat the automated outcome is not a meaningful operational safeguard. Record what the reviewer considered, what additional evidence was obtained and why the outcome was confirmed or changed. These review-record controls support the statutory grievance process; they should not be presented as a substitute for it.
Constitute the actual dispute committee
The final rules specify an Internal Dispute Resolution Committee with a senior-management chairperson, two management personnel and at least three senior gig workers. At least two members must be women. A general customer-support mailbox does not establish that this committee exists.
Keep the constitution document, member details, acceptance records and a process for conflicts and vacancies. The rules contemplate committees in other units or branches as required. Assess the actual operation rather than assuming that a committee with no available members can handle every location.
The grievance framework contains several different periods. The rules provide a seven-working-day worker filing period for the relevant grievance route, a fifteen-working-day resolution endeavour and a thirty-day appeal period from the final decision under that route. The Act and the petition rules also require a written action-taken report within fourteen days and a final order within forty-five days. These are different procedural steps, not interchangeable descriptions of one deadline.
Configure the case system to identify the applicable route and track all relevant dates. Do not postpone the fourteen-day report merely because a forty-five-day final-order period exists. Where redress is unsatisfactory or the report is not received, the statutory escalation provisions also matter. Provide the worker with the correct current contact and route.
Preserve a decision record, not an accusation archive
A useful file contains the original complaint or trigger, relevant contract version, supporting records, notices, delivery evidence, representation, review notes, written decision and any implementation correction. Mark allegations as allegations until findings are made.
Restrict access to sensitive information. An operations dashboard may need the restriction status and next review date, while the committee needs fuller evidence. Do not circulate personal complaints to unrelated teams or put sensitive narratives into ordinary finance notes.
If an incorrect restriction is reversed, confirm that technical implementation follows the decision. Test account restoration, task eligibility and payment corrections. A favourable letter is incomplete if a hidden system flag continues to prevent work.
assureOffice can support the organisation of related financial and practice records, while the platform keeps worker disputes in a suitably restricted process. The tools available at assureoffice.in should not be presented as deciding whether a suspension is legally justified.
Connect the case to registration and welfare records
A suspension can affect engagement data, but it does not automatically prove that every registration should be deleted. Establish whether the relationship continues and apply the correct update requirements. Preserve history so that earlier payments and welfare records remain reconcilable.
The State rules require worker-database updates and transaction reporting, and provide quarterly welfare-fee processes. A February 2026 government direction addresses collection and reporting. The statutory percentage range is not, by itself, the specific rate and cap applicable to a particular service category. Finance should verify the actual rate instrument and category before configuring a charge.
Keep central social-security registration requirements separate from State obligations. A State committee decision does not automatically update every central record. Equally, a central worker identifier does not prove that Karnataka platform registration, disclosures or grievance arrangements are complete.
Before implementing the restriction, have the accountable team confirm coverage, the contractual ground, notice or urgent-action basis, evidence access, communication, committee availability and calendar dates. Then confirm that the actual system action matches the approved decision. Related records at assureoffice.in may help explain financial adjustments, but the substantive decision remains the platform’s responsibility.
Frequently asked questions
1. Is a temporary account block outside the termination rules?
Not merely because it is temporary. The Act’s definition includes material access restrictions and suspension irrespective of duration. Examine what the worker can actually do after the block and apply the relevant legal process to that effect.
2. Does an independent-contractor clause prevent State coverage?
No. Assess the statutory definitions and scheduled service. A contractual label does not settle the Act’s application or determine every employment-status issue under other laws. Keep those analyses connected but distinct.
3. Must every ordinary deactivation have written reasons?
The ordinary section 14 framework requires valid written reasons and prior notice, together with natural justice. Identify the actual ground and evidence. A template saying only that the account breached policy does not explain the underlying decision adequately.
4. Can bodily-harm allegations justify immediate action?
The Act contains a specific immediate-action proviso concerning bodily-harm grounds. Apply it to the facts and preserve the worker’s challenge route. Do not treat an unrelated performance concern as bodily harm simply to avoid the ordinary notice process.
5. What about material or financial fraud?
The final rules address immediate termination for these and other specified serious grounds. Obtain a precise assessment of the applicable provision and evidence, read with the Act. A risk model’s fraud label should trigger investigation rather than be treated as proof by itself.
6. Can the platform rely entirely on an automated score?
Preserve the underlying information and provide the relevant information and grievance routes. A score may be an investigative input, but a reviewer needs enough context to assess errors and the worker’s explanation. Record how the final decision was reached.
7. How quickly must an information query be answered?
The final rules prescribe five working days for the relevant automated-system information queries. Identify these separately from ordinary customer-support messages and committee grievances so that the correct obligation is assigned and monitored.
8. Must disclosures be available in Kannada?
The final disclosure rules require Kannada and English and the relevant preferred Eighth Schedule language. Use plain language. Retain the actual version provided to the worker rather than assuming that an English-only website meets every disclosure obligation.
9. Can customer support serve as the Internal Dispute Resolution Committee?
Only a body constituted with the required membership and process can perform that role. Support staff can receive and route complaints, but the existence of a support queue does not prove that the required committee has been constituted.
10. Can the committee consist only of managers?
No. The final rules include gig-worker representation and women-member requirements as well as management members. Keep current membership evidence and address vacancies so that the committee can actually function when a grievance arrives.
11. Is the final-order deadline the only grievance deadline?
No. The framework includes filing, action-taken-report, resolution and appeal periods. Track the applicable route and distinguish working days from days. A later final-order date does not erase an earlier requirement to provide an action-taken report.
12. Should a blocked worker still be able to reach the grievance route?
Yes, design the process to remain accessible. Test the link, alternative contact and document-submission route after login is disabled. Otherwise the platform may advertise a process that the person affected cannot actually use.
13. Can the company amend the contract immediately before suspension?
Do not assume a newly uploaded ground governs earlier events. Review the applicable contract version and statutory advance-notice requirements for changes. A version history helps establish what was communicated and which terms were in force.
14. Does a low rating automatically justify deactivation?
Assess the contractual ground, reliability of the ratings and surrounding facts. Ratings can reflect errors or discriminatory behaviour. A decision record should explain the evidence and reasoning rather than merely reproduce the numerical score.
15. What if the worker operates in several States?
Map the locations and services relevant to the engagement. A national contract should be administered with the applicable State requirements in view. Preserve sufficient geographic records without assuming that the worker’s home address alone determines every issue.
16. Should a suspension stop all outstanding earnings?
Do not automatically combine the decisions. Identify amounts earned, disputed deductions and any lawful basis for a hold. Communicate settlement treatment separately and preserve the records needed to correct it if the underlying restriction is reversed.
17. Does registration prove that the suspension process is compliant?
No. Registration, welfare reporting, contract disclosure and dispute handling are separate requirements. An enterprise can hold a registration while still having an inadequate notice or committee process. Assess each workstream using its own evidence.
18. Can the statutory welfare-fee range be used as the actual rate?
No. Establish the service category and operative notified rate and cap. Keep the signed instrument with the calculation specification. The existence of a collection direction does not justify selecting any percentage within the legislative range.
19. What should happen after a successful worker challenge?
Communicate the outcome and implement it across the systems affected. Check access, category eligibility, earnings corrections and engagement records. Preserve the earlier decision and reversal history rather than deleting evidence of what occurred.
20. What should management check before approving a restriction?
Confirm coverage, grounds, evidence, timing, notice or urgent-action basis, worker communication and an accessible challenge route. Assign implementation and follow-up owners. Approval should concern the actual restriction and its consequences, rather than an unexplained status code.