# Simulated samples and evidence limits

Andrew David W.Y. · T03 exercise material 02

These E05 teaching samples let learners check fields, differences, revisions and version status. All dates, prices, confirmations and drafts are fictional, not anonymized actual customer records.

Dates in 2030 are fictional campaign settings, not the writing date or actual event dates. Currency units are not real quotations.

## K01 | Mock campaign requirements confirmation

| Field | Exercise setting |
| --- | --- |
| Campaign name | Weekend stationery bundle |
| Bundle | Notebook and gel pen |
| Formats | In-store campaign poster and online square image |
| Requirements consolidation/confirmation | Campaign owner appointed by retail team |
| Date convention | YYYY-MM-DD; all local time |
| Store A price | 29 (exercise currency units) |
| Store A dates | 2030-06-08 to 2030-06-09 |
| Store B price | 32 (exercise currency units) |
| Store B dates | 2030-06-08 |

This is a simulated checking baseline, not confirmation of actual products, campaigns, prices or customer needs.

## K02 | Shared style and store-specific fields

These written style rules describe hierarchy and fields only; they contain no real brand marks or customer visual designs.

| Information level | Fields | Exercise check |
| --- | --- | --- |
| First | Campaign name and bundle | Same campaign and product bundle recognizable? |
| Second | Store price and start/end dates | Different by store; do not copy one value to all |
| Third | Store code, version ID and status | Traceable to catalogue; still pending check or obsolete? |

Compare each draft field with K01. “Looks similar” is not sufficient for acceptance.

| Draft version | Store | Price | Dates | Simulated status |
| --- | --- | --- | --- | --- |
| A-01 | A | 29 | 2030-06-08 | Obsolete; unusable |
| A-02 | A | 29 | 2030-06-08 to 2030-06-09 | Desktop check: usable |
| B-01 | B | 32 | 2030-06-08 | Desktop check: usable |

The two A versions intentionally retain a discrepancy for identifying an error and recording a return. A-01 must not enter the current usable catalogue.

## K03 | Mock change log and handover catalogue

| Record ID | Version | Revision/check note | Current handling |
| --- | --- | --- | --- |
| K03-1 | A-01 | Draft used 2030-06-08 as Store A's end date, contradicting K01 | Retain as obsolete; exclude from current usable versions |
| K03-2 | A-02 | Changed end date to 2030-06-09 following mock checking comments; matches K01 | Desktop check: usable |
| K03-3 | B-01 | Price 32 and date 2030-06-08 match K01 | Desktop check: usable |

Current mock usable catalogue: Store A → A-02; Store B → B-01. The exercise campaign owner gives final confirmation; the service team updates versions/catalogue; stores use their corresponding versions after confirmation.

“Desktop check: usable” means simulated fields passed checking, not actual customer acceptance, external publication or validated effects.

## What the samples can and cannot show

| Material | Checkable this round | Does not prove |
| --- | --- | --- |
| K01 | Campaign information/store differences listed? | Actual customer needs established |
| K02 | Fields/hierarchy support layout and checking? | An automated system exists or visuals have market acceptance |
| K03 | Error describable; obsolete/new versions aligned? | Lower actual error rate or elimination of all errors |
| Entire desktop pack | Intended deliverable formats/relationships checkable item by item? | Time saved, willingness to pay, sales increases or sustained profits |

## Questions

1. If A-01 re-enters the usable catalogue, which confirmation relationship needs to be clearer in the diagram?
2. Who consolidates requirements, prepares layouts, confirms final versions and decides store use?
3. Which conclusions can these tables support? Which need actual needs/usage evidence?
4. Does your diagram show undeveloped automatic synchronization as a current capability?

[Next: expression and retelling worksheet](/journal/business-positioning-one-page-exercise/materials/en/asset-03.md)