Write a four-session smartphone basics course plan for seniors

## Role and objective

You are an education designer creating a four-session smartphone basics course plan for seniors. Produce a practical teaching plan that helps learners perform foundational smartphone tasks with increasing independence. Use a welcoming, non-patronizing approach and accommodate varied confidence, dexterity, vision, hearing, and memory needs without assuming a medical condition or a specific level of ability.

The output must be a four-session course plan with objectives, activities, timings, assessments, materials, and follow-up checks. Completion is demonstrated when every session has observable objectives, guided practice, learner practice, an assessment method, and required materials, while all unresolved planning details remain explicit slots.

## Scope and given facts

In scope:

- A course consisting of exactly four sessions.
- Smartphone basics for senior learners.
- Instructional sequencing from foundational orientation toward practical independent use.
- Session objectives, activities, timing, materials, checks for learning, and support strategies.
- Clear distinctions between instructor demonstration, guided practice, and learner practice.
- Accessibility-conscious teaching without inventing learner diagnoses or capabilities.

The user has not confirmed the learner profile, session duration, delivery setting, smartphone model, operating system, class size, instructor resources, or desired outcome beyond “smartphone basics.” Preserve these as slots:

- [FILL IN: learner age range and prior smartphone experience] — fill with the intended learners’ age range and baseline skills.
- [FILL IN: session length and delivery setting] — fill with the duration and whether instruction is in person, online, or hybrid.
- [FILL IN: smartphone operating system coverage] — fill with iOS, Android, both, or another specified platform.
- [FILL IN: class size and available equipment] — fill with the number of learners and devices or accessories supplied.

Do not arbitrarily fill the four-session structure, the senior audience, or the smartphone-basics scope with unrelated advanced topics such as app development, device repair, or cybersecurity certification.

## Working rules

Use observable learning objectives. Replace “understand smartphones” with actions such as identify, unlock, adjust, enter, call, send, locate, or demonstrate. For each objective, specify what the learner does and the condition or success standard used to judge completion. Do not use “understand” as the sole objective verb.

Sequence prerequisite skills before dependent skills. If learners are complete beginners, begin with device orientation, touch gestures, charging, volume, and safe handling. If the supplied learner profile confirms prior basic navigation, reduce introductory demonstration time and add practice or troubleshooting. If the operating system is unknown, write platform-neutral instructions and mark platform-specific steps with [FILL IN: platform-specific procedure]; do not invent menu names.

Use a gradual release pattern in every session: instructor demonstration, guided practice, independent practice, and a short check. Build repetition and recap into later sessions. Give directions in short steps, use plain language, and identify where learners may need larger text, stronger contrast, captions, hearing support, a stylus, or printed instructions. Present these as optional supports unless the input confirms a required accommodation.

Design activities around realistic tasks, such as making a call, adding a contact, sending a message, taking and finding a photo, using a map, or adjusting accessibility settings. Select only tasks appropriate to the confirmed scope. Include privacy and safety reminders proportionate to basic use, but do not turn the course into a comprehensive digital-security course.

For every question or quiz item, provide the answer, a brief explanation, and why each incorrect option may seem tempting. If no quiz is useful, use a performance check instead and define the observable evidence. State the intended difficulty distribution as [FILL IN: difficulty distribution] unless the user supplies one.

Where standards or an external framework is relevant, name it only if confirmed or required by the supplied context. If a standards framework is requested, leave its exact framework and codes as [FILL IN: applicable standards framework] rather than inventing codes or contents. Use US grade-level phrasing and reading-level conventions only if the audience is school-age; otherwise use accessible adult-learning language.

## Output structure

Order the plan as follows:

1. **Course overview** — State the four-session purpose, intended learner profile, assumed or unresolved planning details, prerequisites, and overall completion test. Allocate approximately 10% of the plan here.
2. **Session plan** — Provide exactly four session sections, each with:
   - Session title and central skill.
   - Two to four observable objectives.
   - A timed sequence covering welcome/recap, demonstration, guided practice, independent practice, and closing check.
   - Instructor actions and learner actions.
   - Materials and accessibility supports.
   - A performance-based assessment with observable success criteria.
   - Likely difficulties and the instructor response.
   Allocate approximately 70% of the plan across the four sessions.
3. **Assessment item format** — If using quiz questions, show question, answer, explanation, and distractor rationale. If using performance tasks, show task, evidence of success, and support allowed. Include [FILL IN: difficulty distribution] if not supplied.
4. **Materials slots** — List devices, chargers, printed guides, sample contacts, practice messages, internet access, accessibility aids, and any other required materials. Mark every unconfirmed item with [FILL IN: item].
5. **Post-lesson checks** — Provide a short learner self-check, instructor observation checklist, optional take-home practice, and a method for identifying topics that require review.

Use tables for the session timetable and assessment checklist where they improve scanability. Do not fill missing durations, platform procedures, class size, or equipment with invented values.

## Style rules

Use a hybrid style. Present the overview, objectives, schedules, materials, assessments, and checklists in itemized form; write brief instructional rationales and accessibility guidance in concise narrative paragraphs. Keep the register patient, respectful, adult-focused, and encouraging. Avoid ageist clichés, patronizing phrases, exaggerated claims about seniors, and language implying that difficulty with technology reflects low intelligence. Prefer concrete verbs and short instructions over motivational filler.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable contains exactly four sessions, not three, five, or a general list of topics.
2. Confirm that every session concerns smartphone basics and does not drift into app development, device repair, or an unrelated advanced curriculum.
3. Confirm that each session includes observable objectives, timed activities, materials, practice, and an assessment or performance check.
4. Confirm that the plan is written for seniors respectfully and does not assume a diagnosis, disability, prior skill level, or preferred device platform.
5. Confirm that any added fact beyond “four-session smartphone basics course for seniors” is either supported by the user input or marked with the correct [FILL IN: item] slot.
6. Confirm that no slot for learner profile, session length, delivery setting, operating system, class size, equipment, or difficulty distribution was filled arbitrarily.
7. Confirm that platform-specific menu names or procedures are not presented as facts when the operating system is unresolved.
8. Confirm that every quiz item, if included, has an answer, explanation, and distractor rationale; otherwise confirm that performance criteria are explicit.
9. Confirm that accessibility supports are concrete, optional where appropriate, and not framed as assumptions about all senior learners.
10. Confirm that the output follows the requested hybrid style, uses itemized sections where specified, and avoids topic-specific ageist clichés.
11. Confirm that materials and post-lesson checks are included and that unresolved requirements remain visible to the course planner.
12. Confirm that the final plan can be used by an instructor without silently inventing session durations, equipment, platform coverage, or learner outcomes.