{"id":993,"date":"2026-11-08T18:40:00","date_gmt":"2026-11-08T18:40:00","guid":{"rendered":"https:\/\/planespart.com\/blog\/?p=993"},"modified":"2026-11-08T18:40:00","modified_gmt":"2026-11-08T18:40:00","slug":"veteran-buyer-vs-parts-desk-runbook","status":"publish","type":"post","link":"https:\/\/planespart.com\/blog\/veteran-buyer-vs-parts-desk-runbook\/","title":{"rendered":"Veteran Buyer or Written Routine: Comparing Parts Desk Methods"},"content":{"rendered":"<p>Every aircraft parts desk eventually faces the same quiet question: do we rely on the experienced buyer who has seen everything, or do we write down how the desk works? The honest answer is that both have strengths, and the choice matters most on the day the experienced buyer is not there. Below, each approach is weighed against the criteria a parts business cares about: speed, consistency, traceability of paperwork, cost, and resilience when people change. It then sets out how to build a parts desk runbook that keeps the best of the veteran&#8217;s judgement.<\/p>\n<h2>The two approaches defined<\/h2>\n<p><strong>The veteran method<\/strong> is what most small suppliers and workshops actually run on. One person, usually with years behind them, knows which suppliers answer quickly, which part families cause confusion, what the paperwork should look like when a consignment arrives, and which customers need a call rather than an email. Their knowledge is deep, flexible and almost entirely unwritten.<\/p>\n<p><strong>The runbook method<\/strong> converts the repeatable parts of that knowledge into short, numbered procedures for each recurring task: quoting a part request, receiving a delivery, checking the accompanying documents, handling a return, closing out an order. It does not remove people. It gives each person a shared, tested way to do the routine parts, and it flags clearly where a human decision is required.<\/p>\n<h2>Comparison on the points that matter<\/h2>\n<h3>Speed on a normal day<\/h3>\n<p>On an ordinary day the veteran is usually faster. They skip steps they know are unnecessary and act on instinct. A runbook costs a little time because the steps are followed deliberately. For routine jobs, though, the gap is small, and the runbook speeds up as it becomes familiar. The veteran&#8217;s advantage is real but narrow, and it tends to disappear when volume rises and the desk has more than one person on it.<\/p>\n<h3>Consistency between people<\/h3>\n<p>Here the runbook wins clearly. Two experienced people will often handle the same task differently, and a newcomer will handle it a third way. In a parts business, small differences in how documents are checked, labelled or filed can turn into disputes later. A single written method means a customer receives the same standard whoever answers.<\/p>\n<h3>Paperwork and traceability<\/h3>\n<p>Parts work lives and dies on records: who supplied the item, what accompanies it, when it arrived, where it went. The veteran usually keeps these straight, but the system is only as strong as one person&#8217;s discipline. A runbook turns record keeping into explicit steps with a named place for each document. That does not replace the rules your regulator or customers set. It makes it much easier to follow them every time, because the routine already contains the required record at the right step.<\/p>\n<h3>Cost and effort<\/h3>\n<p>The veteran method looks free, since nothing needs writing. The runbook method costs an afternoon per routine to write and test, plus a small amount of upkeep. The hidden cost of the veteran method appears when that person leaves, takes leave or is simply overloaded, and the rest of the team has to rebuild their knowledge under pressure. Written routines are a one-off investment that earns its keep the first time anyone is absent.<\/p>\n<h3>Resilience when people change<\/h3>\n<p>This is the decisive difference. A desk run by memory has a single point of failure: one person. A desk with written routines can lose any member and continue. For a supplier whose customers depend on prompt, accurate answers, that resilience is not a luxury.<\/p>\n<h3>Handling the unusual<\/h3>\n<p>The veteran wins on the odd case, the strange part number or the supplier who needs coaxing. A runbook cannot predict everything. The sensible design is to let the runbook handle the routine eighty percent as a matter of course, and to write the &#8220;escalate to the senior buyer&#8221; step plainly for everything else, so the experienced person&#8217;s time goes where it is needed.<\/p>\n<h2>A worked example: receiving a consignment<\/h2>\n<p>To make the comparison concrete, picture a parcel of mixed items arriving on a Thursday afternoon while the senior buyer is away. Under the veteran method, the colleague on the desk signs for the parcel, puts it on the shelf, and plans to ask about the paperwork on Monday. Nothing is wrong yet, but the paperwork has not been matched to the order, and by Monday the delivery note is under a pile.<\/p>\n<p>Under the runbook method, the same colleague opens the receiving routine. Step one: compare the delivery note with the purchase order and note any difference. Step two: check that each item has its accompanying documents and that the part numbers on the paper match the labels on the item. Step three: record the date, the supplier and the shelf location in the stock record. Step four: if anything does not match, mark the item as held, tell the senior buyer by the agreed route, and do not release it to an order. Step five: file the paperwork in the order folder and tick the job as finished. The colleague does not need to be an expert, because the procedure carries the expertise, and the one decision that does require judgement is sent to the person qualified to make it.<\/p>\n<h2>Pitfalls when moving from memory to paper<\/h2>\n<ul>\n<li><strong>Documenting the ideal instead of the real.<\/strong> If the written routine differs from what staff actually do, people will ignore it. Record the real process first, then improve it.<\/li>\n<li><strong>Writing everything.<\/strong> Only recurring tasks deserve a runbook. Rare, complex cases belong with the senior buyer.<\/li>\n<li><strong>Forgetting ownership.<\/strong> Every routine needs a named owner who reviews it after each change in suppliers, forms or systems.<\/li>\n<li><strong>Treating it as a policing tool.<\/strong> The purpose is to help whoever is on the desk succeed, not to catch them out. Teams that introduce it as support find adoption is easy.<\/li>\n<\/ul>\n<h2>What the comparison suggests<\/h2>\n<p>It is not a contest where one method deserves to be dropped. The veteran provides judgement, and the runbook provides repeatability. Teams that combine them do best: the experienced buyer writes the runbook, the newcomer tests it, and the veteran reviews the corrections. The result captures the expert&#8217;s knowledge before it walks out of the door.<\/p>\n<h2>Building a parts desk runbook, step by step<\/h2>\n<ol>\n<li><strong>List the recurring tasks.<\/strong> Quoting, receiving, document checks, returns and closing orders are typical.<\/li>\n<li><strong>Rank them by pain.<\/strong> Start with the task that goes wrong most often or that only one person can do.<\/li>\n<li><strong>Write down the real process.<\/strong> Sit beside the veteran and note what they do, in order, including the checks they perform without thinking.<\/li>\n<li><strong>Define the trigger, owner and finish line.<\/strong> What starts the routine, who is accountable, and what a completed job looks like?<\/li>\n<li><strong>Mark the human decisions.<\/strong> Anything requiring technical or regulatory judgement should name the qualified person who decides.<\/li>\n<li><strong>Test with a newcomer.<\/strong> Every hesitation becomes an edit.<\/li>\n<li><strong>Review after incidents.<\/strong> A fix that worked becomes a step.<\/li>\n<\/ol>\n<h2>Where the runbook helps buyers learn<\/h2>\n<p>The same written routines work as training material. A buyer new to the avionics side can read the receiving routine alongside guidance such as a <a href=\"https:\/\/planespart.com\/blog\/avionics-parts-buying-mistakes-to-avoid\/\">review of common purchasing errors for avionics parts<\/a>, and a colleague moving across to control systems can compare it with advice on <a href=\"https:\/\/planespart.com\/blog\/control-system-parts-buying-mistakes-to-avoid\/\">typical sourcing slips for control system components<\/a>. For hardware, an <a href=\"https:\/\/planespart.com\/blog\/complete-guide-to-aircraft-fasteners-and-hardware\/\">overview of fasteners and hardware used in aircraft<\/a> gives context that the procedure itself deliberately leaves out. The runbook says what to do; the reading explains why.<\/p>\n<h2>A glance at how data teams do it<\/h2>\n<p>Written routines are standard practice well beyond aviation. Teams who keep data pipelines running often maintain a library of short procedures for every repeating job, and the writing on <a href=\"https:\/\/www.thedataops.org\/\">TheDataOps.org<\/a> follows that world&#8217;s shift from DevOps practice towards reliable data work. The parallel is useful because it shows the method does not depend on the industry. It depends on a team that is willing to describe its own routine honestly.<\/p>\n<h2>Verdict<\/h2>\n<p>If you must choose a default, choose written routines for everything that repeats, with a named senior person for everything that does not. Keep the veteran, and give their knowledge a second home on paper. When the next absence arrives, the desk will keep quoting, receiving and filing to the same standard, and customers will have no reason to notice.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Experienced buyer or written procedure? A side-by-side look at how each performs on speed, consistency, records and cover, with a runbook you can copy.<\/p>\n","protected":false},"author":6,"featured_media":994,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[597],"tags":[],"class_list":["post-993","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation"],"_links":{"self":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/993","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/comments?post=993"}],"version-history":[{"count":1,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/993\/revisions"}],"predecessor-version":[{"id":1062,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/993\/revisions\/1062"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media\/994"}],"wp:attachment":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media?parent=993"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/categories?post=993"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/tags?post=993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}