These are original teaching examples with fictional data. The expected outcomes describe how to judge results; they are not measured or recorded model responses.

Write an email to a client

BEFORE
Write a professional email about a delay.

<request>
  <goal>Tell the client that delivery moves from 12 to 15 November. Ask them to confirm the new date.</goal>
  <method>Use only supplied facts. Accept responsibility without inventing causes or promises. Keep the tone direct and polite.</method>
  <attachments>Project: portal upgrade. Verified reason: testing is still underway. Contact: Marta, a fictional name.</attachments>
  <output_format>Subject and body in English, up to 120 words. End with one request to confirm.</output_format>
</request>

The first version leaves dates, audience and reasons to the model. The second defines the facts, responsibility and action requested from the client.
Check for both dates, testing and the confirmation request. There should be no discounts, invented technical causes or unagreed guarantees.

Turn meeting notes into tasks

BEFORE
Summarise this meeting.

<request>
  <goal>Turn notes into a task list to share with the team.</goal>
  <method>Separate decisions and tasks. Do not invent owners or deadlines. Write “to be agreed” in missing fields.</method>
  <attachments>Luca checks the backup by Friday. The team chooses a two-stage release. The manual needs updating; no owner or deadline agreed. Fictional names and scenario.</attachments>
  <output_format>One sentence on decisions, then a table with task, owner, deadline and open question.</output_format>
</request>

A summary can lose the operational actions. The requested format shows what the team needs to work on and what still needs agreement.
The backup should name Luca and Friday; the manual should have “to be agreed” for both owner and deadline. The two-stage release is a decision, not a deadline.

Compare two proposals

BEFORE
Which quote is better?

<request>
  <goal>Prepare a preliminary comparison of two proposals for an information website. The available budget is EUR 5,000.</goal>
  <method>Compare only supplied facts. Do not assume an unmentioned service is included or excluded. Flag questions for suppliers before deciding.</method>
  <attachments>A: EUR 4,200, 6 weeks, maintenance unspecified. B: EUR 4,800, 8 weeks, 12 months of maintenance included. VAT and content unspecified in both. Fictional proposals.</attachments>
  <output_format>Table with cost, schedule, maintenance and unknowns; then three supplier questions. No final choice based on this data alone.</output_format>
</request>

“Better” depends on criteria. The revised prompt states the budget and avoids treating unknown conditions as confirmed facts.
Both prices are below EUR 5,000 before any VAT; the total budget still needs checking. Questions should cover VAT, content and maintenance in A.