Meta description: MIDC single window guide for Maharashtra industries: track applications, service timelines, objections, RTS appeals and approval evidence in 2026.
An approval stuck for 35 days can hold up construction, machinery installation and your production start. The MIDC single window puts many industrial services behind one digital entry point, but it does not turn them into one combined approval or one universal deadline. If nobody owns each application number, objection and promised delivery date, the portal becomes another inbox that everyone assumes someone else is checking.
This guide shows a Maharashtra factory owner or compliance team how to track separate service clocks, preserve proof, follow up and identify a possible Right to Services appeal. Sources were checked on 13 September 2026; recheck live forms and timelines.
What does the MIDC single window actually cover?
The Maharashtra Industrial Development Corporation describes its Single Window Clearance system as a facility for industries and entrepreneurs that streamlines approvals needed to establish and operate a business in Maharashtra. New users can register and existing users can log in from that official page.
The crucial word is “streamlines”. It does not mean that one submission creates every permission your project needs. The live MIDC online service catalogue separates MIDC work into departments, including:
- Land Department services;
- Fire Department services;
- Engineering Department services;
- Special Planning Authority, or SPA, services;
- Technical Advisor Department services; and
- IT SEZ Department services.
The catalogue also displays non-MIDC departments and external services. That makes the window a useful route to multiple processes, not a substitute for legal applicability analysis. A manufacturing unit may still need separate action involving the Maharashtra Pollution Control Board, Directorate of Industrial Safety and Health, electricity distribution company, local authority or a sector regulator. The responsible authority, governing law, documents and appeal route can differ for every approval.
Before filing, create an “approval universe” from the plot, activity, building use, hazardous materials, water, effluent, workforce and electricity load. Map every required approval to the authority that grants it and the portal that accepts it.
If you are still choosing or applying for a plot, first use our MIDC plot availability and land application guide. The workflow below begins once a business knows the plot or MIDC service it must pursue.
Which MIDC approval timelines should you track?
The public catalogue displays a separate time limit beside many MIDC services. These are current portal values, not promises that incomplete applications will be approved automatically. Save the value visible when you file.
Department | Service shown by MIDC | Portal time limit
Land | Duplicate allotment order | 7 days
Land | Plot sub-letting | 8 days
Land | Deed of assignment | 10 days
Land | Mortgage consent | 15 days
Land | Change in manufacturing activity | 21 days
Land | Plot transfer | 30 days
Land | Plot amalgamation | 30 days
Land | Surrender of plot and refund | 34 days
Fire | Final Fire NOC | 15 days
Fire | Renewal of Final Fire NOC | 15 days
Engineering | No-Dues Certificate | 7 days
Engineering | New water connection | 15 days
Engineering | Drainage connection | 15 days
SPA | e-Intimation of commencement after building-plan approval | 1 day
SPA | Occupancy Certificate | 10 days
SPA | Right of Way permission | 21 days
SPA | Combined building-plan approval and provisional Fire NOC | 35 days
SPA | Tree felling, trimming or replantation | 45 days
Technical Advisor | IT/ITES or IT hardware LOI | 10 days
IT SEZ | Co-developer status | 30 days
Do not copy these numbers into a permanent calendar and forget them. A portal timeline may change, and a Right to Services notification may define the enforceable clock differently. Capture four separate dates for every application:
- Submission date: when the portal accepted the application and generated an acknowledgement.
- Completeness date: when all required documents and payments were accepted, if this is separately recorded.
- Portal due date: the displayed service time added according to the portal's counting method.
- Project need date: the date by which the business needs the approval to protect construction, finance or production.
Do not treat “submitted” as “in process”
The MIDC catalogue warns that forms under processing or in draft mode may not appear under the respective service. The live page also displays operational checks involving the water consumer number and outstanding payments. In practice, your tracker should distinguish these states:
- draft saved but not submitted;
- submitted and acknowledgement received;
- fee paid and payment reconciled;
- under scrutiny;
- clarification or defect raised;
- clarification answered;
- inspection scheduled or completed;
- approved and certificate issued; or
- rejected, withdrawn or closed.
A payment debit without an acknowledgement is not proof of submission. A portal dashboard row marked approved is not enough if the digitally issued order or certificate has not been downloaded and checked.
How do you build an approval tracker that catches delays?
A useful tracker is an obligation register, not a colourful project spreadsheet. One row should represent one approval transaction. Use these fields:
- legal entity and MIDC plot or consumer number;
- unit address and industrial area;
- department and exact service name;
- governing law, rule, policy or lease condition;
- application or submission ID;
- submission and completeness dates;
- portal time limit and calculated due date;
- project need date and dependency;
- current status and last verified date;
- latest objection, responsible person and response deadline;
- portal owner and business owner;
- links to the submitted form, attachments, payment and correspondence;
- escalation level and next follow-up date; and
- approval number, issue date, validity and renewal trigger.
Keep the portal owner and business owner separate. A consultant may own the upload; the plant head still owns the consequence if the Occupancy Certificate is late. Review the register at least weekly during project execution.
Use traffic-light rules based on evidence
Define statuses before the first submission:
- Green: acknowledgement saved, no open objection and the due date is more than seven days away.
- Amber: an objection is open, a dependency is unresolved or the due date is within seven days.
- Red: the recorded deadline has passed, the application was rejected, or the business milestone is at risk.
- Grey: the record is a draft, the portal status cannot be verified or the application number is missing.
Grey is not green. “The consultant says it is filed” is not evidence. Require the submission ID and acknowledgement.
Keep one evidence pack per application
Create a controlled folder named with the service and application ID. It should contain:
- the submitted application as rendered by the portal;
- every uploaded attachment in its submitted version;
- the fee calculation, challan and payment confirmation;
- the acknowledgement and submission ID;
- every portal objection or department email;
- each response with its timestamp and attachments;
- inspection notices, reports and closure evidence; and
- the signed approval, certificate, NOC or rejection order.
Do not overwrite a rejected drawing with the corrected one. Version both so the change history remains provable.
Track dependencies as a chain
Some approvals depend on earlier records. The MIDC catalogue itself names “e-Intimation of Commencement of work after Building Plan Approval”, which makes the dependency explicit. An Occupancy Certificate comes after construction compliance, not merely after an online form. A water or drainage connection can also affect commissioning plans.
Write dependencies in the tracker as Approval A → Approval B → production milestone. When the earlier item turns amber, the downstream owner should see the risk immediately. This is where approval tracking becomes commercially useful: it protects the start date rather than merely recording government correspondence.
When can a MIDC delay use the Right to Services appeal route?
Not every portal service automatically carries a statutory appeal right. The MIDC Right to Services page says that, out of 35 services available through the SWC portal, 17 are notified under the Maharashtra Right to Public Services Act, 2015. Several are integrated with the Aaple Sarkar portal.
The same official page says an eligible person may use first and second appeals where a notified service is not delivered within the stipulated time or is rejected without proper grounds. If still dissatisfied, the person may prefer a third appeal to the Maharashtra State Commission for Right to Public Service. It also states that an erring officer can be liable for a penalty of up to ₹5,000 per case.
That officer penalty is not compensation automatically paid to your business, and it does not apply merely because a project manager dislikes the pace. Before escalating, verify all of the following:
- the exact service is in the current RTS notification;
- the applicant is eligible for that notified service;
- the application was complete and validly submitted;
- the stipulated time has actually expired;
- no clarification, inspection or payment remains pending from the applicant; and
- you have the acknowledgement, status history and relevant order.
Use the official MIDC RTS page and linked notification to identify the designated officer and appellate authorities for the service. The page directs applicants to Aaple Sarkar for service timelines, application tracking and grievances when deadlines are missed.
Escalate with a factual chronology
A strong escalation is short and document-led. State:
- the service and application ID;
- the date of valid submission;
- the stipulated time and calculated expiry date;
- each objection and the date you answered it;
- the current portal status;
- the order or action requested; and
- the attached evidence index.
Do not claim a statutory penalty before confirming the notification or open duplicate applications to force movement. The SWC login page warns that duplicate plot registrations using the same company name are not allowed and users may be blocked.
What should you do after an approval is issued?
Approval is not the end of the control. Check the document against the application on the day it arrives:
- legal entity name and registered address;
- MIDC plot number and unit location;
- approved activity, capacity and building use;
- drawing or attachment version referenced;
- conditions that must be completed before construction or operation;
- inspection, reporting or display requirements;
- issue date, effective date and expiry date; and
- amendment, transfer or renewal conditions.
Turn every approval condition into a task with an owner and date. For example, a Final Fire NOC renewal should not sit as a PDF in the project folder; its validity and next action belong in the operating compliance calendar. A change in company name, manufacturing activity, plot use or ownership may also trigger a fresh MIDC service rather than a simple internal update.
Compliance Radar turns these approval conditions, renewals and regulatory changes into one business-specific timeline across central, Maharashtra, municipal and sector authorities. Check the pricing if your current system is a spreadsheet, a consultant's inbox and hope wearing a tie.
MIDC approval tracking checklist
- [ ] Approval universe mapped for the plot, activity and project stage
- [ ] Official portal route and service name verified
- [ ] Governing authority and legal basis recorded
- [ ] One row created for every approval transaction
- [ ] Portal time limit captured on the filing date
- [ ] Project need date and buffer documented
- [ ] Submitted form, attachments, payment and acknowledgement archived
- [ ] Application ID verified; draft is not treated as filed
- [ ] Objections assigned with response deadlines
- [ ] Dependencies linked to construction and production milestones
- [ ] RTS-notified status checked before an appeal
- [ ] Issued approval checked field by field
- [ ] Conditions, expiry dates and renewals moved into operations
Frequently asked questions
Is MIDC single window the same as MAITRI?
No. MIDC SWC is the corporation's online facility for industrial services, while MAITRI is Maharashtra's broader investment facilitation mechanism. Official pages may link or integrate services across portals. Follow the route shown for the exact service and retain the application ID from the system that accepted the filing.
Does one MIDC single window application cover every factory approval?
No. The service catalogue separates land, fire, engineering, planning and other transactions. External authorities may still govern pollution, factory safety, electricity and sector-specific permissions. Build an approval universe for the specific unit instead of assuming one registration covers the project.
How long does MIDC approval take?
There is no single timeline. The public catalogue currently shows examples from one day for e-intimation of commencement to 45 days for tree felling, trimming or replantation. A combined building-plan approval and provisional Fire NOC is displayed as 35 days. Verify the live service and applicable RTS notification when filing.
Can I appeal if the MIDC deadline is missed?
Only after confirming that the service is RTS-notified and that the statutory conditions are met. MIDC says 17 of its 35 SWC services are notified under the Maharashtra Right to Public Services Act, 2015. Its official RTS page describes first and second appeals, followed by a third appeal to the State Commission.
What proof shows that an application was filed?
Keep the submitted form, uploaded documents, payment confirmation and portal-generated acknowledgement with the application ID. A draft, payment debit or consultant message alone does not prove valid submission.
Should I submit a second application if the first one is stuck?
Not casually. The portal warns against duplicate or multiple plot registrations with the same company name and says users may be blocked. Check the existing status, answer objections and use the documented grievance or appeal route where applicable.
How should a multi-unit company track MIDC approvals?
Use one register with a separate row for every entity, plot, unit and service. Keep unit-specific evidence folders, assign local action owners and give a central compliance owner visibility over deadlines, conditions and renewal dates.
Make the portal part of a controlled approval system
The MIDC single window is useful infrastructure, but a login is not an approval strategy. Map each required service, capture its own timeline, preserve the full evidence chain, connect dependencies to project milestones and verify whether the Right to Services route applies before escalating.
The payoff is brutally practical: fewer lost objections, fewer invisible delays and a cleaner handover from project execution to plant operations. Check your compliance posture free at complianceradar.in and put every applicable approval, condition and renewal into one accountable timeline.