Every program, organization, person, rule, question and decision in this packet is invented for training. No financial-aid program is represented. This is a document-maintenance exercise, not an eligibility or award decision.
Assignment
You are supporting the fictional Cedar Valley Learning Office. Its Learning Workshop Support Program provides small grants to community organizations offering learning workshops. Prepare proposed updates to the supplied guidance after a program process change. Do not decide individual applications, publish materials or send messages.
Requested outputs: change table; affected-material inventory; revised FAQ; staff checklist; short training update; management cover note; source map and human review queue.
H0: human-supplied precedence and scope for the exercise
This is an exercise configuration supplied by its author, not evidence of a real official approval.
- S1 is the accepted prior instruction for the 2027 workshop cycle.
- S2 is an accepted change notice. Its enumerated changes apply starting November 16, 2026, and replace only the identified requirements in S1. S1's other provisions remain in effect.
- S3 is an accepted reminder that adds no rule and depends on S2.
- S4 is a draft proposal, not accepted program authority.
- S7 is an unaccepted planning email and cannot override S1/S2.
- A1–A4 are the supplied downstream materials to audit. Their publication does not give them precedence over S1/S2.
- Do not infer that any other agency materials were searched. Flag possible inventory gaps separately.
- If S1/S2 leave an operational question unanswered, record it for the fictional program owner. Do not invent an answer.
S1: prior program instruction, version 1.0
Issue date: September 15, 2026.
Status: Accepted in this training exercise.
Owner: Program owner, Morgan Vale, fictional.
Scope: 2027 workshop cycle.
Section 1, purpose: Organizations may request support for community learning workshops.
Section 2, limit: An organization may request support for up to three workshops in the cycle. No funding amount or other eligibility conditions are supplied in this exercise.
Section 3, submission: Submit the application by December 1, 2026, using the office's email intake process. No real email address is supplied.
Section 4, previously accepted applications: Applications already recorded by the office as accepted for the 2027 cycle do not need to be resubmitted merely because application instructions change.
Section 5, applicant materials: Provide the organization name, workshop description, requested dates and proposed location. No venue-readiness checklist is required in version 1.0.
S2: process change notice, version 2.0
Issue date: October 20, 2026.
Status: Accepted in this training exercise.
Owner: Morgan Vale.
Effective date: November 16, 2026.
Scope: Application process for the 2027 workshop cycle, subject to the exemption below.
C1. The application deadline moves from December 1, 2026, to January 15, 2027. No cutoff time or time zone is specified in this notice.
C2. Starting November 16, 2026, new applications must be submitted through the Learning Portal, replacing email intake for new applications. No functioning portal URL is supplied in this exercise.
C3. New applications submitted through the Learning Portal must include a venue-readiness checklist attachment.
C4. Applications already recorded as accepted for the 2027 cycle remain valid and do not need resubmission because of this process change.
C5. The limit remains up to three workshops per organization.
C6. All other provisions in S1 remain unchanged. This notice does not specify how to handle an application that was started but not submitted before November 16.
S3: reminder, version 1.0
Issue date: October 28, 2026.
Status: Accepted reminder in this exercise.
The updated deadline is January 15, 2027. See S2 for the effective date, submission route, attachment requirement, and exemption for applications already accepted. This reminder introduces no new requirements.
S4: draft planning proposal, version 0.3
Issue date: October 25, 2026.
Status: DRAFT, not accepted.
Proposal for discussion: increase the limit from three to four workshops per organization. No decision has been made. Draft date is not an effective date.
S5: fictional inquiry log
All entries are invented; no real applicants or individual records are included.
| ID | Question from participating organization |
|---|---|
| Q1 | Our application is already accepted. Do we need to submit it again? |
| Q2 | We began writing an application but have not submitted it. Can we email it after November 16? |
| Q3 | Is the deadline December 1, January 15 or January 22? |
| Q4 | Do we need to attach the venue checklist? The form says no attachments. |
| Q5 | We heard the limit was going up to four workshops. Is that approved? |
| Q6 | What time does the application close, and where is the portal link? |
S6: inventory and editorial requirements
Supplied artifacts: A1 FAQ v1.1; A2 staff intake checklist v1.0; A3 training outline v1.0; A4 application form instructions v1.0. Complete excerpts for the scoped sections follow below.
Owners by role: FAQ editor; operations lead; training lead; form owner. Program owner resolves rule questions. Publishing owner checks final pages/files.
Use plain, direct, neutral language. Put cycle, applicability and next action near the top. Preserve the office and program names. Keep three FAQ answers with IDs FAQ1–FAQ3, a short staff checklist, and a five-minute training update. Use headings and numbered steps. Do not add logos, colors, fonts, awards, eligibility criteria or benefit promises. No brand guide or approved boilerplate has been supplied.
All proposed outputs are DRAFT. Use [PORTAL LINK PENDING] and [CONTACT PENDING] where necessary. These are placeholders, not working services. An actual release must replace them with verified operational details or remain on hold.
A1: public FAQ, v1.1
Published October 1, 2026. Owner: FAQ editor.
FAQ1: When and how do we apply? Apply by December 1, 2026, using email intake. Include your organization name, workshop description, dates and location.
FAQ2: If we applied already, do we need to apply again? Every organization must submit a new application when the application instructions change.
FAQ3: How many workshops can we request? You may request support for up to three workshops in the 2027 cycle.
A2: staff intake checklist, v1.0
Published September 20, 2026. Owner: operations lead.
- Monitor email intake for new applications.
- Check the application arrived by December 1, 2026.
- Confirm organization name, workshop description, requested dates and proposed location are present.
- Check requests do not exceed three workshops per organization.
- Record the application for program review.
A3: training outline, v1.0
Published September 22, 2026. Owner: training lead.
- Topic: How organizations apply for 2027 workshop support.
- Key message: Use email intake by December 1, 2026.
- Application contents: organization name, workshop description, dates and location.
- Limit: Three workshops per organization.
- Scenario: An organization plans two workshops. Where should it submit the application?
- Answer: Use email intake before December 1, 2026.
A4: application form instructions, v1.0
Published September 20, 2026. Owner: form owner.
Submission: Email this form by December 1, 2026.
Fields: organization name; workshop description; requested dates; proposed location.
Attachments: Do not attach additional documents.
Workshop count: Maximum three.
S7: unaccepted planning email
Date: October 29, 2026. From: fictional communications coordinator.
I have January 22, 2027, in my planning notes. Could we use that date in the update? I also saw the proposal for four workshops. Please check with the program owner before changing either item.
STOP: first checkpoint
Run the source/authority and comparison prompts on H0, S1–S7 and A1–A4 before using S8. List what can be resolved from the accepted sources and what requires a human answer.
S8: simulated program-owner resolutions · open at checkpoint B
This section is an authored answer for continuing the exercise. It is not a real approval and must never be represented as one.
Record date: October 31, 2026. Resolution owner: Morgan Vale, fictional.
- R1: S2 remains the accepted change notice. January 22 in S7 is incorrect. January 15, 2027, is the deadline.
- R2: For this exercise, the deadline is 5 p.m. Pacific time on January 15, 2027. Include this clarification in the revision packet; it was missing from S2.
- R3: Applications started but not submitted before November 16 must use the Learning Portal if submitted on or after November 16, including the venue-readiness checklist. This is a new clarification for the exercise, not something to infer from S2 alone.
- R4: Applications already recorded as accepted for the cycle remain exempt from resubmission. No new checklist is requested from those organizations solely because of this change.
- R5: Three workshops remains the limit. S4 has not been accepted.
- R6: Keep the four original information fields and add the venue-readiness checklist to new portal applications. The portal URL and public support contact remain unavailable.
- R7: The public guidance update and staff training must be ready before November 16. The scoped guidance is intended for use starting that date; label it accordingly. Do not distribute it as current instructions before then.
- R8: There is no supplied procedure for amending a previously accepted application or handling a new application emailed after the transition. Flag these for the operations owner. Staff should escalate rather than invent a disposition. The public revision packet must not promise acceptance, rejection or an amendment route.
All revised outputs still require simulated editor review and designated release approval. Those decisions have not been supplied. Working URLs/contact details and the missing staff-handling procedures remain release dependencies.