Set a new standard for how you operate with what's new in Smartsheet

Smartsheet is the Execution Hub for how your operation runs

Ask anyone who owns a cross-functional process how it's going, and you'll usually hear that it's running. Requests move, lines run, orders ship, the weekly report goes out.

Look closer, and the process has quietly split. One plant skips a changeover check that slows the line. Another added a sign-off after last year's recall scare. A supplier fills in the inspection form their own way. The handoff from quality to the distribution center lives in one person's inbox. Each change made sense where it was made. None of them made it back to the version you'd show an auditor.

The further a process travels from the people who designed it, the more it changes. AI speeds that up. Every team now moves faster, just not together. Each one has its own tools and its own reading of the standard, and the gaps between them keep widening.

Smartsheet calls this execution drift, the gap between how a process was designed to run and how it actually runs across plants, sites, teams, and suppliers. Day to day, it's the status you ask for twice and the spreadsheet you reconcile by hand on Monday morning. Over a year, this can show up as a late audit finding, an escalated customer complaint, and the missed target nobody can trace back to where it slipped.

Every process that matters crosses teams. A supplier corrective action runs from the plant floor to quality, to engineering, to the supplier, and back. A new product introduction pulls in R&D, sourcing, manufacturing, and logistics. Onboarding a vendor touches procurement, legal, security, and finance. Opening a new site, clinic, or distribution center involves coordinating a dozen functions and a few external partners.

Ask three questions about any one of them.

• Is every plant, site, and team running the current version, or the one it copied last year?
• When a handoff stalls, do you find out before the next team in line does?
• If an auditor asked who changed a step, and why, could you show them in one place?

For most teams, the honest answers are no, rarely, or only after a week of digging. That isn't a people problem, and it isn't a systems problem either. Purchasing runs through ERP. Your WMS runs the warehouse. Your QMS runs inspections. HR software runs people. Each is good at its own job. But the handoffs, approvals, and checks that move between them have no owner and no record. They run on email, chat, and whoever remembers.

That space is what Smartsheet is built for. As the Execution Hub, Smartsheet is where the work between your systems gets done. A process is defined once, runs the same way everywhere it's used, and gives every handoff an owner and a record. Your systems of record stay where they are. The way your organization operates across all of them finally has a home. The Execution Hub is the job all of Smartsheet's products do together, from the work itself to the content it produces and the strategy above it. For how your operation runs, it starts where the work gets run, in Smartsheet. One hub. One job. End execution drift.

Here is how the latest Smartsheet releases close the gap, starting with the process itself.

Smartsheet keeps one process consistent everywhere it runs

The problem: Most drift starts with a copy. The SOP, the checklist, or the standard work gets handed to each team as a file, and from that moment every version is on its own. Nobody can see which copy changed until the numbers stop lining up, and when the process itself changes after an audit finding or a new policy, someone has to chase down and update every copy.

Available now:

• Advanced Portfolios, launching at ENGAGE and natively accessible in Smartsheet, keeps every site on the same version of the process. Every plant, distribution center, region, or product launch starts from one template and rolls up to one live view, at 50 instances or 5,000. When the process changes, Publish changes rolls the revision out to every live instance in one step, so a corrective action or kaizen improvement reaches every site, not just the one that found it.

• The Creation Agent stands up the next site or rollout from a sentence. Answer a few questions, and the plan, automations, and dashboard are created in minutes.

• Dashboards built from a single prompt with dynamic filters let each individual personalize the same view to their own work.

In early access and coming soon:

• Dependent and linked dropdowns are now in early access. They keep every site choosing from the same live list on every inspection form and checklist.
• Soon, markdown files for your written procedures can live in the workspace as pages, right next to the sheets they describe, so your teams and your AI follow the same instructions.

Copies drift. A connected process holds.

See it in your process.  Book a demo

Smartsheet handles the follow-up, so handoffs don't stall

The problem: Most recurring work stalls between teams, rather than within them. The start of the week goes towards pinging owners, scanning sheets for blank fields and stale dates, and assembling a report that shows what you already spent the week chasing.

A process doesn't need AI everywhere. It needs the routine follow-up handled, so people spend their time on the exceptions instead of the reminders. Sometimes that takes a sentence. Sometimes it takes an agent running through the weekly check while you're on the floor or in a meeting. That's the right amount of AI in the right place.

Available now:

• Automations you build by asking turn a described handoff, approval, or reminder into a working rule.
• Agentic workflows let you schedule AI to run recurring work on its own. Ask for something like "every Monday at 6am, before first shift, summarize which handoffs are past due at every plant and who owns each one, and email it to the site leads," and it runs on the schedule you set.

• Specialist agents take the checks that need judgment. Ask Smart Assist for a data quality check, or put one on a schedule, and it flags what would stall the next team, like a corrective action with no owner or a due date nobody has updated.

Coming next:

• Conversational integrations, soon. Ask Smart Assist for the data you need from another system. It sets up the connection, shows you the plan, and lands the rows in your sheet once you approve.
• One view of every automation. Errors surface first with a plain-language reason, like a renamed column, so you can fix them or switch off a batch of stale ones without opening a single sheet.
• In 2027, a central hub adds every integration and agent to that view, including what's running, who owns it, and what's broken right now.

The follow-up still happens. Nobody has to remember to do it.

Smartsheet brings your process into the AI your teams already use

The problem: Your teams already have AI tools they like. The risk isn't the tool. It's that each one works from its own copy of how your department operates.

Available now:

• The Smartsheet MCP Server, available since March, puts your Smartsheet work inside Claude, ChatGPT, Copilot, Gemini, and Amazon Quick, with more than 80 tools and the same capabilities and permissions people already have. If a person can't open something in Smartsheet, their AI can't either.
• Smart Assist, now on mobile too, works across your sheets on the same record as your team. It shows what it's changing, and it asks before it acts.

Here's what that connection changes.

• On its own, an AI model given last week's audit notes produces a tidy list of fixes, then stops. It can't tell which teams run which version of the process, or who owns the next step.

• Connected to Smartsheet, the same model can see that two plants are still on last quarter's inspection checklist, that a supplier review has waited on legal for nine days, and who owns each fix.

The process, the owners, and the history live in Smartsheet, in what we call the Execution Graph, and every cycle of a recurring process adds to what the next answer can draw on. Customer data is never used to train third-party foundation models.

The tool is your team's choice. The process is still yours.

Bring AI inside your process.  Book a demo

Smartsheet keeps you in charge of AI in your process

The problem: Before AI does real work in a process you're accountable for, you need to know what it can reach, what it can change, and who decides. Quality and compliance reviews ask the same questions about every step.

Available now:

• Permissions and logging that cover AI. For work in Smartsheet, AI reaches only what the person asking can reach, because it works within their existing permissions, and every change is logged.
• Admin AI controls let admins decide which AI capabilities are on and which AI connectors the organization allows.
• Data Classification in Safeguard lets admins set the labels and people classify assets as they work, with every label reported, so you can see where sensitive data lives, from supplier pricing to batch records.

A process you can't audit isn't a standard. It's a suggestion.

What to do next

The place to start is wherever holding the standard costs the most time.

• If every site runs its own version of the process, start with the one that drifts most, like a changeover checklist, a supplier onboarding, or a site opening, and put it on one Advanced Portfolios template.
• If your mornings go towards chasing status, turn that recurring check into an agentic workflow and let it come to you.
• If teams are already using AI on their own, connect Smartsheet to their tools using the MCP Server, within the permissions you already set.

• If an auditor will ask who changed what, start with Data Classification and admin AI controls.

   

Stream the ENGAGE 2026 keynote to see it in action, read the main ENGAGE innovation blog for every release, and book a demo or explore Smartsheet for operations to see how it fits the way your team operates.

The standard is yours. Let Smartsheet hold it.