Smartsheet lifecycle checklist: what to review before your next true-up

A true-up has a date on it, which is the only reason most environments ever get reviewed. That’s a shame, but it’s also useful: the deadline creates the one window each year when people will actually answer your questions about what a sheet is for.

So use it. Not as a cost-cutting exercise — as the annual lifecycle pass the environment should have had anyway. Here’s what to work through, and roughly the order that makes each step easier than the last.

Start four to six weeks out

Not because the work takes that long, but because step four requires other people to reply to you, and they will not reply in the same week you ask. Everything below is a metadata question except the ones that need a human, and those are the ones to start early.

1. Get a current count you trust

Before anything else, get the actual number of sheets, workspaces, and owners as of today, not as of the last time someone asked. This sounds trivial. It’s the step most environments skip, and it’s why renewal conversations get conducted on remembered figures from two years ago.

Note that the sheet count is a scale measure, not a health measure. It tells you how much there is, not how much is working. Don’t lead with it.

2. Bucket everything by last activity

Sort the whole environment by when each sheet was last touched. You’ll get something like a long tail of dormancy — in environments we’ve looked at, the large majority of sheets haven’t been touched in months, and roughly a fifth look like genuine lifecycle-review candidates. (Generalized from a real large-environment analysis; illustrative, not a guaranteed result.)

Two things not to do with that number:

• Don’t read dormant as deletable. Annual and quarterly processes look identical to abandonment at a glance. The bucket is a review queue.
• Don’t convert it into a licensing figure. Sheets and seats don’t map one-to-one, and that shortcut collapses under the first question from anyone paying attention.

3. Separate abandoned from stranded

Within the dormant pool there are two very different situations, and only one of them is cleanup.

Abandoned: a process that stopped, or a duplicate of something that moved elsewhere. Archive it and delete it.

Stranded: a live process whose old data got left behind. This happens constantly because of sheet-size limits — a process hits a ceiling, someone spins up “FY24 v2,” and last year’s rows sit in a sheet nobody opens instead of being archived properly and removed. That’s not clutter, it’s a data-retention gap, and Smartsheet’s own Data Shuttle is the right tool for moving that data out to where it belongs — a real system of record, a data warehouse, SharePoint, Drive — before the sheet goes away.

The distinction matters because stranded data is the case where deleting the sheet without archiving first actually loses something.

4. Confirm an owner for anything load-bearing

This is the step that needs humans, which is why you started early. For every sheet that’s clearly doing real work, you want a named person who agrees they own it. Not the historical creator field — a person who says yes.

Where you can’t get a yes, you’ve found something more valuable than a cleanup candidate: an unowned business process. Those are the ones that fail badly and at the worst possible moment. Smart Admin Studio’s institutional-knowledge risk discovery surfaces where ownership concentrates and where it’s about to become a gap, so you’re asking these questions in advance instead of during an incident.

5. Identify the sheets that are really applications

Some of what you’re reviewing isn’t a spreadsheet at all. It has a form feeding it, automations firing off it, cross-sheet formulas holding it together, maybe generated documents coming out of it. Those are business applications and they warrant the same lifecycle and support discipline as any other application in the portfolio — a documented owner, a known dependency list, someone who’d notice if they broke.

You want them identified before the true-up for a practical reason: they’re the evidence. When someone asks what the platform is actually doing for the business, this list is the answer.

6. Check where sensitive data may be sitting

Last pass: which sheets show signs of holding personal or sensitive information, and are any of them in the delete pile? Deleting a sheet with PII in it without a retention decision is worse than keeping it. This is a five-minute check with the right view and a multi-week problem without one.

The output

One page, six sections, real numbers:

• What we have (count, owners, workspaces)
• What’s dormant, and what’s genuinely abandoned versus stranded
• What’s load-bearing, and who owns each piece
• What’s unowned
• What’s actually an application
• Where sensitive data may live

That page is the whole point. It turns your side of the true-up from a negotiation about price into a conversation about value — you can show which parts of the business depend on the platform, who builds them, and what would break without them. That’s the case for growing licensing where it’s earning its keep, and for consolidating where it isn’t.

Working through all six by hand is where a lifecycle review usually dies. Smart Admin Studio scans the environment through the Smartsheet API and answers every one of them from metadata alone — ownership, staleness bucketing, complexity, PII signals — without touching the data inside a single sheet.

Your true-up date isn’t moving. Start your review today — no credit card, no sales call.

---

Smart Admin Studio is an independent product and is not affiliated with, endorsed by, or sponsored by Smartsheet Inc.