Municipal waste management software: requirements your council must meet before adopting it

Summary: Choosing a digital platform to manage your council’s recycling centre is not just a technological decision: it is an operational and regulatory decision with direct consequences for your team’s daily work and compliance with GaIA reporting. This article sets out the minimum requirements—functional, regulatory and implementation—that any tool must satisfy before it makes sense to evaluate it seriously.

Table of contents

• Why requirements matter before the demo
• Basic operational requirements
• Regulatory and reporting requirements
• Custom configuration requirements
• Implementation and go-live requirements
• Training and ongoing support requirements
• Technical and access requirements
• How to organise the internal evaluation in your council

Why requirements matter before the demo

Most council teams arrive at a software demo with a vague question: “Can this work for us?”. The problem is that without a clear requirements list, the demo always seems to say yes.

What works is the opposite: establish first what your council needs irrevocably and then check whether the tool meets it. This way you quickly rule out what does not fit and invest time evaluating what has real options.

The requirements that follow are organised by functional block. Not all councils will need all of them, but it is useful to review each one and decide which are mandatory, which desirable and which dispensable for your actual operations.

Basic operational requirements

These are the requirements that affect the daily work of the operator and the technician responsible for the recycling centre.

• Waste registration by category: the platform must allow registering each waste entry with category, weight or volume, and date. Without this, there is no traceability.
• Registration of users or visitors: if your council keeps track of citizen access, the software must include that module or integrate with the one you already use.
• Role-differentiated access: the operator does not need to see what the technician sees, and the technician should not be able to modify what is only for the council official responsible. Roles and permissions must be configurable.
• Operation without stable connectivity: many recycling centres in Galicia have limited connectivity. The tool must work with intermittent connectivity and synchronise when it regains signal.
• User-friendly interface requiring no prior technical training: if the operator needs more than one training session to register an entry, the interface is not well designed.

To understand how an operator’s daily work is articulated and what errors usually appear in manual registration, you can consult this article on the operator’s role at the recycling centre: functions, registration and most frequent errors.

Regulatory and reporting requirements

This block is the one that generates the most variation between councils and the one with the most consequences if not covered well.

• Generation of the GaIA report: the platform must produce the report in the format required by the Xunta de Galicia, without the council team having to reinterpret the data or recode categories. If it does not automate this, it is not a valid tool for Galicia.
• Waste categories adapted to regional regulations: the software categories must match those required by the GaIA system, not generic categories that then have to be translated manually.
• Export in compatible formats: in addition to the GaIA report, the software must allow data to be exported in standard formats (CSV, Excel, PDF) for other internal administrative uses.
• Complete traceability by fraction: every tonne registered must be traceable from entry through to the authorised waste manager. Without that chain, the council is exposed in the event of an inspection.
• Regulatory updates included: reporting regulations change. The provider must assume system updates when the Xunta’s requirements change, without extra cost or indefinite waiting time.

Errors in council waste reports can result in administrative penalties. You can see the most frequent ones in this article on common mistakes in council waste reports that trigger penalties.

Custom configuration requirements

No two councils operate identically. Software that forces you to adapt your processes to the system—rather than the other way around—generates immediate rejection and incomplete adoption.

• Configurable categories: the waste streams your recycling centre manages must be definable according to your operations, not according to a fixed, unchangeable predefined list.
• Adaptable workflows: the registration, validation and closure sequence must reflect how your team works, not a standard workflow from another council.
• Dashboards and reports configured for each profile: the technician sees what they need; the political leader, what corresponds to them; the operator, only what they use daily.
• Compatibility with mobile recycling centres: if your council operates a mobile recycling centre, the system must accommodate it without forcing manual workarounds.

Implementation and go-live requirements

Implementation is the moment when the software stops being a promise and becomes—or does not become—a useful tool.

• Maximum operational implementation timeframe of 4 weeks: longer periods imply hidden costs for your team (dedicated hours, parallel processes, transition errors).
• Migration of historical data: if you have previous records in Excel or digitised paper, the provider must handle the migration without your team doing it manually.
• Documented implementation plan with clear milestones: without a schedule with deliverables, implementation drags on uncontrolled.
• Test environment before actual start-up: your team must be able to test the system with real data before using it in production.
• Assigned technical contact throughout the entire process: not a generic support team, but a person who knows your council and your configuration.

Training and ongoing support requirements

Training is not an extra: it is part of the product. A council team that does not know how to use the system properly will revert to manual registration within two weeks.

• Initial training included in the price: and tailored to the actual profiles of your team, not a generic session.
• Operational documentation in Spanish or Galician: user manuals in English or with technical jargon do not work for council teams with low tolerance for ambiguity.
• Support channel with guaranteed response time: an email without an SLA (service level agreement) is not support: it is an informal promise.
• Continuous support included, not as an add-on: updates, operational queries and regulatory changes must be covered without negotiating additional budget each time.

Technical and access requirements

• Web browser access without local installation: councils cannot depend on installations on specific computers that later become outdated.
• Access from mobile device: the operator at the recycling centre needs to register from a tablet or phone, not from a desktop computer.
• Hosting on servers complying with GDPR: citizen and waste data are personal or administrative data. The provider must prove where it is hosted and under what conditions.
• Automatic backups: with daily frequency as a minimum and with the possibility of data recovery in the event of incidents.
• Access control by individual user and password: without shared access that prevents auditing who registered what and when.

How to organise the internal evaluation in your council

With the above list, the evaluation process becomes more straightforward:

1. Classify each requirement as mandatory, desirable or dispensable for your specific operations.
2. Prepare a questionnaire with the mandatory requirements and send it to the providers before the demo.
3. Ask for the demo to replicate your actual operations, with your waste categories and your workflows, not a generic example.
4. Request references from Galician councils of similar size to yours that already use the system.
5. Review the contract before the decision: check that implementation, training and support are included and with specific conditions, not open-ended.

Software that cannot clearly answer the requirements in this article before contract signature will not meet them afterwards.

If your council is in the evaluation phase and you want to see how a platform designed specifically for Galician recycling centres works—with integrated GaIA regulations, custom configuration and implementation in 2 to 4 weeks—you can find out about TuPuntoLimpio at tupuntolimpio.es.