What to measure in a reuse pilot

A reuse pilot should answer an operating question. Can the team keep enough items available? Do customers understand where to return them? How much handling work does the arrangement require? Start by naming the decision the trial will inform. A dashboard full of numbers is less useful than a short record that helps the team choose a change.

For a first trial, measure the items and work within a clear boundary. That might be one office kitchen, one shop counter or one event service. Define the item category, participating location and observation period. If the boundary changes halfway through, note the change. Otherwise a busier second week may look like improvement when it simply includes another collection point.

Count opening stock by condition

Record what is available before the pilot begins. Separate ready-to-use items, items awaiting handling, damaged items and any stock held elsewhere. Use categories the team can recognize consistently. A container that is physically present but unavailable for use should not be counted as ready stock just because it is on the premises.

Assign a person to the opening count and a place to record it. If two people count different parts of the system, agree how they avoid counting the same item twice. A simple dated sheet can work for a small pilot. The priority is a repeatable method, not a complicated tool that takes longer to maintain than the service itself.

Keep additions and removals visible during the trial. Replacement stock, newly purchased items and transfers from another location change the inventory. Record them as movements rather than quietly adjusting the total. A final count only makes sense when the team can explain how the opening stock changed.

Distinguish uses from returns

Define an issue or use event for the specific service. In a counter system, it may be an item handed to a customer. In a shared office kitchen, observing every use may be impractical. Choose a measure the team can collect reliably and label it accurately. A replenishment count should not be presented as a precise count of individual users.

Record returns with their own date and location. A return during the second week may relate to an item issued in the first. If you divide all current-week returns by current-week issues, the result can be misleading. Where individual tracking is not appropriate, explain that the counts describe flows during a period rather than a matched return rate for a specific group of items.

An illustrative example makes the problem clear. Suppose a service issues 80 items in a week and receives 70 returns, including 20 from the previous week. The ratio of 70 to 80 does not tell you how many of this week's items came back. Keep the unmatched flow counts separate unless the system has a reliable way to connect an issue with a return.

Give missing items time to be understood

At reconciliation, identify the difference between recorded stock and counted stock. Call it an unresolved difference until you have checked the likely causes. Items may be in use, awaiting collection, stored in the wrong place or omitted from a count. Treating every difference as a loss can hide a process problem that is easier to correct.

Define when an item will be considered lost for this pilot and use that definition consistently. A workplace system may need a different window from an event system. Record confirmed damage separately, including the reason when known. A damaged item returned promptly is operationally different from an item that cannot be located.

Use a short exception note rather than forcing every event into a numeric category. A locked collection room, a moved return bin or a cancelled visit can explain a surprising count. The note should identify the date and effect, with a follow-up owner if action is required. These details often reveal the next improvement more directly than an average.

Measure the work behind the service

Track handling time for a few clearly defined tasks: collection, sorting, preparation, replenishment and administration. Decide whether travel is included or shown separately. Use the same boundary each time. If a staff member pauses to do unrelated work, avoid counting the whole elapsed period as active handling time unless that is deliberately the measure you need.

Keep setup work distinct from recurring work. Designing the first sign or arranging the first storage area may not recur at every visit. Replacing a damaged label or answering repeated return questions might. Both matter, but combining them can make it difficult to estimate how the routine behaves after the initial launch.

The EPA's commercial-building waste guide recommends establishing a benchmark and using tracking to inform goals. Applied to a small pilot, that means agreeing what the starting situation looks like before interpreting change. Record relevant context such as operating days or office attendance where it is available in a suitable aggregate form.

Capture friction with a question someone can answer

Add one place to record what made participation difficult. Staff can note recurring questions at the point of use, or participants can answer a short prompt about their most recent experience. Avoid asking only whether they liked the program. A specific account of not finding the return location gives the team something to fix.

Do not collect personal data simply because a spreadsheet has room for it. Many operating questions can be answered with item counts and anonymous observations. If the service needs individual tracking, decide its purpose, access and retention before starting. Keep the pilot proportionate to the decision rather than creating a permanent customer history by default.

Review the return location in person. A sign can be technically present and still be difficult to see from the route people take. Observe a normal busy period and note what happens without coaching everyone. If the collection point is repeatedly bypassed, test a placement or wording change and mark the date so the next week's figures have context.

Keep environmental conclusions within the evidence

A completed reuse cycle is an operating result. Estimating environmental effects requires more information about the system, including products, transport and handling. Do not turn a count of returned items into a carbon-saving figure without an appropriate method and evidence. A pilot can be useful while reporting only what it directly measured.

The EPA's ecolabel overview shows why the scope of an environmental statement matters. Keep any product-specific documentation separate from the pilot's own counts. A supplier's label does not automatically substantiate a claim about the whole service route or the customer's workplace.

Build the first measurement sheet with opening stock, additions, issues, returns, condition counts, handling time and exception notes. Add a clear review question at the top. At the end of the pilot, explain what changed, which figures remain uncertain and what the next trial should test. That gives the team a decision they can act on without asking the numbers to prove more than they observed.