Compute metering replaces Google Notebook's countable daily quotas on September 2

People's actual pattern with an audio overview is simple: they drop a stack of PDFs into a notebook, generate the podcast, listen for two minutes, decide it buried the part they cared about, and generate it again. Under the outgoing scheme that was two of a free user's three for the day ^[10], and the user knew the cost before pressing the button. From September 2 those same two attempts cost whatever the meter says, priced off prompt complexity, the models and features involved, and the length of the chat ^[3]. PCWorld's account of the announcement carries no compute figure for any single feature and no numeric allowance for any tier ^[8].

Google's suggested response is deferral. Product manager Yesul Shin's example is a user who sees a warning and holds off on an audio or cinematic video overview ^[6]. Deferring only makes sense when you cannot see a price in advance, and that is the real shift here: the planning unit moves from a count you can hand to a colleague to a banner you react to.

Then there is the clock. Five hours does not divide a day, since 24/5 is 4.8 windows ^[14], so the reset floats against a working day rather than landing at midnight. The weekly cap replacing the monthly one ^[2] may land tighter or looser than what it replaces, and with no numbers published that is not knowable from the announcement.

The contrast is between what the buckets did and what teams tell themselves they did. The story is that a daily quota paces usage and teaches restraint. The actual function was administrative: it let one person answer a capacity question in a sentence, and it made tier comparison arithmetic. On the outgoing numbers the top paid tier ran roughly 67x free on audio overviews and 100x on chats ^[15][16]. The comparable sentence after the switch is standard versus more ^[7]. PCWorld reads the whole move as part of a wider clampdown on subscriber usage limits, especially for agentic features that burn tokens fast ^[13].

The sort worth doing before the switch has two axes: whether someone outside your team owns the deadline, and whether the work arrives in a burst or spreads across days. Burst work against an external deadline is the quadrant a five-hour window punishes, because running out means waiting for the next window rather than paying an overage ^[4]. Spread-out work on an internal deadline will barely notice. For tasks in the bad quadrant, the useful check is the count the task needs in its worst week, then whether that task still completes when the only signal you get is a warning near the limit ^[5]. Where it does not, the generation moves a day earlier, or audio and video overviews come off the path that has to finish on time. The category is already pointed here: GitHub Copilot made the same move in April ^[12], and Notebook's windows now match how ChatGPT, Claude and Gemini meter ^[4].