AI agents for research workflows

Conference

Take over a fictional conference folder. Connect scattered documents, resolve conflicting information and make a useful event brief or local website.

Download this folderChoose another scenario

All data and documents are synthetic. Experiment freely; restore the folder from the ZIP whenever you need to.

Get ready

Open the folder in Codex

Click a step to see a screenshot.

Screenshots show the earlier practice guide and ChatGPT Work interface. Use your separate Codex setup instructions for current controls.

What’s in this folder?

Working with your own data? Keep good, up-to-date backups of all your data and know how to restore them.

Scenario · conference

Take over a conference folder

You’ve inherited the planning folder for a fictional event. Find out what is current and turn scattered information into a useful plan.

1. Discover and organise

What’s in this folder? Show how the documents, spreadsheets and website fit together. Identify conflicting or outdated information, with source paths. Suggest useful tasks and let me choose.

2. Reconcile the evidence

Build a source-linked event brief and an action list. Compare the planning workbook with the website, flag differences and distinguish confirmed decisions from proposals. Do not guess which source is current; explain the evidence.

3. Make something useful

Propose updates to the local conference website based on the checked brief. Show the plan first, apply the changes we agree and record the sources, edits and checks. Preview the result locally.
Other directions to try

Explore the feedback spreadsheet, draft a participant email for review, or create a planning dashboard. Check totals and denominators; a registration is not evidence of attendance. Use the fictional local materials. An agent drafting an email or website has not sent or published it.

Finish with Document the workflow. You can restore this mock folder from the ZIP.

Step 05 Continue afterwards

Document the workflow

For any scenario, leave a workflow someone else can understand and use.

Document our steps and set up a repeatable workflow that tracks every change. Include a run guide, an append-only change log and verification checks. Show me the plan first.
Run guideInputs → commands → outputs → checks
Change logWhat changed, why, when and how
Repeatable workflowRecord each run and revision
What should the log capture?

Old/new paths, input/output hashes, commands, environment, decisions and checks. Include failed attempts and corrections. Append entries; do not overwrite earlier history. Log manual changes too, and compare hashes to catch omissions.

Check your result

Start a new conversation and ask the agent to use the run guide. Ask the agent to repeat a step from the guide. Check the result and confirm the new log entry was added without erasing the history.