Compliance
FSSAI Schedule 4 Requirements Checklist
Schedule 4 is a condition of your FSSAI licence, not optional guidance. A plain-language FSSAI Schedule 4 checklist splitting one-time fixes from recurring tasks.
Why a legal schedule decides whether you keep your licence
Search for "FSSAI Schedule 4" and you get scanned government PDFs and Scribd uploads. Nobody explains it in the language of someone running a 40-cover family restaurant in Pune or a two-brand cloud kitchen in HSR Layout. That gap is dangerous, because when a Food Safety Officer walks into your kitchen, the inspection checklist in their hand is built directly from this document.
Schedule 4 sits inside the FSS (Licensing and Registration of Food Businesses) Regulations, 2011. Its formal title is "General Hygienic and Sanitary Practices to be followed by Food Business Operators". Part II covers establishments that need a licence rather than basic registration, which is where restaurants, QSRs, caterers and cloud kitchens sit.
The phrase that matters is condition of licence. When you registered on FoSCoS, you did not just agree to hang a certificate at reception. You agreed to run the premises to Schedule 4 standards every day the licence is live. An FSO does not need to find spoiled food to act against you; premises that fall short of Schedule 4 are grounds on their own.
The requirements in plain kitchen language
The original text reads like it was written for lawyers. Here is what each cluster means on the floor.
Layout and premises
The layout must prevent cross-contamination between raw and cooked food. Receiving, pre-processing (washing, peeling, butchery) and cooking should flow in one direction, so a crate of raw chicken never crosses the counter where biryani gets plated. In a 300 sq ft cloud kitchen you achieve this with strict zoning and workflow discipline rather than walls, but the principle is the same and inspectors check for it.
Floors, walls and ceilings
Surfaces must be impervious, smooth and easy to clean, with no flaking paint or plaster. That bubbled patch above the wok station from last monsoon is not cosmetic; it is a Schedule 4 finding. Inspectors look up as often as they look down.
Ventilation, lighting and water
Air must never flow from contaminated areas to clean ones. Your exhaust should pull air out through the dishwash and waste zones, not drag it across the pass. Lighting must be adequate at every workstation. Water used for anything that touches food, from washing vegetables to making ice, must be potable with a continuous supply. Overhead tanks count as part of that system, which is why they need cleaning on a schedule.
Equipment
Equipment must allow temperature monitoring and control. In practice that means a working, readable thermometer in every chiller and freezer, a calibrated probe for core temperatures, and hot-holding that genuinely holds temperature instead of a tired bain-marie drifting to 50°C.
People
Every food handler needs a medical fitness certificate renewed annually; para 10.1.2 of Part II states it directly, and FSSAI publishes a standard proforma for the examination. Training is also named. FSSAI's FoSTaC mandate requires at least one certified Food Safety Supervisor per 25 food handlers on each premises, and that supervisor must train the rest of the team quarterly, with records to show for it. Our FoSTaC guide covers who to certify and how.
Pest control, waste and cleaning
Schedule 4 names a pest control programme, waste segregation, documented cleaning schedules and FIFO stock rotation. Notice the recurring word: records. A spotless kitchen with no cleaning log is, in an inspector's eyes, an undocumented kitchen, and undocumented reads as non-compliant.
The working checklist: build items versus recurring tasks
The most useful way to read Schedule 4 is to split it in two. Some requirements are one-time build decisions you fix once and verify occasionally. Others are recurring tasks that live or die on whether your team runs them every shift.
One-time build items
- Layout: one-directional flow from receiving to pre-prep to cooking to dispatch, with raw and cooked zones separated.
- Surfaces: impervious, smooth floors, walls and ceilings; zero flaking paint or plaster in food areas.
- Ventilation: extraction that moves air outward through dirty zones, never back across clean ones; adequate lighting throughout.
- Water: potable supply for every food-contact use, including ice; tanks accessible for cleaning.
- Facilities: toilets and handwash stations separate from food handling areas, stocked with soap and running water.
- Equipment: chillers, freezers and hot-holding units with thermometers your staff can actually read.
Audit these once a year and after any renovation. They rarely drift on their own.
Recurring tasks
These drift constantly, which is why each one needs an owner, a timing and evidence.
- Cleaning with records
- Owner: Shift lead | Timing: Every shift, against a written kitchen cleaning schedule
- Evidence/Proof: Signed log per area; photos for weekly deep cleans.
- Escalation: A missed clean is flagged to the manager the same day, not at week end.
- Temperature monitoring
- Owner: Commis per station | Timing: Opening, mid-shift and close, minimum
- Evidence/Proof: A log per unit, filed where you can retrieve it in under a minute.
- Escalation: Out-of-range reading: move stock, call the technician, record the corrective action.
- Pest control
- Owner: Manager plus a licensed operator | Timing: Dry stores every 15 days, per FSSAI's catering guidance
- Evidence/Proof: Service reports filed by date.
- Escalation: Any sighting between services triggers an ad hoc visit.
- Medical fitness certificates
- Owner: Owner or HR | Timing: Annually for every handler, plus each new joiner
- Evidence/Proof: Certificate on the FSSAI proforma, filed per employee.
- Escalation: No certificate means no food-handling duties until cleared.
- FIFO rotation
- Owner: Store in-charge | Timing: Every receiving, every issue
- Evidence/Proof: Date labels on every container, oldest stock in front.
- Escalation: Undated stock is discarded and the receiving process reviewed.
- Water testing
- Owner: Manager | Timing: Every six months, against the IS:10500 potable standard
- Evidence/Proof: Lab reports on file; inspectors treat this as a critical item.
- Escalation: A failed test means switching source and retesting before further use.
- Handler training
- Owner: FoSTaC-certified supervisor | Timing: Quarterly, covering all handlers
- Evidence/Proof: Attendance records with dates and topics.
- Escalation: New joiners are trained before their first solo shift.
The enforcement teeth: Section 32
Schedule 4 is enforced through periodic FSO inspections. When an officer finds non-compliance, Section 32 of the FSS Act lets them issue an improvement notice: fix these items by this date. Ignore the notice and the licence can be suspended, and after continued failure, cancelled. Separately, Section 56 carries a penalty of up to ₹1 lakh for unhygienic or unsanitary processing conditions. The full Act sits on India Code if you want the primary text.
The practical takeaway: an improvement notice is survivable when your recurring tasks have records behind them. It becomes existential when you cannot show any history of compliance. If a visit may be coming, our FSSAI inspection preparation guide lays out a 30-day plan.
Where paper registers break down
A paper cleaning register at a single site can work, provided the manager genuinely reviews it. The failure modes are predictable, though: pages filled in at week end from memory, registers that go missing the morning of an inspection, and no way to prove the 15-day pest cycle actually ran every 15 days. Add a second site, or a cloud kitchen brand where the owner is rarely on premises, and paper stops being evidence and becomes decoration.
Digital checklists fix the retrieval problem. Every Schedule 4 recurring task becomes a scheduled item with an owner, a timestamp and photo proof, and the whole history is searchable the moment an FSO asks. To see Schedule 4 running as a live task calendar instead of a PDF, open the Food Ops demo and walk one shift through it.