How to Automate a Weekly Status Report in Smartsheet

Short answer: Use the sheet’s Automation center to schedule a recurring “send email” workflow with a row-rollup, or build a Dashboard with a Report widget that pulls live data and publish it as a read-only link. The first route takes about 10 minutes per sheet; the second gives stakeholders something that never goes stale.

Weekly status emails are usually a symptom: someone is copying numbers from a sheet into an email because nobody built a view. Fix the view first.

Why does the email approach fail?

Because the data in the email is a snapshot, and by Wednesday it is wrong. Smartsheet automations can send a table of rows, but the email body is static HTML at send time — no live updates, no drill-in.

That is fine for an “items at risk this week” digest. It is bad for a KPI summary that people reference midweek. Pick the mechanism based on that distinction.

How do you set up a scheduled risk digest?

This one is easy to get wrong by over-including rows.

1. Open the sheet and go to Automation → Create workflow → Scheduled.
2. Set frequency: weekly, Monday 07:00 in your workspace time zone. Smartsheet uses the sheet owner’s time zone unless changed.
3. Add a Condition: Status is Blocked, OR End Date is in the next 7 days AND % Complete < 100.
4. Add an Action: send email to the owner and the project lead. Include the row link, not just the text.
5. Save with a filter on the sheet first, and verify the preview shows three or four rows rather than all 60.

The filter is the whole trick. A digest with every task gets ignored by week two.

How do you build a dashboard that stays current?

Reports and dashboards are the right tool for numbers people check repeatedly.

• Create a Report filtered to the project sheet, grouping by Status, with the Health column visible.
• Add a Dashboard, then drop in a Metric widget set to count rows where Health = Red.
• Add a Chart widget grouping tasks by owner.
• Publish via Share → Publish → Read-only with a stable URL. The published view refreshes on load, not on a schedule.

Published dashboards do not consume a license for viewers, which is the main reason finance and leadership stop asking for PDFs.

Which automations are actually worth building?

A short list that pays off in most teams:

Trigger	Action	Why it earns its keep
Status changes to Blocked	notify owner + lead instantly	blockages get unblocked in hours, not weeks
Date reached, 3 days before End	remind assignee	catches slipping tasks early
New row via form	set Assigned To to manager	prevents orphan tasks
Status = Done	move row to archive sheet	keeps the active sheet readable

Four workflows cover a surprising amount of ground. The fifth one usually adds noise.

What are the limits?

Automation runs are capped monthly based on your plan and license count, and the limit is shared across all sheets in the account. A team running hourly checks on six sheets can hit a ceiling that nobody saw coming.

On the Pro plan, workflows can be edited only by licensed users, so you lose the automation if that person leaves and nobody inherits the seat. Transfer ownership explicitly when someone offboards.

One more: cell-linked cross-sheet references are not the same as reports. People build an “all projects” summary sheet with dozens of cross-sheet formulas, then break it every time a column is renamed. A Report handles that case with zero maintenance.

Who should build which?

Ops leads running a weekly steering meeting should build the dashboard. Individual project managers who only need to nudge people should stick to two or three scheduled workflows. Anyone trying to replace a BI tool with Smartsheet dashboards will hit a wall: row limits per report and limited chart types make it awkward past a few thousand rows.

Quick Summary

• Scheduled emails: 10 minutes to set up, static content per send.
• Dashboards: live on load, publishable read-only without extra licenses.
• Best triggers: Blocked status change, 3-day due reminder, form intake, Done-archival.
• Main limit: monthly automation allowance shared across the account.
• Avoid: cell-linked summary sheets; use Reports instead.

Last updated October 2026.