One Person DepartmentA Useful Boundary · Requests and workload
Agree one request queue and a clear urgent route
Give ordinary requests one visible place, agree review windows and make urgent trade-offs someone’s explicit decision.
A message, a corridor conversation and an email can each sound like a small request. Together they can replace a whole morning without anyone deciding what should move. Giving the work one visible place helps, but the list needs an agreement about when it is read and who decides competing priorities.
Begin with the channels people already use. You can record a request from a conversation without first persuading the whole organisation to use another application. The useful change is that a request has an outcome, a desired date and a next decision, rather than surviving only in your memory.
Agree when the list is reviewed
This example is illustrative. A part-time office and communications coordinator works six hours on Monday, Tuesday and Thursday: 18 hours in total. They prepare a staff bulletin, coordinate office notices and follow up ordinary supplier questions. They do not approve spending or decide which manager’s deadline takes precedence. Wednesday and Friday are non-working days.
The coordinator and manager agree two ordinary request reviews, at 10:00 and 14:00 on those three working days. These are review windows, not promises to finish every item immediately. Reading, clarifying and recording requests takes working time and belongs inside the 18 hours.
Agree what people can expect after a review: acknowledgement, a question, a proposed date or a request for a priority decision. If a window is displaced by other agreed work, say when the next review will happen. Do not quietly keep an impossible response promise alive.
Record enough to make the next decision
Use one list you and the relevant decision-maker can access. Record the outcome someone needs, their desired date, the next decision and the agreed next action. A requested date remains a request until capacity and authority are checked.
An illustrative request list after Tuesday’s 10:00 review
Scroll sideways to read all four columns.
| Requested outcome | Desired date | Next decision | Agreed next action |
|---|---|---|---|
| A paragraph for Thursday’s staff bulletin | Tuesday, 12:00 | Manager confirms the approved information. | Prepare the paragraph in Thursday’s protected bulletin block, if information is confirmed. |
| A revised meeting-room notice | Thursday, 12:00 | Manager decides whether it displaces bulletin preparation. | Ask for that decision; no completion date is promised yet. |
| A reply about an ordinary supplier request | Tuesday, 16:00 | Budget holder confirms the response within their authority. | Follow up the missing decision in Tuesday’s afternoon window. |
The list does not need a field for every possible detail. Link to the authorised record where supporting information already lives. Avoid copying private staff or supplier material into a broadly visible queue. The queue explains the work and its next decision; it is not a replacement for the underlying records.
Separate acknowledgement from a commitment
Use a response that makes the next step clear without accepting an unchecked deadline. In the example, a message arriving after Tuesday’s final review may wait until Thursday unless it meets the agreed urgent route.
I have added this to the request list. My next review is Thursday at 10:00. I will confirm the next step after checking the information and agreed work. The requested date is recorded, but I have not yet confirmed completion by then.
For a conflict already visible in the plan, name the actual trade-off. A list cannot choose between two commitments that need the same hour.
Thursday’s bulletin preparation is the agreed priority. Preparing the revised meeting-room notice before noon would move that work. Please confirm which should take priority, or who can take one of the tasks. I will update the list when that decision is agreed.
Adapt the wording to your authority and normal language. If you can make the choice yourself, record it and tell the people affected. If you cannot, make the decision easy for the person who can: outcome, consequence and options.
Give urgency a route that exists during absence
Agree a narrow operational meaning of urgent with the manager. In this example, it means work that cannot wait for the next ordinary review without disrupting an already agreed service or commitment. A requester writing “urgent” does not by itself establish that condition.
The agreed route is to the duty manager, who checks the consequence, decides what moves and arranges someone available to act. Record the real contact and cover arrangement in your workplace. Do not publish a route that depends on the coordinator checking messages on a non-working day. Existing emergency procedures remain separate from this ordinary work-priority agreement.
Review one week of actual decisions
At the end of a working week, look for requests that bypassed the list, waited for missing decisions or repeatedly displaced protected work. Agree one change: a clearer required input, a different review window or a more realistic service promise. Keep the list small enough to maintain within the role’s hours.
If essential demand still exceeds capacity, take that gap to the manager. The next decision may concern scope, support or timing. A better queue makes the gap visible; it cannot provide the missing hours.