Translate the fictional award into deliverables

Translate the fictional award into deliverables — supplied practice

An award matrix records what must be delivered, by when, with which evidence and through whose approval. A report deadline is not automatically the output deadline.

Fictional award terms: reporting period October1–31 of a fictional program year. D1 requires four delivered sessions by October31, supported by session logs and host attendance records. D2 requires six distinct rubric-accepted project outputs within that period, each with ID, review date and reviewer decision. D3 is a narrative report due November5. A request to extend D2 to November15 has been drafted but not approved. These supplied terms govern the exercise only; actual awards may have different conditions. No real report is submitted.

1. 1. Extract the commitments

   Create rows D1 four sessions, D2 six accepted outputs and D3 narrative report.

   You should see: Three distinct deliverables retain their stated conditions.

   An activity and its report are separate obligations.

2. 2. Attach dates and period

   Record October31 output deadlines, October1–31 evidence period and November5 report deadline.

   You should see: D1/D2 due October31; D3 due November5.

   Later report submission does not authorize later counted outputs.

3. 3. Name evidence and owner

   Assign fictional delivery owner H to sessions, review owner R/Q to outputs and report owner C to the narrative; list required evidence.

   You should see: Each row has a responsible role and inspectable evidence type.

   An owner label is useful when the needed record is specified.

4. 4. Preserve change authority

   Add extension request as pending, with an authorized award officer decision required before terms change.

   You should see: Original D2 deadline remains October31.

   A request is not an amendment.