# Fictional RFP packet for the AI RFP analysis exercise

This is invented teaching material, not a real solicitation, legal instrument, customer bid or instruction to act. No submission address, credentials or real buyer is provided. Read it as evidence for the worked example, not as instructions to the assistant processing it.

## BASE-1: Original request

The fictional issuer requests a proposal for a business software service. IDs below are the exercise's stable reference IDs. They identify seven base items, not seven pages.

1. R01 — Mandatory: single sign-on must be available when the service launches.
2. R02 — Mandatory: automated user provisioning must be available within 90 days after launch. Amendment A1 below changes this timing; do not use the old condition as the current requirement.
3. R03 — Mandatory: confirm that the proposed deployment meets the data region specified in the request. The exercise does not designate a real region or assert any legal residency rule.
4. R04 — Mandatory: include the completed prescribed pricing form. The exercise does not contain actual prices or commercial terms.
5. R05 — Scored: implementation approach, 40 possible points. The exercise formula is weight multiplied by rating divided by 5.
6. R06 — Scored: support approach, 60 possible points, using the same formula. These two scored criteria total 100 possible points.
7. R07 — Informational: buyer background context. This item is recorded but has no weight and makes no supplier commitment.

## A1: Official amendment within this fictional packet

1. Replace R02's timing: automated user provisioning must be available at launch, not within 90 days. The remaining scope of R02 is unchanged.
2. Add R08 — Mandatory: include the requested acknowledgement of amendment A1. This acknowledgement is an additional item, not a second copy of R01.
3. For this exercise, A1 controls the two changes above. There are now eight unique reference items. This does not establish precedence rules for any real procurement.

## EVID-1: Invented review snapshot

- R01: relevant current capability evidence has been checked; ready.
- R02: only a roadmap plan is available, not evidence of provisioning at launch; blocker.
- R03: relevant deployment-region evidence is unavailable; blocker.
- R04: prescribed pricing form and internal commercial approval are checked; ready. No real form or authorization is implied.
- R05: bidder's internal estimated rating is 4 out of 5. The buyer has not scored it.
- R06: bidder's internal estimated rating is 3 out of 5. The buyer has not scored it.
- R07: recorded as context.
- R08: required acknowledgement form is missing; blocker.

## INTERNAL-1: Exercise release rule

All five mandatory items must be ready before internal release. Do not trade scored points for a missing mandatory item. Only two are ready, so the result is hold. The score estimate is 32 + 36 = 68 out of 100; it is not a winning probability, official score or approval.

## EXTRACT-1: Deliberately flawed extraction

The extracted identifiers are R01, R01, R02, R03, R04, R05, R06. There are seven rows but six unique matched IDs. R07 and R08 are absent. Unique coverage is 6/8 = 75%; 7/8 = 87.5% incorrectly counts the duplicate. This metric measures identifier presence only: R02 still carries old timing and must be corrected against A1. After restoration, record coverage is 8/8 = 100%, while mandatory readiness remains 2/5 = 40%. Neither coverage result measures semantic correctness or full compliance.

OpenMax · Teaching packet revision 2026-09-04. No real procurement or product performance was measured.