Parts Catalog Cleanup: Marathon Day or 15-Minute Slices?

Parts Catalog Cleanup: Marathon Day or 15-Minute Slices?

Every shop, hangar office and parts desk has one: the backlog nobody wants to touch. Mismatched part numbers in a spreadsheet, supplier notes in three formats, a shelf of unlabelled bags. This article compares three realistic ways to clear that pile and makes the case that breaking the cleanup into 15-minute steps beats the other two for most people. No theory, just trade-offs.

The setup: what we are comparing

Imagine a small parts operation with a records backlog. There are catalog entries to tidy, duplicate listings to merge, old supplier quotes to file and a stockroom list that no longer matches the shelves. Nothing is on fire, which is exactly why it keeps slipping. Three approaches are on the table.

  • The marathon: block a full day, clear the desk and push through.
  • The someday plan: fix things whenever you notice them, with no schedule.
  • The quarter-hour slice: cut the backlog into pieces that each take fifteen minutes and do a few per day.

We will look at each against the same yardsticks: how easy it is to start, how much gets done, how much rework it causes and how well it survives a busy week.

Option one: the marathon day

The marathon has a certain heroic appeal. You tell the team you are unavailable, make coffee and plan to emerge with a clean system. In practice, a few things tend to happen.

Starting is hard. A full day is difficult to find in a working shop, so the marathon gets postponed. It waits for a quiet Friday that never turns up. Meanwhile the backlog grows.

Quality drops late in the day. Data entry and record comparison are exactly the tasks where attention fades. By mid-afternoon, a person merging duplicate listings starts to merge things that should stay separate. The errors then have to be found and undone, which can cost more time than the saved hours.

Progress is invisible until the end. Because the whole job is one lump, there is no way to say “forty per cent done” with any honesty. If an urgent call interrupts at noon, you may end up with a half-merged mess and no clean stopping point.

Verdict: fine for a small, well-defined job. Poor for a backlog with unknown depth.

Option two: the someday plan

The someday plan sounds flexible. Whenever you spot a wrong entry, you fix it. In a small number of cases this is genuinely the right approach, for example when the mess is minor and constantly changing.

For a real backlog, though, it quietly fails. Without a list of pieces, nobody knows what has been fixed. Different people repair the same entry in different ways. The same ugly corners stay untouched because no one chooses to start there. There is also no moment where anyone can say the cleanup is complete, so it drifts on for months.

Verdict: low effort per day, but low reliability. It rarely finishes.

Option three: quarter-hour slices

Here the backlog is first turned into a list of small, specific jobs. Each one must be completable in fifteen minutes by one person. The crew then takes a few per day, usually at predictable moments such as after the morning order check or before the end-of-day tidy.

What does a good slice look like on a parts desk? Some examples:

  1. Pull the ten oldest catalog entries and mark which ones have a duplicate.
  2. Merge exactly three duplicate pairs, noting the surviving record.
  3. Photograph one shelf of unlabelled bags and list what you can read on the bags.
  4. File this month’s supplier quotes under a single folder name.
  5. Compare the stockroom list against one rack and mark mismatches in red.

Each slice has a verb, a countable output and an ending. The person doing it never has to wonder whether they are finished.

Head-to-head results

Set the three options next to each other against our four yardsticks.

  • Ease of starting: the marathon needs a free day, the someday plan needs a trigger, the slice needs only a quarter hour and a written opener. Slices win clearly.
  • Amount finished: the marathon can finish a lot in one burst but only if it gets scheduled. Slices finish a steady amount, and since they actually happen, they tend to finish more in total.
  • Rework risk: the marathon is worst, because fatigue breeds mistakes. Slices are best, since each piece is checked while attention is still fresh.
  • Surviving a busy week: the marathon collapses, the someday plan vanishes, and slices bend. Miss a day and you simply do two slices tomorrow, or none.

The slice approach is not magical. It costs a small amount of upfront planning, and the list has to be maintained. But that cost is modest next to a postponed marathon.

A short worked example

Suppose the backlog holds roughly two hundred catalog entries needing attention. Nobody needs the exact count to plan. Group the entries by supplier, then cut each group into batches of ten. Every batch is one slice: open ten entries, confirm the part number format, fix what is wrong, tick the batch. Two slices a day clear a supplier group in a couple of weeks, and the person doing it can see the group shrinking on the sheet.

Compare that with the marathon, where the same two hundred entries would sit in one window and the person would have no sensible place to stop for lunch. The batches give the day natural seams.

Where slicing can go wrong

Be honest about the weak spots. First, slices that are too large. If a job regularly overruns, it is two jobs. Split it. Second, no owner. Someone must hold the list and tick the slices off, otherwise it decays like a someday plan with extra steps. Third, pieces that depend on each other. If merging duplicates must happen before relabelling, put them in that order on the list.

Another risk is skipping the awkward slices. Teams naturally pick the easy ones first. A good rule is one awkward slice for every two easy ones, so the hard corners get chipped away rather than left as a final cliff.

Borrowing from related reading

If you need to decide what belongs on the list in the first place, existing buyer checklists make a good source of line items. Two earlier articles here make useful sources: one covers how purchasers go wrong with flight-control hardware, the other covers slip-ups to dodge when purchasing avionics. Either can be mined for slices, such as “check that every listing carries a part number” or “compare two supplier descriptions line by line.” Use them as prompts for your own records, not as instructions.

A passing note on tidy online errands

Even outside aviation, small administrative sequences are everywhere. Take an example from a different corner of the web: a site called MotoShareGulf, described as a marketplace where bikes and scooters are put up for hire and where users log in through a central account service. Creating a profile on a site like that is a short run of tiny steps. Treat your catalog the same way and the scale stops feeling frightening.

A practical way to run it

  1. Audit once, briefly. Spend one fifteen-minute sitting just listing the problem areas. Do not fix anything yet.
  2. Cut the list into slices. Aim for thirty or forty small jobs with a verb and a countable output.
  3. Assign one owner for the list, and pin the sheet up in plain view.
  4. Schedule two slices daily, pinned to a fixed event such as the morning order check.
  5. Review weekly. Count ticks, split any slice that overran and reorder the rest.

The bottom line

If you can reliably block a clear day and the job is small and well understood, a marathon might do. If the mess is tiny and constantly shifting, a someday approach can limp along. For nearly everything in between, the quarter-hour slice wins on ease of starting, rework and resilience. It turns a vague obligation into a list you can finish, one tick at a time.