How to Complete Your First Reviewable Task With Codex
Complete your first Codex task with safe source material, a bounded request, and a review checklist that lets you verify every important result.
For your first Codex task, do not try to hand over an entire job. Use one small piece of non-sensitive material, ask for a clearly bounded output, and check every important detail against the source. The skill you are practicing is not clicking the right button. It is completing one full cycle from input to human review.
You may already have chosen a low-risk task, only to freeze when Codex is open: Where should the material go? What should the first instruction say? If Codex returns a polished page, how do you know whether it is usable?
Make the first exercise deliberately small. Do not use a customer document, and do not let the system send a message or modify a production file. In this exercise, you will turn a fictional event notice into a table that you can check line by line.
Prepare material you can verify word for word
Create a plain-text file with this content:
> The internal reading group will meet on September 12 at 2:30 p.m. in the small meeting room on the third floor. The topic is “Using Generative AI for the First Time.” Please reply to Aaron by noon on September 9. Each participant should prepare one small work task they would like to try with AI. No presentation is required.
The material is short, fictional, and contains no real personal information. Every correct answer appears in the source, so you can see whether Codex misses the date, time, location, response deadline, or preparation requirement.
If you use your own material, choose something public, self-written, or clearly non-sensitive that you are authorized to process. Contracts, customer records, HR files, and other formal or sensitive documents are poor choices for a first exercise.
Describe one output that can actually be completed
OpenAI’s Codex guidance recommends including a Goal, Context, Constraints, and a Done when condition. These details help Codex stay scoped, make fewer assumptions, and produce work that is easier to review. OpenAI: Codex best practices
One boundary matters: those four elements come from OpenAI’s guidance. The “material, task, result, review” sequence below is my beginner exercise. It is not an official OpenAI course or a formula that guarantees a correct result.
You do not need to memorize a framework. Start with this instruction:
Read this event notice and organize it as a table.
Use only these fields: event, date, time, location, reply deadline,
and what participants need to prepare.
If the source does not provide something, write “Not provided.”
Do not add information.
After the table, list anything you could not confirm from the source.This instruction identifies the material, defines the expected output, and says what to do when information is missing. It is not elegant, but it is enough for this exercise.
Watch what Codex does, not only what it says
Codex may read the file first or show a plan before acting. The interface can vary by platform and version. You do not need to understand every technical message yet. Check three things:
- Is it reading the material you selected?
- Is its plan still limited to organizing the notice as a table?
- Is it asking for permission to affect another file or external system?
Stop if it tries to modify unrelated files, use external information you did not request, or take a high-impact action you do not understand. This first exercise only requires reading a file and producing a draft. It does not need broader access.
Review the result against evidence, not fluency
OpenAI also recommends running appropriate checks, confirming the result, and reviewing the work before accepting it. OpenAI: Codex best practices
Place the result next to the source and complete this table:
| Item | Source evidence | Codex result | Match? |
|---|---|---|---|
| Date | September 12 | ||
| Time | 2:30 p.m. | ||
| Location | Small meeting room, third floor | ||
| Reply deadline | Noon on September 9 | ||
| Preparation | One small AI task; no presentation |
“It reads well” is not a review. You should be able to point to the sentence supporting each field. If Codex turns “reply to Aaron” into “email every participant,” it has introduced an action that is not in the source.
Give one precise correction:
The date, time, and location are correct.
The preparation field is missing “No presentation is required.”
Add that detail, but do not change the other fields.
Afterward, list exactly what you changed.Keep the correct parts and fix one visible gap. A later lesson will cover revision in more depth. Here, you only need to complete one full cycle yourself.
Save your first Codex run record
First Codex run record
Material:
Task:
Expected result:
What Codex actually did:
What I checked:
Gap I found:
How I corrected it:
What I still had to confirm myself:You are finished when you can show the material, instruction, output, and review evidence—and identify at least one detail you personally confirmed or corrected. A response from Codex alone is not completion.
The next step is to apply the same cycle to a more familiar work object: turning a short meeting transcript into possible decisions and action items. Keep the source and make every extracted item traceable to it.