Acts & Rules · Telangana
Telangana Gig Workers Rules 2026: Platform Compliance Guide
Telangana’s final Rules address platform registration, worker data, contracts, payouts, fees and disputes. Check Gazette commencement and implementation directions.
- Jurisdiction
- Telangana
- Issued on
- 14 November 2026
- Status
- Current
- Reference
- G.O.Ms.No.18, SHAKTI (Lab-I), 14.11.2026
State-wise library
Check another state or UT
Move directly to the published acts & rules records for a jurisdiction.
At a glance
Notification details
Published reference
Notification and guidance
The Telangana Gig Workers Rules 2026, issued through G.O.Ms.No.18 dated 14 November 2026 by the SHAKTI (Lab-I) Department, translate the Platform Based Gig Workers (Registration, Social Security and Welfare) Act, 2026 into operational requirements for platforms, aggregators and registered workers. They cover registration, worker data, contracts, automated decisions, payouts, welfare-fund contributions, safety and dispute handling. Platforms should review the actual application screens, data flows and payment processes alongside their written policies.
At a glance
| Instrument | Final Rules order: G.O.Ms.No.18, SHAKTI (Lab-I), 14 November 2026. |
|---|---|
| Commencement distinction | The order records that the Act commenced on 2 June 2026. Rule 1(2) makes final publication of the Rules in the Official Gazette their commencement trigger. A separate final Gazette publication record has not been independently verified for this guide; the order date alone is not treated as proof of Rules commencement. |
| Who should assess coverage? | Aggregators and platforms operating in Telangana or providing Schedule I services in the State through digital or electronic means, and their platform-based gig workers. |
| Worker-facing changes | Clear contracts and payout statements, advance notice of relevant changes, termination safeguards, human review of algorithm-recommended termination, and accessible support. |
| Welfare Fund Fee | A separate notified rate is required. Rule 12(1) sets a ceiling of 2% of each transaction payout; the platform bears the fee and cannot recover it from workers. |
| Immediate platform work | Confirm the Gazette and implementation directions; map registration, monthly/quarterly reporting, payout and dispute controls to accountable teams. |
Primary reference: the complete government-issued final Rules PDF, retained unchanged on ComplianceHub. The order can also be located in the Telangana Government Order Issue Register using SHAKTI/LABOUR-I, MS No.18 and 14 November 2026.
Keep the Act, Rules and implementation dates separate
The final order records the Act’s commencement on 2 June 2026 and directs publication of the Rules in an Extraordinary Gazette dated 14 November. Rule 1(2) nevertheless makes final Gazette publication the legal trigger for the Rules. The separate Gazette issue and later implementation directions should be retained with the order. A launch announcement alone is not a substitute for that commencement evidence.
Do not automatically count a fresh forty-five days from 14 November. Rules 3(1) and 5(1) measure initial worker-database submission and aggregator registration from commencement of the Act. Because the final Rules were issued later, the designated portal, relevant extension provisions and subsequent Board directions must be checked before communicating a calculated initial deadline. This guide reports the rule text and ongoing requirements without inventing a replacement transition date.
Applicability and registration: map the legal entity and services
Rule 5 covers an aggregator or platform operating in Telangana or providing one or more Schedule I services within the State through digital or electronic means. Coverage should be checked against the Act’s definitions and Schedule I. The Rules should not be treated as automatically applying to every freelancer, outsourced vendor or independent contractor simply because work involves a computer.
Aggregator registration uses Form AGG-1. The required information includes the legal name, authorised person and point of contact, registered office and principal place of business in Telangana, contact details, PAN, GSTIN, CIN or equivalent registration number, service categories and estimated Telangana gig-worker population. Where one legal entity operates multiple distinct platforms, Rule 5(3) provides for a single registration with separate reporting of each sectoral vertical. Multi-sector operators must maintain disaggregated service, payout and worker information.
Under Rule 4, workers may register through the Board’s portal, an integrated aggregator application, or a designated facilitation/Common Service Centre using Form REG-1. The Gig Identification Number (GID) is designed to work across platforms. The Board must check for duplicate registrations; a worker already holding a valid GID is linked to the additional platform rather than being issued another number. Registration should not be confused with eligibility for every particular benefit or scheme.
Worker data, reporting and privacy controls
Rule 3 requires an electronically submitted, machine-readable worker database through the Board-designated secure portal and quarterly updates reflecting additions and separations. Rule 5(1A) separately requires registered aggregators to update their total registered-worker count monthly by the seventh day of the succeeding month. These are different reporting obligations.
The prescribed data includes identity and contact information, the primary operating location, relevant account details and active-work information. Some fields are expressly conditional or voluntary: for example, e-Shram UAN is included if available, and EPFO UAN/PAN-linked tax information and disclosure of concurrent regular employment have stated qualifications. A data specification should preserve those qualifications instead of turning every possible field into a mandatory onboarding condition.
The Rules require secure transfer and safeguards for the Board-held data, and restrict the purposes for which it may be used. A practical implementation file should identify the submission owner, field definitions, access permissions, exception process and reconciliation between the onboarding system and regulatory export. Use the designated government channel and confirmed schema; do not send worker identity or bank data to an unofficial collection address.
Contracts, automated decisions and the right to refuse a task
Rule 7 treats platform terms of service and onboarding arrangements as relevant contracts. The contract must use simple language available in Telugu, Hindi or another Eighth Schedule language preferred by the worker. It should explain the applicable rates, payment structure, incentives, deductions and calculation method, together with applicable working conditions and performance standards.
The contract must state the worker’s right to decline a task without adverse consequences. Rule 7 prohibits reducing ratings, restricting allocation, suspending or otherwise penalising a worker for refusing an assignment. Product teams should therefore review the system’s actual behaviour when a task is declined, as well as the written clause.
Changes to service terms or material aspects of automated monitoring and decision-making systems (AMDMS) require at least fourteen days’ written notice before taking effect. The worker may end the contract within that notice period without forfeiting earned entitlements under the previous contract. Rule 6 also requires a mechanism for seeking AMDMS information and a response within five working days to the specified queries once a dispute-resolution process is filed. The Board may require algorithmic audit reports in the format and time it specifies.
Termination and deactivation require a documented process
Rule 8’s ordinary process requires at least seven days’ prior written notice stating reasons in a language understood by the worker, a fair enquiry with an opportunity to respond, and a written final decision within seven days after the enquiry concludes. An AMDMS-generated or recommended termination cannot take effect until a Human Resource Officer reviews and approves it and records reasons. The platform must also send the Board a monthly consolidated removal list with reasons.
The immediate-termination exception is limited: the rule requires a clear and imminent physical or mental threat to the end consumer and identifies qualifying grounds. Where the exception is used, contemporaneous reasons must be recorded, the reasons communicated to the worker within twenty-four hours, and the worker permitted to raise the specified dispute within thirty days. It should not be treated as a general shortcut for ordinary performance concerns.
Rule 8 also prohibits blacklisting, de-rating, reduced payouts or other penalties as substitutes for the formal termination process. Retain the notice, supporting material, worker response, enquiry record, HR approval and final communication so the decision can be reviewed.
Payouts, statements and Welfare Fund Fee
Under Rule 9, payouts must follow the contract and be made no later than seven days after the applicable payout cycle ends. Each worker must receive a digital transaction statement identifying gross earnings, itemised deductions with reasons and net payout. Payouts are to be made to the bank account linked to the worker’s GID.
The 2% figure is a ceiling in Rule 12(1), not proof that a 2% levy is already payable. The Government must notify the applicable Welfare Fund Fee rate separately. Verify the operative rate, category and effective period before configuring a live charge. This review has not independently verified such a rate notification. The rule also provides for subsequent rate or cap directions, so the current government instrument must be retained with the calculation.
The fee must be borne entirely by the aggregator or platform. Rules 9(2) and 12(5) prohibit direct or indirect recovery from workers, including a reduction in transaction rates or incentives that would not otherwise have occurred. “Settled Payments”, as defined in the Rules, are excluded from the base-payout calculation for this fee but must still be disclosed in the transaction statement.
Rule 12(3) requires monthly calculation, self-declaration and remittance at the notified rate within five working days after month-end. Rules 13–15 address deposit, reconciliation and the Welfare Fund Fee Verification System (WFFVS), including transaction-level information and month-end reconciled data. These financial workflows should be configured against the confirmed rate, government account, portal and schema. A payment-control review can be supported by our payment and compliance reconciliation team.
Worker support, safety and dispute handling
Rule 11 requires a manager-level or equivalent senior point of contact, a facilitation section in the application and responses to worker queries within seventy-two hours, with escalation to the Board where the deadline is missed. The contact details must be prominent in the worker account, official website and communications. Changes must be updated and communicated to the Board within seven days.
Rule 10 addresses a reasonably practicable safe working environment, safety information, a dedicated incident helpline and an applicable panic-button or equivalent feature. It provides for sector-specific Board standards and an implementation period of up to three months from communication or publication on the Board’s portal, whichever is earlier. It also prescribes an annual Safety and Health Compliance Report in Form SAF-1 by 31 July. The actual standards, communication date and reporting implementation should be retained in the compliance calendar.
Internal Dispute Resolution Committee (IDRC): Rule 20(1) expressly sets out a committee requirement for platforms with at least one hundred registered gig workers in Telangana. The stated composition includes a senior management chairperson, two management members and at least three senior gig-worker representatives, with at least two women among the members. Rule 20(3) also uses broader wording requiring every aggregator or platform to constitute an IDRC. A smaller platform should therefore obtain clarity on the applicable requirement rather than assuming the hundred-worker figure creates a complete exemption from dispute handling.
Rule 21 requires acknowledgement within three working days, an action-taken report within fourteen days and a final order within thirty days of a written complaint. The ordinary complaint window is seven working days from the event or intimation; Rule 8 separately gives thirty days for the specified immediate-termination dispute. The distinct windows should be represented correctly in support scripts. Rule 20 also requires quarterly reporting of disputes, decisions and pending matters. Further escalation to the Grievance Redressal Officer and Appellate Authority follows Rules 22–23 and the relevant appointments.
Build an implementation register
The following workstreams preserve the connection between legal requirements and the platform’s operating systems. They are recommended management controls, not an additional statutory filing.
- Registration and data ownership: identify each covered legal entity and service vertical, reconcile worker and GID records, and confirm the government submission channel.
- Contract and product review: compare the app’s terms, task-refusal behaviour, change notices and account-management screens with Rules 6–8.
- Payments: map the payout cycle, statement fields and bank-account validation; keep company-funded fee calculations separate from amounts payable to workers.
- Safety and support: assign the point of contact, incident response, applicable committee and complaint escalation duties; record the trigger and responsible owner for each deadline.
- Evidence and unresolved dependencies: retain the reviewed order, Gazette evidence, fee directions, portal specifications, test results and approved system changes. Give each unresolved government-direction question a named owner.
Our labour-law advisory team can assist with applicability, contract review and dispute-process design. Maintain the resulting record set with support from our statutory records team.
Frequently asked questions
Are these final Rules or a draft?
G.O.Ms.No.18 is the final Rules order. The separate question of their operative commencement is governed by Rule 1(2), which refers to final Gazette publication. Keep the Gazette issue and later implementation directions with the order.
Should a platform immediately deduct 2% from worker payments?
No. The applicable fee rate requires its own notification, and the Rules prohibit recovery of the fee from the worker. The platform bears the charge; the ceiling must not be configured as a worker deduction.
Does each brand or service vertical need a separate registration?
Rule 5(3) provides for a single registration for the legal entity operating multiple distinct platforms, with disaggregated reporting. Check which legal entity operates each platform and maintain the required sectoral information.
Can an automated system make a final termination decision?
An AMDMS-generated or recommended termination requires review and approval by a Human Resource Officer with recorded reasons before taking effect. The notice, enquiry and applicable exception provisions must also be followed.
Is the initial registration deadline forty-five days after the November order?
The text of Rules 3 and 5 refers to commencement of the Act. It does not state a fresh forty-five-day period beginning on the Rules’ issue date. Confirm the Board’s directions, portal and extension provisions before calculating an initial due date.
Does a platform below one hundred workers have no dispute obligation?
That conclusion is unsafe. Rule 20 contains both the hundred-worker wording in sub-rule (1) and broader wording in sub-rule (3), while the Rules impose worker-support and grievance obligations elsewhere. Review the Act, the complete Rules and any clarification for the actual platform.
Official source and review position
Read the complete final Rules PDF and use the official Government Order Issue Register to locate G.O.Ms.No.18, SHAKTI/LABOUR-I, dated 14 November 2026. The hosted PDF is an unchanged copy of the government-issued document. Source position reviewed on 20 November 2026. The separate Gazette publication record, operative fee notification, designated portal and subsequent Board directions should be confirmed for implementation and deadline calculation.
Employer reference
Implementation notes
Employer impact: Covered platforms should review registration, worker data, contracts, automated decisions, payouts, safety and grievances. Rule commencement depends on final Gazette publication, and the applicable welfare-fee rate requires a separate notification. · Action required: Confirm Gazette and implementation directions; map legal entities and service verticals; assign registration and reporting owners; review app terms, payment controls, termination review and complaint processes.
Official document
Check the controlling notification.
Telangana_Gig_Workers_Rules_GO_MS_18_14_Nov_2026.pdf · Government of Telangana, SHAKTI (Lab-I) Department
Get compliance updates by email
Choose your states, topics and frequency for gazettes, notifications, minimum wages and new articles. Change your preferences or unsubscribe anytime.
Source review and connected references
Continue researching
No additional connected publications are available yet.
