Dear people who count my minutes,
On Tuesday I interpreted a conversation about the replacement of a lost identification card. On Wednesday I interpreted a conversation in which a father learned that he would have to leave the room where he had been living with his children. Both assignments occupied thirty minutes on the booking system. Beside each appointment appeared the same green word: completed. I remember looking at the two entries after returning home and wondering how something could be so accurate and tell me so little about the work I had done.
I am an interpreter in an imagined community service. The assignments, families, organization, and experiences described here are fictional, and the circumstances do not represent the policies of an identifiable agency. I write to examine the difference between the duration of work and its demands. A clock measures how much time passes. It cannot, by itself, tell an institution everything that a person must do within that time.
The lost identification card was a straightforward appointment. The applicant understood the questions, the official answered them clearly, and there were no significant misunderstandings. I had prepared the relevant vocabulary beforehand. When the appointment ended, I updated my record and made a cup of tea.
The housing conversation was different. The official had to explain a decision that the father had not expected. He asked questions while trying to understand what the change would mean for his children. Several phrases required careful interpretation because their ordinary meaning was different from their administrative meaning. I had to remain attentive to the words, their tone, and the distinction between something the official knew and something that remained uncertain. My role did not permit me to offer assurances or invent explanations. The precision of that boundary mattered to everyone in the room.
Afterward, I sat in the corridor for a little while. I had not been asked to make the housing decision, and I had no authority to change it. Nevertheless, I had participated in the moment when another person received difficult information. I needed to collect my attention before undertaking a conversation with entirely different requirements.
My next appointment was due to begin almost immediately.
The scheduling team had allowed a short interval between assignments. The interval was the same regardless of the nature of the preceding conversation. Its designers had treated the gap as time required to move between two pieces of work. They had not considered that one conversation might leave an interpreter needing a different kind of transition from another.
I understood the practical appeal of the schedule. An interpreter is paid for a service that people genuinely need, and appointments cannot be arranged without considering cost, availability, and demand. A missed appointment may leave somebody unable to understand information on which an important decision depends. I did not want the organization to become careless about those responsibilities. I wanted it to recognize that the reliability of its service depended on conditions that the clock could not describe.
The published letter on exhaustion as infrastructure offers a useful way to understand what happened in our office. We relied on people to accommodate the differences between scheduled work and experienced work. The differences did not need to be large every day. They accumulated through appointments, transitions, preparation that took longer than planned, and the quiet effort of beginning again after a difficult conversation.
Our reporting system measured several things well. It recorded whether appointments had taken place, how long interpreters had been booked, and whether an assignment had been canceled. Those records helped the organization identify unmet demand. They did not distinguish a routine exchange from an appointment involving unfamiliar terminology, several participants speaking at once, or an unusually difficult account.
The absence of those distinctions affected more than individual comfort. A conversation requiring additional preparation was evaluated against the same expectation as one involving vocabulary I used every morning. An interpreter who took time to review unfamiliar terms might appear less available than somebody assigned to a more predictable set of conversations. The comparison was numerical, but the activities being compared were not interchangeable.
A colleague called Amir noticed that he had begun avoiding certain assignments whenever the booking system allowed him to express a preference. He was capable of interpreting them. He simply knew that they required preparation the schedule did not reliably recognize. Another colleague accepted difficult appointments because she felt that refusing them would leave the work to somebody else. Neither pattern appeared in our records as a response to the design of the service. One employee looked selective, and the other looked exceptionally available.
This was a lesson in the behavior institutions encourage through their ordinary arrangements. A schedule can teach people to protect themselves by avoiding particular kinds of work. It can also teach them to preserve their reputation by accepting demands they find difficult to sustain. Managers may interpret those decisions as expressions of personality when they are partly responses to incentives established by the workplace.
We needed a way of discussing strain that did not require interpreters to disclose the private content of conversations. Confidentiality was essential. The families using the service had not agreed to become examples in a discussion about our workload. We also did not want staff to be ranked according to how distressed they appeared after an assignment. Such a measure might create another reason to conceal a difficulty.
At a review meeting, we proposed a distinction between information needed to arrange a service and information that should remain private. A booking could identify whether an assignment required specialist preparation, prolonged concentration, or particular coordination without recording the intimate details of the people involved. Staff could request an appropriate adjustment through a confidential process. A supervisor could consider the pattern of assignments across a working day rather than examining every appointment in isolation.
The first proposal was too ambitious. We had created a long list of categories that schedulers would struggle to use consistently. A colleague pointed out that an apparently simple conversation could become complicated without warning. We revised our approach. The categories would help identify foreseeable demands, while the schedule would retain a reasonable capacity to respond to demands that could not be predicted.
There would still be uncertainty. We could not promise that every interpreter would experience an assignment in the same way. Nor could we pretend that strain could be expressed through a universal score. People bring different experience, knowledge, and personal circumstances to their work. A useful arrangement needed to acknowledge those differences without turning them into grounds for unfair treatment.
The finance team asked what the changes would cost. Some appointments might require longer booking intervals. Preparation time would become more visible. Capacity might decline on particular days, unless additional staff could be arranged. These were important consequences, and we did not deny them.
I asked whether our existing calculation included the cost of repeated corrections, unsuccessful handovers, and the difficulty of retaining experienced interpreters. Some of these costs were recorded elsewhere. Others were not examined systematically. As in the earlier discussion of efficiency that excludes important costs, the problem was not that the numbers were necessarily wrong. It was that the boundary of the calculation made certain consequences somebody else’s concern.
Our organization eventually tested more realistic scheduling for a limited group of assignments. Staff were given clearer opportunities to identify preparation needs, and supervisors reviewed demanding sequences of work. We preserved access to urgent services through arrangements appropriate to the resources available. The changes were neither a complete solution nor an invitation to regard every uncomfortable moment as a failure of management.
Interpreting remained demanding. That was not surprising. The value of the service lay partly in enabling people to communicate during circumstances that were difficult to navigate. I did not expect the work to become effortless. I wanted the institution to stop confusing necessary effort with an unlimited capacity to recover from it.
The experiment also changed the conversations we had among ourselves. We became better at asking what another person needed before assuming we understood their experience. Sometimes a colleague wanted help preparing unfamiliar terminology. Sometimes they wanted a few minutes to review notes before moving to another assignment. Sometimes no adjustment was necessary. The important change was that asking had become a normal part of organizing responsible work.
I worry that institutions will respond to such concerns by inventing elaborate measurements of emotion. There is a temptation to believe that anything worth acknowledging must first acquire a score. But a worker’s private experience is not simply another resource for management to collect. An organization can establish reasonable conditions, examine workloads, and offer confidential support without demanding that everybody continually quantify their inner life.
Measurement has its proper place. It can show patterns that individual recollections miss. It can help compare arrangements and identify circumstances that deserve investigation. Its limitations should direct our attention toward informed observation and conversation, not persuade us that everything outside the measurement is irrelevant.
Yesterday I completed two more appointments of similar duration. One involved a long explanation of a technical process. The other required an unusually careful distinction between several possible outcomes. I prepared differently for them and used the interval afterward in different ways. Both were completed, and the dashboard recorded them as such.
I have no wish to remove the green word from the screen. It tells the organization something useful. I simply want the people who read it to remember that a completed appointment is the outcome of a human activity, and that the conditions supporting that activity belong to their responsibility.
Dear people who count my minutes, please continue counting them. Then ask what those minutes contain, what preparation makes them useful, and what they require of the person expected to begin the next conversation.
With care for the words that pass through our voices, and for the people whose voices carry them,
An interpreter who is more than a row of completed appointments



