How do I decide whether to redo work after a requirement was missed?
Quick answer
Compare the missed requirement with the work’s intended outcome, then assess what happens if you leave it as is. Consider who or what is affected, whether a smaller revision would resolve the gap, and the time or disruption each option involves. If the consequences are unclear, summarize the gap neutrally and ask the relevant decision-maker what outcome matters most before redoing the work.
The question, the details, the next step.
I noticed that a piece of work missed one of the requirements. How can I decide whether it needs to be redone?
Start by separating the requirement from the result. Write down what was requested, what the work currently does, and what the intended outcome was. Then ask: does the gap prevent that outcome, create a meaningful problem for someone using the work, or make the work unsuitable for its next step? If yes, correction is more likely to be worthwhile. If the outcome is still met, the requirement may be optional, superseded, or open to interpretation—but confirm that rather than assuming.
Next, compare the available options: redo the whole item, make a targeted revision, or accept the current version. Include the effort and disruption of each option, not just the effort of fixing it. If you do not have authority to choose, present the options and ask the person responsible for the decision. The aim is to resolve the gap, not assign blame.
What should I compare so I don't treat every missed detail as equally important?
Use a small set of questions. First, is the requirement clear and still applicable? Second, what specific difference does the omission make to the intended outcome or the next person who will use the work? Third, can a limited change close the gap, or would the underlying approach need to change? Finally, what would each option cost in time, coordination, or disruption?
A requirement can be important even if the visible difference seems small—for example, when another person depends on that detail. Conversely, a noticeable difference might not justify redoing everything if a focused edit solves it. Keep observed facts separate from assumptions: “The requested heading is absent” is an observation; “the reader will be confused” is a possible consequence to check.
Can you give me a simple decision table for redo, revise, or accept?
Use this as a discussion aid, not an automatic rule:
Option: Redo Consider it when: The gap changes the core outcome or a targeted edit cannot make the work fit its intended use. Check first: What specifically must change, and who agrees that a full redo is needed?
Option: Revise Consider it when: The main outcome is sound, but a defined change would satisfy the requirement or improve the work’s usefulness. Check first: Can you name the smallest change that closes the gap and agree on how to confirm it?
Option: Accept as is Consider it when: The requirement is no longer applicable, the outcome is still suitable, or correction would create more disruption than value. Check first: Who can accept the deviation, and should the reason be recorded?
If you cannot tell which row fits, pause before starting extensive rework. Ask for a decision using the same description of the gap and consequences for every option.
How do I raise it neutrally, and what would a worked example look like?
Describe the request and the current state without naming a person as the problem. For example, assuming a draft was meant to include a short summary but does not: “The brief asks for a short summary at the beginning. The current draft starts with the detail section. The main content is present; I’m not sure whether the missing summary affects the intended use. I can add the summary, revise the opening another way, or leave the draft as is. Which outcome should I prioritize, and is there a preferred deadline?”
That message states an observable gap, distinguishes what is known from what is uncertain, and offers choices. Replace the example details with the actual requirement and impact; do not claim the outcome is unaffected unless you have checked. If a deadline or downstream dependency changes the choice, include it as a fact or label it as an assumption. Record the decision and the agreed next step so the same question does not need to be reopened.
A practical checklist
Quote or paraphrase the specific requirement and confirm it still applies.
Describe the current work and the gap using observable details.
State the intended outcome and any likely consequences, separating facts from assumptions.
Compare full redo, targeted revision, and acceptance, including effort and disruption.
Ask the person with decision authority to choose when the impact or acceptable deviation is unclear.
Record the decision, owner, and next step.
A few more useful answers
Should I start redoing the work while I wait for a decision?
Avoid extensive rework if the choice could change what needs to be done. If useful, prepare a small, reversible correction or outline the options, then confirm the priority before investing more effort.
What if the requirement was vague or changed after the work began?
Note the wording or change and when it became clear, then ask which version should govern the work. Treat the mismatch as a clarification issue rather than assuming someone acted carelessly.
What if I think the work is acceptable but someone else wants it redone?
Ask what outcome or concern makes a redo necessary, then clarify the scope and acceptance criteria. You can share the consequences of each option without presenting your preference as the only reasonable choice.