State and Local Business Intelligence
ISSUE 01 · THE PLACE ECONOMYDecisions closer to outcomes
RU

Briefings / Local Business

Fitting More Laundry Services into the Working Day

Shared laundry equipment needs a schedule that includes drying, folding and collection. A worked example shows how the next stage shapes a realistic completion time.

Washing machines, dryers and a folding counter

A washing machine can serve a customer doing their own laundry in the morning and a staff-handled order later in the day. That flexibility makes it tempting to describe every quiet hour as unused business capacity. Yet a finished laundry order requires more than an available washer. Drying, folding, checking, storage and collection all need their own place in the working day.

In the United States, a Forbes article by Jodie Cook, published in June and updated in July 2026, describes Dave Menz combining self-service, wash-and-fold and collection-and-delivery work with shared equipment. The useful operational question is how such services fit together. The following discussion examines scheduling choices rather than projecting the earnings of a machine or recommending a business purchase.

Describe the service before allocating the machine

Self-service customers usually make several decisions for themselves, within the site's rules: when to arrive, which available machine to use and when to move their washing onward. A staff-handled order brings different responsibilities. Employees must identify the order, establish the agreed service, carry it through the required stages and tell the customer when the completed work is ready.

Those differences should appear in the operating plan. A row of machines shared by both services does not make the services interchangeable. A customer waiting in the shop experiences an occupied machine immediately. Someone who has left a bag may not see the queue, but still relies on the promised collection arrangement. Neither demand disappears because the other is easier to observe.

Start with the offer actually being made. Specify which orders the site accepts, how their completion is agreed and which activities employees perform. Keep specialist treatment outside a general scheduling assumption unless the business has separately established that it can provide it. This is a description of workflow, not a substitute for garment-care instructions or equipment operating requirements.

Keep available time separate from usable capacity

A machine can be unoccupied without being available for the next order. It may be awaiting an established check, reserved for another service or unsuitable for the particular work. Equally, a staff member may be present without being free to process a batch: receiving customers, answering questions and handing back finished orders also take time.

Use the site's actual operating information to identify periods that can support additional work. An opening-hours total is a broad boundary, not a production estimate. Within it, record relevant restrictions, observed task durations and the points where one activity depends on another. A useful plan shows why a proposed slot is usable rather than treating every empty square on a timetable as equivalent.

Plan by compatible equipment groups

Do not turn unlike machines into a single count without explanation. Different capacities and permitted uses may make one available unit unsuitable for a waiting order. Establish the applicable grouping from the site's confirmed equipment and service arrangements. The scheduling record then needs to identify the relevant group, not merely say that a machine somewhere in the premises is free.

Likewise, a bag is not a fixed unit of work. Two customer bags can contain different amounts and require different agreed handling. Use the measures appropriate to the service, and retain the connection to the individual order. Counting bags can help organise collection, but on its own it cannot establish how many washing or drying slots will be needed.

Follow the work beyond washing

Map the sequence from acceptance to collection. The point is not to produce an elaborate diagram for every small shop. It is to make the dependencies visible. A batch that finishes washing still needs its next suitable stage. Work that has finished drying may wait for an employee or a clear folding surface. A packed order may occupy collection space until its owner arrives.

Observe where work waits and record the reason. Waiting for equipment, waiting for a service decision and waiting for collection are different conditions. Combining them as unfinished laundry makes it harder to choose a useful change. Additional washer time will not automatically resolve a queue of already-dried orders awaiting packing.

For each stage, identify the information required to proceed. Staff may need a confirmed service choice, an order reference or a resolution to a question raised at acceptance. The timetable should not assume that an unanswered question will resolve itself while equipment runs. Give such orders an explicit next action and a person responsible for following it up.

Washing, drying and folded laundry
Stages of a laundry order

Test a small schedule before promising a larger intake

Consider an invented example designed only to demonstrate sequencing. It is not a manufacturer cycle specification or a recommendation for treating any fabric. Suppose a site has two compatible washing positions and one compatible drying position available for staff work from 09:00. In this simplified exercise, each batch occupies a washing position for 40 minutes and the drying position for 50 minutes, with transfers included in the assumed slots.

Two batches, A and B, begin washing at 09:00 and finish that stage at 09:40. Only A can start the next stage immediately. It occupies the drying position until 10:30. B then uses that position until 11:20. Both washing positions were released at 09:40, but the second batch did not complete drying until much later.

If the team starts two further batches at 09:40, they finish washing at 10:20. At that moment, the drying position is still occupied by A and B is already waiting. Without a revised plan, the additional washing has enlarged the queue for the next stage. The example does not prove that washing should stop; it shows what must be considered before calling the earlier availability extra completed-order capacity.

Add the staffed finishing stage

Now assume that checking, folding and packing each batch occupies one employee for a further 20 minutes in this exercise. A could finish that stage at 10:50 if the employee and workspace are available at 10:30. B could finish at 11:40 under the same assumption. A promise to collect both batches at 11:00 would therefore conflict with the proposed sequence.

These times deliberately omit many real-world variations. They are a way of checking arithmetic and dependencies, not a service standard. A real schedule needs the site's observed durations, applicable operating requirements, staffing arrangements and allowance for the particular work. Its value comes from showing which assumption determines the promised finish, so that an employee can revise the plan when that assumption changes.

Protect the self-service offer while processing orders

Staff-handled work can be moved around more easily than a customer already waiting beside the machines, but flexibility should not become an excuse for continual improvisation. Decide how much equipment availability the self-service offer needs at different periods. Base the discussion on observations from the premises, including waiting and machine availability, rather than assuming that a quiet visit represents the whole week.

A reservation for staff work should have an understood purpose and boundary. Employees need to know when it starts, which equipment it covers and what to do when the expected work is absent or delayed. Customers need clear information about the equipment available to them. Avoid a situation in which an apparently free machine is repeatedly withdrawn without an explanation anyone can give consistently.

Review the arrangement across different days. The period that supports staff orders on one weekday may coincide with heavier self-service use on another. Keep dates with observations and note unusual conditions. A single busy afternoon is useful evidence about that afternoon, but it is not enough to describe the normal pattern of the entire location.

Keep the order identifiable through each handover

Shared equipment makes a reliable order reference important. Staff should be able to connect accepted work, its current stage and the finished package without relying on who remembers a particular bag. Establish an identification method suitable for the site's process and use it consistently. The objective is a clear handover, not an unnecessarily detailed collection of personal information.

When an order is divided into more than one working batch, retain the relationship between the parts. Completing one batch does not complete the whole order. A collection notification should follow the agreed completion check, including whether all expected parts have reached the finished package. Otherwise, progress in the working area can be mistaken for readiness at the counter.

At a shift change, communicate outstanding questions as well as stage labels. The incoming employee needs to know what action remains and whom to contact, not just that an order is waiting. A short handover can separate work ready for the next available slot from work that must remain on hold until a customer or responsible colleague provides an answer.

Make completion messages match physical readiness

The customer-facing promise should describe when the order can actually be collected or delivered under the agreed service. A machine finishing its stage is an internal event. It becomes useful to the customer only after the remaining work and the required checks are complete. Keep that distinction in both staff instructions and any automated status messages.

If a completion time needs to change, communicate the revised position through the agreed channel. Explain the next useful step without claiming a certainty the schedule cannot support. A customer deciding whether to travel to the shop needs an actionable answer. An optimistic message followed by an unavailable order creates another counter interaction as well as a disappointed visitor.

Delivery work adds a further timetable. A packed order might be ready in the premises but miss the planned collection by the delivery team. Establish the relevant handover point and cut-off from the actual service arrangement. The laundry completion record and the delivery record should remain distinguishable, so that a later question reaches the person responsible for the current stage.

Include finished orders in the space plan

Finished work does not leave the building automatically. Shelving and collection areas have practical limits, and orders can remain there for different periods. Review the space required for work awaiting collection alongside the space needed for processing. A plan that fills every surface with incoming bags may make it difficult for staff to find and hand over the orders already completed.

Keep collection status current. The employee accepting a new order should not have to search through outdated entries to establish which packages are still present. Where collection is delayed, use the business's agreed customer-contact process rather than assuming that a scheduled date proves the package has left. Physical collection and a previously expected collection date are different facts.

Space observations can also explain apparent processing delays. A finishing area may be occupied by completed packages rather than active folding. The appropriate response might involve collection organisation or a clearer separation of areas. It need not involve changing machine capacity, and the record should make that distinction visible before the team chooses a response.

Connect new intake to the work still outstanding

Before confirming another completion time, the receiving employee needs a brief current picture rather than the history of every machine cycle. Which orders have already been promised for the next collection period, which stages remain, and what resources are still available? Those answers put the new request alongside commitments the laundry has already accepted, including work that has not yet reached a machine.

Distinguish a preliminary enquiry from an accepted order. A visitor may ask about a service without handing over the items or agreeing the arrangements. That conversation helps reveal possible demand, but should not silently occupy a confirmed slot. If the site offers advance bookings, identify the action that makes the booking a commitment and who updates the information when plans change.

Conversely, a bag already accepted cannot disappear from the calculation simply because processing has not started. It needs a place in the sequence. The employee accepting the next order should see that workload alongside batches currently running. Otherwise, an empty machine can suggest that there is no queue even though several customers already expect service within the same period.

Recheck affected promises when the plan changes

If equipment becomes unavailable, first identify the operations that depended on it. Do not automatically move the entire list to the remaining machines: they may belong to another group or already be allocated to self-service customers. A responsible employee must confirm an appropriate revised arrangement within established requirements. A scheduling review is not an instruction to bypass equipment restrictions.

Check the following stages after making the change. Moving the washing start can move drying, packing and the courier handover. Not every order will necessarily be late: some may have spare time or a different processing route. A list of affected commitments supports specific customer updates instead of a general warning that fails to explain the position of their own belongings.

Keep the time of the latest update with the working plan. If reception uses the morning record while the processing area follows a revised sequence, both teams can give different answers in good faith. Establish one clear way to communicate changes to those who promise completion times. A simple shared log may suffice; its usefulness depends on being current rather than technically elaborate.

For an urgent request, discuss the consequences for other work as well as the possibility of starting earlier. Bringing one batch forward uses equipment and employee time that may have been assigned elsewhere. If the offer cannot be fulfilled without changing previous promises, that should be visible before confirmation, not discovered when customers arrive for evening collection.

At the end of a shift, review orders remaining for the next team separately. Record their actual stage, outstanding actions and the customer's agreed completion time. A general instruction to finish tomorrow is not equivalent. The morning employee needs to understand which order requires an early decision and which dependencies must be checked before new work starts.

It can help to review one actual completed order with reception and the processing team. Compare the promised time, the real transitions and the moment the customer was notified. The purpose is to find where information stopped matching the work, not to judge an employee from one case. The review may reveal a need for clearer stage confirmation rather than more machines or earlier intake.

Put the agreed change into the normal routine. If the team decides to check the drying queue before promising evening collection, every receiving employee should understand the new check. Otherwise, a useful decision remains one person's knowledge and disappears when shifts change, while the same equipment-allocation question continues to arise each day.

Review the whole order, not just machine activity

Choose a small set of observations that supports actual operating decisions. Machine use is one part of the picture. Orders completed as agreed, time waiting between stages, unresolved questions and work carried into the next shift help explain how that activity becomes a usable service. Use consistent definitions and keep the observation period attached to the results.

  • Which equipment group is limiting the next stage?
  • Is work waiting for a machine, a person, information or collection?
  • Can the team identify every part of a divided order?
  • Do readiness messages follow physical completion?
  • Does staff work leave the intended self-service availability?

Discuss one proposed change at a time where practical. A revised intake period, a different staff handover and a new allocation of machines affect different parts of the process. Record what changed and when, then review the relevant observations. That makes the next conversation more useful than a general instruction to work faster or keep every machine occupied.

Sharing equipment can broaden what a local laundry offers, but the operating unit remains the completed customer order. Washing time, drying time, staffed finishing and collection need to fit together. A schedule that keeps those relationships visible gives the team a sounder basis for accepting work and communicating its progress than a machine count or an opening-hours total alone.

Leave a comment