The task and its limits
Correct CSV punctuation does not make the values correct. Practise separating a repeated slip, an explicit zero, a missing field and a conflicting quantity before accepting a proposed record.
Practice goal: Create one reviewed row per fictional request ID, retaining source text and explicitly marking missing or conflicting fields.
Use only the invented information below. Do not paste real emails, personnel records, customer details or confidential business records. Changing a name does not establish permission to upload a real record.
Read the complete fictional source
- [F1] Use these invented stationery requests only. Output columns, in order: request_id,label,quantity,needed_by,review_status. IDs are text; keep their leading zeros. An explicit 0 is a real quantity. For a missing field write NOT_SUPPLIED; for incompatible values on the same ID write CONFLICT in that field. These are exercise conventions, not a universal record standard.
- [F2] Slip A: request 0017; label Folders, "blue"; quantity 4; needed_by 2026-10-20. Slip A-copy repeats every field of A exactly and is a duplicate, not a second request.
- [F3] Slip B: request 0018; label Dividers; quantity 0; needed_by is blank. Keep 0 and mark the date NOT_SUPPLIED; do not treat 0 as a missing quantity.
- [F4] Slip C: request 0019; label Index cards; quantity 3; needed_by 2026-10-22. Slip C-alternate has the same ID, label and date but quantity 6. Neither is identified as newer or authoritative. Do not choose a quantity without clarification.
- [F5] Produce one row per ID. Use review_status ready_for_review if all fields agree and are supplied, needs_date for only a missing date, and needs_quantity_review for the quantity conflict. ready_for_review means awaiting a person’s check; it does not mean approved, ordered or sent.
- [F6] CSV convention for this exercise: separate fields with commas, use one header and one line per record, quote a field containing a comma or quote, and double embedded quotes. Example: the text A, "B" becomes "A, ""B""". View the text locally; importing into a spreadsheet may reinterpret IDs, so check its import settings rather than assuming quotes preserve zeros.
- [F7] Do not total the uncertain quantities, submit requests or replace missing dates with today. Provide the three corrected rows and a short list of unresolved questions. No addresses, customer records, tax forms or real purchases are involved.
You can complete this on paper or in a local document. No external account, upload or purchase is needed.
Try it, then inspect an authored error example
Draft your answer before reading the correction. Optional: use only this fictional prompt in a tool your organization permits. Do not connect accounts, upload other files or send messages for this task.
Using only F1–F7, extract a CSV with the exact five-column header and one row per request ID. Explain duplicate handling, explicit zero, blank date and conflicting quantity. Flag the unresolved date and quantity without deciding them. Never claim the requests were approved or sent.
Complete fictional facts:
- [F1] Use these invented stationery requests only. Output columns, in order: request_id,label,quantity,needed_by,review_status. IDs are text; keep their leading zeros. An explicit 0 is a real quantity. For a missing field write NOT_SUPPLIED; for incompatible values on the same ID write CONFLICT in that field. These are exercise conventions, not a universal record standard.
- [F2] Slip A: request 0017; label Folders, "blue"; quantity 4; needed_by 2026-10-20. Slip A-copy repeats every field of A exactly and is a duplicate, not a second request.
- [F3] Slip B: request 0018; label Dividers; quantity 0; needed_by is blank. Keep 0 and mark the date NOT_SUPPLIED; do not treat 0 as a missing quantity.
- [F4] Slip C: request 0019; label Index cards; quantity 3; needed_by 2026-10-22. Slip C-alternate has the same ID, label and date but quantity 6. Neither is identified as newer or authoritative. Do not choose a quantity without clarification.
- [F5] Produce one row per ID. Use review_status ready_for_review if all fields agree and are supplied, needs_date for only a missing date, and needs_quantity_review for the quantity conflict. ready_for_review means awaiting a person’s check; it does not mean approved, ordered or sent.
- [F6] CSV convention for this exercise: separate fields with commas, use one header and one line per record, quote a field containing a comma or quote, and double embedded quotes. Example: the text A, "B" becomes "A, ""B""". View the text locally; importing into a spreadsheet may reinterpret IDs, so check its import settings rather than assuming quotes preserve zeros.
- [F7] Do not total the uncertain quantities, submit requests or replace missing dates with today. Provide the three corrected rows and a short list of unresolved questions. No addresses, customer records, tax forms or real purchases are involved.
Authored flawed sample, not an actual provider response:
request_id,label,quantity,needed_by,review_status 17,Folders, "blue",4,2026-10-20,approved 17,Folders, "blue",4,2026-10-20,approved 18,Dividers,NOT_SUPPLIED,2026-10-12,approved 19,Index cards,6,2026-10-22,approved
Check the source and revise
-
The ID 0017 must retain its leading zeros. A-copy repeats the same request, so it produces no extra row. Record that the duplicate was found rather than silently counting it twice.
-
The label contains a comma and double quotes. Unquoted text splits it into extra CSV fields. Enclose it in quotes and double the internal quotes; parsing checks structure, not whether the source was copied correctly.
-
Slip B explicitly supplies 0, which must stay 0. Its date is missing, so use NOT_SUPPLIED. The invented 2026-10-12 date has no source and must be removed.
-
Slip C provides two incompatible quantities with no authority ordering. Use CONFLICT and needs_quantity_review. Do not select 6, add 3+6 or assume the second slip is newer.
-
All approval labels are unsupported. Even the complete row is only ready_for_review. Ask for the missing 0018 date and authoritative 0019 quantity; do not submit or total uncertain requests.
One supported correction:
request_id,label,quantity,needed_by,review_status
0017,"Folders, ""blue""",4,2026-10-20,ready_for_review
0018,Dividers,0,NOT_SUPPLIED,needs_date
0019,Index cards,CONFLICT,2026-10-22,needs_quantity_review
Review notes: A-copy is an exact duplicate of 0017, so there are 3 unique request rows. Confirm the needed-by date for 0018 and which quantity is authoritative for 0019. Until then, retain the flags. Nothing has been approved, ordered or sent. The CSV is an authored local-text example, not a tested business-system import.
Check your answer:
- Exactly five columns in the supplied order and three unique request IDs with leading zeros.
- The parsed first label equals Folders, "blue"; its comma stays inside one field.
- 0018 keeps quantity 0 and date NOT_SUPPLIED.
- 0019 has quantity CONFLICT; neither value is silently chosen or added.
- Use only the defined review statuses and preserve both unresolved questions; claim no approval or action.
Different wording can satisfy these checks. Recheck the facts after any rewrite.
Apply the checking habit carefully
Begin real extraction work only through an approved process with appropriate data access. Check schema, individual values and unresolved conflicts separately. Do not paste actual documents into this practice or assume a name change grants upload permission. This example is not tax preparation, contract review, financial reporting or a promise to save time.
Sources and a next step
Primary guidance checked on 2026-10-12. The references support source checking, privacy boundaries and clear presentation; the task facts and sample answers are invented. Use the references for their stated checking, privacy or formatting guidance. They do not establish tool performance, professional competence or approval of a real workflow.
- Common Format and MIME Type for Comma-Separated Values (CSV) Files
- Generative Artificial Intelligence Profile
- Protecting Personal Information: A Guide for Business
Keep real work within your organization’s approved data and review process. These exercises do not establish tested accessibility, time savings, job competence or a professional qualification. No provider trial or human professional review is claimed.
Start free Module 1: account sign-in is required; no card is needed. Or read general AI learning guidance. Keep your practice answer in your own local document if you want to return to it; this page does not save it to your account.
Frequently asked questions
- If the CSV parses, may I treat it as accurate?
- No. Parsing can catch field-count or quoting problems, but a well-formed row can still contain invented dates or the wrong quantity. Compare each value with the source and review conflict flags.
- May I replace the invented information with real business records?
- No. Use only the supplied fiction in this practice. A changed name, internal tool or paid account does not by itself establish permission to share a real record. Follow your organization’s approval process for real work.
- Do I need an AI subscription to complete the task?
- No. Read the source, write an answer and use the explained feedback. An external tool trial is optional; no provider was run to produce these samples.
- How should I handle a fact that is not supplied?
- Say that it is not supplied and ask the appropriate owner through an approved route. Do not turn a plausible guess into a deadline, permission, service or reported result.
- What should I keep so I can practise again?
- Keep the supplied facts, your draft and a short note explaining your corrections in a local document. This page does not save your answer. The linked free Module 1 requires sign-in, with no card needed.
Related reading
- AI for Small Business Owners
- /ai-for/generalcross-persona
