# ChatGPT for Everyday Life
## An original Practivra beginner course

Version 1 — complete text teaching draft, 7 October 2026.

For adults starting with AI: employees, students, retirees and anyone who wants help with everyday tasks. No coding background required. This is an independent Practivra course, not an OpenAI certification or endorsement.

## Welcome

You do not need special words to start. Choose a small task, explain what you need, and read the result carefully. In this course you will practise a repeatable habit: **Ask → Review → Improve → Use**.

Ask for a clear outcome. Review facts, omissions and tone. Improve the draft with a focused follow-up. Use it only when you are satisfied that it fits your purpose.

Suggested pace: one lesson per session. Allow around 15–25 minutes for each lesson; the building lesson and final project may take longer. These are planning estimates, not a promise that every activity takes exactly 15 minutes.

You need a ChatGPT account and a phone or computer. Start with the features your account already provides. Files, image generation, research, connected tools, scheduling and Codex access can differ by account, platform and workspace settings. Check availability before starting the optional activities. You do not need an API key for the basic conversational exercises.

Use the fictional examples supplied here. Before using work material, check your employer's rules and remove information you are not allowed to share. Do not paste passwords or access keys into practice conversations.

AI output can contain errors or unsupported claims. A confident tone is not proof. This course teaches checking, rather than treating an answer as automatically correct.

## Your learning path

| Lesson | Your finished result |
|---|---|
| 1. Your first useful conversation | A short explanation you can understand |
| 2. Give clear instructions | A reusable prompt |
| 3. Emails, plans and summaries | A reviewed email and task plan |
| 4. Work from documents | A summary with traceable evidence |
| 5. Research and check sources | A small evidence table |
| 6. Create clear content | A workshop caption and visual brief |
| 7. Organise ongoing work | A learning project and progress note |
| 8. Work with connected tools | A reviewed tool-use brief |
| 9. Plan repeated tasks | A precise recurring-task specification |
| 10. Understand a small dataset | Verified totals and a useful comparison |
| 11. Build a small tool with Codex | A tested study checklist prototype |
| 12. Complete your final project | A checked beginner workshop pack |

## Lesson 1 — Your first useful conversation

**Goal:** Ask for an explanation, improve it, and recognise the difference between a draft and a verified fact.

### Learn

A prompt is the message you give the assistant. It can be a question or an instruction. Start with a small task that you can judge. You can ask follow-up questions in the same conversation; you do not need to fit everything into your first message.

Open ChatGPT and start a new chat. The interface may differ between devices. For this exercise, use the ordinary conversational experience available to you.

### Demonstration

Copy this prompt:

```text
Explain what a spreadsheet is to an adult who has never used one.
Use plain English, under 100 words, and one example involving a shopping list.
Avoid technical terms unless you explain them.
```

Read the answer. Identify any unfamiliar word. Then ask:

```text
Explain the unfamiliar terms in simpler words.
Then give me three small things I could record in a shopping spreadsheet.
```

An acceptable explanation describes rows and columns used to organise information, with an everyday example. Exact wording will vary.

### Practise

Ask for a simple explanation of a calendar reminder. Request an example and then a shorter version. Save the version you find easiest to understand.

### Check your result

Is it understandable? Does it answer your question? Did it introduce a fact you should verify before relying on it?

**Knowledge check:** If an answer sounds confident, does that make it correct?

**Answer guide:** No. Check factual claims against suitable evidence. Asking the assistant to confirm itself is not independent verification.

## Lesson 2 — Give clear instructions

**Goal:** Build a prompt that tells the assistant what a successful result looks like.

### Learn

Use five pieces when useful: task, context, audience, constraints and format. You do not need every piece for every question. Supply the details that affect the outcome.

Compare “Write something about AI” with a request that identifies what you need and who will read it. Clear instructions reduce ambiguity, but they cannot guarantee a perfect first answer.

### Demonstration

```text
Task: Draft three headlines for a free introductory AI workshop.
Audience: Adults who have never used an AI assistant.
Context: The workshop teaches email drafting and checking answers.
Constraints: Plain English, fewer than 12 words per headline,
and no income guarantees.
Format: A numbered list with one sentence explaining each headline.
```

Possible headline: “Try AI: Write Emails and Check Answers.” It has eight words and names the two activities. Other answers are acceptable if they meet the brief.

### Practise

Write a prompt for a packing checklist for a one-day outing. Specify the audience, weather information you actually have, item limit and format. If the weather is unknown, ask the assistant to mark it as unknown rather than invent a forecast.

Revise your prompt once after inspecting the first output.

### Check your result

Count items or words where limits matter. Check whether the answer matches the audience and uses only the facts you supplied.

**Knowledge check:** What should you do if a requested plan depends on missing information?

**Answer guide:** Provide the missing information, ask for a clarifying question, or explicitly label assumptions. Do not present guessed details as facts.

## Lesson 3 — Emails, plans and summaries

**Goal:** Produce a useful draft without inventing agreements or deadlines.

### Learn

An email needs the right facts, tone and request. A pleasant draft can still be wrong if it adds a promise you never made. Use placeholders when names or details are unknown.

### Demonstration

```text
Write a polite email asking a colleague for a project update.
Context: We agreed to review progress this week.
Ask how the project is going and whether they need anything from me.
Keep the body under 80 words.
Use [Name], [Project] and [Your name] as placeholders.
Do not invent dates, deadlines, progress or promises.
Format: Subject, greeting, body and closing.
```

Example reviewed draft:

> Subject: Update on [Project]
>
> Hi [Name],
>
> I hope you're well. As we agreed to review progress this week, could you share how [Project] is going? Please let me know whether you need anything from me.
>
> Best,
> [Your name]

Follow up: “Make the body warmer and under 60 words. Preserve the facts and placeholders. Do not add a deadline.”

### Practise

Use these fictional notes: “Workshop room booked. Slides unfinished. Registration list needs checking. No date given.” Ask for a three-item action list and a two-sentence summary. Tell the assistant to leave owners and deadlines unspecified.

### Check your result

The room booking is completed; the other two tasks remain. The answer should not invent a date or assign a person.

**Knowledge check:** Is “Please finish the slides by Friday” supported by these notes?

**Answer guide:** No. Friday is not supplied. Remove the deadline or obtain it from the task owner.

## Lesson 4 — Work from documents

**Goal:** Separate what a document says from what the assistant infers.

### Learn

When file upload is available, attach a small practice document you are allowed to use. Otherwise paste the short sample below. Ask for evidence locations: page numbers when available, or section headings and brief passages. Scanned or poorly formatted documents may need extra checking.

### Practice document

**Workshop note — Purpose:** Help adults practise drafting an email and checking AI answers.

**Activities:** Demonstration, individual practice, group review.

**Materials:** Sample prompts and a review checklist.

**Open questions:** Venue and workshop date have not been decided.

### Demonstration

```text
Use only the workshop note supplied above.
Summarise its purpose in one sentence.
List the activities and materials in separate lists.
Identify unanswered questions.
For each factual point, name the relevant section.
If the note does not support an answer, say so.
```

### Practise

Ask: “How many learners will attend, and what does the workshop cost?” Then inspect whether the answer admits that neither detail is supplied.

Ask for three review questions based only on the note. Compare each answer to the source yourself.

### Check your result

Venue and date remain undecided. Attendance and cost are not stated. The materials are sample prompts and a review checklist.

**Knowledge check:** Can the assistant calculate attendance from this note?

**Answer guide:** No. There is no attendance figure or sufficient data to derive one.

## Lesson 5 — Research and check sources

**Goal:** Build a small evidence trail instead of accepting a polished report at face value.

### Learn

Use current official sources for product features, prices or eligibility. Open each cited page and check whether it supports the specific claim. Record the date you checked it. A link can exist without supporting the nearby statement.

If web search or a research mode is available, use it for this exercise. If it is unavailable, supply passages from official documentation and ask for a source-bound summary. Do not describe that alternative as live research.

### Demonstration

```text
Research how ChatGPT projects help organise ongoing learning.
Use current official OpenAI documentation.
Create a table with: claim, source URL, supporting section,
and anything the source leaves unclear.
Keep the report under 250 words.
Do not guess my account's feature access or quote a price without evidence.
```

### Practise

Choose two claims in the output. Open their sources. Write down whether the passage supports each claim completely, partly, or not at all. Ask the assistant to revise any unsupported claim.

### Check your result

Sources must be relevant, accessible to you, and specific enough to check. Separate general product capability from access on your own account.

**Knowledge check:** Does a citation automatically prove a claim?

**Answer guide:** No. You must check the cited passage, its date and its relevance.

## Lesson 6 — Create clear content

**Goal:** Turn a brief into a useful caption and visual idea without inventing benefits.

### Learn

Good content tells the reader what they will get. Specify the audience, message, tone and format. Check whether promotional copy adds unsupported promises. If image generation is available, use the visual brief to create a practice image; otherwise keep it as a design brief.

### Demonstration

```text
Write a social media caption for Practivra's proposed free beginner AI workshop.
It teaches email drafting and checking answers.
Use a friendly tone and plain English, under 60 words.
Invite readers to learn more without inventing a registration link,
date, venue, accreditation or income claim.
```

Example: “New to AI? Practise writing an email and checking an AI answer in Practivra's free beginner workshop. Clear examples and simple exercises will help you get started. Learn more about the workshop.” This is draft promotional copy; publish only once the workshop and its promised activities are ready.

Visual brief:

```text
A welcoming illustration of an adult learning at a laptop,
with a notebook and cup on a bright desk. Calm blue and violet accents,
clear composition, space for a headline added later, no embedded text.
Avoid depicting the image as an actual workshop photograph.
```

### Practise

Create two caption versions: one for employees and one for retirees. Keep the same workshop facts. Compare readability and tone.

### Check your result

Both captions should name the actual activities. Review image details and any text separately before using a visual.

**Knowledge check:** Should you advertise a recognised qualification if none exists?

**Answer guide:** No. Describe only the completion evidence or certificate actually provided.

## Lesson 7 — Organise ongoing work

**Goal:** Make a small learning workspace that you can resume later.

### Learn

A project can bring related chats, files and instructions together. Use a clear purpose and small, relevant source set. Keeping material together helps organisation; it does not remove the need to identify the right source or check an answer.

If projects are unavailable, use one clearly named conversation and a separate progress note.

### Demonstration

Create a project called “My AI Practice”, if available. Add a short note containing your learning goal and the fictional workshop note from Lesson 4. Use these instructions:

```text
Use plain English. Explain unfamiliar terms.
For questions about my notes, use only those notes and name the section.
Say when information is missing.
Finish each practice session with a brief progress note.
```

### Practise

Start a related chat and ask for three questions about the workshop note, one at a time. At the end, ask for a progress note containing completed activities, mistakes to revisit and the next task.

### Check your result

Ensure the questions use the correct note. Review the progress note before saving it; correct any invented achievement.

**Knowledge check:** What belongs in a helpful progress note?

**Answer guide:** Work actually completed, unresolved questions, and a concrete next step.

## Lesson 8 — Work with connected tools

**Goal:** Specify a task and review what a connected tool may access or change.

### Learn

Connected tools can give an assistant access to information or actions in other services. Availability and permissions vary. Read the connection details and the requested action. Distinguish finding or drafting from sending or changing something.

This practice uses fictional data and needs no account connection. An optional live demonstration should begin with a read-only task on material you are allowed to access.

### Demonstration

```text
Using only these fictional messages, draft a meeting agenda.
Message 1: We need to review the workshop slides.
Message 2: We also need to check the registration list.
Return two agenda items and the source message for each.
Draft only; do not send messages or create calendar events.
```

### Practise

Write a brief for a possible calendar task: identify the calendar, meeting title, participants, date, time, time zone and duration. Mark anything missing. Ask the assistant to show the proposed event details before creation. Do not execute this fictional event.

### Check your result

The brief should identify exactly what would be read or changed. If the participant or time is unknown, the assistant should not silently guess it.

**Knowledge check:** Does connecting an email service mean every drafted email has been sent?

**Answer guide:** No. Drafting and sending are separate actions. Check the actual action and result.

## Lesson 9 — Plan repeated tasks

**Goal:** Define a recurring task clearly and verify whether it was actually scheduled.

### Learn

A recurring task needs an action, schedule, time zone, sources and delivery expectations. A written plan is not a running automation. If scheduling is available, inspect the saved task and its next run. If unavailable, keep the specification and use your own calendar reminder.

### Demonstration — planning only

```text
Draft a specification for a weekly AI practice reminder.
Schedule: Every Monday at 7 p.m., Asia/Dubai.
Content: Remind me to practise one prompt and review its answer.
Include a short review checklist.
Do not schedule it yet. Return the specification for review.
```

### Practise

Change the specification to a time that suits you. Explain what should happen if the task cannot access its required source. If you choose to create it through an available scheduling feature, explicitly request creation and verify the saved schedule. Pause or delete your practice task when finished if you do not want it to continue.

### Check your result

Confirm local time, recurrence and actual saved status. A message saying what could be done does not prove that a task exists.

**Knowledge check:** What is missing from “Remind me tomorrow evening”?

**Answer guide:** A precise time and a confirmed time zone; the intended reminder content may also need clarification.

## Lesson 10 — Understand a small dataset

**Goal:** Verify simple calculations and avoid conclusions the data cannot support.

### Learn

Start with a small table whose totals you can check manually. Ask for units and formulas. Distinguish counts from rates: five sign-ups means something different when there were ten visitors than when there were one thousand.

### Fictional practice data

| Week | Visitors | Sign-ups |
|---|---:|---:|
| 1 | 100 | 5 |
| 2 | 120 | 6 |
| 3 | 80 | 8 |
| 4 | 150 | 9 |

### Demonstration

```text
Use only this table. Calculate total visitors, total sign-ups,
and the sign-up rate for each week.
Show each rate as sign-ups divided by visitors times 100.
Identify the highest weekly rate and the highest weekly count separately.
Do not claim the table explains why the figures changed.
```

### Practise

Check the arithmetic with a calculator. Ask for a bar chart of weekly rates if chart creation is available, or a chart specification otherwise. Label the chart as fictional practice data.

### Answer guide

Total visitors: 450. Total sign-ups: 28. Weekly rates: 5%, 5%, 10%, 6%. Week 3 has the highest rate; Week 4 has the highest sign-up count. Overall rate is 28 ÷ 450 × 100 ≈ 6.22%; it is not the simple average of the four weekly percentages.

**Knowledge check:** Does the table prove that a website redesign caused the change?

**Answer guide:** No. It contains no redesign information or evidence establishing cause.

## Lesson 11 — Build a small tool with Codex

**Goal:** Describe a small tool, review its behaviour and test it before relying on it.

### Learn

Codex supports software development work. A beginner still needs to describe the desired behaviour and check the result. Start with a small prototype using fictional data. Ask for an explanation of what was built and any limitations. Keep a working copy before making further changes.

This activity needs an available Codex environment. If you do not have one, complete the requirements and test checklist as a planning exercise. A prototype alone is not a published website.

### Demonstration

```text
Build a simple study checklist prototype for a beginner.
Requirements: add a task, mark it complete, delete it,
and show the number of unfinished tasks.
Use large readable labels and make it usable on a phone.
Use fictional sample tasks. No accounts, payments or external AI calls.
Before implementation, explain how tasks will be stored.
After implementation, explain how to open it and test it,
and report any limitations. Do not publish it.
```

### Practise

Test five behaviours: add a normal task; try an empty task; mark a task complete; delete a task; reload the page. Compare reload behaviour to the stated storage design. Test the interface on a narrow screen and with a keyboard.

Request one focused improvement based on a problem you observed. Repeat the affected checks after the change.

### Check your result

Task counts should change correctly. Empty tasks should be handled clearly. Data persistence should match what was promised. Record remaining problems rather than claiming the tool is finished because it looks attractive.

**Knowledge check:** Is a successful build enough to prove every button works?

**Answer guide:** No. Test the intended behaviours and inspect relevant results.

## Lesson 12 — Complete your final project

**Goal:** Combine prompting, source discipline and review into a complete useful result.

### Your brief

Prepare a beginner AI workshop pack using these supplied facts:

- Audience: adults who have never used an AI assistant.
- Activities: draft an email and practise checking answers.
- Price: free.
- Date, venue, registration link and attendance: not yet supplied.

Create four deliverables: three headlines under 12 words each; an invitation email under 100 words with placeholders for missing logistics; a three-step learner exercise; and a review checklist.

### Starter prompt

```text
Prepare a beginner AI workshop pack using only the supplied brief.
Create: three headlines under 12 words each, an invitation email
under 100 words, a three-step learner exercise, and a review checklist.
Use placeholders for missing logistics.
Do not invent dates, venues, registration links, accreditation,
attendance figures or income guarantees.
Label the result as a draft for review.
```

### Complete the workflow

1. Draft the pack and save the prompt.
2. Check every factual statement against the brief.
3. Count words where limits apply.
4. Run the learner exercise yourself.
5. Ask for a focused revision, then review it again.
6. Save the final pack with a short note describing what you checked.

### Completion rubric

| Criterion | Evidence required |
|---|---|
| Clear instructions | Saved prompt names the task, audience, constraints and format |
| Faithful facts | Claims match the supplied brief; missing details use placeholders |
| Useful output | All four deliverables are included and understandable |
| Review | Word limits and exercise behaviour were checked |
| Improvement | At least one justified revision is documented |

If any criterion is missing, revisit the relevant lesson and revise the pack. Completing the course means demonstrating the workflow, not merely opening all lesson pages.

**Knowledge check:** What should happen before the invitation is sent?

**Answer guide:** Verify the final wording, supply and confirm the actual logistics, and authorise sending through the intended channel.

## Learner reflection

Write three short answers: What task can I now do confidently? What error did I catch? What will I practise next?

Revisit Lesson 2 for unclear prompts; Lessons 3–4 for invented details; Lesson 5 for weak evidence; Lesson 9 for scheduling confusion; Lesson 10 for calculation mistakes; and Lesson 11 for untested tool behaviour.

## Instructor guide and launch notes

This draft supplies the complete text curriculum, prompts, fictional source material, exercises and answer guides. It does not yet include recorded videos, a working course website, enrollment, payments, progress tracking or a certificate system.

For each lesson, record a short introduction, demonstrate the prompt, point out one thing to check, then invite the learner to pause and practise. Record actual output rather than promising identical responses. Display readable text and provide captions and a text version. Let learners pause without a countdown.

Pilot Lessons 1–3 with beginners before selling the course. Record where they get stuck and revise the instructions. Publish the remaining lessons when their demonstrations and activities are tested. Describe optional features and any required account access on the relevant lesson page before purchase.

Do not advertise “200+ tasks” unless that task bank has actually been created. This draft contains one core practice activity per lesson, with some activities containing several checks. Do not market estimated lesson lengths as guaranteed completion times.

If issuing a certificate, use “Practivra Certificate of Completion — ChatGPT for Everyday Life.” Issue it only after the actual completion criteria are satisfied. Do not imply accreditation, guaranteed employment or official OpenAI certification.

Suggested course landing-page copy:

> **Use ChatGPT for everyday tasks, one clear step at a time.**
>
> Practise writing emails, understanding documents, checking sources and creating useful content. Follow short lessons with examples, exercises and answer guides. Start with the introductory lessons and learn at your own pace.

Suggested lesson-page layout: goal, account requirements, text or video demonstration, copyable prompt, practice task, review checklist, answer guide and next lesson.

## Official documentation and maintenance

Product references checked on 7 October 2026:

- [ChatGPT on the web](https://learn.chatgpt.com/docs/web): starting a chat, specifying goals and context, using files and tools, revising results.
- [ChatGPT features](https://learn.chatgpt.com/docs/features): directory of projects, scheduled tasks, search, images and file workflows.
- [ChatGPT quickstart](https://learn.chatgpt.com/docs/quickstart): conversational, deliverable and software development workflows.

These references support product orientation; the fictional examples, exercises and teaching framework are original course material. Linked feature documentation does not prove that every learner has access. Before recording feature-specific demonstrations, open the current detailed documentation and test the workflow on the account and platform shown. Recheck changed interface steps and feature requirements before publishing an update.
