Separate an activity count from an accepted output
See this course’s project requirements
A fictional awarded-program deliverable matrix with scope/due dates, activity-to-evidence links, unresolved reporting gaps, an authorized change request and a truthful narrative report.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Translate the supplied terms into deliverables, deadlines, period, owners and required evidence.
- Show distinct accepted-output counts with duplicate/draft/date exclusions.
- Link session and project evidence to the correct period.
- Provide a gap plan and a separately labeled unsent amendment request.
- Write a reconciled narrative that retains partial delivery and unresolved status.
Review and revise
Use these criteria to check your work and choose what to improve.
- Counts satisfy every stated unique-ID, acceptance and period condition.
- Delivery and narrative deadlines are kept distinct.
- Amendments change terms only with explicit authorized evidence.
- The report states supported results and known gaps without fabricated success.
Want more background?
The idea in everyday life
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.
A received file is not necessarily a unique accepted output. Apply all required conditions before counting it toward a deliverable.
Separate an activity count from an accepted output — supplied practice
A received file is not necessarily a unique accepted output. Apply all required conditions before counting it toward a deliverable.
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.
Fictional received outputs
Paste at A1.
| ARow | BOutput ID | CReview decision | DReview date | EEvidence note |
|---|---|---|---|---|
| 1 | A | Accepted | October10 | Reviewer R signed |
| 2 | B | Accepted | October15 | Reviewer R signed |
| 3 | C | Accepted | October21 | Reviewer Q signed |
| 4 | D | Accepted | October30 | Reviewer Q signed |
| 5 | E | Draft | October30 | No acceptance |
| 6 | A | Accepted | October10 | Duplicate upload of row1 |
| 7 | F | Unreviewed | October31 | No reviewer decision |
| 8 | G | Accepted | November1 | Outside stated period |
Copy as plain text
1. Preserve received rows
Copy all eight supplied rows without deleting duplicate, draft, unreviewed or out-of-period records.
You should see: Eight received rows remain in the evidence register.
Keeping exclusions visible lets another reviewer reproduce the count.
2. Apply acceptance
Mark A/B/C/D accepted; E draft and F unreviewed do not yet satisfy acceptance.
You should see: G is accepted but still needs a period check.
Acceptance is one gate, not the whole eligibility rule.
3. Deduplicate and check period
Count A once, exclude G’s November1 acceptance from October, and retain only distinct accepted October outputs.
You should see: Counted IDs are A/B/C/D: four.
Duplicate uploads and later dates cannot expand the valid set.
4. Reconcile with D2
Compare four valid outputs with six required and label the gap.
You should see: D2 is partial; two more accepted in-period outputs are needed.
The received-row total is not the deliverable count.
What to finish
An eight-row inclusion/exclusion register and reconciled D2 status.
Watch for this
Reporting eight accepted outputs because eight files were received.
How can I tell I understand it?
The valid output count reconciles to the required six.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
This official reference supports the mapped concepts. The supplied exercise inputs and operating rules are original fictional practice, not universal legal requirements or qualification evidence.
Access: official search extract; fullreadererror on 2026-10-01; external resources are optional.
Reuse: Original fictional teaching and practice; source concepts paraphrased and linked, with no copied provider exercises.
Source & access notes · checked 2026-10-01
This official reference supports the mapped concepts. The supplied exercise inputs and operating rules are original fictional practice, not universal legal requirements or qualification evidence.
Access: readable current official regulation on 2026-10-01; external resources are optional.
Reuse: Original fictional teaching and practice; source concepts paraphrased and linked, with no copied provider exercises.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.