In the last box on the scheduling feedback form, Lin writes that she needs to pick up her child on Wednesday evenings and would prefer an early shift whenever possible. Worried that this might not be clear enough, she adds the time.

She presses Submit. A message appears: We’ve received your feedback.

A few days later, the new schedule comes out. She is still on the late shift on Wednesday. When she asks about it, the answer is: We’ve recorded all your comments.

It is easy to jump to a conclusion: they simply don’t care about her. Someone else might say, “They asked for everyone’s preferences. They can’t please everybody.” There’s feeling behind both responses. Neither quite answers the question she wants to ask.

What actually happened to the thing I told you?

The everyday situations below are made-up examples, not findings from an investigation into a particular workplace. Before deciding who is right or wrong, let’s follow that piece of feedback a little further.

1. Written down—and still a remainder

Suppose the shop collected this information so it could assign shifts people could actually work and reduce last-minute swaps. The form listed each person’s available hours and included a box for comments.

But when the person making the schedule received the file, they copied only the names and existing shifts into a new spreadsheet. They never opened the comments, never used them to check availability, and had no colleague responsible for bringing individual constraints into the scheduling discussion. The file was safely stored. Not one comment was lost.

Lin herself was not missing from the list. Her name was there, her shifts were there, even her comment was there. Yet something relevant to this round of scheduling never entered the arrangements: her Wednesday evening constraint. Whether she could come in at that time should have made a difference to which arrangements were considered. Instead, the information stayed in an unused comments field.

That availability constraint is a remainder in this round of scheduling. Calling it a remainder does not mean it was surplus to requirements. It means this particular task failed to take it in. In this essay, a remainder is something specific that matters to a task’s purpose but is not actually used in carrying it out.

A remainder need not sit outside the form, or be a secret nobody knows. Lin knows, and the file says it too. What is missing is the step between writing it down and actually using it to make the schedule. It is inside the record but outside the work.

So “Lin is a remainder” would be the wrong thing to say. We are not sorting people into a leftover category. We are asking which part of her situation was left out of which particular arrangement.

We can make that finding because we have established that the comments were not used—not because she disliked the shift she received. Keep that distinction in mind. We will come back to another late shift that does not support the same finding.

2. A remainder for which task?

Take the same file to the person responsible for archiving it, and the question changes. Suppose their only job was to preserve everyone’s words in full, and they did. Lin’s comment has been archived. The archivist has not failed at their job just because they lack the authority to change a shift.

The same information can have been dealt with for archiving and still be a remainder for scheduling. Its nature has not mysteriously changed. We are asking about different tasks. Remainder names a relationship between a particular item and a particular process. Whenever we call something a remainder, we must be able to add: in relation to which task, on which occasion?

There is another question to answer: why does this detail matter here? Whether Lin can work on Wednesday evening affects which shifts are workable. Whether she prefers blue or green usually does not. Failing to record her favourite colour does not thereby leave a remainder in the scheduling. Relevance is what separates a remainder from details we genuinely do not need to handle this time.

That gives us two questions for a check. First: if this particular fact were different, would pursuing the same purpose call for doing something differently? Second: was it actually used somewhere in the process where, under the relevant conditions, it could affect how the task was handled? The first asks why it matters; the second asks whether it was genuinely taken in.

We cannot casually rewrite the purpose afterwards. If the shop said it was collecting information to make workable schedules, we cannot decide that it “only wanted to collect forms all along” merely because the schedule stayed the same. Conversely, if the task really was just archiving, we cannot quietly expand it into solving everyone’s difficulties. We need to check how the task was described at the time, how the work was passed on, and what actually happened.

If the undertaking and the practice do not match, set them out separately. Treating “the file was safely stored” as an answer to “the scheduler considered this constraint” is precisely the substitution that “We recorded everything” can conceal.

3. Forty minutes won’t tell you which bar went wrong

This way of asking questions is not just for checking on organisations. We can use it to look at our own small habits.

Suppose you practise the piano and record just one number each day: how many minutes you played. Forty on Monday. Forty on Tuesday. Forty again on Wednesday. The neat rows are reassuring.

If all you want to check is whether you practised for at least forty minutes each day, and the times are accurate, the log can already answer your question. Whether you played a particular note wrong is irrelevant to that limited timekeeping task. Leaving it out of the record does not make it a remainder for that task.

But if you want to use the log to decide which bars to focus on tomorrow, forty minutes is not enough. One day you keep getting stuck at the beginning; another day you keep making mistakes at the end. Both entries show the same number. Yet the two situations give you different reasons for where to spend tomorrow’s practice time.

Suppose you have no recording, no marks on the score, and no other notes or memories that you use to plan your practice. You decide tomorrow’s focus from those minute totals alone. Then the location of the difficulty is a remainder for this practice plan: it matters to what you should practise tomorrow, but it has not been used to decide.

This is a different stopping point from the one in Lin’s story. Her constraint was recorded but never used. The place where you went wrong was never preserved by the number “forty minutes” in the first place. In one case, the information was there but unused. In the other, the kind of record being kept did not capture the difference that mattered. Different causes can leave a remainder.

Writing 40.0 minutes, or even recording the time to the second, will not recover the missing bar. What you need might be no more than a sentence: “Went wrong again where the left hand comes in.”

But if your teacher already heard the mistake and used it to plan the next day’s practice, its location has entered the plan by another actual route. You cannot keep staring at the notebook and calling it a remainder for this plan. We need to look beyond what one box contains to how the work as a whole was done.

4. Not everything left out is a remainder

Take another small example. A reading course uses a test to check whether applicants can keep up. Let’s make the conditions explicit: a score of eighty is enough, there are plenty of places, and everyone who reaches the threshold can enrol. Applicants who qualify are not ranked against one another.

One applicant scores ninety, another ninety-five. The person handling enrolment records only “qualifies” and does not retain the five-point difference.

Are those five points a remainder for this admission task? No. Given the purpose and conditions we set out at the start, both people already have the ability the course requires. Ninety or ninety-five makes no difference to how their applications should be handled. That reason comes from what the course requires, not from saying, “They both got in anyway.”

Now change the task: choose the higher-scoring of these two applicants, under an explicit score-based selection rule. Those five points matter. If the selection still relies only on two entries saying “qualifies,” without retrieving the original scores, the distinction needed to rank them is left out of the decision. It is a remainder for this selection. We are now asking about a different task; we cannot simply carry over the earlier finding that the record was adequate.

This is why “there is always something not written down” does not establish that there must still be a remainder. For any particular task, we have to identify what was left out and explain why it matters to that task’s purpose. An application form that does not record all your talents is not thereby denying that you have them. Nor does it need to become a verdict on your entire life.

5. A no is not the same as being ignored

Back to Lin. This is a different version of the situation: set aside what we established about the earlier process.

This time, the scheduler does read her availability. They confirm with her that a late shift would require other arrangements for picking up her child. They check everyone else’s hours and try several possible swaps. Those availability constraints are used to draw up the options; when suitable cover is available, her shift is adjusted accordingly.

In the end, they still cannot move her off this Wednesday’s late shift. She may be disappointed. Whether the arrangement is fair, and whether the extra burden it places on her is reasonable, remain open questions.

But if that work really took place, her availability constraint is not a remainder in this round of scheduling. It helped shape the options, even though it did not outweigh every other factor. Two identical late shifts can be the end points of very different processes.

The reverse is true as well. Getting the result you wanted does not prove that your input was used. A system might happen to assign Lin an early shift without ever reading her comment. We are looking for the actual path in between, not just checking whether the destination suits her.

Here a remainder parts company with an unresolved problem. Lin’s difficulty may persist, and the arrangement may be deeply unfair. Neither changes the fact that her constraint entered the actual weighing of options. Deciding whether something is a remainder and judging whether a decision is good are questions that need separate answers.

Suppose this is the improved approach the shop actually adopts next month. The constraint is then no longer a remainder in that new round of scheduling. Perhaps only the handover changed; not a single line of the form did. We should recognise that the information was taken in. Doing so neither erases the earlier failure to use it nor declares the new arrangement free of every other problem.

6. “We don’t know yet” can be useful

Usually, we do not have all the information these examples give us. We have an automatic reply, a new schedule, or someone saying, “We considered everyone’s circumstances.”

At that point, do not turn suspicion straight into a finding. Ask: who looked at this field later? How was it used in scheduling? Was there a way to review the arrangement or swap shifts, and was it actually used this time? A procedure’s existence on paper does not prove that anyone followed it. Not having seen it happen does not prove that nobody did.

A remainder is not simply something we do not yet know. Lin knows her availability perfectly well, but the scheduler may still leave it out. Conversely, the scheduler may have used it even though we have not yet obtained the records. Whether information entered the process and whether we have established what happened are two different questions.

Sometimes the purpose was never made clear; sometimes records are still missing. If the evidence is not enough to decide, write “not yet established” and say what is missing. Calling something a remainder is a finding that needs support, not a way to give a name to whatever we do not know.

7. A small note is enough

By now, the word remainder should be doing more than giving “ignored” a new name. It brings the unused scheduling comment and the distinction lost in the practice log under one question: what specific thing mattered to this task’s purpose but was left out of carrying it out? The causes can differ. We do not have to begin by guessing whether someone deliberately brushed us off.

Next time someone says, “We’ve recorded it,” take a piece of paper and make that question specific.

1. Which task are we talking about? Note its purpose, the people or things involved, the rules used to handle it, and the particular round or day you are checking.
2. Which difference am I asking about? For example, whether Lin can or cannot work on Wednesday evening. Don’t just write “my whole situation,” and don’t switch purposes mid-check to get the conclusion you want.
3. Why does this difference matter? If it were different, what would need to change in the arrangements for the same purpose? If it is irrelevant, its absence from the record is not grounds for calling it an omission.
4. Where did it go next? Find records, discussions, checks or reviews that were actually used. Check whether another route brought the information back into this particular process. Don’t rely only on whether the answer was yes or no.
5. What can we say so far? Where the evidence supports it, write “a remainder for this task,” “taken into the process,” or “not relevant to this task.” If you cannot decide yet, name the specific evidence still missing. New evidence may justify a different finding.

You do not need to fill the page with remainders for it to be useful. Confirming that a particular item was taken into account is a finding too. Whether anything should change next, how to change it, and who should bear the cost require further judgment. Finding a missing connection does not create time, staff or money.

Lin need not first prove that the whole shop is indifferent to people. The scheduler cannot answer her merely by handing back the archived file. They can now begin with one clear question: how, exactly, was her Wednesday availability used in this round of scheduling? When we can say which item, in relation to which task, and on what evidence, remainder stops being an abstract-sounding word and becomes something we can actually investigate.

We’ve received your feedback. That can be the beginning of something. If there is a next step, the word “received” will not take it for us.

Methodology Series · Han Qin (秦汉) · 2026