The intake desk at a small, fictional legal-information office was never quiet. Phones rang, walk-ins arrived with folders, and the three staff members on duty were forever interrupted by questions that were unrelated to the matter on their screen. In the autumn they tried something modest: a not-now parking list. This is a made-up but realistic account of how it changed a working week. Read it as a general illustration, not as guidance for any real matter.
The desk before the list
Every morning started with a clear plan: draft the plain-language summaries for the day’s enquiries. Every morning the plan fell apart by ten. A caller wanted to know about a deadline unrelated to the queue. A colleague remembered a template that needed updating. A visitor asked whether the office could also help with something outside its remit. Each of these interruptions was reasonable, and each cost the team the thread of the work in front of them.
Mistakes crept in. A summary went out with the wrong reference number, and a follow-up call was missed. Nothing catastrophic happened, but the team could see the pattern: the more they responded in the moment, the less accurately they worked.
The experiment
The office manager introduced one rule. Any request that was not about the current file would be written on a shared sheet headed Not Now, with a brief description and a note of when it came in. The person raising it would be told when it would be looked at, and they would return to their file. Emergencies, such as a visitor in distress or a deadline falling that same day, were handled straight away and recorded afterwards.
The review was scheduled for the end of each day, fifteen minutes, with all three staff present. Each line was marked do, drop or hold. Lines marked do received an owner and a day.
What the sheet captured in its first week
- A request to rewrite the office’s checklist for documents visitors should bring.
- A question about how to explain a procedural term more simply.
- A note that the waiting-area leaflet was out of date.
- An idea to keep a short glossary on the front desk.
- A reminder to ask a partner organisation about its opening hours.
Not one of these needed an immediate answer. Yet each had previously interrupted a file. Come Friday the team estimated, informally, that they had reclaimed several hours of uninterrupted work, and the summaries went out without errors.
The conversation with visitors
The sceptic in the team worried that visitors would feel brushed off. In practice, the opposite happened. Telling a visitor “I will note that and answer it at four o’clock” turned out to be more reassuring than a distracted, half-correct answer in the moment. The desk began to keep a printed card that said what time the review happened, so people knew when to expect a reply.
Staff also learned to separate informational questions from anything that edged toward advice. When a visitor asked what they should do in a particular dispute, the response was to suggest speaking with a qualified lawyer, and to log the logistics of that referral on the list rather than improvising an opinion.
A look at how legal information reaches readers
The team’s side readings became part of the list. One entry pointed to a piece on how to tell that a problem needs legal guidance right away, which the manager wanted as a reference when deciding which requests are emergencies. Another entry noted a question about the records software teams keep, prompted by Reloqui, a release-intelligence site for engineering organizations. The office had no use for it directly, but the idea of a clear paper trail resonated with a team that lived by file notes.
A day at the desk with the list in place
Consider a typical Tuesday after the change. At nine, one staff member begins a plain-language summary of a visitor’s enquiry about a rental paperwork question. At nine twenty the phone rings with a request to update the office’s opening hours on the leaflet; she writes one line on the sheet and thanks the caller. At ten a visitor wonders aloud whether the office could also explain a tax form, which is outside its scope. The desk logs the request and explains that the review is at four, then gives the visitor a general pointer to the relevant public information office.
By noon the summary is finished and checked, a task that previously took most of the day. The afternoon is spent on two more summaries and a quiet pass through the shared glossary. At four the three of them gather, read the day’s five lines, drop two, promote one to the next morning, and hold two. They leave the review knowing exactly what tomorrow holds.
What the manager learned about authority
One surprise was how much the list changed the way staff spoke to each other. Interruptions between colleagues used to be unspoken demands. Now a colleague would say, “Put it on the sheet,” and the exchange was friendly rather than curt. The manager observed that the habit lowered tension, because a request that is written down feels acknowledged, even when it will not be handled right away.
Problems the team hit
Early on, the list became a polite way of avoiding awkward calls. One colleague parked a phone callback that was in truth overdue, and the manager spotted it at review. After that the team added a rule: if a request involves a person waiting for a reply today, it is not a parking item. Another problem was length. The sheet filled quickly, so the group limited each line to a short phrase and began deleting dropped items at every review.
There was also the matter of confidentiality. File details never went on the shared sheet; lines referred to tasks, not to people or cases. That rule kept the list safe to display and easy to discuss.
Four weeks on
Four weeks in, the desk looked calmer, even though the volume of enquiries was unchanged. The review took ten minutes by then, and the team had developed a sense of which items were worth promoting. Summaries took less time to draft, and the office manager noticed that staff left on time more often, which was an unexpected benefit.
What other small offices can take from this
- Choose one place for the list and keep it free of personal or case details.
- Agree a firm definition of what counts as an emergency.
- Hold a short review at the same time every day.
- Always tell the person who raised an item when it will be looked at.
- Drop lines generously, so the list stays small.
The core lesson is that a pause is not a refusal. A clear later, delivered kindly and kept reliably, builds more trust than an instant answer given by someone who is trying to do three things at once.