For months we ran our client blog refreshes on a Google Sheet. One row per article, with columns for status, the original link, the draft, the keyword, and the due dates. It worked, until it stopped scaling. Every new client meant another sheet, another tab, another place to remember to check.

Content refresh tracking now lives inside RequestDesk. Each article is a row on a board with its status, its original and draft links, its feedback, its due dates, and the client’s agent attached. The agent carries the voice, the knowledge, and the terms for that client, so each row is wired to the exact tool that will write it.

Bringing a client’s articles in takes one step. Export the sheet to CSV, pick the agent, upload. The importer maps the columns by name, skips anything already tracked, and shows the count as it runs. A blank template is one click away, so anyone on the team can build a file from scratch.

The board is the same for every client. ItsMoose runs on it today. Triple Crown drops in with its own CSV and its own agent. The client after that is a file and a dropdown, not a new spreadsheet.

We built this because the spreadsheet was the seam where things slipped. A status that never got updated. A draft link pasted in the wrong row. A due date nobody saw. Putting the pipeline next to the agent that writes the content closes that seam.

The tracker is the first step. The rows know which agent owns them, which means the next move is to let a row start its own draft. The tracking came first because you cannot automate what you cannot see.