Quick answer
FSSAI Schedule 4 hygiene requirements generally expect food businesses in Hyderabad and across Telangana to show that pests are actively controlled. In practice, that means keeping a pest control file. It should hold your service agreement and plan, a map of monitoring devices, dated service reports, product information sheets, a pest sighting register and a corrective-action log. Keeping these current, signed and in one place makes inspections and audits much simpler.
Key points
- FSSAI Schedule 4 hygiene requirements generally expect food premises to have a working pest control programme, and records are how you show it runs.
- A typical pest control file holds the contract and plan, site map, service reports, licence and product sheets, a sighting register and a corrective-action log.
- A pest sighting register captures staff sightings between professional visits; each entry should lead to an action and a closure.
- Corrective actions often involve proofing, repairs and sanitation rather than chemicals, and should be verified and signed off.
- A monthly self-check of the file against the premises keeps a food business ready for unannounced inspections.
A food safety officer or third-party auditor may ask to see your pest control records. This applies whether you run a restaurant, cloud kitchen, bakery, catering unit or food store in Hyderabad.
FSSAI pest control records are not a single form. They are a small set of documents that together show pests are being prevented, monitored and dealt with. This guide explains what is typically kept, how to run a sighting register and a corrective-action log, and how to stay ready for an inspection.
Why do pest control records matter for a food business?
Schedule 4 of the FSSAI licensing and registration regulations sets out general hygiene and sanitary requirements. These expect food premises to be kept free of pests and to have a pest control programme in place.
An inspector cannot see the visits that happened last month. Records are how you show that the programme actually runs.
Records also help you. A well-kept file shows patterns, such as the same drain producing cockroaches every few weeks or rodent activity rising in one store room. That lets you fix causes instead of reacting to each sighting.
If you follow a HACCP-based food safety plan, pest control usually sits among its prerequisite programmes. Its records are then reviewed alongside cleaning and temperature logs.
Exact expectations vary with your type of licence or registration, the size of the operation, and whether you also face customer or brand audits. Use this guide as a general framework, and confirm specific requirements with your food safety consultant or auditor.
What documents are typically kept in a pest control file?
Most food businesses keep the following, either in a physical folder or a shared digital folder:
| Document | What it shows | Usually provided by |
|---|---|---|
| Service agreement or contract | Scope, pests covered, visit frequency and areas included | Pest control provider |
| Pest management plan | The approach (inspection, monitoring, proofing, treatment) and who is responsible for what | Provider, agreed with you |
| Site map or device layout | Numbered locations of rodent stations, traps, glue boards and fly control units | Provider, updated whenever devices move |
| Service report for every visit | What was inspected, what was found, what was done and what is recommended | Provider |
| Product information | Product names, CIB&RC registration, labels and Material Safety Data Sheets (MSDS) for products used on site | Provider |
| Operator licence copy | That the provider holds a valid state pest control operator licence under the Insecticides Act, 1968 | Provider |
| Pest sighting register | Pests noticed by your staff between visits | Your team |
| Corrective-action log | What was done about each problem and whether it worked | Your team, with provider input |
| Periodic trend review | A summary of activity by area and pest over recent months | Provider or your food safety lead |
The licence and product documents are worth checking before you sign any contract. Our guide to choosing a licensed pest control operator in Telangana explains what to ask for.
What should a good service report include?
- Date, and time in and time out.
- Name of the technician.
- Areas and device numbers inspected.
- Activity found at each device or area, such as none, droppings, bait taken or insects caught.
- Treatments carried out, and exactly where.
- Products used, so they can be matched to the MSDS in your file.
- Hygiene and proofing observations, such as gaps under doors, torn mesh or food debris behind equipment.
- Signatures of the technician and your representative.
A report that only says "general treatment done" is of little help in an audit. Ask your provider for specifics, and read each report before signing it.
How do you keep a pest sighting register?
Between visits, your own staff are the ones who notice pests. A sighting register captures what they see so that it reaches the people who can act on it.
Keep it in a fixed, easy-to-reach place, for example near the kitchen supervisor's desk or at the goods-receiving area.
| Column | Example entry |
|---|---|
| Date and time | 12 March, 10:40 pm |
| Area / location | Dishwash area, under sink 2 |
| Pest seen | Small cockroaches |
| Number or evidence | Three live, droppings on pipe |
| Reported by | Name of staff member |
| Immediate action | Area cleaned, food moved, supervisor told |
| Provider informed? | Yes, with date |
| Closed and signed | Date and supervisor's initials |
A few habits make the register useful:
- Record every sighting, even a single insect.
- Record evidence as well as live pests: droppings, gnaw marks, shed skins, nesting material or damaged packaging.
- Let any staff member make an entry. Do not wait for a supervisor to be present.
- Review the register weekly, and share it with your provider at each visit.
- Show new staff where it is during induction.
A register with no entries for many months can look less credible than one with honest entries and clear follow-up. What matters is that each entry leads to an action.
What goes into a corrective-action log?
The corrective-action log links a problem to its fix. The problem might come from the sighting register, a recommendation in a service report or an audit finding. Each entry should cover:
- The issue: what was found, where and when.
- Likely cause: for example, a broken drain cover, a door gap, stock stored on the floor or waste left overnight.
- Action agreed, and who is responsible for it: your maintenance team, your housekeeping team or the pest control provider.
- Target date for completion.
- Date completed.
- Verification: a follow-up check, often at the next service visit, confirming the problem has reduced or stopped.
- Sign-off by the person responsible for food safety.
Many corrective actions involve no chemicals at all. Examples include fitting a door sweep, fixing a leaking pipe under a sink, sealing cable entries, changing waste collection times or raising stock onto racks.
Recording these shows that you are managing the conditions pests depend on. That is the core of integrated pest management. In kitchens, cockroaches are often the main driver of entries; see our guide to German cockroaches in Hyderabad restaurant kitchens.
How should you organise the file?
- One file per premises. If you run several outlets, each needs its own records.
- Fixed sections in a fixed order. A sensible order is: contract and plan, licence and product documents, site map, service reports, sighting register, corrective-action log, trend reviews.
- Current site map at the front, so an inspector can walk the floor with it.
- Service reports in date order, so any gap in visits is obvious to you before it is obvious to an auditor.
- Product sheets kept current. When a new product is used, its label and MSDS should be added.
- Digital copies backed up. Scanned or emailed reports should be saved in one shared folder, not on one person's phone.
- Older records retained. Do not throw away past reports; ask your auditor or consultant how long they expect records to be kept.
- A named owner, usually the person responsible for food safety, with a deputy for days off.
Cloud kitchens often run several brands from one kitchen. In that case one file for the kitchen usually makes more sense than one per brand. Our guide to pest control for cloud kitchens in Hyderabad covers the setup in more detail.
How do you stay ready for a food safety inspection?
Inspections and audits are not always announced in advance. A short monthly self-check keeps you prepared:
- The latest service report is filed and signed, and there is no unexplained gap between visits.
- The site map matches the devices on the floor. Numbers are visible, and no device is missing, damaged or blocked by stock.
- Every product named in the reports has a label or MSDS in the file.
- The provider's licence copy is current.
- Every sighting register entry has an action and a closure.
- Open corrective actions have target dates, and any overdue item has a written reason.
- The premises match the paperwork: drains covered, gaps sealed, no food debris under equipment, no standing water.
- Staff on every shift know where the file is and can explain how they report a pest.
Pest pressure also changes through the year. In the Hyderabad region the monsoon tends to bring more flies and more water collecting around premises. The hot, dry summer can draw pests indoors towards water and shade.
A pre-monsoon review of drains, waste areas and door seals is worth recording in your log. The Hyderabad pest calendar and our guide to monsoon pests in Hyderabad can help you plan.
Common gaps in pest control records
- Service reports with no device-level detail.
- Site maps that were never updated after a kitchen layout change.
- Missing product sheets for treatments that were carried out.
- A sighting register kept only by the provider, so staff sightings between visits go unrecorded.
- The same recommendation repeated visit after visit with no corrective action logged.
- No record of how food and food-contact surfaces were protected during a treatment.
Discuss with your provider which device types suit each zone. Toxic baits are generally kept away from open food and food-contact surfaces.
Whenever a treatment is carried out, follow the provider's and the label's instructions. Remove or cover food, ventilate the area, keep staff out until surfaces are dry or as advised, and clean food-contact surfaces before use.
How we approach service records
In our established Goa operation, we follow an integrated pest management approach: inspection, sanitation and proofing advice, and targeted treatment. We share service reports after visits, with WhatsApp updates for clients.
For food businesses in Goa, we provide documentation aligned with HACCP and FSSAI audit expectations. Material Safety Data Sheets are maintained for the products we use. The record-keeping practices in this guide reflect how we work in Goa.
Our Shamshabad branch has recently opened. Tell us your location and the problem, and we'll confirm whether we can help.
You can find out more about the Hyderabad branch in Shamshabad or read the Hyderabad branch FAQs.
Frequently asked questions
QDoes FSSAI prescribe a fixed format for pest control records?
Schedule 4 sets out hygiene and pest control expectations in general terms rather than one mandatory template for every business. What inspectors and auditors generally look for is evidence that a pest control programme exists, runs regularly and leads to action when problems appear. Some customer or brand audits do specify their own formats, so check with your auditor or food safety consultant if you are unsure.
QHow often should a restaurant or food unit have pest control visits?
It depends on the type of premises, the pests involved and the level of activity. Frequency is usually agreed in the pest management plan, and can be weekly, monthly or quarterly. High-risk areas such as busy commercial kitchens generally need more frequent attention than dry stores or offices. Whatever you agree, the records should show visits happening on that schedule without unexplained gaps.
QWho should fill in the pest sighting register?
Anyone on your team who sees a pest or signs of one: cooks, stewards, store staff, cleaners or supervisors. The register works best when entries are made at the time of the sighting, not remembered later. A named person, usually whoever is responsible for food safety, should review it regularly, make sure each entry has an action, and share it with your pest control provider at every visit.
QCan we keep our pest control records digitally?
Generally yes, provided the records are complete, dated, easy to find and can be shown promptly during an inspection. Many businesses keep emailed or scanned service reports in a shared folder and use a printed register in the kitchen for staff sightings. Back up digital files, avoid keeping them on one person's phone, and make sure more than one staff member can access them.
QWhat should we do if an inspector finds pest activity during a visit?
Record it in the sighting register straight away, then open an entry in your corrective-action log noting the likely cause, the action agreed and a target date. Inform your pest control provider so the area can be inspected and treated if needed. Showing a clear, documented response is far better than leaving a finding unrecorded. Keep any written observations from the inspector in your file.
QWhy do we need a copy of our pest control provider's licence?
In India, pest control operators are licensed by state authorities under the Insecticides Act, 1968, and the products they use should be registered with CIB&RC. Keeping a current licence copy and product information in your file shows that the treatment on your premises is carried out by an authorised operator using registered products. Ask for these before signing a contract and check they stay current.
Last updated 13 October 2026. Information on this page is general guidance; your technician will advise on your specific property after inspection.
