A ChatGPT Project for Each Crew Training Topic

1. Choose a single topic. Three examples: "Customer conversations at the door", "Handling a complaint on site", "Leaving a home ready for the customer".
2. Open a document and write the steps as you teach them, in plain words. Keep it to a page.
3. Add three or four "never do this" lines if you have them.
4. Remove names, addresses and anything that points to a real customer.
5. Save it with a clear name, such as "door-conversations-checklist.docx".

What you should see: a one-page checklist that matches how you train in person. Troubleshooting: If your checklist comes from the operations manual, paraphrase it in your own words and check with your franchisor before you upload any official text.

OpenAI's materials describe Projects as a way to group chats and keep project-specific instructions and files together. Menu names change, so look for the closest match.

1. Sign in at chatgpt.com.
2. In the sidebar, look for Projects and choose the option to create a new one.
3. Name it after the topic, for example "Crew huddle: door conversations".
4. Find where to add files and upload your checklist.

What you should see: a project page with your checklist listed and a place for instructions. Troubleshooting: If you cannot find Projects, your plan may not include them. Check OpenAI's pricing and help pages. A regular chat works as a fallback: paste your checklist into the first message.

Look for the instructions area of the project and paste this text.

You help a small service business owner run short crew training huddles.

Rules:
1. Base every question and answer on the checklist file in this project. If something is not in the checklist, say "Not in the checklist" and do not add it.
2. Every customer in a scenario is invented. Use codes such as "Customer C-1". Never use a real name, address, phone number or detail from a real job.
3. Keep each quiz or scenario short enough for a five-minute huddle: 3 quiz questions or 1 role-play scenario with 3 prompts for the crew.
4. Give an answer key after the questions, and next to each answer, quote or name the checklist line it comes from.
5. Do not state any law, safety rule or company policy that is not in the checklist.
6. Use plain, friendly language. Do not use the names of real staff members.
7. All output is a draft for the owner to check against the checklist before use.

What you should see: the instructions saved with the project. Troubleshooting: If an output breaks a rule, name the rule in the chat ("Rule 2: use a code, not a name") and make that line in the instructions stricter.

1. Open a new chat inside the project.
2. Type: "Write a 3-question quiz for a five-minute huddle on this checklist, with an answer key that points to checklist lines."
3. Read the questions and the key.

What you should see: three short questions and an answer key that names a checklist line for each answer. Troubleshooting: If a question has no checklist line behind it, delete it or ask for a replacement.

1. In the same project, type the prompt in the next section.
2. Read the scenario. Check that the customer is invented and carries a code.
3. Choose who plays the customer and who plays the crew member.

What you should see: a short scenario with a code for the customer, three prompts for the crew and a list of what a good response includes. Troubleshooting: If the scenario feels unrealistic, say what is off, such as "Make the customer less angry and more confused", and ask for another version.

1. Read the scenario out loud to the crew from your phone.
2. Let one person answer. Then ask the others what they would add.
3. Compare the answers with your own checklist, not with the chatbot's key.
4. Note any step your crew missed. That is next week's topic.

What you should see: a five-minute huddle with a discussion that comes from your checklist. Troubleshooting: If the answer key contradicts your checklist, your checklist wins. Fix the key, and consider whether the instructions need a stronger Rule 1.