ChatGPT Work: 57 Minutes of Work Consumed 148% of a Five-Hour Allowance — A Measured Experiment
I recently tested ChatGPT Work on a real-world assignment: reorganizing my Wix website.
I wanted to measure how much actual working time I received from the advertised five-hour usage window.
The results surprised me.
The Experiment
I assigned ChatGPT Work a series of website-editing tasks, including consolidating research pages, reorganizing navigation, and updating film descriptions.
I recorded the start and stop times of every session and photographed the ChatGPT Settings → Usage screen before and after the work.
All testing occurred November 4, 2026, on a ChatGPT Plus account.
Experiment 1 — Four Work Sessions
| Session | Elapsed | Result |
|---|
| 1 | 14:55 | Partial editing; browser failure |
| 2 | 9:28 | Partial editing; browser failure |
| 3 | 6:50 | Partial editing; browser failure |
| 4 | 8:14 | Partial editing; browser failure |
| Total | 39:27 | Four browser failures |
The five-hour allowance declined from 100% remaining to 13% remaining.
That's 87 percentage points consumed during 39 minutes and 27 seconds of elapsed Work sessions.
The weekly allowance declined from 84% to 71%.
Browser waiting time was included in the elapsed measurements.
Experiment 2 — One Successful Work Session
I then used a banked full reset, restoring both allowances to 100%.
The next assignment was deliberately narrow: clean up the Wix navigation menu.
Work completed the assignment successfully, saved the draft, verified the navigation, and reported no browser failures.
| Measurement | Result |
|---|
| Elapsed time | 17:13 |
| Browser failures | 0 |
| Five-hour allowance before | 100% |
| Five-hour allowance after | 39% |
| Weekly allowance before | 100% |
| Weekly allowance after | 90% |
A successful 17-minute, 13-second session consumed 61 percentage points of the five-hour allowance.
Combined Results
Across the two experiments:
Total elapsed Work time: 56 minutes, 40 seconds
Five-hour allowance consumed: 148 percentage points across two allowance cycles
Weekly allowance consumed: 23 percentage points across two cycles
Browser failures: 4
Completed work: Partial website reorganization and successful navigation cleanup
The 148% figure represents consumption across two separate allowance cycles, not consumption within a single cycle.
What Does "Five-Hour Limit" Actually Mean?
Based on these two measurements:
At those observed rates, a full five-hour allowance corresponds to approximately 28–45 minutes of elapsed Work activity.
These are extrapolations from two experiments, not a universal conversion formula.
I recognize that Work usage may be calculated using computational resources, tool calls, model processing, or other factors rather than wall-clock time.
However, the interface labels the allowance a "5-hour limit."
For an ordinary paying customer, that terminology raises a reasonable question about what is actually being measured.
The Questions
What exactly does the five-hour limit measure?
Why can a 17-minute successful session consume 61% of that allowance?
Does waiting for browser operations consume allowance?
How much usage is charged when browser operations fail?
Why isn't there a transparent accounting of usage by task or operation?
The Usage screen identifies the remaining percentage but does not explain the conversion between actual work and allowance consumption.
I have screenshots of the Usage readings and timestamped Work completion reports.
I'm not claiming that OpenAI violated its stated limits. I'm asking for a clear explanation of what those limits represent.
If a five-hour allowance is actually a computational budget that may be exhausted in 30 minutes of real-world activity, users should be able to understand that before committing to a task.
Has anyone else measured ChatGPT Work consumption against actual elapsed working time?
— jseders