Situational Writing Task Fulfilment | Complete Every Requirement, Preserve Every Constraint and Finish the Communication Job

A strong situational-writing response is not merely a piece of fluent English. It is a completed communication job. Every instruction must be present, accurate, developed to the necessary depth, and made useful to the reader. This guide builds a transferable system for doing exactly that across emails, letters, reports, speeches, articles, proposals, notices and other constrained writing tasks.

1. Task fulfilment is the difference between writing and completing the job

In open writing, a writer can decide what matters most and shape the piece around personal priorities. Situational writing is different. The examination has already assigned a communication problem. The writer must solve it. That means a response can sound mature, contain accurate grammar and even be pleasant to read while still underperforming because one or more required jobs were not fully completed.

Task fulfilment is therefore the discipline of converting instructions into completed communicative outcomes. It asks four questions about every requirement: Is it present? Is it accurate? Is it developed enough to count? Does it perform the function the task requires? These questions create a practical four-level model:

• Presence: the required point appears.
• Accuracy: it preserves the facts, limits, conditions and relationships of the task.
• Development: it contains enough explanation, detail or reasoning to be meaningful rather than merely mentioned.
• Function: it helps the reader understand, decide, act, respond or evaluate in the way the task demands.

A useful shorthand is P-A-D-F: Presence → Accuracy → Development → Function. A point that fails at an earlier level cannot be rescued by polish at a later one. Elegant phrasing cannot compensate for a missing requirement. Detailed elaboration cannot compensate for distorted information. A complete response protects all four levels.

2. Task fulfilment begins where task decoding ends

The previous stage of the system converts the prompt into an executable model: role, audience, purpose, context, deliverable and constraints. Task fulfilment takes that model and asks a narrower question: Have I actually done every job that the model requires?

This distinction matters. Decoding identifies the obligations. Fulfilment closes them. Source transformation decides how stimulus information can be used accurately and purposefully. Fulfilment checks whether the required information has made it into the response in a complete form. Audience and register, information architecture, format transfer, language control and timing all affect quality, but task fulfilment owns the completion problem itself.

Think of the task as a set of open loops. A loop might be “explain why the event is being organised”, “compare the two options”, “recommend one option”, “state the deadline”, “tell readers how to respond”, or “describe two likely benefits”. The response is complete only when every required loop has been closed.

3. Build a requirement inventory before drafting

A requirement inventory is a short list of the communication jobs the response must complete. It is deliberately more precise than a loose set of ideas. “Write about the school fair” is not an inventory item. “Explain the purpose of the fair”, “state the date and venue”, “describe two activities”, “persuade students to volunteer”, and “tell them how to sign up” are.

A good inventory separates content requirements from constraint requirements. Content requirements tell you what must be communicated. Constraints tell you what must remain true while you communicate it. A task may require three reasons, a choice between two options, a deadline, a respectful tone, use of supplied evidence, no invention beyond the source, and a particular relationship between writer and reader. Some of these are visible as content; others control whether the content is valid.

Maren uses a simple margin code when the task is dense. She marks each required job R1, R2, R3 and so on. She then writes a tiny completion test beside it. For example: R3 recommend venue — must name one venue + give grounds + show fit with event needs. The code is not a rigid formula. Its purpose is to prevent an instruction from disappearing once drafting begins.

4. Explicit requirements and implied obligations

Some tasks are explicit. They say “give two reasons”, “compare the options”, “state which you prefer”, or “explain how students can participate”. These should become direct inventory items. Other obligations are implied by the communication job. If the reader must choose whether to attend, the response may need enough practical information to make attendance possible. If the writer is requesting permission, a bare request may be incomplete without sufficient grounds for the reader to decide responsibly.

Implied does not mean invented. It means logically required by the stated purpose. The safest test is: Could the reader complete the expected next action using only what I have written and the information legitimately available in the task? If not, the response may still contain an open loop.

Iona is careful here because implied obligations are easy to confuse with imagined facts. She distinguishes between communication completion and content invention. If a task asks her to invite classmates to a workshop and provides the date, venue and registration link, she should deploy those details. She should not invent a fee, guest speaker or dress code merely because real invitations sometimes contain them.

5. Compound instructions must be split before they can be completed

A frequent source of lost marks is the compound instruction: “Describe the problem and explain how your proposal would solve it.” A student may produce an excellent description and only a vague solution, or a strong proposal with almost no explanation of the original problem. The sentence looks like one instruction but contains at least two scoring obligations.

Split compound instructions at the verb level. Describe + explain. Compare + recommend. Inform + persuade. Summarise + evaluate. State + justify. Each verb creates a different completion condition. The response should make it possible for a marker—or any careful reader—to point to where each job is done.

A particularly dangerous form is the instruction with an embedded condition: “Recommend one activity, explaining why it is suitable for younger students.” Naming an activity completes only the first half. The second half requires suitability to be demonstrated against the stated audience. “It is fun” may not be enough. “It uses simple equipment, can be completed in short turns and does not require prior experience” makes the suitability test visible.

6. Preserve quantities exactly

Quantities are small words with large consequences. If a task asks for two benefits, one well-developed benefit does not satisfy the whole requirement. If it asks for one recommendation, presenting three competing recommendations can weaken decisiveness. If it asks for at least two examples, the response needs to cross the minimum threshold.

Students often remember the topic while forgetting the count. To prevent this, turn quantities into visible completion markers: R2a and R2b, Reason 1 and Reason 2, Option A and Option B. The numbering is for planning, not necessarily for final prose. Its purpose is to stop the mind from compressing plural requirements into a single general statement.

Quantities can also be relational. “Compare the two proposals” does not merely require mentioning Proposal A and Proposal B. It requires a relationship between them. A complete comparison normally establishes at least one shared criterion and shows how the options differ on that criterion. Two disconnected summaries can leave the comparison obligation open.

7. Conditions, exceptions and boundaries are part of the requirement

A task may contain information such as “available only on weekdays”, “for students aged thirteen and above”, “unless the weather is severe”, “subject to approval”, “registration closes once places are filled”, or “participants must bring their own equipment”. These are not decorative details. They define where a statement remains true.

Removing a condition can turn accurate information into a false promise. “The hall is available” is not equivalent to “the hall is available on weekdays after 4 p.m.” “All students may join” is not equivalent to “students aged thirteen and above may join”. Task fulfilment therefore includes constraint preservation: the response must retain material limits when those limits affect the reader’s decision or action.

A useful check is to circle high-risk boundary words in the prompt or source: only, except, unless, before, after, at least, no more than, if, provided that, subject to, while places last. These words often carry more task value than longer descriptive passages because losing them changes what the message authorises the reader to believe.

8. Deadlines and action windows must remain operational

When a task involves registration, submission, attendance, booking, voting, volunteering, payment, collection or another action, time information often becomes part of task fulfilment. A date without an action can be incomplete; an action without a date can be unusable. “Please sign up soon” is weaker than “Please submit the form by 18 March so that teams can be confirmed before the briefing.”

Time information should be handled with the same fidelity as other evidence. If registration opens on Monday and closes on Friday, do not collapse the window into a vague “this week” if precision matters. If a task distinguishes event date from registration deadline, preserve both. If the source says “applications may close earlier when all places are filled”, the exception may need to travel with the deadline because it changes the reader’s risk.

9. Reader action is often the real completion test

Many situational-writing tasks end in an action: attend, register, approve, choose, donate, submit, reply, volunteer, consider, vote, adopt, investigate or change a practice. A response may contain all the background facts yet still stop short of enabling the action. Task fulfilment is stronger when the writer identifies the reader’s next move and makes it executable.

Leonie calls this the handoff test: when the message ends, what can the reader do next? If the answer is unclear, she checks whether a required instruction, deadline, location, contact route, decision criterion or request has been omitted. The handoff test is especially useful under time pressure because it converts a vague “Does this feel complete?” into a concrete operational question.

Reader action should not become mechanical. A report may end not with a direct command but with a decision-ready recommendation. A complaint may ask for investigation and response. A proposal may define the approval needed. A speech may aim for commitment rather than a form submission. Function changes by task, but completion still requires the reader to know what the communication is trying to make possible.

10. Mentioning a point is not the same as fulfilling it

One of the most common weak habits is the tick-box mention: a required idea appears in the script, but so briefly that it does not perform its job. “The library is convenient” mentions convenience. It does not explain why the library is the better meeting venue. “The new system will help students” names a benefit. It does not show how. “I recommend Option B because it is better” completes almost nothing beyond the existence of a preference.

The solution is not to make every point long. It is to identify the minimum complete unit for the requirement. A reason usually needs a claim plus a relevant ground. An explanation usually needs information plus meaning or consequence. A recommendation usually needs a choice plus grounds that connect the choice to task criteria. A comparison needs both sides connected through a shared dimension. A request needs the desired action and, when necessary, enough context or justification for the reader to respond.

11. Sufficient development is requirement-specific

Students often ask, “How many sentences should I write for each point?” The better question is, “What does this particular requirement need before it is complete?” Sentence count is only an indirect measure. Some factual requirements may be satisfied accurately in one sentence. A recommendation may need several sentences because the reader must see the decision, evidence, fit and practical consequence.

Development should therefore be calibrated by function. If the task says state, precision may matter more than expansion. If it says explain, the response must move beyond naming to show why or how. If it says justify, a reason must connect to the decision. If it says evaluate, the writing normally needs criteria, evidence and judgement. If it says persuade, reader-relevant reasons matter more than raw description.

This is the boundary between Task Fulfilment and the later Development and Elaboration system. Here, development is treated only as the amount of material needed to close a required job. The broader craft of making ideas richer, more vivid or more intellectually layered belongs elsewhere.

12. Comparison is a relational obligation

Suppose a task provides two venues. Venue A is cheaper and near public transport. Venue B is larger and has better equipment. A weak response describes each venue separately and then declares a preference. A fulfilled comparison asks what matters for this event and makes the relationship visible: cost, accessibility, capacity, equipment, supervision, timing or another relevant criterion.

A simple completion pattern is: criterion → Option A → Option B → implication. “Although Hall A costs less and is easier to reach, Hall B can accommodate the expected audience and already has the sound equipment required for the performances. For this event, capacity and technical readiness matter more than the saving in rental cost.” Now the comparison does decision work.

13. Recommendation is a decision obligation

A recommendation is not simply an opinion sentence. It usually has at least three completion layers: choice, grounds and fit. The response should identify what is recommended, explain why, and show why those reasons matter for the particular purpose, audience or constraints of the task.

When constraints matter, add a fourth layer: qualification. “I recommend the outdoor courtyard because it can hold the larger audience and creates a more visible event, provided that the wet-weather hall is reserved as a backup.” The qualification does not weaken the recommendation. It demonstrates that the decision remains valid under the real conditions of the task.

14. Explanation is a meaning obligation

An explanation completes the movement from information to significance. If the source says the new reading programme runs for twenty minutes each morning, repeating that fact is not an explanation of why the programme may help. The response needs the bridge: regular short practice gives students repeated exposure to texts, builds routine and reduces the dependence on occasional long sessions.

Do not confuse explanation with unsupported certainty. If the source permits only a likely effect, preserve that level of confidence. “This may make participation easier” can be more accurate than “This will solve the problem.” Task fulfilment includes completing the explanatory job without overstating what the evidence supports.

15. Justification links a decision to reasons that matter

Justification is stronger than adding the word “because”. The reason must actually support the decision under the task’s criteria. “Choose the museum because it is interesting” may be true but weak. “Choose the museum because its guided programme directly supports the history project, it can accommodate the full cohort, and the weekday school rate keeps the trip within budget” makes the grounds visible and relevant.

A good justification passes a substitution test. If the reason could be attached equally well to every option, it may not explain the choice. “It will be enjoyable” often fails this test. “It is the only option that can host all eighty participants indoors within the stated budget” does not.

16. A completion matrix turns a long prompt into controllable work

For dense tasks, use a small completion matrix. The columns are: Requirement | Evidence or content | Constraint | Completion test | Status. A planning line might read: “Recommend one venue | Hall B data | acknowledge higher cost | choice + grounds + fit | open.” After drafting the relevant paragraph, the status becomes closed only if the whole completion test is visible.

The matrix is especially useful for students who produce long scripts but lose marks through omissions. It separates length from completion. A 700-word response can still contain open requirements. A shorter, tightly controlled response can sometimes fulfil the communication job more successfully because every sentence has a clear task function.

17. The requirement graph: some obligations depend on others

Not every requirement is independent. A recommendation may depend on a comparison. A request may depend on an explanation of the problem. A conclusion may depend on evidence established earlier. These relationships create a requirement graph: one completed job provides the basis for another.

If the graph is ignored, the response can feel logically hollow. For example, a writer may recommend extending library hours before explaining the access problem that makes the recommendation necessary. The individual sentences may all be relevant, but the decision lacks visible support at the point where the reader needs it. Information architecture will later refine ordering, but task fulfilment must first ensure that dependent requirements have the material needed to function.

18. Completion states: open, partial, closed and verified

Instead of treating every requirement as either done or not done, use four states. Open means nothing has been written. Partial means the requirement appears but one part is missing—for example, a recommendation without justification. Closed means the content requirement has been completed. Verified means it has also been checked against source accuracy, quantities, conditions and the task wording.

This state model improves revision because it directs attention to the real risk. Rewriting already verified material is usually less valuable than closing a partial requirement. Under examination conditions, Leonie prioritises open and partial loops before stylistic polishing.

19. The first weak link is often not language

When a script underperforms, teachers sometimes begin by correcting grammar and vocabulary because those errors are visible. But the first weak link may be earlier: a missed quantity, a condition dropped from a source, a comparison that became two summaries, a recommendation without decision grounds, or a request that never tells the reader what to do.

Diagnosis should therefore begin with task fulfilment before sentence-level editing. Ask: Which required jobs are open? Which are partial? Which were distorted? Which were developed beyond necessity while another requirement was neglected? Once the task structure is secure, language correction becomes more valuable because it improves a response that is already doing the right work.

Next: the system becomes more demanding when several requirements compete for limited time and word space. The following sections build prioritisation, high-pressure completion, worked task types, error diagnosis, deliberate practice and transfer.

20. High-risk omissions are predictable

Not every requirement is equally likely to disappear during drafting. High-risk omissions tend to have one of five features. They are small compared with the main topic; they occur late in the prompt; they are embedded inside a longer sentence; they qualify another instruction rather than appearing as a separate point; or they require the writer to switch function, such as moving from explanation to recommendation.

This is why students sometimes write three strong paragraphs about an event and forget to state how readers can register. The registration instruction may occupy only six words in the prompt, but those six words may be essential to the communication job. Requirement importance cannot be estimated by prompt length.

A practical defence is to identify the small-but-critical items before drafting. Dates, quantities, exceptions, named audiences, deadlines, response routes, choice requirements and conditional clauses belong on this list. They should receive a visible mark in the planning stage and a separate verification mark at the end.

21. Omission and underdevelopment are different failures

An omission is absent. Underdevelopment is present but insufficient. The distinction matters because the repair is different. If the writer never states the deadline, the point must be added. If the writer states a recommendation but gives no task-relevant reason, the point needs development rather than mere insertion.

Teachers can diagnose this rapidly with a two-column review. Column one asks, “Is the requirement visible?” Column two asks, “Is it complete?” A yes/no pattern reveals the failure type. No/No means omission. Yes/No means partial fulfilment. Yes/Yes means the requirement is closed, though it may still require accuracy or language checks.

This prevents inefficient feedback. There is little value in telling a student to “add more detail” when the real problem is that an entire required point is missing. Equally, telling a student to “include the recommendation” is unhelpful if a recommendation is already present but unsupported.

22. Overdevelopment can create under-fulfilment elsewhere

A response has limited time and limited attention. Spending too much of both on one requirement can starve later requirements. This is a common pattern among capable writers: the first body paragraph becomes excellent, detailed and polished; the final required point is then rushed into one sentence because time has almost expired.

Task fulfilment therefore includes development control. The writer should stop expanding a point once it has done its job unless additional depth contributes materially to the overall purpose. A point that is already accurate, adequately supported and functional does not automatically deserve another example, adjective or explanation.

Leonie uses a simple question: “What requirement is paying for this sentence?” If the answer is unclear, she checks whether the sentence is consuming time that a still-open requirement needs more urgently. This does not make writing mechanical. It protects completeness before stylistic enrichment.

23. Balanced depth does not mean equal word count

Students sometimes try to divide a response into equal-sized paragraphs because symmetry feels safe. But requirements rarely demand equal space. “State the venue” may need a phrase. “Explain why this venue is suitable for a three-day exhibition” may need a developed paragraph. “Tell participants where to register” may need one precise sentence.

A better principle is proportional completion: allocate words according to the work each requirement must perform. The result may look uneven on the page but be far more balanced as communication. This is especially important when a task combines logistical facts with evaluation or persuasion.

24. Opening and closing obligations can also be task requirements

An opening should not be treated as decorative ceremony. In many tasks it must establish enough context for the reader to understand why the message exists. A closing may need to secure a response, state a final recommendation, reinforce a call to action or clarify what happens next. These functions can be part of task fulfilment even when the prompt does not label them “opening” and “closing”.

The completion test remains functional. Does the opening orient the reader without wasting space? Does the closing finish the communication job rather than merely repeat earlier sentences? A formal sign-off cannot compensate for an unresolved request. A motivational final line cannot compensate for a missing registration route.

25. Dense source material increases fulfilment risk

When the task includes a poster, schedule, email thread, chart, table, notes or several short texts, students often focus so heavily on extracting information that they lose sight of the actual requirements. The presence of many source details can create an illusion of productivity: the script contains numerous facts, yet the required comparison, recommendation or explanation remains incomplete.

The antidote is to keep the requirement inventory separate from the evidence pool. Requirements answer what jobs must be completed? Sources answer what information is available to complete them? A source point has no automatic right to enter the response. It earns a place by serving a requirement or the overall communicative function.

Iona draws an arrow from each selected source detail to the requirement it supports. Unlinked details are treated cautiously. This reduces both omission and source dumping because evidence remains subordinate to the communication job.

26. Incomplete evidence requires calibrated completion

Sometimes the supplied material does not provide every detail a real-world writer might want. A proposal may include cost and capacity but not travel time. A complaint may identify repeated delays but not their precise cause. A notice may announce a programme without explaining why one date was chosen.

Task fulfilment does not permit the writer to fill these gaps with convenient inventions. Instead, complete the requirement using the strongest legitimate material available and calibrate claims to the evidence. “The larger room appears more suitable because it can accommodate the expected attendance” is safer than inventing an unprovided claim that it also has superior lighting.

If the task genuinely requires a decision under uncertainty, the response can acknowledge the missing information and make a conditional recommendation. This is often more mature than pretending certainty. “On the information provided, Venue B is the stronger choice because of capacity; transport arrangements should be confirmed before the booking is finalised.”

27. Conflicting requirements need prioritisation, not panic

A demanding task may contain tensions. The writer may need to be concise but give enough reasoning. The audience may want low cost while the event requires high capacity. A proposal may need to sound confident while acknowledging a risk. These are not necessarily contradictions. They are constraints that require prioritised completion.

Use the task hierarchy. First protect explicit instructions and factual accuracy. Next protect the main purpose. Then optimise secondary goals such as elegance, nuance or extra detail. If two desirable qualities conflict, choose the one more directly tied to the stated communication job.

Maren frames this as must, should, could. A must is required for validity: answer all required points, preserve conditions, make the decision, give the requested reasons. A should improves effectiveness: make transitions clear, tailor examples, sharpen emphasis. A could is optional enrichment. Under time pressure, never sacrifice a must for a could.

28. Negative instructions are easy to lose

Prompts sometimes tell writers what not to do: do not reveal a confidential detail, do not confirm the booking yet, avoid promising a refund, exclude one unavailable option, or write without naming a particular individual. Negative constraints are cognitively fragile because the draft is built mainly from positive content.

Mark negative instructions with a separate symbol during planning. Then verify them at the end. A response can fulfil every positive requirement and still fail the task by violating one prohibition. In real communication, this is obvious: a confidential memo that includes the forbidden detail is not successful merely because everything else is accurate.

29. Conditional branches must remain conditional

Some tasks contain branch logic: if the event is outdoors, explain the wet-weather plan; if a student cannot attend the first session, tell them how to join later; if the proposal is approved, outline the next step. The response should not flatten these branches into universal claims.

A simple branch model is condition → action → consequence. “If the outdoor court is unavailable because of rain, participants will move to the hall; the programme will begin at the same time.” The condition stays attached to the action. This protects both factual accuracy and reader usability.

30. Multiple audiences create layered fulfilment

A communication can have more than one audience. A speech may be delivered to students but also heard by teachers. A report may be written for a committee whose decision affects a wider community. An article may address readers directly while representing an organisation. Task fulfilment should identify whose action or understanding each requirement is meant to change.

This does not mean writing separate mini-messages to every possible reader. It means avoiding completion that works for one audience but leaves the primary decision-maker unable to act. If the committee needs cost justification, a student-centred description of how enjoyable the programme will be may not be enough. The required job is completed only when the relevant reader receives decision-useful information.

31. Compound purposes create layered completion tests

Many tasks combine purposes: inform and persuade; explain and recommend; complain and request action; report and evaluate; invite and reassure. These combinations should be visible in the requirement inventory. Otherwise one purpose can dominate the script while the other survives only in a token sentence.

For an “inform + persuade” task, ask two separate questions. Does the reader have the information needed to understand the event? Does the response give reader-relevant reasons to participate? For “complain + request action”, ask whether the problem is documented accurately and whether the requested remedy is explicit and proportionate.

32. The mid-draft check protects the second half of the task

A final check is valuable, but waiting until the end can be too late if three requirements remain open and only two minutes remain. A mid-draft check takes a few seconds. At roughly the halfway point, scan the requirement inventory and ask: Which items are closed? Which remain open? Has one section expanded beyond its budget?

This check is especially useful for students who write fluently. Fluency can create momentum that carries the writer away from the task. A short interruption restores executive control. Leonie treats it like checking a route during a journey: not because the destination has changed, but because small deviations are easier to correct early.

33. End-of-script verification should follow risk, not reading order

Many students reread from the first word to the last and hope errors will reveal themselves. A more reliable fulfilment check begins with the inventory, not the prose. Verify the highest-risk requirements first: quantities, choice, conditions, deadline, requested action, required reasons, exceptions and any late prompt item that was easy to overlook.

Only after requirement verification should the writer move to sentence-level proofreading. This order is rational because a missing task requirement usually cannot be repaired by correcting punctuation. Completion errors are structural; language errors are local. Check structural validity first.

34. Recovery when a missing requirement is discovered

Discovering an omission late is not a reason to panic. Use a recovery sequence: identify → locate → insert → reconnect → verify. Identify exactly what is missing. Locate the most natural place for it. Insert the minimum complete unit. Reconnect the surrounding sentences if necessary. Verify that the new material preserves accuracy and does not create contradiction.

The key is minimum complete repair. If the missing requirement is “state how to register”, the writer may need only one precise sentence. Rewriting an entire paragraph wastes time and creates new error opportunities. Recovery is a controlled patch, not a restart.

35. Compression rules when time is running out

When time becomes scarce, protect completion in this order: required decision or action; missing required content; quantities and conditions; necessary reasoning; then stylistic refinement. Compress wording before deleting obligations. A short complete sentence is preferable to an elegant unfinished paragraph.

Three compression moves are particularly safe. First, combine fact and consequence: “The venue is beside the station, so participants can reach it without arranging additional transport.” Second, combine comparison and recommendation: “Although Hall A is cheaper, Hall B is the better choice because it is the only venue large enough for the expected audience.” Third, remove redundant framing while keeping the requirement itself.

Do not compress away qualifiers. “Only”, “if”, “before”, “up to”, “at least” and similar words may be essential to accuracy. The goal is economical completion, not careless shortening.

36. A task-fulfilment error taxonomy

A useful error taxonomy makes repeated weaknesses visible. The main categories are:

• Omission: a required job is absent.
• Partial completion: the job appears but one component is missing.
• Distortion: the requirement is addressed using inaccurate or altered information.
• Constraint loss: a limit, condition, quantity or exception disappears.
• Function failure: the content is present but does not enable the intended reader response.
• Misallocation: excessive space is given to one requirement while another is starved.
• Purpose imbalance: one part of a compound purpose dominates.
• Premature closure: the writer believes a point is complete because it has been mentioned.
• Contradictory completion: separate parts of the response satisfy different instructions in mutually inconsistent ways.
• Decorative drift: interesting but non-required material consumes the budget needed for task obligations.

Students should track which category recurs. Improvement becomes faster when “I am bad at situational writing” is replaced by a precise statement such as “I often lose conditions when transforming source points” or “my recommendations are present but under-justified”.

37. Failure autopsy 1: the beautiful incomplete email

A student writes an engaging email inviting peers to a community event. The tone is warm, the vocabulary controlled and the event activities are described vividly. The task also requires the writer to explain why volunteers are needed, give the reporting time and tell interested students how to sign up. The response mentions that “help would be appreciated” but never explains the need, gives the event start time rather than the volunteer reporting time, and ends with “Hope to see you there!” without a registration route.

The script feels successful because it sounds like an email. Functionally, however, three loops remain open. The repair is not “use better language”. It is: explain the volunteer role, distinguish reporting time from public start time, and make the sign-up action executable.

38. Failure autopsy 2: the report that describes but never evaluates

A report compares two after-school programmes. It accurately summarises their schedules, fees and activities. The task asks the writer to recommend which programme should receive school support. The response ends after the summaries. No criteria are prioritised and no recommendation is made.

This is a classic function failure. The source handling may be excellent, but the communication job is unfinished. To close it, the writer must convert description into judgement: identify what matters for the school’s purpose, compare the options against those criteria and state the recommendation.

39. Failure autopsy 3: the speech with the missing condition

A speech encourages students to join a weekend activity and correctly states that transport will be provided. The source says transport is provided only for participants who register by Wednesday. The response drops the condition and tells the audience that “transport is provided for everyone”.

The required point is present but inaccurate because constraint preservation failed. The safest repair keeps the benefit and its boundary together: “Transport will be provided for students who register by Wednesday, so sign up early if you need a seat on the bus.”

40. Failure autopsy 4: the proposal with one giant reason

A proposal asks for three reasons why a peer-support programme should be introduced. The writer develops one reason—improved student confidence—over three paragraphs and then adds two short fragments near the end: “It also builds friendship. It may improve school spirit.” All three themes are present, but only one is meaningfully fulfilled.

The repair is proportional completion. Each required reason needs enough explanation to establish its relevance. The first reason can be shortened; the recovered space can then be used to explain how peer contact builds connection and how visible cross-level support contributes to school belonging.

41. Failure autopsy 5: the complaint without a remedy

A complaint describes a recurring problem in detail: dates, effects, previous attempts to resolve it and the inconvenience caused. The task asks the writer to request a practical response. The letter ends with “I hope you will take this matter seriously.”

The reader understands the problem but does not know what resolution is being sought. A complete version might request investigation, a repair, clarification, replacement, revised procedure or written response, depending on the facts supplied. Complaining is not the same as completing the requested communication job.

42. Worked email: invitation, explanation and action

Consider a task in which a student leader must email classmates about a weekend book-donation drive. The source material gives the collection date, two accepted categories of books, a drop-off location, a reason the partner organisation needs the books, and a volunteer briefing time. The task asks the writer to explain the drive, encourage classmates to donate and invite some of them to volunteer.

The requirement inventory might be: R1 explain the purpose of the drive; R2 state what books are accepted; R3 give collection logistics; R4 persuade classmates to donate; R5 invite volunteers; R6 state the briefing time; R7 explain how to respond. Notice that the source contains information, while the inventory contains jobs. They are related but not identical.

A weak draft might say: “We are collecting books for children. Please bring storybooks and textbooks to the foyer on Saturday. It will be a meaningful activity and we hope many of you can help.” Several facts appear, but the volunteer role is underdeveloped, the briefing time is missing, and the response route is absent. The word “meaningful” also does little persuasive work because it is not connected to the actual need.

A more complete version would make the jobs visible: “The books will go to a community reading programme that is expanding its small library, so donations can be used directly by younger readers. Please bring children’s storybooks or current school textbooks to the main foyer this Saturday between 9 a.m. and noon. We also need volunteers to sort the books by age group and help prepare the boxes for collection. If you can volunteer, reply by Thursday; the short briefing begins at 8.30 a.m. on Saturday.”

The improvement is not mainly stylistic. The message now completes the purpose, accepted items, logistics, reason, volunteer role, response route and briefing time. It gives the reader enough information to donate or volunteer. The communication job closes.

43. Worked report: evidence, evaluation and recommendation

Imagine a report comparing two spaces for a student exhibition. Room A costs less and is beside the main entrance but holds only sixty people. Room B costs more, holds one hundred and twenty people, has built-in display panels and can be secured overnight. Expected attendance is around ninety, and artworks must remain in place for two days. The task asks the writer to compare the rooms and recommend one.

The minimum comparison obligation is not “mention both rooms”. The writer must connect them through criteria relevant to the exhibition. Capacity is decisive because expected attendance exceeds Room A’s limit. Overnight security matters because work remains installed. Display equipment affects setup. Cost matters, but it cannot be treated in isolation.

A fulfilled recommendation might read: “Room A is the cheaper option and would make the exhibition highly visible to people entering the building. However, its sixty-person capacity is below the expected attendance of about ninety, and the room cannot be secured overnight. Room B costs more, but it can hold the full audience, includes display panels and can remain locked while the work stays in place. I therefore recommend Room B. The additional cost buys the capacity and security the two-day exhibition actually requires.”

The key movement is evidence → criterion → judgement. The response does not dump all available facts. It selects the facts that complete the requested comparison and recommendation. The recommendation is not simply appended at the end; it emerges from the criteria already established.

44. Worked speech: inform, motivate and qualify

A speech task asks a student representative to encourage peers to join a one-day environmental project. The source states that participants will work in teams, training is provided, lunch is included, transport is available only to students who register before a stated deadline, and places are limited. The speech must explain the project, address a likely concern and persuade students to take part.

A superficial speech may sound energetic but fail to close the concern. “It will be fun, and everyone should come!” does not explain what inexperienced students should expect. A stronger completion unit directly handles the objection: “You do not need previous experience. The organisers begin with a short safety and task briefing, and each group works with a trained supervisor.”

The transport condition must travel intact: “Transport is available to students who register by Tuesday, so submit the form early if you need a seat.” Saying merely “transport is provided” would make the speech more reassuring but less accurate. Task fulfilment values truth under constraints over easy persuasion.

The final call to action should also be executable: “If you want to join us, complete the online form by Tuesday. Places are limited, and the transport list closes at the same time.” The speech now informs, reassures, persuades and hands the audience a clear next step.

45. Worked complaint: document the problem and request proportionate action

A complaint task supplies three dates on which a service failed, the consequences for users, an earlier report that received no response, and a request to write to the responsible organisation. The writer must explain the recurring problem, show its impact and request action.

A common failure is emotional expansion. The student spends many sentences describing frustration while the operational facts remain scattered. Task fulfilment asks instead: What must the reader know to investigate? What impact makes the problem material? What response is being requested?

A complete unit could read: “The service failed on 3, 10 and 17 May, each time during the morning period. On the last two occasions, users were unable to access the booking system for more than forty minutes. I reported the issue after the second failure but did not receive a reply. Please investigate the recurring outage, confirm whether a permanent repair is planned, and advise what users should do if the system fails again.”

The request is specific without inventing a solution. The writer does not demand a refund, replacement or disciplinary action unless the task supports it. Fulfilment is not maximal aggression; it is the accurate completion of the communication job.

46. Worked proposal: problem, mechanism, benefit and approval

A proposal asks a student to recommend a lunchtime peer-help desk. The prompt gives evidence that new students frequently ask for directions, club information and timetable help. It provides an unused desk near the office, a possible volunteer rota and one concern: student volunteers must not give advice on confidential welfare matters.

Several loops must close. The proposal should establish the problem, define what the desk would do, explain how it would operate, show why the arrangement is useful, preserve the boundary around confidential matters, and state what approval or support is needed.

A fulfilled core might say: “The desk would provide practical information such as directions, club contacts and timetable guidance during lunch. Two trained volunteers could staff it each day using a simple rota. Questions involving personal welfare or confidential concerns would be referred directly to the appropriate staff member rather than handled by students. This would give new students a visible first point of contact without asking peer volunteers to perform roles beyond their responsibility. I recommend a four-week trial using the unused desk beside the office, after which usage can be reviewed before the arrangement is made permanent.”

The proposal succeeds because the mechanism and boundary are part of the recommendation. It does not merely assert that peer help is a good idea. It makes the idea operational enough for the reader to approve or reject responsibly.

47. Worked article: inform, interpret and guide the reader

Article tasks can tempt students into free-form composition because the genre feels open. Yet when an examination task specifies content and purpose, task fulfilment remains constrained. Suppose the writer must explain a new school recycling system, address two common mistakes and encourage correct use.

A complete article must do more than sound lively. It should explain the change, tell readers what belongs where, correct the two specified mistakes and give a practical reason to follow the system. A catchy opening may help engagement, but it cannot substitute for any of these obligations.

For example: “The new stations separate paper, drink containers and general waste. The first common mistake is putting food-stained paper into the paper section; contaminated paper belongs with general waste. The second is leaving liquid in bottles and cups. Empty them first so the collection is not rejected. These small steps matter because one badly contaminated bin can make an entire batch harder to recycle.”

The article can then expand its voice and examples, but the specified teaching job is already secure. Task fulfilment gives creativity a stable floor rather than removing creativity.

48. Fulfilment patterns by communication job

Across formats, several recurring jobs have recognisable completion patterns. These are not sentence templates; they are functional checklists.

• Inform: relevant fact + necessary context + usable implication where needed.
• Explain: fact or claim + how/why relationship + consequence or significance.
• Compare: shared criterion + both options + meaningful relationship.
• Recommend: clear choice + relevant grounds + fit with purpose/constraints.
• Justify: decision + evidence/reason + explicit connection.
• Request: desired action + necessary context + realistic response expectation.
• Invite: event/purpose + essential logistics + reason to attend + action route.
• Complain: documented issue + impact + relevant history + requested remedy/action.
• Report: findings + interpretation + decision-relevant conclusion where requested.
• Persuade: desired action/view + reader-relevant grounds + barriers answered where necessary.
• Warn: risk + condition + consequence + safe action.
• Reassure: concern acknowledged + credible evidence/process + bounded assurance.

These patterns help students recognise when a requirement is partial. If a recommendation has choice and grounds but no connection to the task criteria, the missing function becomes easier to see.

49. Format does not determine fulfilment

An email can request, persuade, complain, explain or report. A speech can inform, persuade, reassure or call for action. A report can compare, evaluate or recommend. Therefore task fulfilment should be tracked by communication job rather than by memorised genre alone.

This matters for transfer. A student who learns that “a recommendation needs choice + grounds + fit” can carry that logic into an email, report, proposal or speech. A student who memorises “paragraph three of a report is the recommendation paragraph” may struggle when an unfamiliar format asks for the same function in a different place.

The later Format Transfer guide will handle conventions and genre interfaces in depth. Here the rule is simpler: format shapes how a job is presented; it does not erase the job’s completion conditions.

50. The minimum complete unit drill

This drill trains students to stop both under-writing and over-writing. Give one isolated requirement at a time and ask for the shortest response that genuinely completes it. Examples include: recommend one of two venues using cost and capacity; explain why a deadline matters; invite readers to volunteer and tell them how to respond; warn participants about a weather condition; justify one timetable change.

After each attempt, test four things: Is the required action or claim present? Is the information accurate? Is there enough development to satisfy the command verb? Can the reader use it? Then ask the student to remove any sentence that does not contribute to completion. The exercise develops precision before full-length performance.

51. The omission hunt

Give students a polished but deliberately incomplete response. Hide three or four fulfilment faults inside it: one missing quantity, one dropped condition, one unsupported recommendation and one missing response route. The task is not to rewrite the English. It is to identify which loops are still open.

This is powerful because strong surface language can distract even experienced students. The drill trains them to inspect function beneath fluency. A second round can reverse the challenge: give a plain but complete response and ask students not to “improve” it until they have first proved that every requirement is closed.

52. The constraint-preservation drill

Create ten short source statements containing boundaries: “free for members under sixteen”, “open after 4 p.m. except Fridays”, “up to two guests”, “refunds only before the stated date”, “outdoor activity unless lightning is detected”. Students transform each statement for a new reader without changing its truth conditions.

The teacher then removes one small word—only, except, up to, unless—and asks what changed. Students quickly discover that grammatical size and informational importance are not the same. This drill strengthens both source transformation and task fulfilment without becoming a general paraphrasing lesson.

53. The compound-command split drill

Present instructions such as: “Describe the two options and recommend the one that would best suit younger participants.” Students underline each operative verb and rewrite the instruction as separate completion tests. For example: describe Option A; describe Option B; compare them on suitability; choose one; justify the choice against younger participants’ needs.

Then give a short response that completes only some of the tests. Students label each requirement open, partial, closed or verified. This converts a vague feeling of incompleteness into observable task control.

54. The quantity and scope drill

Use prompts where small quantity words change the task: “one reason”, “two possible benefits”, “at least two concerns”, “the main drawback”, “both options”, “one immediate action and one longer-term action”. Students create inventories before writing anything. The goal is to make count and scope automatic.

A useful variation is to show two apparently similar prompts and ask students to explain why the completion conditions differ. “Give reasons for your choice” is not identical to “give two reasons for your choice”. “Discuss the options” is not identical to “compare both options and recommend one.” Precision in reading produces precision in fulfilment.

55. The functional rewrite drill

Give students sentences that are grammatically correct but functionally weak: “The venue is nice.” “This programme is useful.” “Please consider my request.” “There are many benefits.” “Option A is better.” Their task is to rewrite each line so that it completes a named job using supplied evidence.

For example, if the job is to justify Venue A for a small evening event, “The venue is nice” might become: “Venue A is the more practical choice because its fifty-person capacity matches the expected attendance and its evening rate stays within the stated budget.” The exercise teaches students that task value comes from what a sentence does, not how sophisticated it sounds.

56. Selective redrafting beats whole-script rewriting

When a student has one recurring fulfilment weakness, rewriting an entire script can bury the learning signal. Selective redrafting isolates the failed unit. If the problem is unsupported recommendation, rewrite only the recommendation. If the problem is quantity loss, repair only the section containing the plural requirement. If the problem is the reader handoff, rebuild only the close.

The sequence is: diagnose one failure, state the missing completion condition, redraft the smallest affected unit, compare old and new versions, then transfer the same skill to a fresh prompt. This creates more deliberate repetitions in less time and makes progress easier to observe.

57. Feedback should identify the open loop

“Needs more detail” is often too vague. Better feedback names the unclosed job: “You chose Venue B but did not connect the capacity evidence to the expected attendance.” “You gave the event date but not the registration deadline.” “You explained the problem but did not state what action you want from the reader.” “You listed both options but did not compare them on a shared criterion.”

Specific feedback gives the learner a repair mechanism. It also separates task fulfilment from language quality. A sentence may be perfectly grammatical and still leave a loop open. Conversely, a response may have some language errors while showing strong completion control. Teachers need both diagnoses, not one blended judgement.

58. A teacher’s diagnostic sequence

Task-fulfilment diagnosis is fastest when teachers inspect work in a fixed order. First compare the response with the requirement inventory. Second identify open and partial loops. Third check quantities, conditions and source accuracy. Fourth inspect whether each completed point performs the requested function. Only then move into organisation, register and language.

This sequence prevents surface errors from hiding structural problems. A teacher may notice a tense mistake in the first line, but if the response never makes the required recommendation, the recommendation failure is more fundamental. The diagnostic order should follow causal depth rather than visual salience.

A practical marking code can remain small: O for omitted, P for partial, C for constraint loss, F for function failure and X for contradiction. The purpose is not to cover a script in symbols. It is to make the first weak link observable so the next practice task can target it.

59. Small-group practice should expose different failure modes

In a small group, three students can learn from one prompt without producing three identical rewrites. Give each learner a different responsibility. One student checks requirement presence. Another checks accuracy and constraints. The third checks development and function. They then compare findings before seeing teacher feedback.

This creates a useful disagreement surface. One student may claim a recommendation is complete because the choice is stated. Another may point out that the reason does not connect to the task criteria. The group must resolve the difference by returning to the completion model rather than relying on taste.

A second round can rotate roles. Over time, students internalise the whole system. The goal is not to make them dependent on checklists forever; it is to turn the checklist into an automatic mental scan that survives when they write alone.

60. Parent support: ask completion questions, not composition questions

Parents can help without becoming substitute teachers. Instead of asking, “Is this good writing?” or rewriting sentences, they can ask functional questions: What exactly did the task ask you to do? Show me where you completed each part. Which instruction was easiest to forget? What does the reader need to do after reading this? Which condition would change the meaning if removed?

These questions preserve student ownership. They also make progress visible even when vocabulary and grammar are still developing. A learner who once missed two requirements but now closes all of them has improved in an important dimension of examination control.

Parents should avoid rewarding length for its own sake. “You wrote a lot” is not the same as “you finished the task”. A shorter response that closes every requirement accurately is often a stronger foundation than a long script filled with attractive but irrelevant detail.

61. A four-band task-fulfilment rubric

A training rubric can make the P-A-D-F model visible without pretending to replace any official examination mark scheme. Use four broad bands:

• Band 1 — Fragile: important requirements are missing, distorted or unsupported; quantities and conditions are unreliable; reader action is often unclear.
• Band 2 — Emerging: most requirements appear, but several are partial, unevenly developed or weakly connected to purpose; constraints may occasionally be lost.
• Band 3 — Secure: all major requirements are completed accurately; development is proportionate; conditions are preserved; the reader can understand and act.
• Band 4 — Independent: completion remains secure under dense sources, unfamiliar formats and time pressure; the writer prioritises intelligently, repairs omissions efficiently and preserves nuance.

The rubric should be used diagnostically. A Band 2 script does not need “Band 4 vocabulary”. It needs the missing completion mechanics that prevent the task from collapsing. Once the structural layer is secure, other performance dimensions can rise with it.

62. Novice progression: make the invisible jobs visible

Novice learners benefit from external structure. They should mark command verbs, number requirements, underline quantities and conditions, and use a visible completion matrix. At this stage, speed matters less than building a reliable representation of what “done” means.

The teacher can simplify source load while keeping task complexity. For example, provide a short prompt with four explicit jobs and only six source points. The learner practises converting each job into a completion test. Once this becomes stable, source density can increase.

The novice milestone is not sophisticated prose. It is the ability to point to every required job and show where it has been completed accurately. That achievement creates the platform for later speed and style.

63. Developing progression: reduce scaffolds without losing completion

Developing learners should begin compressing the visible system. Instead of writing a full matrix, they may use a numbered margin list. Instead of writing long completion tests, they may use shorthand such as “2 benefits + evidence”, “choice + why”, “deadline + route”. The challenge is to become faster without becoming vague.

At this level, introduce mixed task types. One prompt might require informing and persuading; another comparing and recommending; another explaining and requesting action. The learner must identify the changing completion conditions rather than applying one memorised structure to every task.

The developing milestone is reliable transfer across familiar formats. The student should be able to complete a recommendation in an email one day and a report the next without needing to relearn what a recommendation is.

64. Advanced progression: preserve completion under complexity

Advanced learners need harder problems, not more decorative vocabulary. Give them sources containing competing evidence, implicit obligations, multi-part instructions, conditional branches and unequal priorities. Ask them to complete the task while staying concise.

The advanced challenge is judgement. Which condition must be stated because it materially affects the reader? Which source detail can be omitted because it serves no requirement? Which point needs one sentence and which needs a paragraph? Where should uncertainty be preserved rather than resolved artificially?

At this stage, a strong writer is not merely complete. The writer is selectively complete: nothing essential is missing, nothing important is distorted, and unnecessary material does not crowd out the task.

65. Unseen-task transfer begins with verbs, not formats

When students meet an unfamiliar task, the format label can create unnecessary anxiety. They may think, “I have never written this kind of notice” or “I do not know the exact structure of this proposal.” A more stable starting point is to identify the communication verbs: inform, explain, compare, recommend, request, reassure, persuade, evaluate.

Those verbs reveal the completion logic. The format then tells the writer how to package the completed jobs for the reader. This order improves transfer because communication functions recur even when genres change.

Maren tests transfer by hiding the format label and showing only the situation, reader and instructions. Once the student identifies the jobs and completion tests, the format is revealed. This separates genuine task understanding from memorised layout.

66. Transfer challenge set 1: familiar job, unfamiliar wrapper

Take one recommendation problem and move it through several formats. First write it as an email to a teacher. Then convert it into a short report for a committee. Then present the same recommendation as a speech to students. Finally turn it into a proposal summary.

The facts remain largely stable. What changes is the interface: degree of directness, structure, reader cues and placement. The core completion condition—choice + grounds + fit—should survive every version. If it disappears when the format changes, the student has memorised a genre rather than learned the function.

67. Transfer challenge set 2: familiar format, unfamiliar job

Now keep the email format but vary the communication job. Write one email to invite, one to complain, one to recommend, one to request permission and one to explain a procedural change. The layout may remain broadly similar, but the completion tests change sharply.

This drill exposes an important truth: knowing how an email looks is not the same as knowing how to complete an email task. A learner who relies on stock openings and closings but cannot identify the reader’s required decision will remain fragile despite good formatting.

68. Transfer challenge set 3: change one constraint only

Create paired tasks that differ in only one small element. In Task A, transport is available to all participants. In Task B, transport is available only to those who register by Tuesday. In Task A, recommend one option. In Task B, recommend one option but acknowledge a stated drawback. In Task A, write to peers. In Task B, write to a senior decision-maker.

The student should identify exactly what the changed constraint does to completion. This is more powerful than practising completely different prompts because it isolates causal relationships. Small wording changes should produce deliberate changes in the response.

69. The seven-day fulfilment bootcamp

A focused seven-day cycle can repair task-completion weaknesses without requiring seven full essays.

• Day 1: decode ten prompts into requirement inventories. No drafting.
• Day 2: practise quantities, conditions, exceptions and negative instructions.
• Day 3: write twenty minimum complete units for recommendations, explanations, comparisons and requests.
• Day 4: perform omission hunts on polished but incomplete scripts.
• Day 5: complete two short timed responses with a mid-draft check.
• Day 6: perform selective redrafts based on one recurring failure category.
• Day 7: write one full unseen task and conduct a requirement-first final audit.

The purpose is not cramming. It is concentrated signal. Each day isolates one part of the completion system so the student can feel what reliable control looks like before full examination pressure is reintroduced.

70. A thirty-day progression for durable control

A longer programme can be divided into four phases. Week 1: visibility. Number requirements, split compound commands and build completion tests. Week 2: precision. Focus on quantities, conditions, scope and source fidelity. Week 3: function. Practise recommendation, comparison, explanation, request and persuasion units across formats. Week 4: pressure. Add timed tasks, dense sources, recovery and unseen transfer.

Track one or two metrics rather than everything at once. Examples: number of omitted requirements per script, number of lost constraints, number of unsupported decisions, or number of end-stage emergency repairs. A downward trend shows that control is becoming more stable.

At the end of the month, repeat an early task under the same time conditions. The comparison should focus not only on marks or teacher comments but on process: Was the inventory faster? Were fewer loops left open? Did the student need less external prompting? Could they recover from an omission without destabilising the whole response?

71. Mock-paper completion protocol

In full simulations, task fulfilment must operate without pausing the entire writing process. A practical protocol has five checkpoints: decode, inventory, midpoint, closure, verification. Decode the situation. Build the requirement inventory. At the midpoint, scan open loops. Before closing, ensure the final reader action or decision is present. Then verify high-risk constraints before proofreading language.

The protocol should be practised until it feels light. A checklist that consumes excessive time has not yet become a usable examination tool. The aim is not to perform paperwork inside the exam; it is to install a reliable mental control loop.

72. Score stability is more valuable than occasional brilliance

A student may produce one excellent script when the topic is familiar and then collapse on the next task because two requirements were missed. That is not yet stable performance. Task fulfilment should reduce the variance between best and worst attempts.

Measure stability across a run of unseen tasks. Does the student complete all explicit requirements repeatedly? Do conditions survive even when source material becomes dense? Do recommendations remain justified when the topic changes? Does the writer still close the reader’s next action under time pressure?

Stable writers are not error-free. Their errors are smaller and recoverable. They rarely lose the whole communication job because one difficult paragraph consumed too much time or one unfamiliar format caused them to forget what the task required.

73. Independence means the student can generate the checklist mentally

External checklists are scaffolds. The independence goal is a student who can read a new prompt and spontaneously ask: What must I do? How many parts? What conditions matter? What does complete look like? What will the reader need at the end?

A useful independence test removes support in stages. First allow the full matrix. Then allow only margin codes. Then allow only underlining. Finally provide a clean prompt and observe whether the student still produces a complete response. If performance collapses when the scaffold disappears, training is not finished.

74. Independence under interruption and pressure

Real examination performance can be disrupted by uncertainty, a hard source, an awkward phrase or awareness of time passing. A robust system should survive interruption. Practise stopping midway, covering the draft, and reconstructing the remaining open requirements from the inventory. Then resume writing.

Another drill removes two minutes from the expected writing window. The student must preserve task completion by compressing expression rather than deleting obligations. A third drill inserts one intentionally ambiguous source point and asks the student to preserve uncertainty instead of inventing certainty.

These exercises develop recovery without turning task fulfilment into a general time-management programme. The focus remains specific: protect the required communication jobs when conditions deteriorate.

75. Twenty transfer prompts for task fulfilment practice

The following prompts are intentionally brief. They are designed for planning, requirement mapping or minimum-complete-unit practice rather than full essays every time.

1. Email a club adviser to recommend one of two meeting times and justify the choice using attendance data.
2. Write to participants explaining a venue change, including what remains unchanged and what action they must take.
3. Prepare a report comparing two fundraising methods and recommend one under a fixed budget.
4. Address students about a new borrowing system, explain two changes and correct one likely misunderstanding.
5. Write a complaint about repeated delivery delays, document two incidents and request a practical response.
6. Propose a lunchtime activity, explaining how it would operate and one limitation that needs management.
7. Invite families to an event, give essential logistics, explain its purpose and state how to register.
8. Recommend one of two transport options for a trip, considering capacity, cost and a weather condition.
9. Write an article explaining a new recycling procedure and correcting two common mistakes.
10. Report on feedback from two groups and identify one action that should follow.
11. Ask permission to run a trial programme, justify the request and state how success would be reviewed.
12. Explain a timetable change to affected users, including an exception that applies on one day only.
13. Persuade classmates to volunteer, answering one likely concern and giving the sign-up deadline.
14. Write to an organiser about a booking problem, explain the impact and request confirmation of next steps.
15. Compare two venues and recommend one, while acknowledging a meaningful drawback in the chosen option.
16. Write a safety notice explaining a conditional rule: what happens normally and what happens in severe weather.
17. Prepare a speech asking for support for a proposal, using two supplied benefits and one supplied concern.
18. Write a report that distinguishes immediate action from a longer-term recommendation.
19. Explain a new digital process to first-time users, including the action to take if verification fails.
20. Recommend one of two community projects and explain why it better suits the stated target group.

For every prompt, the first task is the same: identify the loops before writing. If the student cannot state the completion conditions, drafting should not begin yet.

76. A task-fulfilment checklist that is short enough to use

Long checklists are useful during training but impractical under pressure. The final compact version can be remembered as six questions:

• All? Have I answered every required part?
• Exact? Are quantities, conditions, names, dates and facts preserved?
• Enough? Is each point developed enough for its command verb?
• Useful? Does the content perform the required function for the reader?
• Balanced? Have I over-written one point while starving another?
• Closed? Can the reader understand, decide or act when the response ends?

If a learner can answer these six questions quickly and accurately, much of the longer system has become internal. The next stage is to make the same completion reliable under increasingly unfamiliar topics, formats and evidence sets.

77. The requirement ledger for complex tasks

When a task becomes unusually dense, a simple list may not be enough. Use a requirement ledger with four columns: job, dependency, evidence, risk. The job states what must be completed. Dependency records what must be established first. Evidence records the source material or reasoning needed. Risk identifies what is easiest to lose: quantity, condition, contrast, qualification, deadline or reader action.

For example, “recommend one activity for younger students” may depend on first identifying the relevant needs of younger participants. Its evidence may include supervision level, duration and equipment. Its risk may be a generic recommendation that never proves suitability. The ledger exposes that danger before drafting.

The ledger is not intended for every routine task. It is a training tool for teaching students how requirements interact. As competence increases, most of the ledger can become mental.

78. Dependency mistakes: when later claims have no foundation

Some responses technically include all requested parts but still feel incomplete because the dependencies are broken. A writer may state a recommendation before identifying the problem it solves, or request funding without showing what the money is for. Every sentence may be relevant, yet the communication logic is weak.

Task fulfilment therefore checks not only whether a job exists but whether it has the information required to function. A conclusion depends on earlier evidence. A request may depend on a documented need. A warning depends on a stated risk or condition. A recommendation depends on criteria or grounds.

Do not turn this into a full organisation lesson. The immediate question is narrower: Can this required job stand up using information already established or contained within the same unit? If not, the loop is not truly closed.

79. Completion under conflicting evidence

Advanced tasks may provide evidence that points in different directions. One venue is cheaper; another is safer. One programme attracts more participants; another produces better long-term outcomes. One source praises a change; another raises a practical concern. The writer is not required to make the evidence artificially consistent.

A complete response acknowledges the conflict, identifies the criterion that matters for the task, and makes a bounded judgement. “Although Option A is cheaper, Option B is the stronger choice for this event because the larger capacity is necessary for the expected audience.” The cost evidence has not been erased. It has been weighed.

This distinction is important because one-sided selection can create pseudo-fulfilment: the recommendation appears complete only because inconvenient evidence was ignored. A stronger writer preserves the tension and still finishes the decision.

80. Completion when the task requires uncertainty

Not every task permits certainty. The source may say a change could increase participation, a new service may reduce waiting time, or a trial suggests one option is more popular. If the writer turns these into definite guarantees, the requirement is no longer accurate even if it sounds decisive.

Use calibrated language that completes the job without exceeding the evidence: likely, may, appears, suggests, is expected to, would probably, on the information available. A recommendation can remain strong while acknowledging uncertainty: “On the available evidence, Option B is the safer recommendation because it meets the capacity requirement and has already been tested with a similar group.”

Task fulfilment is not the elimination of ambiguity. It is accurate communication despite ambiguity.

81. Numerical information: preserve denominator, scale and direction

Numbers often look objective, but they are easy to distort. “Thirty students preferred Option A” means something different if thirty students were surveyed than if three hundred were. A rise from 20 to 30 is an increase of ten units and a fifty per cent increase relative to the starting value; those are not interchangeable descriptions. A figure for one month should not be described as a yearly pattern without evidence.

For task fulfilment, preserve three things when numbers matter: denominator, scale and direction. Who or what does the number refer to? What unit or timeframe does it use? Is the change an increase, decrease, proportion, difference or total?

Iona treats any numerical statement that supports a recommendation as high-risk evidence. If the number is wrong, the recommendation may still be present but no longer valid.

82. Procedures: sequence is part of completion

When the task asks the writer to explain a process, order can become a requirement. Registration may need to happen before payment. Approval may be required before equipment is collected. Participants may have to report to one location before moving to another. Reversing the sequence can make a factually accurate set of steps unusable.

A procedure is complete when the reader knows what to do, in what order, under what conditions and what happens after key branches. “Submit the form, wait for confirmation, then make payment through the link in the confirmation message” is operational. “Submit the form and payment details will be sent” may still be sufficient in a simpler task, but only if the missing sequence is not material.

83. Cause and correlation: do not manufacture the link

If a task provides two facts together, students may assume one caused the other. Attendance rose after a timetable change; complaints fell after new signage appeared; participation increased during a promotional campaign. Unless the evidence supports causality, a response should avoid turning sequence into proof.

A complete explanation can remain cautious: “Attendance increased after the timetable changed, suggesting the later start may have made participation easier.” This fulfils the interpretive job while preserving the evidence boundary. “The timetable change caused the increase” makes a stronger claim and therefore requires stronger support.

Source Transformation owns the detailed evidence-handling mechanics. Task Fulfilment asks only whether the explanatory requirement was completed without crossing what the evidence allows.

84. Requirement collisions: when one sentence accidentally breaks another

A response can close one loop while opening another. For example, a writer tries to reassure readers by saying “Everyone is guaranteed a place”, but the source states that places are limited. The reassurance requirement is addressed, yet the accuracy constraint is violated. Or the writer tries to sound decisive by declaring an option “clearly best”, even though the task requires acknowledging a stated drawback.

Call these requirement collisions. The repair is to satisfy both obligations at once: “Places are limited, but students who register early will receive confirmation before the event.” “Option B is the stronger choice for capacity, although its higher cost should be considered before approval.”

Advanced performance often depends on solving these collisions rather than maximising one quality at the expense of another.

85. Redundancy can hide incompleteness

Students sometimes repeat the same fulfilled point in several forms and mistake repetition for coverage. A response may say a venue is convenient, easy to reach, accessible and well located—four expressions of essentially the same idea—while never addressing the required cost or capacity criterion.

During review, collapse synonymous points mentally. Ask how many distinct requirements have been closed, not how many positive statements have been written. Variety of wording is not variety of task coverage.

This is another reason the requirement inventory matters. It prevents the draft from creating a false sense of completeness through verbal abundance.

86. Topic knowledge must not outrun task authority

Students sometimes know a topic well and add outside facts that were not requested or supported. Knowledge can enrich writing, but in constrained tasks it can also create risk. A student writing about public transport may introduce environmental statistics from memory; one writing about exercise may add medical claims; one writing about technology may invent technical benefits.

The task-authority test is simple: Am I allowed to assert this here? If the examination expects use of supplied material, unsupported outside facts may distract or distort. If some reasonable development is permitted, it should remain generic and plausible rather than becoming a new factual dependency.

Task fulfilment is not a display of everything the writer knows. It is disciplined selection of what the assigned communication job needs.

87. Voice and tone cannot compensate for an unfinished job

A warm email, authoritative report or energetic speech may create a strong impression. But tone operates on completed content; it does not replace it. “We would be delighted if you joined us” sounds inviting, yet if the reader does not know when or how to register, the invitation remains incomplete.

This boundary matters because students often polish tone before verifying coverage. The later Audience and Register guide will teach relationship, distance, politeness, authority and voice in depth. Here, tone is subordinate to fulfilment: first finish the job, then make the finished job sound right for the reader.

88. Paragraphing cannot manufacture missing logic

Breaking a script into neat paragraphs can make it look organised while required reasoning remains absent. One paragraph may be labelled “Advantages” and another “Recommendation”, but the recommendation still needs grounds connected to the task. Visual structure is helpful; functional completion is prior.

Use paragraphs to contain completed units, not to disguise incomplete ones. A paragraph that begins with a recommendation and then supplies evidence and fit has a clear job. A paragraph filled with loosely relevant details has shape without closure.

89. The requirement budget

Every task has a finite attention budget. Think of each major requirement as needing enough space to cross its completion threshold. Some thresholds are cheap: a date, place or contact route. Others are expensive: a comparison, evaluation or justified recommendation. Good writers distribute attention according to threshold, not according to whichever idea they enjoy writing about most.

A planning budget can use rough units rather than word counts. Give a simple factual requirement one unit, an explanation two, a comparison three, and a recommendation with justification three or four. These values are not rules. They merely expose when a response plan has allocated ten units to one attractive point and one unit to everything else.

The later timing system will handle actual minutes. Task fulfilment owns only the allocation principle: no essential job should be starved below the amount of development it needs.

90. The completion-first planning order

A reliable planning order is: jobs → constraints → evidence → completion test → sequence. First identify what must be done. Then identify the limits. Then choose the evidence or content that can do the work. Then state what would make the job complete. Only after that decide where each unit will go.

This order reduces a common planning error: arranging paragraphs before the writer knows what must be inside them. “Introduction, three body paragraphs, conclusion” is a container plan. Task fulfilment needs a job plan. Containers become useful only after the jobs are understood.

91. The final sixty-second audit

If only a short review window remains, do not reread every sentence with equal attention. Run the six-question checklist quickly, then scan the prompt for small high-risk words. Check numbers, names, dates, quantities, conditions, negatives and the required action. Look specifically at the final paragraph: does the reader know the decision or next step?

Then scan for contradictions created during drafting. Did an early paragraph say the event is free while a later paragraph mentions a fee? Did the recommendation change from Option A to Option B without the conclusion being updated? Did a condition disappear when a sentence was compressed?

Only after this structural audit should remaining seconds be spent on obvious spelling, punctuation or grammar corrections. The order protects the largest task risks first.

92. The five-script stability test

One successful script can be luck. To test whether task fulfilment has become a skill, use five unseen prompts with different topics and formats. At least one should contain a compound instruction, one a meaningful condition, one a comparison plus recommendation, one a multi-purpose task and one a dense source set.

Track four outcomes for each script: number of omitted requirements, number of partial requirements, number of constraint errors and number of functional failures. The target is not perfection on the first cycle. The target is consistency and a clear downward trend.

When the learner can complete all major jobs across five unfamiliar tasks without teacher prompting, the system is beginning to hold under transfer.

93. The independence interview

After a timed response, ask the learner to explain their process without looking at teacher notes. What were the requirements? Which one was highest risk? Which source detail supported the recommendation? Which condition had to be preserved? Where did you decide a point was developed enough? What would you repair first if given two more minutes?

The answers reveal whether task control is internal or accidental. A student who can articulate the completion logic is more likely to transfer it. A student who says “I just wrote what sounded right” may have produced a good script but has not yet built a dependable method.

94. Current international assessment context

Different examination systems use different labels, task forms and marking criteria, so students should always follow the specification for the qualification they are actually taking. The transferable principles in this guide sit below those local rules.

Cambridge IGCSE First Language English continues to include Directed Writing in Paper 2. Cambridge describes the wider course as developing clear, accurate and effective communication, awareness of audience, and the ability to order facts and present opinions effectively. For examinations from 2027, Cambridge has restructured the Directed Writing task into linked reading and writing parts while retaining the directed-writing focus.

Pearson Edexcel International GCSE English Language A also retains transactional writing. Its current modular specification describes a writing task involving a given audience, form or purpose and assesses effective communication together with adaptation of form, tone and register for specific purposes and audiences.

The practical lesson is not to memorise one board’s surface pattern and assume it applies everywhere. The durable layer is deeper: identify the communication job, preserve the task’s constraints, complete every required content function, and make the response usable for the intended reader.

Official references: Cambridge IGCSE First Language English (0500); Pearson Edexcel International GCSE English Language A modular specification. Check the current specification for your own examination year before relying on any format detail.

95. What task fulfilment does not own

A strong system needs boundaries. Task Fulfilment does not own the detailed method for decoding role, audience, purpose and context; that belongs to Task Decoding. It does not own the detailed method for converting source material accurately into new wording; that belongs to Source Transformation.

It also does not own the full craft of audience/register, information ordering, format conventions, development and elaboration, sentence-level language control or general time management. Those systems need their own depth. Task Fulfilment owns one question: Did the response completely and accurately do every communication job the task required?

96. Final operating model: Presence → Accuracy → Development → Function → Verification

The simplest durable model is now five steps. Presence: every required job appears. Accuracy: facts, quantities, conditions and scope remain true. Development: each job receives enough explanation or reasoning to satisfy its command. Function: the material enables the reader to understand, decide or act. Verification: the completed response is checked against the original task before submission.

When students struggle, move backwards through the chain. If the reader cannot act, check function. If the function is weak, check development. If the development is built on a distorted fact, repair accuracy. If the point is absent, restore presence. The chain gives diagnosis a direction.

Maren, Iona and Leonie approach the same chain from different angles. Maren asks whether each idea has enough structure to complete its job. Iona checks whether evidence, scope and meaning remain faithful. Leonie checks whether open loops are closed before time expires. Together they model the central principle: good situational writing is not merely well written. It is finished.

Return to the Secondary English Situational Writing Examination Performance hub to continue the full system. The next major layer is Audience and Register Performance: how relationship, authority, distance, politeness and voice change the way a completed message should sound.

97. Micro-omissions: the tiny detail that keeps the job open

Some omissions are obvious: a whole requested recommendation is missing. Others are microscopic. The writer gives the location but not the room number, the deadline but not the submission route, the activity but not the eligibility condition, the meeting date but not the revised start time. Because most of the requirement appears, the writer feels that it has been completed.

Micro-omissions matter when the missing detail changes whether the reader can understand or act. A useful test is to imagine the reader following the message literally. Where would they stop and need to ask a question? That point often reveals the missing operational detail.

Train micro-omission detection with short notices rather than full essays. Give students a six-line response and ask them to act as the reader. They should circle every place where the communication requires information that has not actually been supplied. This develops completion sensitivity without the noise of a long script.

98. Direct requirements and inferred completion are not equally strong

If the prompt explicitly asks for two reasons, the response should make both reasons visible. Do not rely on the marker or reader to infer that an example secretly counts as a second reason. Direct requirements deserve direct completion.

Inferred completion is more appropriate when the task asks for a broader outcome and the relationship is obvious. A persuasive message does not need to announce, “I am now persuading you.” Its reasons and reader benefits perform that purpose. But a task that explicitly asks for a deadline, a choice or two drawbacks should not make the reader reconstruct those elements from hints.

A useful rule is: the more explicit the instruction, the less interpretive work the reader should have to do to find its completion.

99. Mixed fact-and-decision tasks require a deliberate gear change

Many situational tasks begin with factual reporting and then switch into judgement. The writer may have to explain what happened, compare alternatives and recommend what should happen next. Students who are comfortable with factual transfer can remain stuck in reporting mode and never complete the decision.

Mark the gear change in the inventory. For example: R1–R3 = establish facts; R4 = compare; R5 = recommend. When the draft reaches R4, the writer should deliberately move from “what the source says” to “what the evidence means for the task”. This shift is functional, not merely stylistic.

The reverse can also happen. A student begins recommending too early and treats assumptions as facts. Completion becomes stronger when evidence and decision are both present and clearly distinguished.

100. Two-stage reader actions

Some communications require more than one action. A participant may need to register first and then attend a briefing. A committee may need to approve a trial and later review results. A customer may need to return an item before a replacement can be issued. If the response mentions only the final action, the process may remain unusable.

Map two-stage actions as Action 1 → trigger/confirmation → Action 2. “Submit the registration form by Friday. Once your place is confirmed, attend the online briefing on Monday.” The sequence prevents the reader from assuming that attendance is possible without registration.

When the task has several actions, do not automatically include all of them. Include those necessary to complete the assigned communication job. Task fulfilment is selective usefulness, not procedural excess.

101. Deadlines with contingencies

A deadline can contain its own branch logic. Registration may close on Friday unless all places are filled earlier. A booking may be held until noon and released after that time. A submission may be accepted late only with prior approval. These details change the reader’s risk and should remain attached to the deadline when relevant.

A weak compression says, “Register by Friday.” A stronger completion says, “Register by Friday, although applications may close earlier once all places are taken.” The second version preserves both the formal deadline and the capacity contingency.

The practical test is whether removing the contingency could cause a reasonable reader to act too late or make a wrong assumption. If yes, it belongs to the completed requirement.

102. Complaint remedies should be proportionate to the evidence

In complaint writing, students sometimes believe a stronger demand creates a stronger response. It can do the opposite. If the evidence shows a repeated delay, asking for investigation and a revised procedure may be justified; demanding dismissal of an employee may exceed the task. If a damaged item is documented, replacement or refund may be reasonable; demanding unrelated compensation may not be.

Task fulfilment requires a remedy that matches the problem, the writer’s role and the available evidence. The completion condition is not “sound angry enough”. It is “make the required response clear and supportable”.

A useful training question is: What is the smallest action from the reader that would genuinely resolve the stated problem? This often produces a more precise and credible request.

103. Permission requests need a decision package

A request for permission is incomplete if it merely says, “May we do this?” The decision-maker may need enough information to judge feasibility, risk, timing, resources and responsibility. Exactly how much depends on the task.

A compact decision package may contain: the proposed action, why it is needed, when and where it would happen, what resources are required, one relevant safeguard and the specific approval sought. If the task supplies only some of these, do not invent the rest; use the information legitimately available.

The reader-action test is especially useful here: could the recipient reasonably say yes, no or ask one targeted follow-up question after reading the response? If they still do not know what they are being asked to approve, the request is not complete.

104. Invitations are logistics plus motive plus response

Invitations often look easy because their format is familiar. Yet examination invitations frequently combine several jobs: explain the event, persuade the reader that it is worth attending, provide logistics, state any eligibility condition and tell the reader how to respond.

A complete invitation answers three broad questions: What is this and why might I care? When and where does it happen? What do I do if I want to take part? If the source contains a meaningful restriction—limited places, age range, equipment requirement, advance registration—that boundary belongs with the action.

A warm closing improves tone, but the operational core must already be intact.

105. Reports must distinguish findings from recommendations

A report may ask the writer to present findings and recommend action. Students sometimes blend the two so heavily that the reader cannot tell what was observed and what the writer proposes. This weakens both accuracy and decision quality.

Complete the finding as a finding: what the evidence shows, with necessary qualifications. Complete the recommendation as a recommendation: what should happen and why the findings support it. The two may appear in the same paragraph, but their functions should remain distinct.

For example: “Most respondents preferred a later start, although the sample was small. I therefore recommend a two-week trial of the later timetable rather than a permanent change, followed by a second survey.” The response preserves the evidence limitation and still closes the action.

106. Notices and announcements: brevity raises the accuracy burden

A short format does not reduce the number of essential jobs. It reduces the space available to complete them. Notices and announcements therefore punish vague wording. If the reader needs the date, place, eligibility, action and deadline, those elements must survive compression.

Prioritise operational information. “Exciting news! Our wonderful activity is returning!” may be appropriate as a brief hook, but it should not displace the information that lets the reader participate. In a constrained short form, each sentence should earn its place by closing a task loop or supporting the main purpose.

107. Articles and speeches can hide an action requirement inside broad purpose

A task may say “encourage students to reduce food waste” rather than explicitly “tell them what to do”. Yet encouragement is more complete when readers are given a realistic action: take smaller first portions, return for more if needed, separate unavoidable scraps, or use a collection point, depending on the supplied context.

This is an implied completion issue. The writer is not inventing a new requirement; the writer is making the stated persuasive purpose executable. However, the action must remain within the task’s evidence and authority.

The test is whether the broad purpose has been translated into something the audience can actually do, believe or decide.

108. Multi-source cross-checking

When information is distributed across several sources, a requirement may need details from more than one place. One source gives the event time; another gives an exception. One table gives cost; a note gives a discount condition. One email gives the requested action; a poster supplies the deadline.

Before declaring a requirement closed, cross-check whether another source qualifies it. A useful method is to mark each requirement with all relevant source labels: R3 = Source B + Note C. This prevents the first matching fact from being mistaken for the whole answer.

The Source Transformation guide teaches deeper source handling. Here the concern is narrower: a requirement is not complete until all material conditions relevant to that requirement have been reconciled.

109. Contradictory sources require explicit control

If two sources disagree, the writer should not silently choose the more convenient one unless the task gives a basis for doing so. The discrepancy may itself be important. Perhaps one message is older, one is a draft, or one contains a later correction. Perhaps the conflict cannot be resolved from the material provided.

Completion under contradiction can take several forms: use the clearly newer source; state the corrected information; acknowledge that confirmation is needed; or frame the recommendation conditionally. What matters is that the response does not manufacture certainty by pretending the conflict does not exist.

In training, give students two nearly identical notices with one changed detail and ask which information should govern the final response and why.

110. Sampling and denominator caveats can affect the decision

If a survey says “80% preferred the later session”, the sample size and sample type may matter. Eight out of ten volunteers is not the same evidential base as eight hundred responses from the whole cohort. A task may not require statistical analysis, but a recommendation should avoid giving fragile evidence more certainty than it deserves.

Use the caveat only when it changes the completion of the decision. “Most respondents preferred the later session, though only a small group replied; a short trial would therefore be safer than an immediate permanent change.” The limitation has become part of a proportionate recommendation.

111. Comparing evidence that does not use the same measure

One option may be described by cost while another is described by satisfaction. One programme gives an attendance figure while another gives a percentage. Students sometimes compare these as if they are directly equivalent. They are not.

Before completing a comparison, identify a shared criterion or acknowledge that the evidence measures different things. “The data does not allow a direct popularity comparison because one source reports total attendance and the other reports satisfaction among participants.” That statement can itself be part of an accurate evaluation.

A complete response does not force symmetry where the source does not provide it.

112. Counterargument becomes a requirement when the task makes it one

Writers are sometimes told to acknowledge a concern, drawback or opposing view. In that case, counterargument is not an optional sophistication feature; it is part of task fulfilment. Mentioning the concern without responding to it may still leave the loop partial.

A minimum complete unit is often concern → response → residual limit. “The larger venue costs more, but it is the only option with enough capacity. The extra cost should therefore be weighed against the risk of turning participants away.” The writer does not pretend the drawback disappears.

If the task does not ask for a counterargument and the response budget is tight, do not add one merely to sound sophisticated. Requirements, not habits, should drive inclusion.

113. Acknowledging a drawback without weakening the recommendation

Students sometimes fear that admitting a drawback will make their recommendation sound indecisive. In fact, a bounded acknowledgement can strengthen it because the decision appears to have survived scrutiny.

Use a three-part structure: drawback → why the recommendation still holds → mitigation if supported. “Option B is more expensive, but its larger capacity is essential for the expected attendance. If approved, the higher fee could be managed by reducing decorative spending elsewhere.” Only include the mitigation if the task provides or permits it.

The recommendation remains complete because the main criterion has been prioritised rather than the drawback being ignored.

114. Mandatory and optional source points

A source may contain ten facts while the task requires only six of them. Students often assume more source use means better fulfilment. It does not. A source detail is mandatory when an instruction directly requires it or when the communication cannot function accurately without it. Other details may be optional support.

Classify source points as M for mandatory, S for supporting and D for distractor/non-useful in this task. The categories can change when the purpose changes. A price may be mandatory for a budget recommendation but merely supporting in a general invitation.

This classification prevents source completeness from being confused with task completeness.

115. The phrase “all relevant information” is a judgement problem

Some tasks do not list every content point. They ask writers to use relevant information from supplied material. Now fulfilment requires judgement. The writer must infer which details the reader needs for the stated purpose.

Use three filters: purpose, reader decision, consequence of omission. Does the detail help achieve the purpose? Does the reader need it to understand or act? Would leaving it out create a misleading or unusable message? Details that pass none of these filters probably do not deserve space.

This is one of the points where rigid tick-box methods reach their limit. Advanced task fulfilment is selective judgement governed by the communication problem.

116. Control assumptions before they become false facts

Everyday reasoning fills gaps automatically. If an event is at a park, a student may assume it is outdoors. If a programme is for younger children, a student may assume parents attend. If a venue is more expensive, a student may assume it is better equipped. These assumptions feel natural because they are plausible.

Plausibility is not evidence. Before using an unstated assumption, ask whether it is necessary for completion and whether the task authorises it. If not, remove it or frame it explicitly as a possibility only when such inference is permitted.

A useful drill gives students five plausible but unsupported additions and asks them to identify why each one exceeds the task.

117. Pronouns and referents can create hidden fulfilment errors

A response may contain the required information but attach it to the wrong person or organisation through an unclear pronoun. “They will provide the equipment” is useless if two groups were just mentioned. “It closes on Friday” is risky if both registration and payment windows appear in the paragraph.

For high-value requirements, prefer explicit referents when ambiguity is possible: “The organisers will provide the equipment”; “Registration closes on Friday.” Clarity is not stylistic fussiness here. It protects the identity of the requirement.

Iona treats referent ambiguity as an accuracy risk because a reader who cannot tell what a deadline or condition refers to cannot reliably act on the message.

118. Names, dates and entity consistency

Dense tasks can contain similar names: Room 2 and Room 12, Green Hall and Greenfield Hall, Tuesday 14 May and Thursday 16 May. A student may transfer the correct type of information but attach it to the wrong entity.

During final verification, scan proper nouns, numbers and dates as a separate layer. This is faster than rereading every sentence for everything at once. Check that each entity retains its own attributes: cost, capacity, time, restriction or contact.

Task fulfilment fails when the correct fact is assigned to the wrong option, even if the sentence itself is fluent.

119. Board-neutral transfer: learn the mechanism, then obey the local specification

Examination boards differ in labels, lengths, source structures, permitted text types and mark schemes. The transferable mechanism should therefore be learned separately from any one format. Presence, accuracy, development, function and verification remain useful because they describe what it means to complete a communication job.

Before an actual examination, overlay the board-specific rules: exact task type, timing, word guidance, assessment objectives and required conventions. Do not assume a training routine overrides the official specification. The mechanism travels; the specification governs.

120. Low-confidence completion: what to do when you are unsure

Sometimes a writer cannot decide whether a detail is required, whether an inference is safe or whether a sentence fully satisfies a command. Under pressure, uncertainty can produce either paralysis or over-writing.

Use a low-confidence protocol. First protect explicit instructions. Second preserve source wording at the level of meaning without copying mechanically. Third avoid adding unsupported facts. Fourth choose the interpretation that makes the fewest extra assumptions. Fifth use cautious language if uncertainty is genuine and the task permits it.

The goal is not perfect certainty. It is to prevent uncertainty from causing a larger violation than the original ambiguity.

121. The three-minute rescue drill

Give the student a nearly finished response with three minutes on the clock and four planted problems: one omitted point, one lost condition, one weak recommendation and one unnecessary paragraph. The student must rescue the task rather than beautify it.

The correct priority is structural: add the missing point, restore the condition, strengthen the recommendation to its minimum complete unit, then trim the paragraph only if time remains or if trimming creates the space needed for repair.

This drill teaches a crucial examination truth: when the script is threatened, completion triage beats cosmetic improvement.

122. High-pressure triage: protect the task in the right order

When several problems are discovered at once, use this priority order: missing required job → factual/constraint error → unsupported decision → unusable reader action → underdevelopment → organisation → style → polish. The order is not a universal mark scheme. It is a repair strategy based on which failures are most likely to invalidate the communication.

Leonie practises triage until it becomes automatic. She does not spend forty seconds replacing an ordinary verb while a required deadline is absent. She does not rewrite an introduction while the final recommendation contradicts the evidence. Under pressure, priorities are part of competence.

The later Timing and Recovery guide will develop exam-time control in depth. Here the lesson is simply to protect required completion before optional refinement.

123. The end-of-paragraph closure test

At the end of each major paragraph, ask one question: What job is now closed that was open before this paragraph began? The answer should be specific. “I explained why the change is necessary.” “I compared the two venues on capacity and cost.” “I made the recommendation and justified it.”

If the answer is only “I wrote about the event” or “I added more detail”, the paragraph may be drifting. This test is especially useful for students who can generate fluent prose without noticing that their writing has stopped moving the task forward.

Not every paragraph must close a whole requirement; some may establish evidence needed by the next unit. But the writer should know its function. A paragraph without a defined job is a candidate for compression or redesign.

124. The “one sentence too many” trimming drill

Give students a complete response in which each paragraph contains one unnecessary sentence. Their task is to remove exactly one sentence from each paragraph without damaging fulfilment. The exercise teaches them to distinguish support from redundancy.

After trimming, ask why the deleted sentence was expendable. Perhaps it repeated the same benefit, gave an irrelevant example, restated the prompt, or added general background that the reader did not need. Then ask what would happen if a different sentence were deleted. This reveals which sentences are carrying the actual task load.

Trimming is not about making every response short. It is about preserving the highest ratio of task function to words used.

125. The “one sentence too few” expansion drill

Now reverse the problem. Give students a response in which every required point is mentioned but several are one sentence short of completion. A recommendation lacks fit; an explanation lacks consequence; a request lacks the exact action; a comparison names both options but never connects them.

The student may add only one sentence to each weak unit. This forces precise diagnosis. They cannot solve the problem by writing a new paragraph of general detail. The added sentence must supply the exact missing function.

This drill is particularly effective for learners who have been told repeatedly to “elaborate” but do not know what useful elaboration looks like.

126. Contrast pair 1: present versus fulfilled

Present: “I recommend the community hall because it is suitable.” Fulfilled: “I recommend the community hall because its 150-person capacity accommodates the expected audience and its fixed indoor space removes the weather risk.”

Both versions contain a recommendation. Only the second makes the grounds and task fit visible. Use contrast pairs like this to train students to see that presence is only the first layer of completion.

127. Contrast pair 2: accurate fact versus usable fact

Accurate: “Registration closes on 12 June.” Usable: “Register through the online form by 12 June; places are confirmed in the order completed forms are received.”

The first sentence may be enough if the task asks only for the deadline. The second is needed when the reader also requires a response route and the order-of-confirmation condition. Completion is always judged against the job, not against a universal preference for more detail.

128. Contrast pair 3: two descriptions versus a comparison

Two descriptions: “Option A costs less. Option B has more equipment.” Comparison: “Option A is cheaper, but Option B’s included equipment avoids the separate rental the event would otherwise require, narrowing the real cost difference.”

The second version establishes a common decision dimension. The point is not that it is longer; it completes the relational job the word compare demands.

129. Contrast pair 4: persuasion versus unsupported enthusiasm

Enthusiasm: “This will be an amazing experience, so everyone should join!” Persuasion: “The session gives beginners guided practice with the equipment before the main activity, so you can take part even if you have never tried it before.”

The persuasive version identifies a likely barrier and answers it using task-relevant information. Excitement can support voice, but it does not itself complete the reader-benefit job.

130. Contrast pair 5: reassurance versus false certainty

False certainty: “You are guaranteed a place.” Bounded reassurance: “Places are limited, but everyone who secures a place will receive confirmation before payment is required.”

The second sentence reassures without violating the source constraint. This is a useful model for advanced tasks in which two communication goals must coexist.

131. Contrast pair 6: complaint versus actionable complaint

Complaint: “The repeated delay has been extremely frustrating.” Actionable complaint: “The service was delayed on three consecutive Mondays, causing users to miss the first scheduled connection. Please investigate the recurring delay and confirm whether the revised timetable will address it.”

Emotion can be legitimate, but the actionable version gives the reader a documented problem and a clear response target. That is what closes the task.

132. Contrast pair 7: justification versus generic praise

Generic: “The library is a good choice because it is convenient.” Justified: “The library is the better meeting place because it is beside the station and remains open until 8 p.m., so all group members can reach it after afternoon activities.”

Generic praise becomes justification when the reason is attached to the specific needs of the task.

133. Contrast pair 8: condition lost versus condition preserved

Lost: “Equipment is provided.” Preserved: “Equipment is provided for participants who register for the full-day session; half-day participants must bring their own.”

The first version is simpler and wrong. The second is slightly longer and accurate. Constraint words often deserve space because they protect truth.

134. Contrast pair 9: information dump versus reader selection

Dump: a paragraph repeats every feature listed in a brochure. Selected: the paragraph uses only the three features that answer the reader’s question about suitability, cost and access.

Students should learn that omission of irrelevant source material is not a failure. It is often evidence of control. The failure is omitting material the task actually needs.

135. Contrast pair 10: ending versus closure

Ending: “Thank you for reading and I hope you consider my ideas.” Closure: “I recommend approving the four-week trial. If permission is granted this week, volunteers can be trained before the start of next month.”

A response ends when the words stop. It closes when the reader knows the decision, action or next stage the task requires.

136. Thirty micro-prompts for rapid completion practice

These are designed for two-to-five-minute practice. Students should state the completion test, then write only the minimum complete unit.

1. Recommend one of two rooms using capacity and opening hours.
2. Explain why a registration deadline exists.
3. Invite a reader and include one eligibility condition.
4. Request a timetable change and give one operational reason.
5. Compare two transport options on cost and reliability.
6. Warn participants about a weather contingency.
7. Explain a new rule and one consequence of ignoring it.
8. Recommend an activity for beginners and prove suitability.
9. State two benefits of a trial programme without repeating the same idea.
10. Complain about a recurring error and request one proportionate remedy.
11. Reassure a nervous participant without making a guarantee.
12. Report one finding and distinguish it from your recommendation.
13. Explain a two-stage sign-up process.
14. Correct a false assumption using supplied information.
15. Recommend an option while acknowledging one drawback.
16. State a deadline with an early-closure condition.
17. Explain why a cheaper option is not necessarily the best value.
18. Ask for permission and state exactly what approval is needed.
19. Compare percentages when the sample sizes differ.
20. State what information is still unknown before a final decision.
21. Turn a bullet-point feature into a reader benefit.
22. Convert a general request into an executable action.
23. Preserve an “only if” condition while rewriting a sentence.
24. Write a recommendation based on incomplete evidence without overstating certainty.
25. Explain why two separately described options have not yet been compared.
26. Give a reader the next action after a complaint is acknowledged.
27. Write a one-sentence recovery patch for a missing deadline.
28. Compress a three-sentence explanation into one complete sentence.
29. Expand a one-line reason so it becomes a justification.
30. Close a speech with an action rather than a generic motivational ending.

Micro-practice is valuable because it creates many correct repetitions without the fatigue of constant full scripts. Full tasks remain necessary, but they should not be the only unit of training.

137. Teacher calibration: agree on what “complete” means

When several teachers work with the same learners, inconsistent feedback can make task fulfilment feel subjective. One teacher may accept a one-line reason while another expects a full paragraph. Calibration should return to the requirement itself: what does the command verb demand, what information is available, and what must the reader understand or do?

Use three anonymised scripts representing partial, secure and overdeveloped completion. Teachers independently mark the open loops, then compare. The goal is not identical stylistic preference. It is agreement about whether required jobs are present, accurate, sufficiently developed and functional.

This also improves student feedback because comments become tied to observable completion conditions rather than general impressions.

138. Self-marking protocol: separate writer mode from auditor mode

Students often struggle to detect their own omissions immediately after writing because they remember what they intended to say. Their mind fills in missing information. Self-marking becomes stronger when writer mode and auditor mode are separated.

After drafting, look back at the prompt before rereading the response. Rebuild the requirement inventory from the prompt alone. Then inspect the response as if it belonged to someone else. Mark each item open, partial, closed or verified. Only after that assess language.

When training outside an exam, add a short delay before self-marking. Even ten minutes spent on another task can reduce the memory effect and make omissions easier to see.

139. The task-fulfilment error log

Keep a compact log with five columns: task, failure, cause, repair, next drill. A line might read: “Report — recommendation partial — used generic reason — connect evidence to criterion — five recommendation units.” Another might read: “Email — deadline omitted — late prompt item — mark small-but-critical details — omission hunt.”

The log should not become a diary of every grammar mistake. Its purpose is to identify recurring completion failures and prescribe targeted practice. Review it weekly and look for patterns: quantities, conditions, actions, justification, overdevelopment or source accuracy.

When a failure no longer appears across several unseen tasks, retire it from active focus and move to the next weak link.

140. Spaced practice: return after forgetting begins

A skill that works only immediately after a lesson is fragile. Revisit task fulfilment after gaps: later the same week, the following week, and again after several weeks. Use new topics rather than repeating the exact prompt.

The first return can isolate one mechanism, such as conditions. The second can combine conditions with recommendation. The third can place the same risk inside a different format. Spacing forces retrieval and reveals whether the completion model has become durable rather than temporarily familiar.

141. Interleaving: mix the jobs so recognition becomes part of the skill

Blocked practice gives ten recommendations in a row. Interleaved practice mixes recommendation, explanation, comparison, request, invitation, complaint and reassurance. The student must first recognise what kind of completion problem is present before solving it.

This is harder and often feels less fluent, but it better resembles unseen examination work. The prompt will not announce which drill from last Tuesday is being tested. Recognition is part of transfer.

142. Retrieval practice: reconstruct the system without notes

At the start of a practice session, ask students to reconstruct the P-A-D-F-V chain, the six compact audit questions and three high-risk omission types from memory. Then compare with the reference version.

Retrieval strengthens access. A checklist is useful only if the learner can bring it to mind when the paper is unfamiliar and no teacher is present. The aim is not memorising slogans for their own sake; it is making the decision rules available under pressure.

143. Delayed transfer: test the mechanism after the format changes

Teach recommendation completion using an email, then wait several days and test it in a report. Teach condition preservation in a notice, then later place the same risk inside a speech. Teach two-stage reader action in a registration message, then later test it in a complaint-resolution task.

If performance survives both the delay and the format change, the learner has probably acquired the underlying mechanism. If it collapses, return to the functional completion rule rather than simply repeating the original genre.

144. Benchmark script A: fluent but fragile

Benchmark A reads smoothly. It uses varied vocabulary, natural transitions and an appropriate voice. Yet one of four required points is missing, a condition has been simplified away and the recommendation is generic. This script is useful because it demonstrates why surface quality can mask incomplete task control.

Ask learners to mark it without correcting language. Their job is to identify the missing loop, the distorted condition and the unsupported decision. Then compare how few sentences are actually needed to repair the structure.

145. Benchmark script B: complete but mechanically expressed

Benchmark B closes every major requirement accurately. Quantities and conditions are preserved; the recommendation is supported; the reader can act. However, the prose is repetitive and the organisation is basic.

This script teaches an equally important lesson: completion is a foundation, not the whole of writing quality. Once the communication job is secure, audience/register, information architecture, development and language control can improve the delivery without rebuilding the task from zero.

146. Benchmark script C: complete, selective and transferable

Benchmark C uses only the source information needed for the reader’s decision, preserves all material constraints, develops each requirement proportionately and closes with a clear next step. It does not include every interesting detail. Its strength is selective completion.

Students should compare C with both A and B. The aim is not maximal length or maximal sophistication. It is controlled communication: everything essential is there, everything there has a job, and no important truth has been bent for convenience.

147. An advanced task-fulfilment rubric

For advanced training, score five dimensions separately on a four-point scale. Coverage: are all required jobs present? Fidelity: are facts, quantities and conditions preserved? Sufficiency: is each job developed to its command? Function: can the reader understand, decide or act? Control: does the writer maintain completion under complexity and pressure?

A profile such as 4-4-2-3-3 is more informative than one overall label. It says the student finds all requirements and preserves evidence but habitually underdevelops explanations. Practice can then target sufficiency rather than repeating full tasks indiscriminately.

This rubric remains a training tool, not a substitute for the official mark scheme of any examination board.

148. Readiness test: can the student finish unfamiliar communication jobs alone?

A learner is approaching readiness when they can do six things without prompting: build a requirement inventory quickly; preserve quantities and conditions; distinguish source fact from judgement; recognise when a point is only mentioned rather than fulfilled; repair a missing loop efficiently; and complete an unfamiliar task without relying on a memorised paragraph pattern.

Test these abilities across at least three formats and several topics. Do not use only favourite themes. Readiness is demonstrated by transfer, not comfort.

149. Final learner checklist before submission

• Have I completed every explicit instruction?
• Have I split compound commands so no hidden half is missing?
• Are quantities, conditions, exceptions, deadlines and names exact?
• Have I avoided inventing facts the task does not provide?
• Does every major reason, explanation, comparison or recommendation contain enough to perform its function?
• Have I used source details because they serve the task, not merely because they exist?
• Have I given too much space to one point while another remains thin?
• If the reader must act, is the next action clear and executable?
• If evidence is uncertain or conflicting, have I preserved that uncertainty honestly?
• Does the final decision still match the evidence used earlier?
• Can I point to where each requirement closes?
• Have I checked the prompt one last time rather than trusting memory?

150. From completion to audience and register

Once the task is complete, another question becomes unavoidable: How should this completed message sound to this particular reader? The same recommendation changes when addressed to a close friend, a teacher, a committee, a customer, a public audience or an institution. Authority, distance, politeness, confidence and warmth alter expression even when the underlying task remains the same.

That is the next layer of the system. Task Fulfilment ensures that no communication job is left open. Audience and Register Performance will ensure that the finished job is delivered in a voice that fits the relationship and purpose without becoming artificial, submissive, aggressive or generic.

For now, keep the central operating rule: finish the communication before polishing the performance of it. Presence gives the task a body. Accuracy keeps it true. Development makes each part sufficient. Function makes it useful. Verification keeps the whole system aligned with the prompt.

151. Case study: the event email with three clocks

An event email contains three different times: registration closes at noon on Wednesday, volunteers report at 8.15 a.m. on Saturday, and the event opens to visitors at 9 a.m. A weak response says, “The event starts at 9 a.m. and registration closes on Wednesday.” It is not false, but it is incomplete for volunteers because their reporting time has vanished.

The fulfilment lesson is that similar information must remain attached to its function. Registration time controls eligibility. Reporting time controls volunteer arrival. Opening time controls public attendance. The writer should not compress them into one vague “event time”.

A complete version might say: “Register by noon on Wednesday if you would like to volunteer. Confirmed volunteers should report at 8.15 a.m. on Saturday for the briefing, before the event opens to visitors at 9 a.m.” One sentence now preserves all three clocks and their relationships.

152. Case study: the cheaper venue that fails the task

Venue A costs 20% less than Venue B. A student immediately recommends A because the prompt mentions a limited budget. But the source also states that ninety people are expected and Venue A holds only sixty. Venue B holds one hundred and includes the equipment that would otherwise need separate rental.

The fulfilment failure is not arithmetic. It is incomplete criterion handling. Cost matters, but capacity is a hard constraint: a venue that cannot hold the expected audience may be invalid regardless of its lower headline price. The equipment inclusion also changes the meaning of the price comparison.

A stronger response distinguishes desirable criteria from non-negotiable constraints. It might recommend B while acknowledging cost: “Although Venue B is more expensive, it is the only option large enough for the expected audience and its included equipment reduces additional rental needs.” The recommendation now survives the whole task rather than one attractive fact.

153. Case study: the invitation that forgets who may attend

A source announces a workshop “for students aged fourteen to sixteen”. The response enthusiastically invites “everyone” to attend. The writer has preserved the event, date, venue and activities but has widened eligibility beyond the source.

This is a constraint-loss error disguised as friendliness. Audience-facing language such as “everyone is welcome” feels natural in invitations, which is precisely why it is dangerous when eligibility is restricted.

The repair can remain warm without becoming inaccurate: “If you are aged fourteen to sixteen and would like to try the workshop, register by Friday.” The eligibility boundary is now part of the invitation rather than an awkward footnote.

154. Case study: the report that uses every fact and answers nothing

A student receives two pages of survey findings and writes a detailed report containing nearly every figure. The task asks which of two programmes should be expanded. The response accurately reproduces attendance, satisfaction, cost, session length, participant comments and staffing data but never states which programme better satisfies the organisation’s priority.

This is source completeness without task completion. The response has treated evidence collection as the final product. A report becomes decision-ready only when the evidence is selected and related to the requested judgement.

The repair begins by returning to the requirement: recommend which programme should be expanded. Then identify the criteria that matter to that decision. Perhaps Programme A reaches more people but Programme B produces much stronger completion rates at similar cost. The report should state that trade-off and make a recommendation rather than hiding behind data volume.

155. Case study: the persuasive speech with no barrier removal

A speech urges students to join a weekend project. The response contains energy and several benefits but ignores a source note saying that many students are concerned they lack experience. Because the task specifically asks the speaker to address a concern, the speech leaves a required persuasive obstacle untouched.

A complete response should not merely repeat benefits. It must answer the stated barrier using legitimate evidence: “No previous experience is required. The first thirty minutes are a guided training session, and each group works with an experienced leader.”

The difference is important. Persuasion is not cumulative praise. When a task identifies resistance, fulfilment may require removing or reducing that resistance.

156. Case study: the complaint that asks for the impossible

A complaint concerns two delayed deliveries. The student requests a lifetime guarantee of same-day service and a full refund for future orders. The response certainly makes a request, but the remedy bears little relationship to the documented problem or the writer’s authority.

Task fulfilment includes proportionality because a communication job is not complete when the requested action is implausible or unsupported. A better request might ask the organisation to investigate the recurring delay, confirm the expected delivery window and explain what remedy applies to the affected orders.

Strong functional writing does not confuse force with effectiveness. The best request is the one the evidence justifies and the reader can realistically act on.

157. Case study: the proposal that forgets the safeguard

A proposal suggests a student-run equipment-lending desk. The source provides a workable rota, a storage area and a clear benefit, but also states that expensive equipment may be issued only after staff authorisation. The student explains the benefits and operation but omits the authorisation rule because it seems like a small administrative detail.

That detail is actually part of feasibility. Without it, the proposal appears to give students authority the source does not grant. A complete version integrates the safeguard into the operating mechanism: “Student volunteers can manage routine loans, while any high-value equipment is released only after staff authorisation.”

Constraints are often what make a proposal credible. Removing them can make the idea sound simpler while making it less valid.

158. Case study: two purposes, one forgotten

A task asks the writer to inform residents about a new collection system and persuade them to use it correctly. The response explains the schedule and locations perfectly but contains no reason why correct use matters. The informational purpose is secure; the persuasive purpose is barely present.

Compound purposes should be treated as separate completion obligations. To close the persuasive loop, the writer might explain a consequence supported by the source: incorrectly sorted items contaminate the collection and can prevent recyclable material from being processed.

The final response should not split into two artificial halves labelled “information” and “persuasion”. The functions can be integrated. What matters is that neither disappears.

159. Case study: one recommendation, three competing answers

A prompt asks for one recommended location. The student writes that Venue A is cheapest, Venue B is most accessible and Venue C has the best facilities, then concludes that “any of the three could work”. The response contains evaluation but refuses the decision the task requires.

When one choice is required, task fulfilment demands a prioritisation rule. Which criterion matters most under the stated purpose and constraints? Perhaps accessibility is essential because the audience includes participants with limited mobility; perhaps capacity is non-negotiable; perhaps the budget ceiling eliminates one option completely.

A mature answer can acknowledge trade-offs and still decide. Nuance is not indecision.

160. Case study: the condition hidden in a footnote

A poster advertises free entry. A small note states that the offer applies only to advance bookings. The student writes, “Entry is free,” because the headline is more visually prominent than the footnote. The response has copied the largest text but not the full truth.

Visual prominence is not the same as informational priority. In stimulus-based tasks, conditions may appear in captions, footnotes, sidebars or table notes. If they materially qualify a required point, they must survive transformation.

The fulfilled version is simple: “Entry is free for visitors who book in advance.” The extra five words protect accuracy and reader action.

161. Case study: the statistic with the missing base

A chart shows that participation rose from twenty students to thirty. A response says participation “increased by 50 students” because the writer confuses a 50% relative increase with an absolute increase. The recommendation built on the figure now rests on a factual error.

Task fulfilment requires numerical claims to preserve the original scale. The safe statement is: “Participation rose from twenty to thirty students, an increase of ten students.” If percentage interpretation is useful and the student is confident, “a 50% increase” is also correct—but it should not replace the underlying figures when ambiguity is possible.

Numbers should clarify the communication job, not become a separate display of mathematical sophistication.

162. Case study: the procedure with the wrong order

A registration process requires applicants to submit a form, wait for confirmation and then pay. The response tells readers to “submit the form and payment” because those are the two visible actions. The facts are present but the sequence is wrong.

Procedural fulfilment includes order because order changes what the reader should do. A correct response keeps the dependency explicit: “Submit the form first. If your place is confirmed, use the payment link in the confirmation message.”

This illustrates why a checklist based only on whether key nouns appear can fail. The relationship between the nouns may be the requirement.

163. Case study: the source that changed later

One source states that the event ends at 5 p.m. A later email says the programme has been shortened and will finish at 4.30 p.m. A student uses the first time because it appeared in the main poster. Another uses the later time but never signals that it is an update.

The strongest completion recognises source chronology: “The updated schedule now ends at 4.30 p.m.” If the task expects readers to know about the change, naming it as an update may be useful because it prevents confusion among people who saw the earlier version.

When sources conflict, recency can be a resolution rule—but only when the later source clearly supersedes the earlier one.

164. Case study: the implied reader question

A task asks students to explain that a planned outdoor activity has moved indoors because of weather. The response states the new venue but does not say whether the start time has changed. The source explicitly says “all other arrangements remain unchanged”.

The reader’s natural question is: do I arrive at the same time? Because the source answers that question, including it improves completion: “The activity will move to the indoor hall, but the 3 p.m. start time and registration arrangements remain unchanged.”

This is not unnecessary reassurance. It resolves the uncertainty created by the change itself.

165. Case study: the elegant conclusion that changes the decision

During drafting, a student initially recommends Option A. After comparing the evidence more carefully, the body of the response shifts toward Option B. Under time pressure, the student forgets to update the conclusion, which still recommends A.

This creates contradictory completion: both choices appear, and the reader cannot know which one governs. The final audit should therefore include a decision-consistency check. Circle the named recommendation wherever it appears and confirm that every occurrence matches.

The same principle applies to dates, quantities, names and actions that may have changed while drafting.

166. Case study: the student who writes in source order

A stimulus sheet lists background, price, venue, activities, restrictions and contact details. The student reproduces those categories in the same order. Unfortunately, the task asks first for a recommendation, then reasons, then instructions for registration. The response contains the right material but makes the reader work to reconstruct the job.

Task fulfilment does not require source order. The requirement inventory should govern selection and completion. Information Architecture will later govern the most effective sequence, but even at this stage the writer should group material by the job it performs rather than by where it happened to appear in the stimulus.

Source order is an input property. Communication order is an output decision.

167. Case study: the overdeveloped opening

A student spends one hundred words establishing context that the reader already knows. The opening is polished and atmospheric, but the task contains four required body points. By the final point, the student is short of time and writes only one rushed sentence.

The fulfilment problem is budget misallocation. In constrained writing, an opening should orient the reader and establish purpose; it should not consume the resources required by substantive obligations.

A useful practice rule is to draft the shortest opening that makes the situation clear, then invest the recovered attention in requirements with higher completion thresholds.

168. Case study: the writer who answers the topic instead of the task

The topic is community volunteering. The student has many ideas and writes an impressive paragraph about the social value of volunteering. The actual task asks the writer to compare two volunteering programmes, recommend one for younger participants and explain how to register.

The paragraph may be relevant to the broad topic but irrelevant to the assigned communication job. Topic relevance is a weak filter. Requirement relevance is stronger.

Before keeping any substantial paragraph, ask: Which requirement does this close or materially support? If the answer is none, the paragraph is probably stealing time from the task.

169. Case study: the memorised template collision

A student has memorised that every formal email should end with “I look forward to your favourable response.” The phrase is inserted into an informational email that does not actually ask the reader for anything. The sentence sounds formal but invents a response expectation that the task never created.

Templates become dangerous when they add functions rather than merely packaging required ones. A sign-off, greeting or transition should serve the actual task. Do not create requests, promises, gratitude or urgency simply because a memorised model contains them.

Format Transfer will handle conventions in depth. The task-fulfilment rule is enough here: never let a template override the communication job.

170. Case study: the writer who checks grammar first

A student finishes with three minutes left and immediately begins correcting articles, commas and verb forms from the first sentence. The last paragraph contains no registration route even though the prompt requires one. Time expires before the student reaches it.

The error is not that grammar was checked. It is that verification was sequenced badly. Structural validity should be checked before local polish. A missing required action can leave the communication unfinished; a minor article error usually does not.

Train a fixed final sequence: prompt → requirements → constraints → decision/action → contradictions → language. When repeated often enough, this order reduces the chance that visible small errors consume the time needed to repair invisible large ones.

171. A twelve-task mastery circuit

For a serious training cycle, use twelve short-to-medium tasks rather than twelve full-length essays. Task 1 isolates quantities. Task 2 conditions. Task 3 comparison. Task 4 recommendation. Task 5 explanation. Task 6 request. Task 7 compound purpose. Task 8 multi-source reconciliation. Task 9 uncertainty. Task 10 recovery under reduced time. Task 11 format transfer. Task 12 combines all of them in one unseen simulation.

Score each task using Coverage, Fidelity, Sufficiency, Function and Control. The pattern will reveal whether the learner has one dominant weakness or whether completion breaks only when several demands appear together.

The circuit can be repeated later with new topics. Improvement is shown when the same mechanisms survive different surface content.

172. Frequently asked question: should every source point be used?

No. Use the source points the task and reader need. A source may contain context, examples, decorative details, alternatives that are ruled out, or information relevant to a different purpose. Including everything can dilute the response and consume the budget needed for required functions.

The safer principle is not “use more”. It is “use enough, accurately and purposefully”. If a detail is necessary to fulfil an instruction, preserve it. If it changes a condition, decision or reader action, it is likely important. If it does neither, test whether it earns its space.

173. Frequently asked question: how much development is enough?

Enough means the requirement has crossed its functional threshold. A factual statement may need one precise sentence. An explanation needs the why or how relationship. A comparison needs a shared criterion. A recommendation needs a choice and reasons connected to the task. A justification needs the bridge between reason and decision.

Do not measure adequacy only by sentence count. Ask whether removing the final sentence would reopen the job. If yes, it was probably doing necessary work. If no, it may be enrichment rather than required development.

174. Frequently asked question: what if the task is ambiguous?

Start with the explicit wording, the writer’s role, the intended reader, the stated purpose and the available evidence. Prefer interpretations that require fewer unsupported assumptions. Preserve uncertainty when the source is genuinely uncertain, and do not invent facts merely to make the response feel complete.

If two interpretations remain plausible, choose the one that best fits the whole task rather than one isolated phrase. Then write consistently. In training, discuss the ambiguity afterward; in an examination, the goal is a defensible completion based on the information actually provided.

175. Frequently asked question: is task fulfilment just a checklist?

At the beginning, it may look like one. Checklists are useful because they externalise invisible obligations. But mature task fulfilment is judgement. The writer decides what matters, how much development each requirement needs, which evidence is strong enough, which constraint must travel with a fact, which trade-off governs a recommendation and when a reader has enough information to act.

The checklist is scaffolding for that judgement. Over time, it should compress into fast questions and eventually into habits. Expert performance looks less mechanical precisely because the control system has become internal.

That is the final goal of this guide: not a student who can recite a formula, but a writer who reliably recognises an assigned communication job, finishes every essential part of it, preserves the truth of the task and hands the reader a response that works.