Requirement discussion

About requirement discussion

Clarify the facility, activity and environmental application stage.

Environmental consent requirements concern a facility, its location and the activities carried out. Consent to establish and consent to operate are distinct application stages where applicable. A consultancy discussion should identify the relevant pollution-control authority, the site and the current project stage before treating the requirement as a generic pollution certificate.

For requirement discussion, agree the product, activity, application or record involved and the working output. Focus the preparation on the information needed at this stage, with clear evidence references and an understandable handover for the person continuing the work.

When this support is useful

Businesses planning or operating a facility, or reviewing a change to an existing consent record, can explore this support. The route depends on location, activity and the current authority requirements; this guide does not assign an industry category or give site-specific legal clearance.

This subservice can be discussed when the business has reached the relevant stage, received a request for information or identified a gap it cannot resolve from its existing records. Start with the actual request and explain what work has already been completed. That avoids both duplicating earlier preparation and overlooking an unresolved dependency.

Pollution-control consent, factory licensing, waste authorisation and product certification have different purposes. The relevant authority determines which permissions apply and their conditions; one approval should not be assumed to replace another.

The starting information for this work

The task-specific inputs are: Location, process description, existing consents and project changes.

Identify the current version of each input and the person who can confirm it. Keep the original requirement alongside any summary. Where an input has not yet been verified, mark that point clearly so the preparation does not convert an assumption into an application statement.

• Applicant, site and location information
• Process-flow and capacity descriptions
• Available water, effluent, emission and waste information
• Pollution-control and relevant monitoring records
• Existing consent or authorisation documents
• Authority notices, questions and proposed-change details

How the work is organised

1. Identify the relevant authority.

   Begin with the relevant source record and the scope agreed with the applicant. Record the fact being checked and identify what would establish it, rather than relying only on a title or a previous file name.

2. Distinguish establishment and operation questions.

   Compare the related information as a connected set. A change to one attachment can affect a product description, application field or evidence reference elsewhere, so keep those relationships visible.

3. Record the factual boundary.

   Retain the reviewed result and any question that remains open. Identify the next owner and the evidence needed before the applicant treats the work as ready for the next stage.

The steps should be agreed with the business and adapted to the actual record or product. Where a question requires a technical, regulatory or other professional conclusion, the preparation should identify the appropriate reviewer. Administrative organisation and professional assessment remain different responsibilities.

Evidence and consistency checks

Use this wider service context to check whether the task-specific records remain coherent. For example, names, models, locations and reporting periods should be understandable across related files. If they differ for a valid reason, explain the relationship with the applicant and keep the source evidence accessible.

The working output and its handover

A site-specific application-scope brief.

A useful handover identifies what was reviewed, the version or date, the evidence references and the outstanding questions. It should also identify the next responsible person. That allows another team member or an external reviewer to continue the work without reconstructing the preparation history from scattered messages.

An organised output is not a substitute for the relevant external decision. Where the next step is a submission, test, assessment or professional review, agree who authorises it and which reviewed information will be used. Keep the acknowledgement or response with the same record.

Why careful preparation matters

• A more accurate description of the site and application stage.
• Consistent process and environmental information.
• Better visibility of existing conditions and proposed changes.
• An organised basis for authority correspondence.

For this subservice, judge the preparation by how clearly it resolves the task and supports the next decision. An output that still contains unexplained identity or scope differences can create avoidable questions later, even if the folder appears complete. The practical aim is a record that the business can understand and stand behind.

An illustrative working example

A unit proposes increasing output and adds a new process. Before reusing old application files, the team records the planned change, compares it with the existing consent and gathers updated process and control information. It then asks the relevant authority-route questions rather than assuming the old record covers the expansion.

At the requirement discussion stage, the team would focus on this question: Does the requested route fit the facility’s present stage? The evidence for the answer should be recorded in the working output, with any unresolved point assigned to a person rather than silently treated as settled.

Common issues and the final review

• Treating establishment consent as permission to operate in every case.
• Reusing process or capacity figures that no longer describe the site.
• Ignoring conditions attached to an existing consent or authorisation.

The task-specific review question is: Does the requested route fit the facility’s present stage?

Separate a missing document from an unsupported claim and from a technical question. These need different actions. Obtaining a file may resolve the first; correcting the statement or obtaining competent review may be necessary for the others. Keep those actions visible until the responsible person has reviewed the result.

After this stage is completed

Keep the issued conditions, monitoring information and proposed operational changes under review. Confirm the applicable continuation, renewal or modification route for the particular record.

Retain the task output with the source information, reviewed version and relevant correspondence. If the underlying business facts change before the next submission or assessment, check the effect on the prepared material rather than assuming the earlier result still applies.

Discuss your requirement with TenderCert

Start with the outcome you need and the evidence you already hold. Bring the exact buyer clause, authority request or assessment enquiry where available, together with a short description of the product, activity or site. This makes the conversation more useful than asking for an unspecified certificate.

TenderCert’s consultancy scope can then identify the preparation and coordination tasks to discuss, the person responsible for each input and the questions for the relevant decision-maker. The applicant should review information and declarations before any external submission. Keep the final reviewed version and the acknowledgement together so later follow-up begins from the same record.

Common questions