Form V Data Collection: How to Build a Monthly Readiness System in an Indian Factory

Form V may be submitted once a year, but almost every number reported in it is generated throughout the year.

Production is recorded by the production team. Raw-material movement sits with stores or ERP. Water readings come from utilities. Monitoring reports remain with EHS, the laboratory or the consultant. Waste quantities are distributed across registers, manifests, weighbridge slips and disposal acknowledgements. Environmental expenditure is maintained by finance and projects.

By the time EHS begins preparing the annual environmental statement, the information may be spread across several departments, files and definitions.

This is where Form V data collection becomes difficult.

The main challenge is usually not filling the final format. It is collecting 12 months of complete, consistently defined, supported and approved information from different parts of the factory.

A practical Form V system therefore does not begin shortly before submission. It operates as a monthly environmental data-close process.

Form V is an annual output of a monthly data-readiness system.

This article focuses specifically on that monthly operating system: responsibilities, evidence, review status, reconciliation, escalation and correction control.

For applicability, due date, Parts A–I, calculations and the Form V format, refer to EHSSaral’s separate Form 5 Environmental Statement Guide. Keeping these two subjects separate helps EHS teams understand both the final statement and the operating process behind it.

Why Form V Preparation Becomes Difficult Near September

Under Rule 14 of the Environment (Protection) Rules, Form V is the environmental statement for the financial year ending 31 March. The reporting date was changed to 30 September through the 1993 amendment. India Code records the applicable amendment and Form V format.

In many Indian plants, however, serious Form V data preparation starts only after the financial year has closed.

EHS then sends requests to several departments:

• Production provides product-wise output.
• Stores provides raw-material receipts and consumption.
• Utilities provides water withdrawal and consumption.
• ETP or STP operators provide treatment and reuse figures.
• Laboratories provide monitoring reports.
• Waste coordinators provide generation and disposal records.
• Finance provides environmental expenditure.
• Projects and maintenance provide improvement details.

Each department may maintain its information for a different purpose.

Production may report in pieces while Form V requires tonnes. Stores may provide material issued instead of material consumed. Utilities may have total water-purchase figures but no source-wise or use-wise allocation. Finance may identify every pollution-control expense under a general maintenance ledger.

None of these records is necessarily wrong. They were simply created for different operational purposes.

The annual difficulty arises when EHS has to convert them into one consistent environmental statement.

What usually goes wrong

Common situations include:

• A month is missing from a production file.
• Product names differ between the consent, ERP and annual report.
• Raw-material issues are treated as consumption without inventory adjustment.
• Water bills and meter readings cover different date ranges.
• A monitoring report belongs to another sampling period or location.
• Waste is recorded as generated in one file and dispatched in another.
• A TSDF acknowledgement remains pending.
• Finance cannot separate environmental expenditure from general maintenance.
• A revised document silently replaces the earlier version.
• A blank cell is interpreted as zero even though the information was never received.

These are data-governance problems. They cannot be resolved reliably by asking EHS to work faster during the filing period.

Form V Is an Annual Output of Different Record Cycles

Not every Form V input should be collected in the same way.

Some information is generated every day and closed monthly. Some becomes available only when monitoring is conducted. Some changes only when a project is implemented or the consent is amended.

A useful Form V data collection system separates information by its natural record cycle.

This distinction is important.

For example, asking a department to upload the same consent details every month creates unnecessary work. At the same time, waiting until year-end to identify missing water readings creates avoidable uncertainty.

A good system applies the right frequency to each dataset.

Define the Reporting Boundary Before Collecting Data

Form V data can appear complete and still be inconsistent if departments are reporting against different boundaries.

Before starting monthly collection, define:

• The factory, unit or site covered
• The financial year
• Included production lines
• Included warehouses and utility areas
• Treatment plants covered
• Water sources covered
• Waste-storage areas covered
• Treatment or disposal activities performed within the site
• Job-work production treatment
• Inter-unit material transfer treatment
• Treatment of trial production
• Treatment of shutdown and maintenance periods
• Cut-off dates for receipts, dispatches and invoices

Consider a plant with two production blocks and a common ETP.

The production team may submit figures for only one block, while utilities report total water supplied to both. The two datasets may be individually accurate but cannot be used together without explaining the boundary difference.

From a practical standpoint, the first monthly control should be:

Are all departments reporting for the same site, period and operational boundary?

This becomes especially important when a plant expands, introduces a new product, adds a borewell, changes its waste route or commissions new pollution-control equipment during the financial year.

Data Provider, Verifier and Approver Are Different Roles

One of the most common Form V department responsibility problems is the assumption that EHS owns every number because EHS prepares the final statement.

EHS usually coordinates Form V, but the source information belongs to several departments.

A practical responsibility structure should distinguish three roles.

Data provider

The data provider is the person or department maintaining the original operational record.

Examples include:

• Production planning for monthly output
• Stores for receipts and inventory
• Utilities for water-meter readings
• ETP operations for effluent treatment
• Finance for expenditure
• Projects for implementation status

Verifier

The verifier checks whether the information is complete, correctly defined and supported by the underlying records.

For example, a stores manager may verify that reported raw-material consumption has considered opening stock, receipts, issues, returns and closing stock.

Final approver

The final approver accepts the reviewed dataset for use in the plant’s annual environmental reporting.

This may be the production head, utilities head, finance head, EHS head, plant head or authorised signatory, depending on the dataset and the factory’s internal authority structure.

A useful operating principle is:

The department closest to the source should confirm the number. EHS should confirm its environmental meaning, reporting relevance and consistency with connected records.

EHS should not be expected to silently certify a production or financial figure that the responsible department has not reviewed.

Form V Responsibility Matrix

The responsibility matrix should identify who provides each dataset, what EHS checks and what evidence supports it.

The exact titles can be adapted to the factory. The important point is that each dataset has a named source owner and does not remain addressed simply to “concerned department.”

Create a Common Naming and Unit Dictionary

A Form V monthly checklist is incomplete without a controlled naming and unit dictionary.

Over a year, the same item may appear under several names:

• ETP sludge
• Chemical sludge
• Treatment residue
• Hazardous-waste category stated in the authorisation

Similarly, a product may appear under its commercial name in production reports, its internal code in ERP and its consented name in regulatory documents.

If these variations are not mapped early, annual consolidation becomes dependent on one person’s memory.

The dictionary should standardise:

• Product names
• Product codes
• Raw-material names
• Raw-material codes
• Waste names and authorised categories
• Water sources
• Water-use categories
• Effluent streams
• Stack names
• Monitoring locations
• Pollution-control equipment names
• Reporting units
• Conversion factors
• Rounding rules
• Department names
• Data-owner names

Important distinctions to define

The dictionary should also distinguish between concepts that are often mixed:

A blank cell should not be allowed to represent zero, pending, not applicable and unknown at the same time.

Monthly Production and Raw-Material Close

Production and raw materials form the operational base for several Form V comparisons.

A monthly close should capture:

• Product-wise production
• Reporting unit
• Production days
• Shutdown periods
• Trial production
• Rejected or reprocessed batches
• Job-work production
• Inter-unit transfers
• New or discontinued products
• Opening raw-material stock
• Material receipts
• Material issues
• Returns
• Closing stock
• Approved inventory adjustments

A practical raw-material relationship is:

Opening stock + receipts − closing stock ± approved adjustments = material consumed

However, this equation should be applied with an understanding of the plant’s process.

ERP issues do not necessarily equal actual consumption. Materials may remain on the shop floor, be returned to stores, become part of work-in-progress or be transferred between units.

Monthly EHS cross-check

EHS does not need to repeat the production department’s accounting process. It should check whether:

• Product names match the reporting dictionary.
• Units remain consistent.
• All operating months are covered.
• Major production changes have explanations.
• Reported output belongs to the defined boundary.
• New products are evaluated against the consent.
• Raw-material quantities are logically related to production.
• Current-year information can be compared with the previous year.

Where commercial confidentiality applies to a raw material, the reporting treatment should be agreed and documented rather than decided during final preparation.

Source-Wise Water and Effluent Reconciliation

Water information often becomes difficult because it comes from several records covering different periods.

The monthly dataset should identify water received from:

• Municipal supply
• Groundwater
• Surface water
• Tankers
• Other approved sources
• Recycled or reused water

Water use should be classified, as relevant, into:

• Process
• Cooling
• Boiler
• Scrubber
• Washing
• Domestic
• Gardening
• Pollution-control operations
• Other site-specific uses

The effluent record should separately capture:

• Effluent generated
• Effluent received at the treatment plant
• Effluent treated
• Water reused
• Water recycled
• Water discharged, where permitted
• Sludge or residue generated
• Exceptional diversion or maintenance events

Issues that need documented treatment

A monthly reconciliation should identify:

• Missing meter readings
• Meter breakdown or replacement
• Meter reset
• Estimated readings
• Tanker supply without complete evidence
• Bills spanning two months
• Abnormal consumption
• Leaks or overflows
• Shutdown months
• Treatment-plant bypass for maintenance, where applicable and authorised
• Difference between freshwater withdrawal and total water circulated
• Change in recycled-water use

The purpose is not to force every water balance to become mathematically perfect.

Real plants have evaporation, moisture in products, floor washing, domestic consumption, gardening, sludge moisture and other legitimate differences. The objective is to make the basis and significant differences understandable.

For a detailed discussion of water-balance scrutiny, readers can refer to EHSSaral’s separate guide on how water bills and effluent records are examined in ZLD audits.

Monitoring-Report Completeness Close

The monthly Form V system should not duplicate the plant’s environmental monitoring programme. Instead, it should verify whether the evidence expected during the period is complete.

For every applicable monitoring activity, check:

• Was monitoring due during the month or quarter?
• Was sampling completed?
• Was the correct source or location monitored?
• Were the required parameters included?
• Does the report identify the correct site and unit?
• Does it cover the correct sampling date?
• Is the report signed or authenticated?
• Is the final report available?
• Has a revised report been clearly identified?
• Are abnormal results connected to review or action records?
• Is the report stored against the correct financial year?

For example, “monitoring completed” is not sufficient if the report covers the wrong stack or omits a consent-specified parameter.

The detailed explanation of monitoring types, parameters and operational interpretation already exists in EHSSaral’s Environmental Monitoring Guide for Indian Factories. The Form V data-readiness process should refer to that framework and focus only on completeness and traceability.

Hazardous and Non-Hazardous Waste Monthly Close

Waste information should be closed stream by stream.

For each applicable waste, record:

• Opening stock
• Quantity generated
• Quantity received from another internal process, if applicable
• Quantity reused or recovered internally
• Quantity dispatched
• Quantity treated
• Quantity disposed
• Closing stock
• Disposal or recovery route
• Transport or manifest reference
• Weighbridge quantity
• Receiver quantity
• Acknowledgement status
• Physical-stock difference
• Adjustment reason

The basic stock relationship is:

Opening stock + generation − authorised movement or treatment = closing stock, subject to documented adjustments

For hazardous waste, the monthly Form V close should use the same source records that support Form 3, Form 10 and the annual Form IV return.

This does not mean every number will look identical without interpretation. Timing, stock, moisture and document cut-offs can create legitimate differences.

The detailed reasons and reconciliation method are covered separately in Why Form IV and Form V Numbers Do Not Match. This article is concerned with preventing those differences from remaining undiscovered until annual preparation.

Non-hazardous waste also requires control

In many plants, non-hazardous waste records are less structured than hazardous-waste records.

The monthly close should still confirm:

• Waste classification
• Quantity generated
• Storage location
• Internal reuse, if any
• Quantity sold or transferred
• Receiver
• Dispatch evidence
• Closing stock

Non-hazardous waste should not become a balancing quantity used to absorb unexplained differences in other records.

Maintain an Environmental Project and Expenditure Register

Environmental projects and expenditure are often reconstructed from emails, purchase orders and personal memory.

A monthly project register can include:

• ETP or STP upgrades
• Air-pollution-control equipment
• Water-reuse systems
• Flowmeters and monitoring instruments
• Waste-reduction projects
• Energy-efficiency improvements
• Process modifications
• Environmental studies
• Greenbelt or conservation activities
• Repair or replacement of pollution-control equipment

Each project should carry a clear status:

The register should separately identify:

• Capital expenditure
• Operating expenditure
• Approved value
• Invoiced value
• Paid value, where relevant
• Expected environmental benefit
• Actual implementation evidence
• Responsible department

An approved budget should not automatically be reported as completed environmental expenditure.

Similarly, a completed physical project may not appear in the same month’s finance ledger if the invoice is pending. The difference should be visible and explained.

Data Completeness and Evidence Completeness Are Different

A spreadsheet can show a value in every row and still not be Form V ready.

For each dataset, the monthly system should ask five separate questions:

1. Is the value available?
2. Is the value recorded in the correct unit and definition?
3. Is supporting evidence available?
4. Has the responsible department verified it?
5. Has EHS completed the environmental cross-check?

Consider two examples.

Example 1: Production

Production reports 850 MT for the month. The number is available, but the ERP extract includes two products under internal codes that have not been mapped to the reporting dictionary.

The data exists, but it is not yet fully ready.

Example 2: Hazardous waste

A disposal quantity is entered in the waste tracker. Form 10 and the weighbridge slip are available, but the receiver acknowledgement remains pending.

The transaction has a number and partial evidence, but its evidence chain is incomplete.

This distinction prevents “cell filled” from being treated as “review complete.”

Use Clear Readiness Statuses

Every monthly dataset should carry a visible readiness status.

“Not applicable” and “nil activity” should remain separate.

A waste category may apply to the facility but have nil generation during a shutdown month. A particular water source may be completely inapplicable because the plant has no connection or permission for it.

The difference matters when annual records are reviewed.

Missing-Data and Delayed-Evidence Escalation

Monthly Form V data collection depends on several departments, so some delays are inevitable.

The response should be structured rather than personal.

A practical escalation sequence can be:

1. Automatic or routine reminder to the data provider
2. Reminder to the departmental verifier
3. Exception shown to EHS before monthly close
4. Escalation to the department head if the due date passes
5. Open item recorded in the monthly action register
6. Closure with data, evidence or an approved explanation

The system should show exactly what is pending:

• Value
• Source document
• Department confirmation
• EHS review
• Correction
• Final approval

A general reminder such as “Form V data pending” is less useful than:

April tanker-water invoices are available, but the source-wise quantity has not been confirmed by Utilities.

This is where EHSSaral helps reduce routine follow-up work. Instead of EHS manually checking different spreadsheets and sending general reminders, the system can identify the exact value, document, verification or approval that remains pending and alert the responsible stakeholder.

EHS can then focus on unresolved exceptions rather than repeatedly chasing information that has already been submitted.

When an estimate is necessary

There may be situations where exact information is temporarily unavailable because of meter failure, damaged records or delayed external evidence.

If an estimate is used, preserve:

• The estimated value
• Estimation method
• Source used
• Reason actual information was unavailable
• Person who prepared the estimate
• Person who approved it
• Date of approval
• Whether replacement with actual data remains pending

An estimate should remain visibly different from a measured or source-confirmed value.

Monthly Freeze and Controlled Corrections

A monthly freeze creates an approved reference point.

It does not mean that a record can never be corrected. It means later changes follow a controlled process instead of silently replacing the earlier value.

A correction record should preserve:

• Original value
• Revised value
• Reason for correction
• Supporting evidence
• Person making the change
• Reviewer
• Approver
• Date of correction
• Related datasets affected

For example, if March hazardous-waste generation is corrected, the change may also affect:

• March closing stock
• April opening stock
• Form IV quantities
• Form V annual totals
• Waste-generation intensity
• Storage-age calculations

A connected correction should therefore be reflected across the relevant records, with the history preserved.

In EHSSaral, a correction can remain connected to the records it affects. For example, a revised hazardous-waste generation quantity can update the relevant monthly balance and Form V preview while preserving the original value, reason, evidence and approval trail.

This helps prevent one corrected number from leaving inconsistent figures elsewhere.

This is one of the most important differences between a controlled monthly system and an annually rebuilt spreadsheet.

Document-Version Control

Documents used during Form V preparation may pass through several versions.

A monitoring report may be corrected. Finance may issue a revised expenditure statement. Production may update output after the monthly accounting close.

The document-control process should identify:

• Document name
• Site
• Reporting period
• Dataset
• Version number
• Date received
• Source department
• Review status
• Replaced version
• Reason for revision
• Final approved version

Old versions should not remain mixed with final versions in one folder without any indication of which document is current.

At the same time, an earlier document should not be deleted if it formed the basis of a previously approved record. Preserving the trail makes later corrections understandable.

Suggested Monthly Form V Closing Calendar

A plant can adapt the following calendar to its accounting and operational close.

The dates are illustrative.

Some factories may close production and finance at different times. The system should accommodate that reality while retaining a clear cut-off and ownership structure.

Form V Monthly Checklist

Before freezing the month, review the following.

Reporting control

• Reporting boundary remains unchanged or an approved change is recorded.
• All applicable datasets have a status.
• Site and financial year are correct.
• New products, processes, sources or waste streams are identified.

Production and materials

• Product-wise production is closed.
• Product names and units follow the reporting dictionary.
• Raw-material consumption is inventory-adjusted.
• Shutdowns, trials and major variations are explained.

Water and effluent

• All water sources are captured.
• Bills and meter readings are available.
• Water use is classified.
• Effluent generation, treatment and reuse are recorded.
• Significant differences have an explanation.

Monitoring

• Monitoring due versus completed is checked.
• Correct locations and parameters are covered.
• Final reports are available.
• Revised reports are version-controlled.
• Abnormal findings are linked to review or action records.

Waste

• Hazardous-waste opening, generation, movement and closing stock reconcile.
• Manifests and weighbridge records are connected.
• Receiver acknowledgements are tracked.
• Non-hazardous waste is classified and closed separately.
• Physical differences are investigated and documented.

Projects and expenditure

• Project status is updated.
• Proposed, approved and completed work is distinguished.
• Capex and Opex are classified.
• Finance evidence is attached.
• Environmental benefits are described conservatively.

Review and approval

• Pending information has an owner and due date.
• Inconsistencies remain visible until resolved.
• Estimated values are clearly identified.
• Department verification is complete.
• Corrections retain their history.
• The month is approved and frozen.
• The Form V preview is refreshed.

Quarterly Review: Look Beyond Missing Cells

A monthly close checks completeness. A quarterly review checks whether the information makes operational sense.

Useful comparisons include:

• Production versus water consumption
• Production versus raw-material consumption
• Production versus waste generation
• Water withdrawal versus effluent generation
• Effluent treatment versus reuse or discharge
• Waste generation versus dispatch and closing stock
• Monitoring due versus completed
• Environmental expenditure versus project progress
• Current quarter versus the same quarter last year
• Current year-to-date versus previous year-to-date

A variance should create a review, not an automatic conclusion that the data is wrong.

Production mix, weather, shutdowns, maintenance, cleaning cycles and project commissioning can all affect environmental performance.

The objective is to identify unexplained variation early enough for the responsible department to review it.

What Continuously Form V Ready Means

A plant is not continuously ready merely because it has created a Form V template.

It is continuously ready when:

• Every required month has a visible status.
• Annual figures can be traced to monthly records.
• Data providers and approvers are identified.
• Units and names remain controlled.
• Evidence is connected to the relevant data.
• Missing documents are visible.
• Related records have been cross-checked.
• Corrections preserve their history.
• Open inconsistencies are known.
• The current Form V preview can be generated from reviewed information.

By the end of March, the plant should already know which datasets are complete and which exceptions remain open.

Annual preparation then becomes a process of review, consolidation and management approval rather than information recovery.

How EHSSaral Supports Monthly Form V Data Collection

EHSSaral is designed to function as the coordination and exception layer between source departments and the annual environmental statement.

It helps plants:

• Assign each dataset to the responsible department
• Create recurring monthly data responsibilities
• Alert concerned stakeholders when information, evidence or approval is pending
• Maintain common reporting names and units
• Connect information with the correct site and financial year
• Identify missing months
• Identify incomplete supporting documents
• Show inconsistencies across connected information
• Preserve review, correction and version history
• Track complete, pending, inconsistent, nil-activity and not-applicable records
• Carry reviewed monthly information into the Form V preview
• Show management what is complete and where action is still required

EHSSaral does not wait until September to create Form V. It helps the plant keep the underlying information ready throughout the year.

This distinction is important.

A one-time Form V generator can help populate the final format. A Form V data-readiness system helps determine whether the numbers entering that format are complete, consistent, approved and traceable.

EHSSaral does not replace the source department’s judgement or the EHS professional’s interpretation. It provides a common structure through which responsibilities, evidence, reviews and exceptions can remain visible.

A Simple Example of Monthly Readiness

Consider the water dataset for June.

Utilities submits:

• Municipal water: 1,200 KL
• Tanker water: 180 KL
• Recycled water used: 450 KL
• Effluent treated: 520 KL

The municipal bill and ETP logbook are attached. Tanker invoices are available, but two trips do not have inward gate records. The recycled-water figure is based on a meter that was replaced during the month.

The monthly status should not simply be “complete” because all four numbers have been entered.

A more useful status would show:

• Municipal water: complete
• Tanker water: inconsistent pending gate-record verification
• Recycled water: pending review of the meter-replacement calculation
• Effluent treated: complete
• Overall water dataset: inconsistent

The exception is then assigned to the appropriate person.

Once the gate entries and meter-replacement calculation are verified, the dataset can be approved and frozen.

This small monthly discipline prevents the same issue from becoming an unexplained annual difference several months later.

Common Mistakes While Building a Monthly System

Collecting only annual totals

An annual number without monthly traceability makes it difficult to identify missing periods, unit changes and abnormal variations.

Making EHS the owner of every dataset

EHS can coordinate and cross-check, but source departments should verify production, inventory, utility and financial information.

Treating uploaded evidence as verified evidence

A document may cover the wrong site, period, parameter or version.

Using one status for every situation

Pending information, inconsistent information, nil activity and not-applicable information require different treatment.

Replacing records without preserving history

Silent changes weaken confidence in the dataset and can create continuity problems in connected records.

Forcing balances to match

A difference should be understood and explained. Unsupported adjustments made only to create a perfect balance can hide the actual operational reason.

Tracking data but not approvals

A complete number without confirmation from the source department may still create uncertainty during final sign-off.

Building a second system beside existing trackers

If the monthly system adds duplicate entry without clarifying the source of truth, departments may continue maintaining several conflicting versions.

The implementation should identify which operational source remains authoritative and how verified information moves into the Form V readiness layer.

Practical Implementation Approach

Factories do not need to redesign every environmental process at once.

A phased approach can work better.

Phase 1: Define the structure

• Confirm the reporting boundary.
• List the required datasets.
• Identify source owners.
• Create the naming and unit dictionary.
• Define readiness statuses.
• Agree on the monthly close calendar.

Phase 2: Start with core quantitative data

Begin with:

• Production
• Raw materials
• Water
• Effluent
• Hazardous waste
• Non-hazardous waste

These datasets create most of the reconciliation work.

Phase 3: Add evidence and approvals

Connect:

• Bills
• Meter logs
• Laboratory reports
• Manifests
• Weighbridge slips
• Acknowledgements
• Finance records
• Department approvals

Phase 4: Introduce exception review

Track:

• Missing months
• Delayed evidence
• Unit mismatches
• Unexplained variances
• Pending acknowledgements
• Unapproved corrections

Phase 5: Review the live Form V position

Once the monthly system is stable, review the accumulated Form V preview quarterly.

This allows EHS and management to identify structural gaps before the financial year closes.

Final Takeaway

Form V data collection is not a single annual request sent by EHS.

It is a coordinated process through which production, stores, utilities, treatment operations, laboratories, waste stakeholders, projects and finance provide information in a consistent and reviewable form.

The strongest monthly system has:

• A defined reporting boundary
• Named data providers, verifiers and approvers
• Common names and units
• Monthly operational closes
• Evidence-completeness checks
• Clear readiness statuses
• Controlled escalation
• Version history
• Controlled corrections
• Quarterly cross-dataset review

When these controls operate throughout the year, Form V preparation becomes more predictable.

By September, the plant should be reviewing an already-developed environmental statement-not searching across departments for the information needed to create one.

Good Form V preparation begins with monthly ownership, not annual paperwork.

Frequently Asked Questions

1. What information is normally required for Form V data preparation?

Form V uses plant details and information related to production, water, raw materials, pollution discharged, hazardous waste, solid waste, pollution-control measures, conservation initiatives and other environmental improvements.

For the complete part-by-part structure, refer to the Form 5 Environmental Statement Guide.

2. Should Form V data be collected monthly?

Most quantitative operational information is best closed monthly because production, raw materials, water, effluent and waste are generated throughout the year.

Monitoring should be tracked according to its applicable frequency, while project and improvement information can be updated when an event occurs and reviewed monthly.

3. Which department is responsible for Form V data?

EHS generally coordinates the final environmental statement, but responsibility for source data is distributed across production, stores, utilities, ETP operations, laboratories, projects, maintenance and finance.

Each dataset should have a provider, verifier and approver.

4. Is EHS responsible for approving production and financial figures?

EHS should check environmental relevance and cross-dataset consistency. The responsible production or finance authority should confirm the source figure.

EHS should not be expected to independently certify information controlled by another department.

5. What is the difference between data completeness and evidence completeness?

Data completeness means the required value is available.

Evidence completeness means the source documents, departmental confirmation and relevant review records are also available. A number can exist while its supporting trail remains incomplete.

6. How should missing monthly data be handled?

Assign the missing item to the source owner, record what is pending and set a review date.

If an estimate is temporarily necessary, document the estimation method, source, reason and approval. Replace it with actual information when available.

7. What is the difference between nil activity and not applicable?

Nil activity means the dataset applies, but no activity occurred during that month.

Not applicable means the dataset does not apply to the facility, process or reporting boundary.

8. Can a frozen monthly record be corrected later?

Yes. A freeze creates an approved version; it does not prohibit correction.

Later corrections should preserve the original value, revised value, reason, evidence, reviewer, approver and effect on connected datasets.

9. Should Form IV and Form V hazardous-waste quantities match?

They should be reconcilable, but the figures may require interpretation because of opening stock, closing stock, generation, dispatch timing, moisture differences and reporting boundaries.

See the detailed guide on Form IV and Form V quantity mismatches.

10. How does Form V software help with departmental data collection?

A well-designed Form V system can assign responsibilities, send reminders, standardise units, connect evidence, identify missing months, preserve correction history and show the current readiness position.

The software should support departmental accountability rather than transferring every responsibility to EHS.

11. Can the same data support ESG or BRSR reporting?

Some reviewed environmental information-such as water, energy, waste and environmental projects-may support sustainability reporting.

However, regulatory and sustainability disclosures can use different boundaries, definitions and calculation methods. The information should be mapped carefully rather than copied without review.

EHSSaral explains this relationship in its separate article on ESG data management for Indian factories.

12. When should a factory begin monthly Form V data collection?

A plant can begin at any point in the financial year.

If earlier months are incomplete, first create a gap register showing what is available, missing, inconsistent or not applicable. The current month should then follow the new closing process while historical gaps are resolved separately.