# Canyon Response Logistics proposal sprint

**Case packet version:** 2026.08.31-practice-3

This is a fictional, sanitized training case. Solicitation identifiers, agencies, companies, people, pricing, and performance records are invented and are not legal, contracting, pricing, or government representations advice.

## Case brief · CB01

Canyon Response Logistics, a fictional small business, is considering a federal request for quotations for emergency warehouse staging. The official package was downloaded on September 3 and requires electronic submission by 2:00 p.m. Eastern on September 18. It contains 47 stated requirements, a price schedule with 12 line items, two mandatory representations, three past-performance examples, and a 12-page technical limit. An amendment issued September 10 changes the delivery window from 30 days to 14 days, replaces one line-item quantity, and requires explicit amendment acknowledgment. The capture lead's calendar still uses the original deadline in Mountain Time and the draft compliance matrix has not incorporated the amendment. Operations believes 14-day delivery is possible only if a subcontracted warehouse is available; the subcontractor supplied an unsigned availability email but no binding commitment. Finance's workbook totals $486,200, while the price form totals $468,200 because a freight row is omitted. A resume says the proposed project manager led a $3 million federal program, but the approved employment record shows the person served as deputy for nine months. One past-performance reference has not granted current contact permission. The draft technical narrative is 13.5 pages before final graphics. The company president may sign offers up to $500,000, but the proposal coordinator has no signature or certification authority. The government portal requires multi-factor authentication and has a 25-megabyte package limit; the current folder is 31 megabytes and contains working notes that should not be submitted. Learners must qualify the opportunity, rebuild compliance control, coordinate evidence and review, and demonstrate a submission process. They must not invent commitments, alter official instructions, or represent that training guarantees award or eligibility.

## Case record

- **F01 · confirmed:** The official submission deadline is September 18 at 2:00 p.m. Eastern.
- **F02 · confirmed:** The base package contains 47 requirements, 12 price line items, and two mandatory representations.
- **F03 · confirmed:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **F04 · confirmed:** The internal calendar still displays the original deadline in Mountain Time.
- **F05 · confirmed:** The compliance matrix and current drafts do not reflect the amendment.
- **F06 · provisional:** A proposed subcontract warehouse supplied only an unsigned availability email.
- **F07 · conflicting:** Finance totals $486,200 and the required price form totals $468,200.
- **F08 · conflicting:** The resume claims program leadership while approved records show a deputy role for nine months.
- **F09 · confirmed:** One proposed past-performance contact has not provided current reference permission.
- **F10 · confirmed:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **F11 · confirmed:** The coordinator lacks authority to sign the offer or certify representations.
- **F12 · confirmed:** The current upload folder is 31 megabytes and includes internal working notes.

## Module assignments and operating guides

### Module 1 — Qualify before bidding

**Task mode:** bounded-case-starter

Evaluate strategic fit, delivery feasibility, authority, evidence, schedule, and bid cost before committing the team.

**Deliverable:** A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.

**Provided inputs**

- **M01-I01 · case-fact · F01:** The official submission deadline is September 18 at 2:00 p.m. Eastern.
- **M01-I02 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M01-I03 · case-fact · F06:** A proposed subcontract warehouse supplied only an unsigned availability email.
- **M01-I04 · case-fact · F07:** Finance totals $486,200 and the required price form totals $468,200.
- **M01-I05 · case-fact · F10:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **M01-I06 · case-fact · F11:** The coordinator lacks authority to sign the offer or certify representations.
- **M01-I07 · case-fact · F12:** The current upload folder is 31 megabytes and includes internal working notes.
- **M01-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M01-S01 · assignment-scope · F01, F03, F06, F07, F10, F11, F12:** Build a starter version of “A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F01, F03, F06, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M01-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm official deadline, amendment, warehouse evidence, price conflict, page overage, signature boundary, and upload-folder condition.
- [ ] Treat the current solicitation and amendment as controlling; internal calendars and drafts are secondary records.
- [ ] Identify bid, price, representation, and submission decision owners by role only.

### Operating procedure

1. State the bid decision and cite the controlling deadline and amendment before considering internal schedule assumptions.
2. List evidence supporting pursuit separately from disqualifiers, unresolved dependencies, and authority limits.
3. Treat the unsigned warehouse email and 14-day delivery as dependencies requiring evidence rather than confirmed capability.
4. Record the price conflict, page overage, signature boundary, and upload-folder exposure as decision risks.
5. Compare proceed, proceed conditionally, pause, and no-bid choices with explicit tradeoffs and closure evidence.
6. Route bid authorization, price approval, representations, and final submission to their authorized owners.
7. Quality-check source priority, deadline expression, amendment status, authority, and absence of invented approvals.

### Field-by-field guidance — M01-A01

| Field | What high-quality completion requires |
|---|---|
| Decision | State the bounded bid/no-bid or conditional-pursuit decision under review. |
| Evidence for | List only supplied facts supporting continued pursuit and cite their inputs. |
| Evidence against | List disqualifiers, conflicts, gaps, and authority limits without resolving them by assumption. |
| Options and tradeoffs | Compare no-bid, pause, conditional proceed, and proceed only after defined closure evidence. |
| Decision owner | Use Authorized proposal lead or contracting reviewer; no named owner is supplied. |
| Required approval | Identify bid, price, representation, signature, and submission approvals still required. |
| Status | Use Draft decision, Blocked, Conditional, or Authorized disposition pending. |

### Completed supported example — M01-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Whether to continue the Canyon Response Logistics proposal sprint | Official deadline is September 18 at 2:00 p.m. Eastern. Source M01-I01 (F01, confirmed). | Price totals conflict; technical volume exceeds the limit; coordinator lacks signature authority; upload folder includes working notes. | Pause pending blocker closure; conditional proceed with owner assignments; no-bid if mandatory controls cannot close. | Authorized proposal lead or contracting reviewer | Bid, price, representations, signature, and final-submission approvals: not supplied. | Decision pending — blockers open |

### Completed known-gap example — M01-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Whether proposed warehouse evidence supports the amended 14-day delivery requirement | An unsigned availability email exists. Source M01-I03 (F06, provisional). | Signed commitment, capacity evidence, terms, and authorized delivery assessment are not supplied. | Hold dependency open; request approved evidence; no representation of confirmed warehouse availability. | Authorized proposal lead or contracting reviewer | Qualified delivery and subcontract commitment review: not supplied. | Gap open — delivery representation blocked |

### Supporting artifact build sequence

1. **M01-A02 · Disqualifier and owner register** — Produce a bounded, reviewable disqualifier and owner register from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M01-I02, M01-I03 and address M01-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M01-A03 · Opportunity decision-gate record** — Produce a bounded, reviewable opportunity decision-gate record from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M01-I03 and address M01-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop pursuit or submission when a mandatory disqualifier, deadline, price, representation, signature, or package control cannot close in time. |
| **Go** | Go conditionally when each blocker has an authorized owner, closure evidence, due point, and fallback. |
| **Escalate** | Escalate bid, pricing, subcontract, representations, and final submission authority to the authorized proposal or contracting owner. |

### Completion test

- [ ] The decision brief uses the official deadline and amendment as controlling evidence.
- [ ] All mandatory blockers and authority limits remain visible with no invented closure.
- [ ] The authorized owner can make a bounded bid/no-bid disposition from the brief.

### Artifact map

- **M01-A01 · Bid/no-bid decision brief:** Produce a bounded, reviewable bid/no-bid decision brief from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 1. Criteria: M01-EC01, M01-EC03, M01-EC04. Scoped inputs: M01-I01, M01-I04, M01-I05, M01-I06, M01-I07.
- **M01-A02 · Disqualifier and owner register:** Produce a bounded, reviewable disqualifier and owner register from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M01-EC02. Scoped inputs: M01-I02, M01-I03.
- **M01-A03 · Opportunity decision-gate record:** Produce a bounded, reviewable opportunity decision-gate record from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 1. Criteria: M01-EC03. Scoped inputs: M01-I03.

### Evidence criteria

- **M01-EC01:** Uses the current official solicitation and amendment as controlling sources
- **M01-EC02:** Treats warehouse availability and 14-day delivery as unresolved dependencies
- **M01-EC03:** Names who may authorize bid, price, representations, and final submission
- **M01-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Module 2 — Rebuild compliance

**Task mode:** bounded-case-starter

Create a delta-aware requirement matrix covering instructions, evaluation factors, deliverables, and acknowledgments.

**Deliverable:** A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.

**Provided inputs**

- **M02-I01 · case-fact · F02:** The base package contains 47 requirements, 12 price line items, and two mandatory representations.
- **M02-I02 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M02-I03 · case-fact · F04:** The internal calendar still displays the original deadline in Mountain Time.
- **M02-I04 · case-fact · F05:** The compliance matrix and current drafts do not reflect the amendment.
- **M02-I05 · case-fact · F07:** Finance totals $486,200 and the required price form totals $468,200.
- **M02-I06 · case-fact · F10:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **M02-I07 · case-fact · F12:** The current upload folder is 31 megabytes and includes internal working notes.
- **M02-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M02-S01 · assignment-scope · F02, F03, F04, F05, F07, F10, F12:** Build a starter version of “A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F02, F03, F04, F05, F07, F10, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M02-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm the aggregate 47 requirements, 12 price lines, and two representations are supplied, but exact requirement text and section/page locations are not.
- [ ] Confirm amendment, calendar, draft, price, page-limit, and upload-folder constraints remain separate.
- [ ] Use all 47 REQ rows; do not invent solicitation wording to make them appear complete.

### Operating procedure

1. Capture each known constraint in the principal matrix and cite the exact module input that establishes it.
2. Initialize REQ-01 through REQ-47 in the requirement register without populating absent section, page, or requirement text.
3. For each retrieved requirement in future work, copy exact text, section/page, amendment effect, owner, response location, evidence source, and review status.
4. Apply amendments by preserving the superseded base text and recording the changed delivery, quantity, or acknowledgment requirement separately.
5. Assign response owners and locations only when authorized records exist; otherwise mark owner and location not supplied.
6. Reconcile page, file-size, price, delivery, deadline, and acknowledgment constraints before declaring the matrix ready.
7. Run a 47-row completeness check and an amendment back-check; no row may be marked compliant from aggregate counts alone.

### Field-by-field guidance — M02-A01

| Field | What high-quality completion requires |
|---|---|
| Item ID | Use a stable constraint identifier distinct from REQ-01 through REQ-47. |
| Supported evidence | State the supplied deadline, amendment, price conflict, page overage, or folder condition exactly. |
| Source input ID | Cite the exact M02-Ixx input and preserve confidence. |
| Criterion or required state | Name the control required for compliance, such as current amendment, price-form agreement, page limit, or clean package. |
| Gap or learner proposal | State missing source text, threshold, response evidence, owner, or disposition; label any workflow proposal. |
| Owner or reviewer | Use Authorized proposal lead or contracting reviewer. |
| Status | Use Constraint confirmed, Gap open, Amendment pending, Conflict open, or Review pending. |

### Completed supported example — M02-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| CONSTRAINT-PRICE-01 | Finance totals $486,200 while the required price form totals $468,200. | M02-I05 (F07, conflicting) | All price artifacts must reconcile to the authorized required form before release. | Line-level reconciliation, correct authorized total, owner, and disposition: not supplied. | Authorized proposal lead and pricing reviewer | Conflict open — release blocker |

### Completed known-gap example — M02-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| CONSTRAINT-REQ-TEXT | The base package contains 47 requirements, but exact source text is not supplied. | M02-I01 (F02, confirmed) | Each requirement must be traced to exact base section/page and amendment effect. | Official base text, section/page, response owner, response location, and review status: not supplied. | Authorized proposal lead or contracting reviewer | Gap open — 47 rows unverified |

### Supporting artifact build sequence

1. **M02-A02 · Forty-seven-requirement gap register** — Produce a bounded, reviewable forty-seven-requirement gap register from cited packet evidence while exposing unsupported fields and required approvals. Build 47 rows from M02-I01 and address M02-EC01. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M02-A03 · Amendment-control register** — Produce a bounded, reviewable amendment-control register from cited packet evidence while exposing unsupported fields and required approvals. Build 3 rows from M02-I02, M02-I03, M02-I04 and address M02-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

#### M02-A02 · Forty-seven-requirement gap register

**Reference-only completed row.** Use it to understand the evidence boundary; do not present it as your own completed work.

**Criterion demonstrated:** M02-EC01

**Why this row is included:** This completed training row demonstrates the declared criterion route for Forty-seven-requirement gap register without claiming live execution or approval.

| Requirement ID | Base section/page | Exact requirement text | Amendment effect | Owner | Response location | Evidence source | Review status | Gap/request |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| REQ-01 | Not supplied | Not supplied; aggregate existence only is confirmed. | Not determined for this requirement; amendment one changes delivery, quantity, and acknowledgment generally. | Not supplied — authorized proposal lead must assign after source retrieval. | Not supplied | M02-I01 (F02, confirmed); M02-I02 (F03, confirmed) for amendment context only | Source retrieval and amendment review pending | Retrieve official base section/page and exact text, then compare amendment one without inventing requirement content. |

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop compliance sign-off when any mandatory row lacks exact source text, amendment treatment, owner, response location, evidence, or review status. |
| **Go** | Go to controlled drafting only for rows whose current requirement and amendment effect are traceable. |
| **Escalate** | Escalate unresolved solicitation interpretation, pricing, representations, page, and submission controls to authorized reviewers. |

### Completion test

- [ ] All 47 REQ identifiers exist and no missing requirement text is fabricated.
- [ ] Known constraints are traceable, and the amendment register preserves superseded versus current requirements.
- [ ] No row is labeled compliant or complete without exact source, owner, response location, and review evidence.

### Artifact map

- **M02-A01 · Known-constraint compliance matrix:** Produce a bounded, reviewable known-constraint compliance matrix from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 6. Criteria: M02-EC02. Scoped inputs: M02-I02, M02-I03, M02-I04, M02-I05, M02-I06, M02-I07.
- **M02-A02 · Forty-seven-requirement gap register:** Produce a bounded, reviewable forty-seven-requirement gap register from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 47. Criteria: M02-EC01. Scoped inputs: M02-I01.
- **M02-A03 · Amendment-control register:** Produce a bounded, reviewable amendment-control register from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 3. Criteria: M02-EC03. Scoped inputs: M02-I02, M02-I03, M02-I04.

### Evidence criteria

- **M02-EC01:** Cites supplied fact IDs and creates columns for section, page, exact requirement, owner, artifact, and status without inventing missing solicitation text
- **M02-EC02:** Flags the known page, file-size, pricing, delivery, and acknowledgment constraints
- **M02-EC03:** Explains how superseded requirements would be preserved once the official base document and amendment are available

### Module 3 — Recover the calendar

**Task mode:** bounded-case-starter

Build a backward schedule with review windows, dependencies, and a documented time-zone conversion.

**Deliverable:** A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.

**Provided inputs**

- **M03-I01 · case-fact · F01:** The official submission deadline is September 18 at 2:00 p.m. Eastern.
- **M03-I02 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M03-I03 · case-fact · F04:** The internal calendar still displays the original deadline in Mountain Time.
- **M03-I04 · case-fact · F07:** Finance totals $486,200 and the required price form totals $468,200.
- **M03-I05 · case-fact · F10:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **M03-I06 · case-fact · F11:** The coordinator lacks authority to sign the offer or certify representations.
- **M03-I07 · case-fact · F12:** The current upload folder is 31 megabytes and includes internal working notes.
- **M03-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M03-S01 · assignment-scope · F01, F03, F04, F07, F10, F11, F12:** Build a starter version of “A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F01, F03, F04, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M03-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm the official Eastern deadline and internal Mountain-time discrepancy.
- [ ] Do not calculate a local deadline without the year and date-specific conversion evidence.
- [ ] Identify price and representation approvals that must precede packaging.

### Operating procedure

1. Anchor the calendar on September 18 at 2:00 p.m. Eastern and cite F01.
2. Mark the year and date-specific local conversion not supplied instead of using the internal Mountain-time entry.
3. Sequence compliance, amendment, price, representation, page, package, and submission reviews backward from the official deadline.
4. Place price reconciliation and representation authorization before final packaging or upload preparation.
5. Assign accountable owner and backup roles to each critical handoff without inventing staff names.
6. Add exception triggers for deadline conflict, page overage, price mismatch, signature boundary, and package contamination.
7. Quality-check time zone, dependencies, review gates, and absence of invented dates or completed milestones.

### Field-by-field guidance — M03-A01

| Field | What high-quality completion requires |
|---|---|
| Milestone or date | Use the official deadline or a proposed relative milestone; mark calendar dates not supplied. |
| Deliverable | Name the specific compliance, price, representation, page, package, or submission output. |
| Evidence | Cite the supplied deadline or constraint and preserve its status. |
| Owner | Use accountable proposal, pricing, representation, packaging, or submission roles only. |
| Dependency | State prerequisite evidence or approval that must close first. |
| Review gate | Define the evidence and authorized disposition required to advance. |
| Exception | Name deadline, version, price, page, authority, or package problem. |
| Status | Use Proposed, Conflict open, Blocked, Review pending, or Ready for authorized review. |

### Completed supported example — M03-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Milestone or date | Deliverable | Evidence | Owner | Dependency | Review gate | Exception | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| September 18, 2:00 p.m. Eastern; year and local conversion not supplied | Authorized final submission | M03-I01 (F01, confirmed) | Authorized submission owner; name not supplied | Price, representations, page limit, package, signature, and amendment acknowledgment must be approved. | Proceed only after authorized package-readiness disposition and confirmed portal plan. | Internal calendar uses original Mountain-time deadline. M03-I03 (F04, confirmed). | Official deadline recorded — conversion gap open |

### Completed known-gap example — M03-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Milestone or date | Deliverable | Evidence | Owner | Dependency | Review gate | Exception | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Date-specific internal cutoff | Verified local deadline and team handoff schedule | Official Eastern deadline supplied; year and correct local conversion not supplied. | Authorized proposal lead | Official year, date-specific time-zone conversion, and approved internal buffer. | Do not publish the local cutoff until verified against the controlling source. | Current internal Mountain-time entry conflicts with official deadline. | Gap open — schedule not final |

### Supporting artifact build sequence

1. **M03-A02 · Responsibility map** — Produce a bounded, reviewable responsibility map from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I02 and address M03-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M03-A03 · Deadline-verification request** — Produce a bounded, reviewable deadline-verification request from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M03-I03 and address M03-EC01, M03-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
3. **M03-A04 · Daily exception-report template** — Produce a bounded, reviewable daily exception-report template from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I04 and address M03-EC01. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop packaging or submission when deadline conversion, price, representations, version, page limit, or authority remains unresolved. |
| **Go** | Go to the next calendar gate when its dependencies, owner, backup, and evidence are visible. |
| **Escalate** | Escalate official deadline interpretation and submission authority to the authorized proposal or contracting reviewer. |

### Completion test

- [ ] The official Eastern deadline is preserved and missing year/local conversion remain explicit.
- [ ] Critical approvals precede packaging and submission.
- [ ] Each handoff has accountable and backup roles without invented staff names.

### Artifact map

- **M03-A01 · Proposal calendar:** Produce a bounded, reviewable proposal calendar from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M03-EC01. Scoped inputs: M03-I01, M03-I03, M03-I05, M03-I06, M03-I07.
- **M03-A02 · Responsibility map:** Produce a bounded, reviewable responsibility map from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M03-EC02. Scoped inputs: M03-I02.
- **M03-A03 · Deadline-verification request:** Produce a bounded, reviewable deadline-verification request from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 1. Criteria: M03-EC01, M03-EC03. Scoped inputs: M03-I03.
- **M03-A04 · Daily exception-report template:** Produce a bounded, reviewable daily exception-report template from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M03-EC01. Scoped inputs: M03-I04.

### Evidence criteria

- **M03-EC01:** Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence
- **M03-EC02:** Places price and representation approval before packaging
- **M03-EC03:** Assigns an accountable owner and backup to the critical handoffs evidenced by the packet without inventing staff names

### Module 4 — Repair evidence claims

**Task mode:** bounded-case-starter

Validate resume, past performance, subcontractor, delivery, and price-support statements.

**Deliverable:** An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.

**Provided inputs**

- **M04-I01 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M04-I02 · case-fact · F06:** A proposed subcontract warehouse supplied only an unsigned availability email.
- **M04-I03 · case-fact · F07:** Finance totals $486,200 and the required price form totals $468,200.
- **M04-I04 · case-fact · F08:** The resume claims program leadership while approved records show a deputy role for nine months.
- **M04-I05 · case-fact · F09:** One proposed past-performance contact has not provided current reference permission.
- **M04-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M04-S01 · assignment-scope · F03, F06, F07, F08, F09:** Build a starter version of “An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F03, F06, F07, F08, F09, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M04-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm the amendment, provisional warehouse evidence, price conflict, resume conflict, and missing reference permission.
- [ ] Separate a claim defect from a missing source record and from an authorized corrected claim.
- [ ] Do not contact references or rewrite resumes as approved evidence in this exercise.

### Operating procedure

1. Create one ledger entry for each material delivery, price, role, date, scope, and permission claim.
2. Record the claim as currently stated and cite the supplied fact showing confirmation, conflict, provisional status, or missing permission.
3. Identify the exact underlying source needed to support or correct the claim.
4. Distinguish correction text as a learner proposal and preserve the original claim and version history.
5. Route price, resume, subcontract availability, delivery, and reference permission to their authorized source owners.
6. Block claim use until the source, permission, reviewer, and corrected version are documented.
7. Quality-check every ledger entry for role, dates, value, scope, delivery, price, permission, and no invented source.

### Field-by-field guidance — M04-A01

| Field | What high-quality completion requires |
|---|---|
| Entry ID | Use a stable claim identifier tied to one statement. |
| Issue or event | Quote or summarize the claim defect without adding unsupported detail. |
| Evidence and source ID | Cite the exact M04-Ixx fact and confidence. |
| Risk or impact | State the compliance, credibility, pricing, delivery, or permission exposure. |
| Owner | Use the authorized source owner or proposal reviewer role. |
| Bounded next step | Request or locate the specific source, then propose correction for review. |
| Review point | Define when the claim must be rechecked before reuse. |
| Status | Use Confirmed defect, Conflict open, Permission missing, Source pending, or Approved use not supplied. |

### Completed supported example — M04-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-ROLE-01 | Resume claims program leadership while approved records show a deputy role for nine months. | M04-I04 (F08, conflicting) | Role and duration may be materially overstated in the proposal. | Authorized resume source owner and proposal reviewer | Approved role and date source: not supplied. Obtain it, draft a source-faithful correction, and retain both versions. | Before resume or past-performance content is released. | Conflict open — claim use blocked |

### Completed known-gap example — M04-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-PERM-01 | Proposed past-performance contact has not provided current reference permission. | M04-I05 (F09, confirmed) | Unpermitted contact use may create privacy, relationship, or compliance exposure. | Authorized past-performance source owner | Record a permission request requirement; do not contact or claim permission in this exercise. | Before naming the contact or submitting the reference. | Permission not supplied — use blocked |

### Supporting artifact build sequence

1. **M04-A02 · Claim-correction plan** — Produce a bounded, reviewable claim-correction plan from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M04-I02 and address M04-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M04-A03 · Source-permission register** — Produce a bounded, reviewable source-permission register from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M04-I01, M04-I03, M04-I04, M04-I05 and address M04-EC02, M04-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop use of any claim whose role, date, value, scope, delivery, price, or permission lacks authorized source support. |
| **Go** | Go to review when original claim, source conflict, proposed correction, owner, and version history are visible. |
| **Escalate** | Escalate price, resume, subcontract, delivery, and reference-permission claims to their authorized source owners. |

### Completion test

- [ ] All five supplied claim issues are separated into source, defect, correction, permission, and owner fields.
- [ ] No corrected claim is represented as approved or used.
- [ ] Version history and review status preserve original and proposed wording.

### Artifact map

- **M04-A01 · Claim-evidence ledger:** Produce a bounded, reviewable claim-evidence ledger from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M04-EC01. Scoped inputs: M04-I01.
- **M04-A02 · Claim-correction plan:** Produce a bounded, reviewable claim-correction plan from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M04-EC03. Scoped inputs: M04-I02.
- **M04-A03 · Source-permission register:** Produce a bounded, reviewable source-permission register from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M04-EC02, M04-EC03. Scoped inputs: M04-I01, M04-I03, M04-I04, M04-I05.

### Evidence criteria

- **M04-EC01:** Uses F03, F06, F07, F08, and F09 to separate known claim defects from missing source records
- **M04-EC02:** Provides fields for role, dates, value, scope, delivery, price, and permission without inventing the unavailable underlying documents
- **M04-EC03:** Routes each corrected excerpt and commitment claim to the authorized source owner before use

### Module 5 — Run controlled reviews

**Task mode:** bounded-case-starter

Plan compliance, content, price, and final-production reviews with finding closure.

**Deliverable:** A review plan and finding log showing retest and authorized disposition.

**Provided inputs**

- **M05-I01 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M05-I02 · case-fact · F05:** The compliance matrix and current drafts do not reflect the amendment.
- **M05-I03 · case-fact · F07:** Finance totals $486,200 and the required price form totals $468,200.
- **M05-I04 · case-fact · F10:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **M05-I05 · case-fact · F11:** The coordinator lacks authority to sign the offer or certify representations.
- **M05-I06 · case-fact · F12:** The current upload folder is 31 megabytes and includes internal working notes.
- **M05-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M05-S01 · assignment-scope · F03, F05, F07, F10, F11, F12:** Build a starter version of “A review plan and finding log showing retest and authorized disposition.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F03, F05, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M05-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm amendment omission, price conflict, page overage, signature limit, and upload-folder condition.
- [ ] Define review entry criteria and severity before assigning reviewers.
- [ ] No reviewer names, retest results, dispositions, or approved package versions are supplied.

### Operating procedure

1. Define each review’s purpose, entry evidence, reviewer role, severity scale, due point, and exit evidence.
2. Sequence compliance, pricing, technical/page, representations, and package reviews against one controlled version.
3. Create findings for amendment omission and price mismatch with exact source IDs and release-blocker severity.
4. Assign corrective evidence and retest method without rewriting the artifact for its owner.
5. Record authorized disposition separately from finding closure and never infer approval from a retest request.
6. Block release when the wrong version, unresolved price, amendment, page, signature, or internal-note issue remains.
7. Quality-check reviewer independence, version identity, finding trace, owner, retest evidence, and disposition status.

### Field-by-field guidance — M05-A01

| Field | What high-quality completion requires |
|---|---|
| Step or milestone | Name a specific review stage and purpose. |
| Trigger or date | State the entry condition or mark due time not supplied. |
| Evidence and source ID | Cite the facts that justify the review or blocker. |
| Owner | Use the authorized review role, not an invented person. |
| Gate or threshold | Define entry, severity, closure evidence, and authorized exit disposition. |
| Dependency or gap | Record missing current version, correction, reviewer, time, or retest evidence. |
| Status | Use Proposed review, Entry blocked, Finding open, Retest pending, or Disposition pending. |

### Completed supported example — M05-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Compliance review of amendment one | Before price, technical, and package release; exact review time not supplied. | M05-I01 (F03, confirmed); M05-I02 (F05, confirmed) | Authorized compliance reviewer | Current matrix and drafts must reflect changed delivery, quantity, and acknowledgment before release. | Corrected controlled version, reviewer identity, retest evidence, and disposition: not supplied. | Release blocker — finding and retest pending |

### Completed known-gap example — M05-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Package review for clean upload set | Before portal upload; exact cutoff not supplied. | M05-I06 (F12, confirmed) | Authorized package and submission reviewer | Only required files, no internal notes, and approved size/version controls may pass. | Portal size limit, clean package, hash, review evidence, and disposition: not supplied. | Entry blocked — package evidence missing |

### Supporting artifact build sequence

1. **M05-A02 · Finding and retest log** — Produce a bounded, reviewable finding and retest log from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M05-I02, M05-I03 and address M05-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M05-A03 · Authorized disposition record** — Produce a bounded, reviewable authorized disposition record from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M05-I03 and address M05-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop release while any material compliance, price, page, representation, version, signature, or package finding remains open. |
| **Go** | Go to authorized disposition only after a focused retest confirms the exact closure evidence on the controlled version. |
| **Escalate** | Escalate final finding disposition and release authority to the authorized proposal lead or contracting reviewer. |

### Completion test

- [ ] Every review names purpose, entry criteria, severity, owner, due point, and exit evidence.
- [ ] Unresolved compliance and price findings are release blockers.
- [ ] Review, retest, disposition, and package version remain distinct records.

### Artifact map

- **M05-A01 · Controlled review plan:** Produce a bounded, reviewable controlled review plan from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M05-EC01, M05-EC04. Scoped inputs: M05-I01, M05-I04, M05-I05, M05-I06.
- **M05-A02 · Finding and retest log:** Produce a bounded, reviewable finding and retest log from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M05-EC02. Scoped inputs: M05-I02, M05-I03.
- **M05-A03 · Authorized disposition record:** Produce a bounded, reviewable authorized disposition record from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 1. Criteria: M05-EC03. Scoped inputs: M05-I03.

### Evidence criteria

- **M05-EC01:** Defines reviewer purpose, entry criteria, severity, owner, and due time
- **M05-EC02:** Treats unresolved compliance and price gaps as release blockers
- **M05-EC03:** Uses version control so reviewers assess the correct package
- **M05-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Module 6 — Prove submission readiness

**Task mode:** bounded-case-starter

Design a clean-package and portal-submission simulation without uploading, signing, hashing, timestamping, or claiming receipt.

**Deliverable:** A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.

**Provided inputs**

- **M06-I01 · case-fact · F01:** The official submission deadline is September 18 at 2:00 p.m. Eastern.
- **M06-I02 · case-fact · F02:** The base package contains 47 requirements, 12 price line items, and two mandatory representations.
- **M06-I03 · case-fact · F03:** Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
- **M06-I04 · case-fact · F10:** The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
- **M06-I05 · case-fact · F11:** The coordinator lacks authority to sign the offer or certify representations.
- **M06-I06 · case-fact · F12:** The current upload folder is 31 megabytes and includes internal working notes.
- **M06-B01 · case-brief · CB01:** Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
- **M06-S01 · assignment-scope · F01, F02, F03, F10, F11, F12:** Build a starter version of “A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

**Completion boundary**

Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

**Workbook plan:** M06-WP01 · 2026.09.01-workbook-plan-2

### Prerequisite check

- [ ] Confirm official deadline, base-package counts, amendment acknowledgment, page overage, signature boundary, and upload-folder condition.
- [ ] Treat package hash, portal timestamp, receipt, retained version, and authorized signatures as future fields only.
- [ ] No upload, portal action, acknowledgment, signature, or receipt is supplied.

### Operating procedure

1. List every required package and portal control supported by the packet before preparing a readiness result.
2. Define evidence required for page limit, file size, clean files, price agreement, amendment acknowledgment, representations, and authorized signature.
3. Cite the source input for each check and distinguish fact supplied from result not supplied.
4. Assign role-level owners for content, price, representations, signature, packaging, and submission.
5. Use the manifest and mock receipt fields only as templates; never fabricate hash, timestamp, portal receipt, or retained version.
6. Block readiness if internal notes, page overage, price conflict, signature, or acknowledgment remain unresolved.
7. Quality-check manifest-to-checklist coverage, versions, permissions, exact deadline, and absence of implied submission.

### Field-by-field guidance — M06-A01

| Field | What high-quality completion requires |
|---|---|
| Check ID | Use a stable readiness-control identifier. |
| Control or check | Name the exact file, page, price, acknowledgment, signature, representation, or portal control. |
| Evidence required | Specify the file, comparison, approval, receipt, hash, or timestamp needed. |
| Source input ID | Cite the supplied fact that creates the control. |
| Owner | Use authorized content, pricing, signature, packaging, or submission role. |
| Result | Use Not tested, Fact supplied, Exception present, or Approval not supplied. |
| Exception or gap | State the exact missing or failing evidence. |
| Status | Use Blocking, Ready for review, Template only, or Submission not performed. |

### Completed supported example — M06-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| READY-PAGE-01 | Technical volume complies with stated page limit | Controlled final technical volume and independent page-count evidence. | M06-I04 (F10, confirmed) | Authorized technical-volume and compliance reviewer | Current draft exceeds its stated limit by 1.5 pages before final graphics. | Corrected final volume, final graphics impact, page-count evidence, and approval: not supplied. | Blocking — readiness not demonstrated |

### Completed known-gap example — M06-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| READY-PORTAL-01 | Portal package upload and receipt evidence | Approved package hash, upload timestamp, portal receipt, and retained submitted version. | M06-I06 (F12, confirmed, package condition only) | Authorized submission owner | No upload or receipt is supplied; current folder contains internal working notes. | Clean package, portal limit, hash, timestamp, receipt, and retained version: not supplied. | Template only — submission not performed |

### Supporting artifact build sequence

1. **M06-A02 · Package-manifest starter** — Produce a bounded, reviewable package-manifest starter from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I02, M06-I03, M06-I05 and address M06-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M06-A03 · Mock receipt template** — Produce a bounded, reviewable mock receipt template from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M06-I03 and address M06-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
3. **M06-A04 · Lessons-learned template** — Produce a bounded, reviewable lessons-learned template from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I04 and address M06-EC04. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop upload when any required file, size, page, price, acknowledgment, representation, signature, version, or package-cleanliness control is unresolved. |
| **Go** | Go to authorized upload only after every readiness check has traceable evidence and approval. |
| **Escalate** | Escalate signature, representations, amendment acknowledgment, and final submission to authorized owners. |

### Completion test

- [ ] The checklist covers required files, portal controls, page, package, signature, representations, and acknowledgment.
- [ ] Future hash, timestamp, receipt, and retained-version fields remain not supplied.
- [ ] No submission, signature, acknowledgment, or portal result is fabricated.

### Artifact map

- **M06-A01 · Submission-readiness checklist:** Produce a bounded, reviewable submission-readiness checklist from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M06-EC01. Scoped inputs: M06-I01, M06-I04, M06-I06.
- **M06-A02 · Package-manifest starter:** Produce a bounded, reviewable package-manifest starter from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M06-EC02. Scoped inputs: M06-I02, M06-I03, M06-I05.
- **M06-A03 · Mock receipt template:** Produce a bounded, reviewable mock receipt template from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 1. Criteria: M06-EC03. Scoped inputs: M06-I03.
- **M06-A04 · Lessons-learned template:** Produce a bounded, reviewable lessons-learned template from cited packet evidence while exposing unsupported fields and required approvals. Expected rows: 2. Criteria: M06-EC04. Scoped inputs: M06-I04.

### Evidence criteria

- **M06-EC01:** Lists the required-file and portal-size controls supported by F10 and F12 while leaving exact final files pending
- **M06-EC02:** Requires authorized signature, representations, and amendment acknowledgment without recording completion
- **M06-EC03:** Provides fields for a future package hash, portal timestamp, receipt, and retained version but does not fabricate those results
- **M06-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

## Ambiguities to preserve

### The subcontractor expresses availability but has not made an authorized commitment for the revised delivery period.

**Judgment required:** Decide whether to secure evidence, qualify the claim, redesign the approach, or recommend no-bid before the internal gate.

**Do not assume:** Do not present informal availability as committed capacity or guaranteed 14-day performance.

### The pricing discrepancy may be an omitted freight row, an outdated quantity, or both.

**Judgment required:** Reconcile the approved pricing source to every required line and identify who may approve the final offer.

**Do not assume:** Do not choose the lower or higher total without tracing scope, formula, amendment, and authority.

## Debrief guide

There is no single universal bid decision. A defensible recommendation shows how official requirements, evidence gaps, schedule, authority, and delivery risk affect the choice.

### Module 1

A potentially attractive opportunity can still be a no-bid if mandatory capacity or authority cannot be secured. The brief should distinguish a solvable gap from a disqualifying one.

**Strong evidence may include**

- Current source package
- Owned dependency and decision log

### Module 2

A complete matrix does more than count rows. It connects each instruction and evaluation requirement to content, proof, owner, review, and amendment status.

**Strong evidence may include**

- Requirement citations
- Amendment delta trace

### Module 3

Backward scheduling should protect review and authorization time, not merely fill every hour with drafting. Time-zone and portal constraints belong in the critical path.

**Strong evidence may include**

- Verified deadline conversion
- Dependency-aware calendar

### Module 4

Past-performance and resume claims should describe the documented role accurately. A narrower true claim is stronger than an inflated one that creates representation risk.

**Strong evidence may include**

- Approved source records
- Permission and claim ledger

### Module 5

Review findings need severity, ownership, disposition, and retest. A review meeting without closure evidence is activity, not control.

**Strong evidence may include**

- Requirement-linked findings
- Verified correction status

### Module 6

The final proof is the exact authorized package and system confirmation. Local files and calendar completion do not establish timely receipt by the designated system.

**Strong evidence may include**

- Final package manifest
- Timestamped mock acceptance record

## Specialist escalation boundaries

### Questions about solicitation meaning, representations, eligibility, protests, organizational conflicts, or contract terms

**Route to:** Authorized contracts leader and qualified government-contracts counsel as appropriate

**Learner boundary:** The coordinator tracks requirements but does not issue legal interpretations or certify eligibility.

### Final pricing, cost treatment, offer signature, certifications, or binding subcontract commitments

**Route to:** Authorized company officer, pricing or accounting reviewer, and authorized subcontract representatives

**Learner boundary:** Preparation does not create authority to bind any party or certify facts.

## Use of the self-review rubric

Use the accompanying rubric to inspect the work, identify revisions, and prepare questions. It is formative guidance only—not a grade, verified completion, credential assessment, professional approval, or substitute for a qualified reviewer.