Lesson 12 — Work With Documents Without Losing the Details

STAGE 01 · PART B · LESSON 12 OF 20

Work With Documents Without Losing the Details

Ask useful questions about permitted documents, extract evidence and stop summaries from quietly changing the source.

35 MINUTES FREE · GOING DEEPER

Full course overview

1. A document is a source, not a suggestion

AI can help read a long public guide, pull out headings, draft a summary or turn instructions into a checklist. But a summary is an interpretation. Important exceptions, footnotes and dates can vanish unless you insist on source checks.

2. Start with permission

Use a public document, a document you own or one you’re expressly authorised to process with that service. Don’t upload HR, customer, legal or commercially sensitive files into an unapproved tool. Where access isn’t permitted, create a fictional sample instead.

3. Ask for evidence alongside the answer

Rather than “Summarise this”, try “Give me the five main points and show which section or paragraph supports each. Identify any ambiguous or missing details.” If a page or section reference isn’t available, don’t let the assistant invent one. Reopen the source to check quotations and figures.

4. Turn documents into practical outputs

For a public event guide, you might extract the checklist, deadline references and questions to confirm. Another useful pattern is asking for a two-column table: What the source says and What I need to do. Keep facts separate from recommendations and write “not stated” when necessary.

5. What if the file is scanned or messy?

Some products struggle with complex layouts, tables, handwriting or scanned pages. Missing text is not proof that the original lacks the information. Verify against the original visible pages before relying on a summary.

See it in action

This example shows how to apply the lesson. You can reuse the structure with safe, fictional or public details.

Using the public text I provide, create a table with: point, source passage/heading, proposed next step and unresolved questions. Quote only short relevant phrases. Do not invent section numbers or dates. Label anything you cannot locate.

Try spotting a bad summary

Fictional source: The community workshop starts at 10:00 on Saturday. Bring a notebook. Outdoor activities will be cancelled if it rains, but the indoor workshop will continue. Booking is required; the notice gives no booking deadline.

AI draft: “The whole workshop is cancelled if it rains. Book by Friday.”

Before opening the answer, identify both unsupported claims.

Show the checked answer

Only the outdoor activities are cancelled in rain. The indoor workshop continues. No booking deadline is stated, so Friday must be removed and the deadline marked unknown. A useful summary preserves exceptions and admits missing information.

PRACTISE

Your practical exercise

Choose a public information page or write a fictional one-page event guide. Ask AI for a summary, then a source-linked checklist. Check three extracted details yourself and correct any unsupported statement.

Before moving on: check the result yourself, and save one thing you learned or improved.
KNOWLEDGE CHECK

Check your understanding

Answer in your own words before opening each explanation.

1. What should you do if a summary omits an important exception?

Correct it by checking and referencing the original source.

2. Can a page number be trusted if the AI cannot access the page layout?

No. Ask it to mark the reference unavailable and verify manually.

3. What should you check before uploading a workplace document?

Whether the service and workflow are approved for that information.

Key idea: Treat the original document as the source of truth; AI helps you navigate it.
Artificially Us · Stage 1 AI Foundations · Part B