Skip to lesson content
Free course

AI Foundations / Module 4 / M04-U08 · 15-20 minutes

M04-U08 · 15-20 minutes

Applied Checkpoint: Improve Three Vague Requests

Complete the activity before revealing the model answer. Record one change you would make after comparison.

Instructions

For each request:

  1. Identify the important gaps.
  2. Write a usable task specification.
  3. Name the human review or approval.
  4. For Situation 2, divide the work into stages.
  5. For Situation 3, diagnose the supplied output defect and make a targeted revision.

All people, organisations, and source material in this activity are fictional.

Situation 1: learner reminder

Vague request:

Write a reminder for the class.

Available approved facts:

  • Audience: adults registered for the introductory spreadsheet class.
  • Date: Tuesday, 22 September.
  • Time: 6:00 p.m. to 7:30 p.m.
  • Place: Learning Room 3.
  • Bring: a charged laptop.
  • Contact: [email protected].

Write a complete specification for a short email.

Situation 2: compare service proposals

Vague request:

Compare these providers and choose one.

Available material:

  • An approved requirements sheet.
  • Two provider proposals.
  • Pricing must be checked by Finance.
  • Accessibility evidence must be reviewed by the accessibility lead.
  • The programme director makes the final decision.

Create a staged workflow that preserves those decisions.

Situation 3: diagnose and revise

Original request:

Summarise this office move proposal for staff.

Output defect:

The summary is polished but says the new office has free parking, a larger cafeteria, and a guaranteed opening date. None of those claims appears in the proposal.

Diagnose the likely specification gap and write a targeted revision.

Scoring guide

Your work meets the standard when it:

  • Defines outcome and audience.
  • Names authorised context and sources.
  • States material constraints and boundaries.
  • Defines an inspectable output format.
  • Includes observable review criteria.
  • Preserves named human authority.
  • Uses clarification or missing-information labels where needed.
  • Connects the Situation 3 defect to a targeted change.
Reveal the model answer

Situation 1

Outcome: Draft a reminder email that lets registered learners identify when and where the class takes place, what to bring, and how to ask a question. Audience: Adults registered for an introductory spreadsheet class; assume no technical background. Source: Use only the six approved facts supplied. Constraints: 90-120 words; warm and direct; do not add cost, software, instructor, parking, registration, or preparation claims. If a required detail is missing, label it for the class organiser instead of guessing. Format: Subject line, greeting, two short paragraphs, and contact line. Criteria: Every date, time, place, item, and contact detail matches the source; the required action is easy to find; no unsupported detail is added. Review: The class organiser compares the email with the approved facts before sending. The system must return a draft and must not send it.

Situation 2

Stage 1: prepare evidence

Extract each approved requirement into a table. The programme manager confirms the requirement list. Stop if requirements conflict.

Stage 2: compare proposals

For each requirement, quote or point to evidence in each proposal. Mark Not found where evidence is absent. Do not score or recommend.

Stage 3: specialist checks

Finance verifies pricing and assumptions. The accessibility lead verifies accessibility evidence. Record their corrections and unresolved questions.

Stage 4: decision brief

Draft a neutral brief with verified differences, missing evidence, risks, and open questions. Do not choose a provider.

Stage 5: decision

The programme director reviews the evidence and makes the final decision. No AI-generated score or recommendation replaces that authority.

Situation 3

Diagnosis:

The request did not name the proposal as the only factual source, define how to handle missing information, or prohibit added facilities and dates.

Targeted revision:

Summarise the office move proposal for staff who have not read it. Use only the supplied approved proposal for facts. Include location, proposed timing, stated facilities, expected staff actions, and unresolved questions. If any item is absent or uncertain, write Not stated or Not confirmed. Do not add transport, parking, cafeteria, cost, or opening-date claims. Return a 250-word draft with headings. The project owner must compare every factual statement with the proposal before sharing.

Reflection

Which specification field prevented the largest likely error in your work? Explain in one sentence.