Why RO and UV service records matter for FSSAI and FDA compliance

What Indian food businesses are actually required to keep, and why a service report is not the same as a water-test report.

If a restaurant, hotel, cloud kitchen or food factory uses an RO or UV system, is it compulsory to keep an “RO/UV servicing report” under FSSAI or FDA standards?

The accurate answer is more useful than a simple yes or no:

The exact documents that apply depend on the kind of food business, its licence, how water is used, the water source and current FSSAI/FoSCoS directions.

This distinction protects a food business from two costly mistakes:

1. assuming that an annual maintenance invoice proves the water is potable; or
2. paying for unnecessary RO treatment because someone says “FSSAI requires RO.”

The regulatory position in one table

[Source: FDA Maharashtra, Food Administration]

FSSAI, state FDA and BIS: three roles that should not be confused

FSSAI sets the national food-safety framework

The Food Safety and Standards Authority of India administers the national framework under the Food Safety and Standards Act. Its Licensing and Registration Regulations include Schedule 4 hygiene and sanitary requirements for food businesses.

State food-safety authorities enforce it

In Maharashtra, the Food and Drug Administration is the state regulatory authority responsible for enforcement of food-safety laws. Food Safety Officers may inspect food premises and examine compliance evidence. Other states use their own food-safety enforcement machinery.

Calling a record an “FDA certificate” can therefore be misleading. A service company does not issue an FSSAI or state-FDA approval merely by servicing an RO or changing a UV lamp.

BIS publishes the drinking-water specification

IS 10500 is the Indian Standard for drinking-water specification. It covers requirements and methods of sampling and testing, including physical, chemical and bacteriological aspects. FSSAI guidance and checklists refer to potable water meeting the applicable/latest IS 10500 requirements. [Source: BIS, IS 10500 overview]

The applicable edition, amendments, test parameters and sampling plan should be confirmed for the facility at the time of testing. A generic “water is OK” statement is not a substitute for a report that identifies the sample, method, result, unit and applicable limit.

What FSSAI actually says about water evidence

FSSAI’s published licensing FAQs provide unusually specific answers for businesses using water as a food ingredient.

Municipal-government potable supply

FSSAI FAQ 121 says that an FBO using potable water supplied by a municipal corporation as an ingredient may submit commercial water bills instead of a water-test report for the licence.

FAQ 123 further states that the testing requirement does not apply to potable water supplied by a municipal corporation, subject to the FBO maintaining water bills as evidence.

This exception does not prove that water remains protected after it enters a building. Underground tanks, overhead tanks, internal plumbing, cross-connections and an incorrectly maintained treatment system can create risks downstream of the municipal supply. The FBO must still control water used in its operation.

Water supplied by a mall, commercial hub or private authority

FAQ 122 says that an FBO receiving water from a mall, commercial hub, market or private authority should obtain the water-testing report from that authority. For the licensing submission described in the FAQ, the report should not be older than one year.

FAQ 123 says businesses supplied by such an authority should obtain testing reports from it at the stated frequency. The FBO should keep the report traceable to the actual supply and period, not merely rely on an informal assurance from facility management.

Water used as an ingredient

FAQ 123 says food businesses using water as an ingredient must test it against BIS IS 10500, except radioactive parameters, at least once in every financial year, with at least a six-month gap between two successive water samples. It also says the water-testing report must be produced to the Food Safety Officer or an authorised third-party auditor during inspection or audit.

This wording should not be rewritten as “exactly every six months.” The FAQ states a minimum annual requirement and a minimum gap between successive samples. A licence condition, product standard, customer scheme, internal HACCP plan, source-risk assessment or later FSSAI direction may justify or require additional testing.

[Source: FSSAI, Frequently Asked Questions on Licensing and Registration, questions 121–123]

Licensing documents vary by kind of business

FoSCoS’s state-licence document page lists a chemical and bacteriological analysis report for water used as an ingredient, from a recognised/public-health laboratory to confirm potability, as mandatory for manufacturing and processing units. The exact document list varies by Kind of Business and licence application. [Source: FoSCoS, documents required for State Licence]

Businesses should therefore check their current FoSCoS application requirements, licence conditions and category-specific standard rather than copying a document list from another business.

Why maintenance records still matter

The absence of a universally named “UV/RO service report” does not make maintenance paperwork optional in practice.

FSSAI’s revised Schedule 4 material states that where water filters are used, they must be regularly changed or effectively maintained. FSSAI inspection checklists also assess preventive maintenance of equipment and ask inspectors to check records. [Source: FSSAI, operationalisation of revised Schedule 4 requirements]

FSSAI’s inspection matrices are used by Food Safety Officers to record compliance, partial compliance and non-compliance across areas including control of operation, maintenance and sanitation. [Source: FSSAI, inspection matrices]

For an installed RO or UV unit, a proper service record helps answer questions such as:

• Was the equipment maintained at the required time or operating hours?
• Were alarms, sensors and safety interlocks functional?
• Was a fouled, exhausted or failed component identified?
• What was replaced, cleaned, repaired or sanitised?
• Were abnormal readings investigated?
• Was the unit returned to service only after suitable checks?
• Does the service history agree with operator logs and laboratory results?

These are evidence questions. A blank service sticker or invoice does not answer them.

Four records, four different purposes

1. Laboratory water-test report

What it shows: the measured quality of a specifically identified sample at a specific time and sampling point.

It should identify, as applicable:

• the client and facility;
• the source and exact sampling point;
• the date and time of sampling;
• who collected the sample;
• sample condition or identification;
• test method;
• result and unit;
• comparison limit or specification;
• laboratory identity and authorised signatory; and
• the laboratory’s relevant recognition/accreditation status and scope where required.

FoSCoS provides a sample document description requiring a chemical and bacteriological report from a recognised/public-health laboratory, including the authorised laboratory representative who collected the sample and the date of collection. [Source: FoSCoS sample water-test report requirement]

What it does not show: whether the RO membrane, UV lamp or pretreatment will remain effective until the next sample.

2. RO/UV service and maintenance report

What it shows: the condition observed, work performed, parts used, readings taken, faults found and corrective action completed during a particular visit.

What it does not show: full chemical and microbiological compliance of the treated water unless an appropriate laboratory separately tested a correctly collected sample.

3. Operating log

What it shows: whether important readings, alarms and operating conditions stayed within the system’s approved range between service visits.

Depending on the design, the log may cover pressure, flow, conductivity, UV intensity, lamp status, tank level, differential pressure, chemical dose, alarm events and corrective action. The parameters and limits must come from the approved design, validation and equipment manuals, not a generic internet checklist.

4. Source evidence

This may include municipal commercial water bills, an authorised supplier’s report, source declarations, tanker delivery records or other records applicable to the facility.

Source evidence establishes where the water came from. It does not automatically establish the condition of the facility’s tanks, plumbing or point-of-use system.

A simple evidence chain for audit readiness

An audit-ready water-safety file should connect the complete chain:

If one link is missing, the remaining documents may not answer the inspector’s question.

For example:

• A compliant lab report with no sampling-point description may not establish whether raw water or final-use water was tested.
• A signed RO service report with no laboratory report cannot establish microbiological potability.
• A UV lamp replacement invoice with no lamp-status or intensity check cannot show that the reactor operated as intended.
• A municipal bill may establish the incoming source but not hygienic condition after an unclean building tank.
• A daily TDS log cannot detect coliform bacteria.

Why an RO system needs more than a filter-change sticker

Reverse osmosis is a membrane-separation process. Its performance depends on feed-water characteristics, pretreatment, pressure, temperature, recovery, membrane condition, flow and maintenance.

An RO service record may need to capture:

• feed, permeate and concentrate flow;
• feed and stage pressures where instruments are installed;
• prefilter differential pressure;
• feed and permeate conductivity;
• calculated salt rejection, using a defined formula and suitable instruments;
• temperature and pH where relevant to performance evaluation;
• recovery and normalised performance where required;
• membrane cleaning, replacement or sanitisation;
• leaks, seal integrity and valve condition;
• storage-tank and distribution hygiene; and
• alarms, shutdowns and corrective work.

DuPont’s current FilmTec technical manual recommends keeping start-up and operating records, including pressure, flow, conductivity, pH and temperature, for performance tracking and troubleshooting. These are technical good practices, not a universal FSSAI form. The exact parameters depend on the installed plant. [Source: DuPont, FilmTec Reverse Osmosis Membranes Technical Manual, February 2026]

RO does not by itself prove safe drinking water

A low permeate TDS value is not a microbiological certificate. Contamination can occur through an unclean tank, biofilm, a damaged seal, a bypass, poor sanitisation, the distribution system or sampling error. RO performance data and laboratory testing answer different questions and should be used together.

Why UV service records need operating evidence

UV disinfection performance is affected by the dose delivered to the target organisms. In a real reactor, performance can be influenced by:

• lamp output and age;
• lamp failure or ballast fault;
• quartz-sleeve fouling;
• UV transmittance of the water;
• flow through the reactor;
• reactor design and validation conditions;
• sensor cleanliness and calibration; and
• alarm and shut-off function.

The US EPA’s UV guidance explains that flow, lamp status and UV intensity are core operating parameters for validated UV operation, and that sleeve fouling can depend on water chemistry including hardness, alkalinity, pH, iron and calcium. This is a technical reference, not an Indian FSSAI requirement, but the engineering principles are relevant to Indian installations with hard, iron-bearing or variable water. [Source: US EPA, Ultraviolet Disinfection Guidance Manual]

WHO technical guidance also notes that UV lamps require periodic replacement, sleeves require cleaning and UV leaves no disinfectant residual to protect water against contamination after treatment. [Source: WHO, Managing Water in the Home]

That last point is important. A working UV unit does not protect water that is subsequently exposed to a dirty tank, open vent, contaminated pipe, cross-connection or unhygienic dispenser.

Do not publish a universal UV-lamp replacement interval

Lamp life is model- and duty-specific. A service provider should record operating hours and follow the reactor manufacturer’s instructions. “Change every year” may be a common service convention for some systems, but it is not a universal FSSAI rule and should not be presented as one.

What a defensible RO/UV service report should contain

A useful report should make the visit reconstructable by someone who was not present.

Facility and equipment identity

• FBO name, site address and FSSAI licence number where relevant;
• area or process served;
• water source in use on the service date;
• equipment type, make, model, capacity and serial/asset number;
• treatment flow diagram or train reference;
• service date, start and finish time; and
• technician name, organisation and signature.

Reason and scope of visit

• scheduled preventive maintenance, breakdown, alarm, adverse water result or commissioning follow-up;
• stated scope and exclusions;
• previous unresolved observations; and
• safety isolation and return-to-service status.

Condition before service

• operating status and active alarms;
• visible leaks, corrosion, fouling or damage;
• instrument readings with units;
• consumable age or operating hours where known;
• bypass and valve position; and
• deviations from the approved operating range.

Work performed

• components cleaned, adjusted, repaired or replaced;
• part description, rating and batch/serial number where traceability is important;
• RO membrane cleaning or replacement details;
• UV lamp, sleeve, sensor and ballast work;
• filter-cartridge or media work;
• tank or line sanitisation performed within scope;
• chemical name, concentration and contact time where sanitisation is performed and controlled; and
• waste disposal or flushing relevant to safe return to service.

Verification after service

• final readings, units and acceptance range;
• alarm, interlock and shutdown tests;
• leak and flow verification;
• instruments used and calibration/verification status;
• water flushed or discarded before use;
• sample taken, exact sampling point and laboratory reference if applicable;
• open deviations and interim controls; and
• authorised release or explicit statement that the system remains out of service.

Recommendations and approvals

• root-cause assessment where a failure occurred;
• corrective and preventive actions;
• due date and responsible person;
• next service based on the approved plan or manufacturer requirement;
• technician and client representative sign-off; and
• supporting photographs where useful.

A signature should confirm what was observed and performed. It should not convert the service report into a statutory certificate of potability.

Which businesses need which evidence?

The following is a planning guide, not a substitute for the current FoSCoS document list or licence condition.

Groundwater permissions and packaged drinking-water requirements are separate regulatory subjects. A general RO service report does not satisfy them.

How often should water be tested and equipment serviced?

There are three different clocks.

Regulatory testing frequency

For water used as a food ingredient, FSSAI FAQ 123 states at least one test in every financial year with at least six months between two successive samples, subject to the stated municipal and private-authority provisions. Check for later orders and requirements specific to the licence or product.

Risk-based additional testing

Additional testing may be appropriate after:

• a source switch or tanker-supplier change;
• flood, ingress or suspected sewage contamination;
• tank or distribution contamination;
• an adverse microbiological or chemical result;
• prolonged shutdown;
• major repair, membrane replacement or sanitisation;
• abnormal taste, odour, colour or turbidity;
• a treatment alarm or loss of control; or
• a change in process that affects water use.

These are prudent risk-based triggers, not a claim that FSSAI prescribes the same extra schedule for every business.

Equipment-maintenance frequency

Service frequency should follow:

• the equipment manufacturer’s instructions;
• actual operating hours and loading;
• feed-water quality and variability;
• differential pressure and performance trend;
• validated operating limits;
• the facility’s preventive-maintenance and food-safety plans; and
• previous failures or adverse trends.

A fixed calendar interval copied from another installation may be too frequent, too late or technically irrelevant.

What to do after an adverse result or treatment failure

A food business should have a written corrective-action procedure before a failure occurs. Depending on the hazard and affected use, a defensible response can include:

1. identify and isolate the affected water route;
2. stop using suspect water for food, beverages, ice or relevant food-contact operations;
3. arrange a verified alternative potable supply where appropriate;
4. protect or hold potentially affected product under the facility’s food-safety procedure;
5. inform the responsible food-safety, quality and management personnel;
6. investigate the source, treatment, tank, distribution and sampling method;
7. repair, clean, disinfect or otherwise correct the cause;
8. take representative follow-up samples through a competent laboratory; and
9. document the evidence and authorised decision before normal use resumes.

The exact escalation, notification, product disposition and release criteria must follow the facility’s HACCP/FSMS plan, licence conditions and applicable law. A service technician should not make product-release decisions outside their authorised competence.

Common misconceptions

“FSSAI certification means the RO is approved”

FSSAI licenses food businesses; it does not turn every installed treatment unit into an “FSSAI-certified RO.” Equipment may carry other product certifications, but those must be checked for the exact model and performance claim.

“The water is municipal, so internal maintenance does not matter”

The FSSAI FAQ provides a testing-document exception for qualifying municipal potable supply. It does not eliminate contamination risks in a building’s storage, treatment and distribution system.

“The technician measured TDS, so no laboratory test is needed”

TDS is only one aggregate water-quality measure. It cannot confirm bacteriological safety or compliance with the applicable chemical parameters.

“A new UV lamp guarantees disinfection”

Not necessarily. Sleeve condition, water UV transmittance, flow, lamp output, sensor/alarm function and downstream hygiene can all matter.

“An AMC invoice is enough for inspection”

An invoice may support commercial traceability, but it does not record the equipment’s condition, before-and-after readings, deviations, corrective work or release checks.

“A laboratory report means the system is safe for the whole year”

A laboratory result applies to the sample, place and time identified in the report. Ongoing control requires source management, hygienic storage, operating checks, maintenance and response to abnormal events.

An audit-ready water-compliance file

Keep one controlled file, physical, digital or both, with:

• current FSSAI licence and relevant conditions;
• current Kind-of-Business document checklist;
• water-source map and intended-use list;
• municipal bills or private-supplier/source records;
• water-risk assessment and sampling plan;
• laboratory reports and sampling traceability;
• approved treatment flow diagram and equipment list;
• equipment manuals and approved operating limits;
• daily/shift operating logs where applicable;
• signed RO/UV and pretreatment service reports;
• filter, lamp, membrane and chemical traceability;
• tank-cleaning and distribution-sanitisation records;
• instrument calibration or verification records;
• alarms, breakdowns and deviations;
• corrective-action and follow-up test records; and
• responsible-person review and closure.

Records should be legible, dated, attributable and protected from untraceable editing. The facility’s retention schedule must meet the applicable FSSAI requirement, licence condition, product shelf-life rule, customer standard and internal FSMS, not an arbitrary period stated by a vendor.

Questions to ask an RO/UV service provider

Before awarding an AMC or service contract, ask:

1. Will every visit produce a signed, asset-specific report?
2. Which readings will be captured before and after service?
3. Are the instruments suitable and currently calibrated or verified?
4. Will parts and consumables be traceable?
5. Will the report identify open deviations instead of marking every visit “OK”?
6. Are alarm, interlock and safe-shutdown checks included?
7. Who is responsible for tanks and downstream distribution?
8. Does sanitisation include a written method and return-to-service criteria?
9. Can the provider coordinate sampling without presenting itself as the testing laboratory?
10. Will the maintenance plan follow the exact equipment manual and observed water conditions?

Frequently asked questions

The practical conclusion

The compliance objective is not to collect a folder of generic certificates. It is to demonstrate control of water from source to point of use.

For an Indian food business, that normally means:

• confirm which water rule and document list applies to the exact licence and use;
• establish potable-water evidence through the appropriate source records and laboratory testing;
• select RO, UV or another treatment only when justified by the water and application;
• monitor the parameters that demonstrate that the installed system remains under control;
• keep detailed, signed preventive-maintenance and repair records; and
• investigate deviations, correct the cause and verify the water before release.

An RO/UV service report is therefore not a substitute for FSSAI compliance. It is one part of the evidence that a food business has maintained the controls on which safe water depends.

How DhwaNeer can help

DhwaNeer can support commercial food facilities with:

• source and point-of-use mapping;
• RO, UV and pretreatment condition assessment;
• asset-specific preventive-maintenance plans;
• structured service reports and operating-log formats;
• performance trending and failure investigation;
• tank, treatment and distribution interface review; and
• coordination of an appropriate laboratory sampling plan.

Laboratory potability reports must be issued by the competent laboratory required for the application. Final regulatory responsibility remains with the Food Business Operator.

Sources and verification notes

This article was checked against the cited sources on 8 August 2026. FSSAI advisories, FoSCoS document lists, BIS standards, state directions and licence conditions can change. Verify the current requirements for your facility’s state, Kind of Business, licence and product category. This article is educational material, not legal advice or a laboratory certificate.

1. FSSAI: FAQs on Licensing and Registration, questions 121–123
2. FSSAI: Operationalisation of revised Schedule 4 requirements
3. FSSAI: Inspection matrices
4. FoSCoS: Documents required for State Licence
5. FoSCoS: Sample water-test report requirement
6. BIS: IS 10500 drinking-water specification overview
7. FDA Maharashtra: Food Administration
8. Government of India: Uniform Drinking Water Quality Monitoring Protocol
9. DuPont: FilmTec RO/NF Technical Manual, February 2026
10. US EPA: Ultraviolet Disinfection Guidance Manual
11. WHO: Managing Water in the Home