Students read, interpret and accurately complete everyday functional documents such as forms, applications, agreements and official correspondence for real purposes

A Section III extended response worth 15 marks, arguing the future value of a module with reference to one text. Achieving through English lets you draw on this dot point about reading and completing functional documents.

Open by naming the module and your text, then state your line: the module is valuable because adult life is full of forms and agreements that demand accurate reading. Develop with the text, explaining how it taught you to read the exact wording of a field, follow small-print instructions, and notice obligation words such as must, due and penalty in agreements, and argue these skills protect you from costly errors.

Markers reward a clear sense of future value, well-chosen evidence, accurate metalanguage (functional document, instruction, obligation, deadline), and language suited to the audience. Avoid summarising the document; argue why the skill lasts.

A short reading task of the kind the exam uses on functional documents. The marker wants you to show how precise language carries real consequences.

A strong answer identifies obligation words such as must, due, within and penalty, and explains that each binds the reader to a condition or a deadline. It notes that an agreement is not just information but a binding text once signed, so reading what you agree to, and noticing conditions and dates, is the whole skill.

Markers reward precise identification of obligation language and an explanation of the consequences it creates, not a summary of the agreement's topic.

Given name vs family name (about 1.5 marks). "Given name" asks for your first name (the name given to you at birth or by choice); "family name" asks for your surname (the name shared with your family).

Residential vs postal address (about 1.5 marks). "Residential address" is the physical place where you live day to day; "postal address" is where mail should be sent, which can differ (e.g. a PO box or a relative's address).

Marking spine: both pairs correctly distinguished (0.75 each, up to 3). Reversing given/family name or treating the two address types as identical loses the relevant mark.

Any three of: "tick one only" (choosing more than one invalidates the answer); "block letters" (handwriting must be printed clearly, often for scanning); "include cents" (a whole-number amount would be read as incomplete or incorrect); "do not write in this section" (that space is reserved for staff use, and writing there can confuse processing); "N/A where not applicable" (tells the reader you did not simply miss the field).

Marking spine: 1 mark per instruction named with an accurate reason (up to 3). An instruction with no reason, or a reason that misdescribes the instruction, earns no mark for that item.

A 5-mark reading task rewards precise identification of obligation language plus an explanation of the consequence each creates, not a summary of the topic (timesheets and absences).

Obligation words identified (about 2-3 marks). "Must" (twice) creates a binding duty, not a suggestion; "within 48 hours" sets a hard deadline; "may be subject to" signals a real, though not automatic, penalty (delayed payment); "prior to" sets a second deadline (before the shift, not after).

Consequences explained (about 2-3 marks). Missing the 48-hour deadline risks the employee's own pay being delayed, a direct financial consequence; failing to report an absence before the shift (rather than after) breaches a separate obligation regardless of the reason for the absence. Together, the extract shows that agreement language binds the reader to exact deadlines and exact procedures, not general good intentions.

Marking spine: at least two obligation words or phrases correctly identified and quoted (2), the real-world consequence of each explained (2), and a concluding point that the language is genuinely binding rather than advisory (1). A response that paraphrases the extract without naming obligation language stays low band.

Why blank fields are risky (about 2 marks). A blank field is ambiguous: the reader cannot tell whether you deliberately skipped a field that does not apply to you, or simply missed it by accident, which can cause the form to be rejected or sent back for clarification, delaying the outcome. Writing "N/A" (or the form's expected equivalent) removes that ambiguity and shows the field was considered.

Two other habits (2 marks each). (1) Reading the entire form and its small-print instructions before writing anything, since forms often require sections to be skipped or completed in a specific order, and writing out of order can invalidate an answer. (2) Checking every number twice (dates, phone numbers, account numbers, amounts), since a single wrong digit can send a payment to the wrong account or record the wrong date, and these errors are far harder to fix after submission than to prevent before it.

Marking spine: the blank-vs-N/A explanation (2), two distinct additional habits each with a reason (2 marks each, 4 total). Listing habits with no reason given caps the mark for that habit at 1.

The distinction (about 3 marks). An informational document tells the reader something but does not, by itself, create an obligation the reader must meet; a binding document (an agreement, contract or signed form) creates real obligations and consequences once accepted or signed, often carrying deadlines, conditions and penalties expressed through words such as must, due, within and penalty.

Why it matters (about 2 marks). Because a binding document has real consequences (a fee, a loss of a right, a breach of contract) if its conditions are not met, it demands slower, more careful reading, ideally re-reading key clauses and clarifying anything unclear before signing, whereas an informational document mainly needs to be understood, not agreed to.

Marking spine: distinction drawn with the idea of created obligation vs information only (3), the practical consequence for reading care explained (2). Naming examples without explaining the underlying difference caps the mark at 3.

A 7-mark "evaluate" response needs a judgement about clarity, evidence from the extract, and a specific, workable improvement, not just a restatement of the clause.

Judgement and evidence (about 4-5 marks). The clause is a poor communicator of its obligations because its key terms are vague rather than precise: "shall endeavour" is weaker than "must", suggesting an effort rather than a firm requirement; "in a timely fashion" gives no actual deadline (unlike "within 7 days"); and "appropriate measures" gives no indication of what will actually happen if payment is late. A reader could not say, from this clause alone, exactly when payment is due or what the real consequence of lateness is, which defeats the purpose of a binding agreement (to set out enforceable, specific obligations).

Improvement (about 2-3 marks). Replace vague phrasing with precise obligation language and a concrete deadline and consequence, e.g.: "Each resident must pay their share of the utility bill within 7 days of the bill being issued. Payment more than 7 days late will incur a $10 late fee, payable to the resident who covered the shortfall." This keeps the same intent but removes ambiguity about the deadline, the amount and the consequence.

Marking spine: a clear judgement that the language is too vague to function as an enforceable obligation (2), at least two specific vague phrases quoted and explained (2-3), a concrete rewrite that fixes the vagueness with a real deadline and consequence (2). A response that only asserts "this is unclear" with no quoted evidence or fix stays low-mid band.