NWSS-M006 — Collector engagement
Provisional. Usable pending approval; a project-proposed concept only by the project that proposed it.
- Code: NWSS-M006
- Version: NWSS-2026-11-09
- Approval status: Provisional
Counting the collectors a project engages and the days they work, from the service visits and facility weighing records that name them: active collectors and collector-days worked, by collector kind, facility and service area. Earnings, rates and income sharing are bounty terms and outside this methodology (ADR-0009).
underlying principles and assumptions
A collector is an agent in the collector role, in the graph only as an IRI with its role and kind (ADR-0004). Work counts only where a record names the collector. A tag that resolves to no agent is not a collector. Days are counted, not hours or contracts, which the graph does not hold.
methods and procedures
Enrol each collector once, recording the collector kind and assigning a collector tag in the people register. On each service visit and facility weighing, scan the collector’s tag so that the record names the collector. Count as the rules state.
data requirements and inputs
Collector enrolment records with the agent role and collector kind; service visits (NWSS-M003) and facility weighing records with collector and observedAt; the collector tag assignment windows, resolved in the people register to agent IRIs. From the project design: the time zone.
calculation and transformation rules
The collector of a record is the agent its collector tag resolves to at its observedAt under the scan resolution rule of ADR-0003, gaps included; the kind is the collector kind of that agent’s collector role in force on that date. (1) Active collectors = number of distinct agents named as collector on at least one service visit or facility weighing record dated in the reporting period, by collector kind, facility and service area; an agent active at two facilities counts once in their total. Records whose collector tag resolves to no agent are counted alongside as unresolved. (2) Collector-days worked = number of distinct pairs of agent and local date with at least one such record, by collector kind, facility and service area.
outputs and units of measure
Active collectors (count, NUM) and collector-days worked (count, NUM), by collector kind, facility and service area, with unresolved records alongside.
validation and verification approach
Validation: a reviewer with Knowledge and Skills Reputation in informal-sector inclusion and labour checks that collectors are enrolled with a kind and that collector tags are assigned in the people register, not the graph. Verification: a reviewer in data and evidence quality samples collector-days and checks each against the records that name the collector and their evidence.
limitations and applicability boundaries
Counts evidenced days, not hours, contracts or full-time equivalents, and says nothing about income or working conditions. A collector who works without scanning their tag is not counted. Gender, age and other personal attributes stay in the people register; disaggregation by them needs an aggregate from that register, outside the graph.
rationale
Collector labels on the dashboard counted unresolved tags as people and the only active-collector figure was a monthly label count. Counting agent IRIs on records gives a jobs figure that carries no personal data and leaves remuneration to bounties.
Indicators it serves
Activity types
- Collection round
- Collector enrolment
- Facility weighing
Knowledge domains a reviewer needs
- Data and evidence quality
- Informal-sector inclusion and labour
Variables
| Variable | Role | Unit | Description |
|---|---|---|---|
| Active collectors | DerivedOutput | NUM | Distinct agents named as collector on a service visit or weighing record dated in the period. |
| Collector-days worked | DerivedOutput | NUM | Distinct pairs of collector agent and local date with such a record. |
| Visit outcome | DerivedOutput | UNITLESS | The outcome of a service point-date: the first present of collected, collected without a tag scan, no waste presented, no access to the container, no access to the service point. |
| Collector (k) | MeasuredInput | UNITLESS | The agent in the collector role named on a record, resolved from the collector tag at observedAt under the scan resolution rule of ADR-0003. |
| Collector kind | MeasuredInput | UNITLESS | The kind of agent holding the collector role. |
| Facility (f) | MeasuredInput | UNITLESS | The facility a record was made at. |
| Observed at (t) | MeasuredInput | UNITLESS | The instant the observation or record was made; its local date in the project’s time zone is the record’s date. |
| Restated record | MeasuredInput | UNITLESS | The earlier record a record replaces; of a record and its restatements only the latest counts (ADR-0006). |
| Tag assigned to | MeasuredInput | UNITLESS | The entity a tag bore under an assignment; a scan resolves to it while the assignment is valid, and in a gap after it unless the code was next assigned to a different entity (ADR-0003). |
| Tag assignment valid from | MeasuredInput | UNITLESS | Start of a tag assignment’s validity window. |
| Tag assignment valid until | MeasuredInput | UNITLESS | End of a tag assignment’s validity window; open while the assignment is not superseded. |
| Withdrawn record | MeasuredInput | UNITLESS | The record a withdrawal declares never happened; a withdrawn record never counts (ADR-0006). |