PDF

What the terms mean (short & practical)

Text‑centred: the question makes the provided text (a statute clause, contract clause, judgment extract, or passage) the primary object of analysis. You must do a close reading: interpret wording, structure, tone, devices, and show how meaning flows from the text itself.

Text‑based: the text is a starting point or piece of evidence. You must place it in a legal argument: identify issues, state the rule(s) (statute/case), apply the law to facts (or to the text), and reach a conclusion. The answer integrates the text with broader doctrine, policy and argumentation.

Why the distinction matters in exams

  • Mark schemes reward different skills: close reading and textual analysis for text‑centred tasks; rule application, problem solving and legal reasoning for text‑based tasks.
  • Time allocation changes: text‑centred answers need careful parsing and quotation; text‑based answers need clear IRAC structure, citation and balanced argument.

How to read the question (first 2–4 minutes)

  1. Spot language: words like “discuss the meaning of”, “analyse the wording”, “how does the extract illustrate” → text‑centred. Words like “advise”, “would X be liable”, “apply the statute to the facts” → text‑based.
  2. Highlight what you must use: if you must use the extract/quote, that signals text‑centred; if the extract is background only, it’s likely text‑based.
  3. Record the assessment objectives from the question (e.g., close reading, policy critique, application of authorities).

Templates: step‑by‑step

Text‑centred template (close reading)

  1. Lead: 1–2 lines stating the extract and what you will show (thesis).
  2. Paraphrase: one short paraphrase of the clause/paragraph in plain English.
  3. Structural analysis: point out sentence structure, punctuation, clause boundaries that affect meaning.
  4. Lexical choices: examine key words/phrases; consider ambiguity, semantic range, and legal meaning.
  5. Figures/tonal features: if relevant, mention rhetorical devices, voice (passive/active), modality (may/shall/must), and what those signal about intent or scope.
  6. Interpretive options & consequences: offer plausible readings and evaluate which the text itself supports best (use short textual quotations as evidence).
  7. Conclude: short verdict emphasising the text’s most defensible meaning and any limits of the text as authority.

Text‑based template (legal problem/IRAC with the text)

  1. Issue: one sentence identifying the legal question(s).
  2. Rule(s): state relevant statute/precedent and the relevant portion of the given text (quote briefly).
  3. Application: apply the rule to the facts (or to the meaning of the text). For statute/text interpretation, analyse how wording supports or weakens each argument; include counterarguments and policy if required.
  4. Conclusion: short, firm answer to the issue with reasoning and, if exam asks, advice on likely outcome or further steps.

Examples: same prompt, two approaches

Prompt (shortened): "A contract clause says ‘delivery shall occur within 30 days’. Discuss the clause."

Text‑centred answer (opening paragraph):

"Read literally, ‘delivery shall occur within 30 days’ uses mandatory language (‘shall’) and a precise temporal marker (‘within 30 days’). The clause’s syntax—subject omitted, verb focused—centres the obligation on the act of delivery rather than on a party’s due diligence. The prepositional phrase ‘within 30 days’ can mean: (a) from contract formation, (b) from notice, or (c) from a stated triggering event; the sentence does not resolve which, so a textualist interpreter must look for adjoining clauses (compare neighbouring provisions for triggers) before imputing an implied condition."

Text‑based answer (opening IRAC):

"Issue: When does the 30‑day period begin for the seller’s obligation to deliver? Rule: Contractual time obligations are interpreted by reference to wording, surrounding clauses and commercial common sense (see cases X, Y). The clause states 'delivery shall occur within 30 days'—the absence of a trigger suggests either (i) from contract formation or (ii) from a specified notice; applying commercial common sense (and reading the contract as a whole), the seller’s obligation is most plausibly from the buyer’s request because an earlier clause conditions delivery on 'buyer acceptance'. Therefore, the seller likely is not in breach if 30 days run from the buyer’s request. Alternative reading and counterargument: if the context shows no request mechanism, the court may prefer formation date to avoid indefinite delay. Conclusion: advising the client depends on which surrounding clause controls; key evidence: clause X and trade practice."

Using an 'Ally McBeal' cadence—what that means and when to use it

Ally McBeal’s speech is conversational, punchy, rhetorical, with brief parenthetical thoughts and a lively rhythm. Translating that into exam answers means:

  • Short, crisp sentences to highlight conclusions or issue statements.
  • Rhetorical signposting: ask a quick question and answer it, e.g., “What does ‘shall’ mean here? Mandatory — yes, usually.”
  • Occasional bracketed asides to signal nuance: (but note the context) — use sparingly.

Warning: formal exams reward precision and convention. Use the Ally cadence to improve readability and engagement, not to be flippant. Keep legal terminology, cite authority where required, and avoid slang.

Micro examples: Ally cadence vs traditional legalese

Traditional: "The clause is mandatory in terms; accordingly, the party will be liable upon failure to deliver within 30 days."

Ally‑tinged (exam‑safe): "'Shall'—that’s mandatory. Miss 30 days? You’re likely in breach (unless the contract says otherwise)."

Examiner expectations & marking tips

  • Answer the question directly — don’t waste marks on irrelevant exposition.
  • For text‑centred: quote selectively, explain how the quoted wording supports your reading, and show awareness of alternative readings.
  • For text‑based: use a clear structure (IRAC), bring in authority, weigh policy and counterarguments, and give a firm conclusion/advice.
  • Clarity beats showy vocabulary. Use the Ally cadence to make your key points memorable, but keep formality where it matters (definitions, citations, conclusions).
  • Time management: spend first few minutes identifying task type; allocate more time to the required skill (close reading vs problem solving).

Quick checklist before you hand in

  • Have I answered the specific question asked?
  • Did I use the text when required (quotes + analysis)?
  • Is my structure clear — can a marker spot the issue, rule, application, conclusion or the textual steps?
  • Have I acknowledged the main counterargument or ambiguity?
  • Is my conclusion precise and proportionate to the evidence/argument?

Final practical tips

  • Practice both modes. Take the same passage and write a 10‑minute text‑centred paragraph and a 20‑minute IRAC application.
  • Develop short signalling phrases that carry Ally cadence: "Key point:…", "But notice…", "In plain terms…" — they help readability.
  • When in doubt, be explicit about your method: "I will first analyse the text, then apply it to the facts." Examiners like visible structure.

Summary: identify whether the question asks you to do close textual work or to use the text within legal argument. Use concise, rhythmic sentences (the Ally trick) to make your analysis lively and clear, but always anchor statements in textual evidence and legal doctrine. Balance personality with precision.


Ask a followup question

Loading...