Keeping the Template Library Alive and Trusted

Wednesday, 11:05, at Acme. Ravi is in his second week on the desk and has sent the "how to request access" template to twelve people since Monday. That is because it is the one the list offers when you type "access", and it reads well. It tells the requester to log in to the old portal, choose Access Requests, and pick their manager from the list. The twelfth recipient, Hannah in finance, replies: "What portal? The one that was switched off before I joined?" Ravi checks. The portal was replaced long before he arrived. The template was written by someone who has since left. The manager list it mentions never existed in the new system. And the previous eleven people either worked it out, asked a colleague, or gave up. Nobody on the desk had read the template in a year. They had only sent it.

A template library is a set of documents the desk sends to requesters every day and reads almost never. That is the exact condition under which documents go stale without anyone noticing. Keeping it alive means giving it an owner and naming its contents so they can be found. It means agreeing what is shared and what is personal, reviewing it on a schedule, and retiring what no longer earns its place. This article is part of our Templates & Canned Responses Done Right series. This article is about the upkeep. The twenty templates worth keeping in the first place are in The Twenty Templates Every Help Desk Needs.

It covers why libraries rot and the five causes, then one named owner and what they do. Next comes naming so a stranger finds the right template in five seconds. It covers shared versus personal templates and the rule between them, then the quarterly review with its four verdicts. It covers retiring a template without losing anything, then the template that drifted, which is the subtle failure. It ends with adding a new template without growing the pile, a short war story, and the template review sheet to copy, in that order.

Why Libraries Rot

Libraries rot for five reasons, and the first is that nobody owns them. The library at Acme belonged to the desk, which is to say to everyone, which is to say to nobody in particular. A document that belongs to nobody is never read for accuracy because reading it is nobody's job. The second reason is that everyone can add and nobody removes. Each technician who wished a template existed wrote one, saved it, and moved on. Nobody ever wished a template did not exist strongly enough to delete it. Template libraries grow the way a shared drive grows. Nothing is ever decided and nothing ever leaves.

The third reason is that the world changes under the text. The portal is replaced, the phone extension is reassigned, and the desk's hours change. The person whose name is in the sign-off leaves. The knowledge article the template links to is rewritten under a new address. None of those events touches the template, because the template is a document in a list and not a thing that anyone is notified about. The fourth reason is that nobody reads what they send. A technician who has used a template fifty times stops seeing its words. They see its shape, insert it, change the name and press send. And the sentence about the old portal passes under their eye fifty times without once being read. The fifth reason follows from the fourth: the requester is the first person to read the template critically. And the requester is the last person the desk wants doing its proofreading.

All five causes are structural, which is good news, because structural problems have structural fixes. An owner fixes the first. A rule about adding fixes the second. A scheduled review fixes the third and fourth together, because a review is the one moment when someone reads the template as the requester will. The fifth fixes itself once the other four are in place. None of it requires a new tool or a budget. It requires one person's name and one hour a quarter.

One Owner, Named

The library has one owner, by name, written at the top of the library where the purpose card sits. The owner is not the author of every template, and not the only person allowed to write one. The owner is the person who says yes or no to a new shared template, runs the quarterly review, and decides what is retired. They are the person a technician tells when a template turns out to be wrong. On a desk of one, the owner is you. On a desk of ten, it is usually the lead or whichever senior technician writes most clearly. It is a role, not a job: an hour a quarter for the review and a few minutes per proposal.

Ownership works because it converts "someone should fix that" into "I will tell Priya". Ravi, discovering that the access template mentions a dead portal, has three options on a desk without an owner. He can fix it himself and hope nobody minds, leave it and feel bad, or raise it in a meeting that happens monthly. On a desk with an owner he sends one line to Priya. Priya fixes it in two minutes. Priya also knows to check the other templates written by the same departed author. The fix is the same. The difference is that it happens the same day, and the pattern behind it is noticed.

Write down what the owner does, in four lines, because an owner whose duties are not written is an owner in name. Approves new shared templates against the skeleton and the purpose card. Runs the quarterly review and records the verdicts. Retires templates and tells the desk. Receives reports of wrong templates and fixes them within a day. A shared library with an owner who does those four things stays trustworthy. One whose owner does only the first gradually becomes a well-curated collection of out-of-date messages, which is what Acme had.

Naming So a Stranger Finds It

Name every shared template so that a technician in their second week finds the right one in five seconds from the situation in front of them. That means the name states the purpose, in the words a technician would type while looking for it: "Missing information", "Cannot reproduce", "Waiting on vendor". It means a number prefix so the list sorts into the order of a ticket's life rather than alphabetically. Alphabetical sorting puts "Acknowledgment" next to "Approval needed" and "Closed" next to "Cannot reproduce" and helps nobody. And it means the trigger written as the template's first line, so that a technician who opens the wrong one knows within a second.

Names that fail the five-second test share a few habits. They name the author: "Acknowledgement - Pete" tells a stranger nothing about when to use it and everything about who to blame. They carry a version: "ack2", "New ticket reply FINAL", "FINAL2", each of which is a confession that nobody retired the previous one. They name the situation from the desk's side rather than the message's purpose. "Shutter till" is a template about a known fault, but nobody searching for the workaround template will type "shutter". The name is a label on a drawer, and labels on drawers describe what is inside in the words of the person looking for it.

Personal templates can be named however their owner likes, within reason; nobody else has to find them. The moment one is proposed for the shared library, it gets a number and a purpose name. If it duplicates a shared template under a different name, the duplication is the first thing the owner notices. That is the reason it is merged rather than added. Most of what Ines found at Northgate, in the previous article, was forty-one templates that were one template with forty-one names.

Shared Versus Personal

A shared template is one every technician on the desk can insert. And it is the desk's voice: what the desk says, in the desk's agreed words, about a situation that recurs. A personal template is one a single technician keeps for their own use, for phrasing they repeat, and it is that technician's voice. Most help desks, QuerySolv included, keep predefined replies that can be personal or shared. And the distinction matters more than the mechanism. Shared templates are owned, named and reviewed. Personal templates are allowed, and lightly governed. Governing them heavily drives them into a text file on the desktop where nobody can see them at all.

Two rules govern personal templates, and both are short. First, a personal template follows the same skeleton as a shared one. It has slots for the name, the specific thing, the time and the added sentence, no filler, one ask. The desk's voice is partly its shape, and a personal template with no slots is the robotic failure under a private name. Second, anything a technician sends daily from a personal template is proposed for the shared library. A message sent daily by one person is a message the desk sends, and the desk should agree on its words. The proposal takes one line to the owner. The owner either shares it, merges it with an existing template, or says why not.

The risk in personal templates is not that they exist; it is that they diverge. Five technicians each keep a personal copy of the resolved message. Each edits theirs a little over a year, and the desk is now sending five different closing messages that began as one. A requester who deals with two technicians notices the desk has two voices. The way to keep one voice with five people is the subject of One Voice Across Five People. The library's part in it is that the shared version is the reference and the personal copies are compared to it at the review.

The Quarterly Review

The quarterly review is one hour, once a quarter, in which the owner reads every shared template as a requester would and gives each one a verdict. The reading has five questions. Is every fact in it still true: the systems named, the phone numbers, the links, the hours, the sign-off? Has it been sent this quarter, and roughly how often? Does it still have one ask, five lines and no filler, or has it grown? Does it still sound like a person, or has a hedge crept in? And, the question most reviews skip, what do five real sent copies of it look like? Pull five messages sent from the template this quarter and read them. The template may be fine and the copies may show that nobody fills the slots, which is a different problem with a different fix.

Each template gets one of four verdicts. Keep: true, used, still five lines, slots being filled. Fix: true in purpose but with a stale fact, a grown paragraph or a missing slot. The owner edits it during the review, which is why the review takes an hour and not ten minutes. Merge: it duplicates another template under a different name, or two templates differ only in a slot that should be a slot. The better one survives with the other's name noted in it. Retire: unused for two quarters, or about a situation that no longer arises, or so wrong that rewriting is starting over. The table gives the signs for each.

Keep the review to an hour by reviewing twenty templates, not a hundred and twelve. If the library is larger than that, the first review is a dig-out and will take an afternoon. In that case, most of its verdicts will be Merge and Retire. After that, an hour is honest. Put the review in the calendar as a recurring appointment with the owner's name on it, in the same week each quarter. A review that depends on someone remembering is a review that happens once.

Retiring Without Losing Anything

Retire a template by renaming it rather than deleting it, at least for a quarter. Put RETIRED at the front of the name, and after it the number of the template that replaces it: "RETIRED - use 02 Missing information". A technician who reaches for the old one by habit sees the pointer and learns the new one. A technician who deleted it would see nothing and write a new one by hand. After a quarter with no sends, the owner removes it. The name and the reason go on one line of the review sheet so that nobody rewrites it next year from memory.

Tell the desk, in one line, when a template is retired or changed: "Retired the old access template, use 20 Pointer to a knowledge article with the new access guide; the old one named the dead portal." It takes ten seconds in the team chat and it means the twelve people Ravi sent the dead portal to are the last twelve. A change made silently is a change half the desk learns about from a requester. (The other half learns about it from the first half, which is slower.)

Never retire a template because it is uncomfortable. Cannot reproduce and the plan has changed are the two most often found unused at review. The reason is not that the situations stopped arising; it is that technicians avoided the message. An unused template about a situation that still happens is a sign that the situation is being handled by hand, probably badly. In that case, the verdict is Fix, with a conversation, not Retire.

The Template That Drifted

Drift is what happens to a template that has been edited many times by many hands until it says something nobody decided. It has two forms. Edit drift is the shared template itself changing. A sentence is added after one incident, a caveat after another, a line about hours after a complaint. Eventually the five-line acknowledgment is eleven lines and reads like the terms and conditions of a car park. Copy drift is the personal copies diverging from the shared original, so that the desk's resolved message exists in five versions. One has lost the line about how to reopen and one has gained an exclamation mark.

Drift is found by comparison, which is why the review reads sent copies and not just the template. Put five sent copies of the resolved message, from five technicians, side by side. If they differ in the slots only, the template is healthy. If they differ in the fixed text, somebody is not using the shared version. In that case, the owner finds out which personal copy has wandered and whether it wandered somewhere better. Sometimes it has. The technician who added "if it comes back, reply to this message" to their personal copy improved the desk's template. In that case, the fix is to adopt the improvement, not to stamp out the copy.

Fix edit drift by going back to the skeleton. Take the eleven-line acknowledgment, identify the five lines that do the work, and cut the rest. Keep a note of what was cut and why it was once added so the next review does not add it back. Most of what is cut was added in response to one incident and has been read by nobody since. The desk can usually name the incident, and sometimes the requester. Documentation that nobody rereads goes stale in exactly this way wherever it lives. The case for treating written things as living ones, made for a desk of one in Documentation as Your Second Person, applies to a template library word for word.

Adding a New One Without Growing the Pile

A new shared template is added when the same message has been written by hand three times in a month, by anyone, and not before. One occurrence is a situation; two is a coincidence; three is a shape, and shapes get templates. The technician who notices proposes it to the owner in one line with a real example attached. The owner checks it against the existing twenty. The most common outcome of a proposal is that a template for it already exists under a name the proposer did not search for. That outcome is a naming fix rather than a new entry.

If it is genuinely new, one person writes it from the real example using the skeleton. Then one other person reads it and asks the stranger's question, "what do I do next?" The owner then gives it a number, a purpose name, a trigger on the first line and a place in the right group. Then it is announced in one line and sent for a week before it is called finished. The bar is deliberately a little high. A library of twenty that gains one template a quarter is at thirty in two and a half years, and thirty is fine. A library that gains one a week is at a hundred and twelve, and a hundred and twelve is Acme.

Prefer replacing to adding. If the new shape is a near relative of an existing template, the question is whether a slot would make the existing one cover both, and usually it would. The resolved message and the resolved-with-workaround message are different templates because their required content differs. The resolved message for a laptop and the resolved message for a phone are one template with a slot. Whether the library is earning its place at all, by the numbers, is the subject of Knowing Whether Your Templates Actually Help. The library's usage counts feed straight into the next review.

A Short War Story: The Extension That Rang Finance at Fernleigh Dental

Fernleigh Dental ran six practices from one small IT desk. Its password-reset confirmation template ended: "If you still cannot sign in, call extension 2140 and we will help straight away." When the head office moved floors, extension 2140 was reassigned to a finance clerk called Beatriz. For the next five months every receptionist across six practices who could not sign in after a reset phoned finance. There Beatriz took the call, apologised, looked up the IT number, and passed it on. She did that about sixty times by her own tally before anyone asked why she was keeping one. Each misdirected call cost a receptionist a few minutes at a front desk with patients waiting, and cost Beatriz the same. It cost the desk a reputation for being unreachable that nobody could trace because the tickets all looked fine. Beatriz raised it, as a ticket. The desk lead found the extension in the template in under a minute and in two other templates in under five. Fernleigh gave the library an owner that afternoon and put the quarterly review in the calendar. The lesson it wrote down was that a template is a document that goes stale like any other. And the people who send it are the last to find out.

The Template Review Sheet

The sheet is the quarterly review on one page: one row per shared template, five questions, one verdict. There is a short section at the bottom for the proposals, retirements and drift found. Fill one in each quarter and keep the completed sheets. The second-most useful thing about a review is being able to see what the last one decided and why. The owner fills it in; anyone on the desk can read it. It is deliberately plain. An interesting review sheet is a sign of a library that went too long without one.

TEMPLATE REVIEW SHEET — ONE PAGE, ONCE A QUARTER
Desk: ______________________   Owner: ______________   Review date: ________   Next: ________
Shared templates in library at start: ____   at end: ____

FOR EACH SHARED TEMPLATE (one row each)
  #   Name                         Facts true?  Sent this  Five lines,  Sounds like  Five sent     Verdict
                                                quarter?   one ask?     a person?    copies read?  K / F / M / R
  __  _________________________    [ ]          ____       [ ]          [ ]          [ ]           ___
  __  _________________________    [ ]          ____       [ ]          [ ]          [ ]           ___
  __  _________________________    [ ]          ____       [ ]          [ ]          [ ]           ___
  __  _________________________    [ ]          ____       [ ]          [ ]          [ ]           ___
  (continue for every template; twenty rows is normal)

FIXES MADE DURING THE REVIEW
  Template ____: changed ______________________________ because ______________________________
  Template ____: changed ______________________________ because ______________________________

MERGED
  ____ merged into ____ ; slot added: ______________   Old name retired with pointer [ ]

RETIRED
  ____ renamed "RETIRED - use ____"   reason: ______________________   remove after: ________
  ____ renamed "RETIRED - use ____"   reason: ______________________   remove after: ________

DRIFT FOUND (sent copies differ in fixed text)
  Template ____: personal copies by ______________ differ in ______________________
  Adopted the improvement [ ]   Reissued the shared version [ ]   Told the desk [ ]

PROPOSALS SINCE LAST REVIEW
  Proposed by ________: "______________________"   Decision: added as ____ / merged into ____ / declined because ______

TEMPLATES UNUSED BUT ABOUT A SITUATION THAT STILL HAPPENS
  ____  ______________________   Being handled by hand?  Conversation with: ______________

ANNOUNCED TO THE DESK ON: ________   (one line per change)

Priya ran the first review at Acme the week after Hannah's reply. It took an afternoon rather than an hour, because the library had sixty-eight shared templates and had never been read. It ended with twenty-three, four of them fixed that day. The access template was retired with a pointer to the knowledge article that had replaced the portal. The second review, a quarter later, took fifty minutes and changed two templates. Ravi, by then, was the one who had proposed one of them, with a real example attached. The proposed template was added as number twenty-four. Nobody at Acme has been sent to the old portal since, which is a small thing to be proud of and the entire point.

Frequently Asked Questions