From fact file to research plan · Lesson 1

Sort facts, issues and limits

6 min read

Lesson objectives

  • Sort facts, issues and limits: produce a checkable result and explain its limit.
Reading tools

from a fact file to a researchable question

A training project team in an Arab city sends you a note: “The supplier delivered two devices late; can we recover what we paid?” The file contains a purchase order dated 4 March, a receipt dated 19 March, and the supplier's message saying that “shipment was completed on 12 March.” It does not contain the complete contract, the agreed due date, or a reliable choice of governing law and forum. A broad search for “refund for late delivery” would silently assume both a breach and a jurisdiction. The first task is to sort the record before searching for a remedy.

Mark each proposition as a documented fact, a party's assertion, or an inference. The purchase order and receipt support their dates, subject to checking completeness and authenticity in actual work. The 19 March receipt does not itself prove lateness: the due date and the contractual meaning of delivery are missing. The supplier's message records its position about shipment; it does not necessarily establish contractual delivery. “We are entitled to a refund” is a proposed legal conclusion, not a fact to be copied into the chronology.

Use four columns: proposition, supporting item, confidence, and the item needed to resolve the uncertainty. For “due date,” the file is silent; request the agreed contract or accepted schedule. For “actual delivery,” the supplier points to dispatch while the buyer points to receipt. Ask how the agreement defines performance and retain both records. This table turns missing information into a precise request instead of burying it as an assumption in the memorandum.

Formulate a conditional issue: “Under the law and agreement that govern this transaction, does missing the contractual delivery date permit recovery of the payment if receipt occurred on 19 March and dispatch occurred on 12 March?” The wording deliberately leaves the governing law and due date open. It can then be divided into research questions about the obligation, proof of delay, available remedy, and possible effect of accepting the goods. Research the predicate before the remedy. A search hit about refunds is not a substitute for showing that the rule applies to the proved facts.

The team's city is the location of the training team in this scenario, not an automatic answer to the governing-law question. The agreement could point elsewhere or involve more than one place. Record the location as a scope lead to investigate. Nor should the supplier's dispatch claim be called false without resolving the difference between dispatch and receipt. If key terms remain missing, escalate the limitation to the supervising professional and present a conditional, narrower answer.

A document's presence and the truth or legal effect of its content are different. A purchase-order image shows wording and a date; it does not alone prove the other side accepted every term. A warehouse receipt might be signed by someone authorized to acknowledge a package but not to accept final conformity. Put the reason for confidence beside each item: “document exists, acceptance not shown,” or “date supported, contractual meaning unresolved.” New evidence then updates one row and the issue depending on it rather than forcing a fresh start.

Test the conditional issue by deleting a qualifier. Without “under the governing system,” the researcher may import a convenient foreign rule. Without “if the agreed deadline is established,” lateness becomes an assumed fact. Without distinguishing dispatch and receipt, one date is chosen without a reason. Each qualifier corresponds to a source to find or a document to request. In the practice file, the seller's promise to send on 10 June does not prove handoff to the carrier that day. The 11 June carrier notice and 14 June buyer receipt record different events.

Lesson summary

Sort facts, issues and limits output and verification limit.