Morning: what is waiting comes first
The illustrative day begins when the merchandising lead opens the Today tab and reads the morning brief. Waiting on them, at the top: a batch of rewrites for the knitwear collection, ready for review, and one Merchant Center disapproval with a proposed fix. Below that, yesterday in one line: which rewrites went live on approval, which feed items were cleared, and a note that nothing was invented. Spend against the month's budget sits in the corner, as it always does.
The lead reads the brief in about the time it takes to drink half a coffee. That is the point of the brief: the workspace tells the manager what needs a decision before it tells them anything else.
Mid-morning: a rewrite batch in Approvals
The lead opens Approvals and the knitwear batch. Each SKU shows the title, attributes and description before and after, and beside the draft a map from every claim to its source: fibre content from the catalog field, weight from the supplier sheet uploaded last week, the care line from copy the lead approved for a sister collection. Two variants show a flagged gap where the sheet lists no gauge; the draft says nothing about gauge rather than guessing.
The lead approves most of the batch unchanged, edits one title to lead with the fit because that is how the store talks about knitwear, and sends one back with a note: never call anything luxurious. The note becomes a remit rule before the next batch is drafted.
Midday: a feed disapproval fixed at the source
The disapproval in the brief is a price mismatch: the feed carried yesterday's sale price, the page carries today's. The Product Catalog FTE has named the failing field, traced the cause to a scheduled promotion that ended overnight, drafted the correction in the product record rather than in a feed rule, and re-checked it against the same Merchant Center rule before proposing it.
The lead approves. The brief tomorrow will show the item cleared. Nothing in the process asked the lead to open Merchant Center, and the fix lives where the data lives, so the mismatch will not return on the next feed refresh.
Afternoon: the gap it would not fill
In the Catalog tab, the audit for a new outerwear collection shows a cluster of flagged gaps: no supplier sheet, so no fabric weight, no water-resistance rating, no fill material. The Product Catalog FTE has not written around the gaps. It has proposed a field-fill request listing the exact attributes it needs and the SKUs affected, and it has ranked the collection by revenue at risk so the lead can see it sits near the top because the season is close.
The lead forwards the request to the supplier. Until the sheet arrives, the collection's descriptions stay short and accurate rather than long and invented. That is the fact-gate doing its job in the least dramatic way possible.
Late afternoon: a diagnostic question
The lead asks a question in Missions: why did the accessories collection lose impressions last month? The Product Catalog FTE returns ranked hypotheses with evidence rather than an answer: several sibling SKUs share one description and may be competing with each other; two pages lost their canonical tag in a theme update; a competitor now ranks for the collection's main query. Each hypothesis carries what the FTE can see and what it cannot.
The lead picks the duplication hypothesis to act on first, and a rewrite batch for those siblings is queued for tomorrow's brief. The other hypotheses stay in the mission with their evidence, not discarded and not asserted.
Evening: the log
At the end of the illustrative day the Performance tab shows what happened: rewrites approved, the one edited title, the one send-back and its rule, the disapproval cleared, the field-fill request sent, and the mission opened. Every entry has the person who decided and the evidence attached. The completeness score for knitwear has moved; the score for outerwear has not, and the report says why.
Nothing in the day asked the lead to trust a system. It asked them to approve evidence, refuse one adjective, and forward one request. The record of all of it exists already, which is what an audit trail means when it is built in rather than reconstructed.