Choose one single output
“Organizing my work” describes an intention, but it doesn’t say which file must exist at the end. Swap that intention for an observable output: a table with the requests received today. Also define the unit of work. One line represents a request, not a customer or an entire conversation. This decision prevents the assistant from grouping different requests and hiding tasks.
In this course, we’ll use fictional scenarios of a small services workshop called Oficina Aurora. It needs to organize requests, consult documents, and present results. You can replace this scenario with your own after completing the initial practice.
Why learn
A concrete output lets you compare the request with the result. Without that comparison, a well-written answer can seem finished even when important information is missing.
✓ Do
Keep identifiers and entry dates.
✗ Avoid
Inventing a date to make the table look complete.
Key concepts
Fill in the scope sheet
A short scope sheet works like a work agreement. It describes the goal, input, output, exclusions, and acceptance criteria. Write these fields before choosing a tool. If you only need to transform text into a table, adding a calendar increases the effort without improving the first delivery.
Include a common case and an incomplete case. The common case shows the expected path; the incomplete case shows how the process behaves when reality doesn’t fit the perfect example. A missing deadline should remain missing until someone tells you about it.
Why learn
The scope sheet reduces back-and-forth and helps identify scope changes. A new function goes into a future list instead of silently changing the work in progress.
A way to apply
- Choose the output and write the scope sheet.
- Prepare one complete case and one incomplete one.
- Execute, compare the fields, and save the evidence.
Key concepts
Request a faithful transformation
A good request states which fields must be preserved, which format should be used, and how to handle missing information. Don’t ask only “make a beautiful table.” Specify columns, one row per request, and forbid filling in data based on assumptions.
Separate the instruction text from the input data. Clearly identify where the requests start and end. This helps the assistant treat received sentences as content to organize, without confusing them with new orders about the process.
Why learn
The quality of the output depends on how clear the transformation is. Specifying how to handle gaps is usually more useful than adding adjectives like perfect, complete, or professional.
Goal: organize orders in a table.
Input: three fictitious requests.
Output: CSV with id, customer, task, deadline.
Rule: missing deadline = pending.
Out of scope: sending messages or scheduling services.
Key concepts
Check before scaling up
Make a line-by-line comparison. The identifier, client, task, and deadline must match the input. A table with three lines isn’t enough: you can have three lines and still swap the date across clients. Verify content and quantity.
If a line is wrong, correct the rule that led to the error and run the same example again. Save the input and the corrected output. This small evidence helps you see whether a future change reintroduced the problem.
Why learn
Review turns an impression into proof. It also shows where to fix: in extraction, in the format, or in the business rule—without rebuilding the entire process.
✓ Do
Ask for the deadline when it’s missing.
✗ Avoid
Add notifications before validating the table.
Key concepts
Close one step at a time
A step ends when it delivers what was agreed and passes the checks. New ideas can be valuable, but they need a separate place. Create a list called “next improvements” and record notifications, the calendar, and a visual dashboard there.
Use simple states: to do, in progress, done, and blocked by missing data. Blocked doesn’t mean failure; it means the process identified something it can’t invent. Record which information is missing and who could provide it.
Why learn
Limiting work in progress reduces the feeling of having many projects almost ready. You start accumulating small deliveries that work and can be combined.
| Criterion | Expected evidence |
|---|---|
| Quantity | Three requests produce three lines. |
| Fidelity | The client and task remain associated. |
| Absence | A request without a date stays pending. |
Key concepts
Practice: organize three requests
Create a folder for the exercise and save the input text before using the assistant. Produce the table and check the criteria below. Do not connect services: in this practice, the output is a file that you can open.
After the first run, remove the date from another order and repeat. The rule needs to work for any incomplete record, not just the third example. Record in one sentence what changed and whether the behavior remained correct.
Why learn
The practice teaches you to close a small task and introduces a central idea of the course: vary the input to see whether the solution understood the rule or simply copied the example.
Your exercise
A-01: Padaria Horizonte asks to review the menu until 22/10/2026. A-02: Ateliê Nuvem asks to catalog 12 products until 24/10/2026. A-03: Floricultura Vale asks to organize frequently asked questions, without stating a deadline.
Download practice sheetCheck the commented answer
id,customer,task,deadline A-01,Bakery Horizonte,Review the menu,2026-10-22 A-02,Ateliê Nuvem,Catalog 12 products,2026-10-24 A-03,Floricultura Vale,Organize frequently asked questions,pending Question: what deadline is desired for A-03?
Check your understanding
An order does not include the date. What should you do?
Key concepts
What stays from this module
One scope sheet and a table faithful to the requests received.
- ✓ Three orders produce three lines.
- ✓ Customer and task remain associated.
- ✓ An order without a date stays pending.
Progress records your reading. The practice is completed when you check the submission.