Module 04 / 10 · 40 planned minutes
Read documents with evidence
Build a short extraction table with source locations, versions and uncertainty, and independently check material fields.
Use AI03's bounded instruction to extract facts from identified documents. Your goal is a finding another person can trace, not a polished answer with decorative citations.
First pass: check four fields in C03 against C04. Move on when every material row has a location and status, and missing information remains missing rather than becoming an invented term.
Learn 14 planned minutes
A file is not necessarily usable text
An attachment may contain scanned pages, tables, handwriting, comments or tracked changes. Optical character recognition, or OCR, turns an image of text into machine-readable text; it can misread digits, dates and layout. A summary can therefore be wrong before the assistant begins reasoning about it.
Keep the original unchanged. Work from a copy, record any OCR or conversion and compare material passages with the original. Check the document title, version, date, page count and whether the relevant table or annex is present. Do not assume a system has read the whole upload because it mentions the filename.
Use smaller labelled extracts if the document is large or the tool has limits. The context window is a limit on material available for processing. More material does not guarantee better results; irrelevant or conflicting documents can obscure the controlling instruction. A retrieval system may select only some passages. Missing search results do not prove that a clause or event does not exist. NIST OAIPROMPT
Keep three things separate
A source statement is what a document says. An inference is what you think follows. A decision is what an authorised person chooses to do. For example, an email saying “we can discuss weekends” is evidence of a proposal or discussion, not proof that weekend service was agreed.
Capture the finding, source location, version/status, uncertainty and your check. “Not supplied” is different from “none exists”. “The pack contains no signed amendment” is narrower than “the contract can never have been amended”. Preserve these distinctions even in a short summary.
Document dates also mean different things. A signature date, event date, effective date and upload date are not interchangeable. A newly uploaded draft does not automatically replace an older signed agreement. Chronologies should record the event and its source rather than arranging filenames and assuming they show legal effect.
Verify the important fields
Compare parties, amounts, dates, obligations, exceptions and status with the original passages. Recalculate totals using a calculator or transparent spreadsheet. For a small training exercise, check every material row. In real work, any sampling approach and remaining risk need an appropriate review design; the assistant's confidence score is not a substitute.
Watch for material embedded instructions. A source might contain text telling the assistant to ignore its task or disclose a file. Treat such text as untrusted content, not authority. AI08 will practise this specifically.
Worked example
Separate fictional example: document D1, marked signed, says “delivery on 20 August”; email D2 says “we would prefer 15 August”.
Useful row: “Signed extract: 20 August (D1, paragraph 2). Email request: 15 August (D2, paragraph 1). No acceptance of the request supplied. Question: has an authorised change been agreed?”
Unreliable row: “Delivery due 15 August; source D2.” The citation identifies a real source but does not make the conclusion sound. Checking citation existence and checking what it supports are different tasks.
Practise 20 planned minutes
Guided practice
Extract Cedar's service period, monthly charge, support commitment and weekend coverage using C03/C04. Use source paragraphs and document status. In simulation, correct S04. Identify at least one field where the pack does not let you give a legal conclusion. Then spend two minutes on T01: correct the omitted exception without guessing whether a particular date is an examination day. This replaces part of the same practice block; it is not extra homework.
Feedback — compare after your attempt
C03.2 states 1 July–31 December 2026 and no automatic renewal under the extract. C03.3 states KES 12,000 per month excluding tax. C03.4 promises acknowledgement within four business hours, not restoration. C03.5 excludes weekend support from the stated service. C04 supplies different statements but no signed amendment. Legal effect is a question outside the instruction, not a gap to fill with model memory. T01's general closing time must retain the examination-day exception; the missing calendar prevents a date-specific answer.
Practice assignment
Complete A04's four-row evidence table. Add a two-event chronology: signature on 9 June 2026 and sales email on 10 June 2026, with source IDs. Give one missing-document request and keep your one-sentence T01 correction. Do not infer legal priority merely from which event came later.
Participation
Ask a peer to locate one finding without your help. Solo alternative: close your draft, reopen the cited paragraph and check whether it independently supports the sentence you wrote.
Check 6 planned minutes
Two formative checks. Choose an answer, then check it or open the comparison. Retry freely; this is not an award or an observed-skill record.
Source study and completion check
Optional pointer: NIST's publication summary for the generative-AI risk profile. Relate information integrity to one error you corrected; do not read the entire report for this short module. Complete AI04's two checks.
Before moving on, compare your artifact with the module feedback, correct material errors and keep its actual route label. This page does not record or certify completion.