HubSpot Work Tables: How Teams Organize Operational Data

HubSpot Work Tables are spreadsheet-style tables inside HubSpot Work where teams track operational work, like client onboardings, content requests, and deal desk queues, with direct links to the CRM records behind that work. They give your work around contacts, deals, and tickets a home in HubSpot, so it stops living in spreadsheets and project tools that drift out of sync with the CRM.

Each row in a Work Table is one piece of work, and each column holds a detail your team tracks, such as the owner, stage, due date, or linked HubSpot company. Tables also anchor every HubSpot Work project, since the documents, forms, and AI agents inside it read from or write to them.

Getting real value from HubSpot Work starts with a solid setup and a CRM that's ready for it. At Campaign Creators, we help teams set up HubSpot Work, map their processes into tables and agents, and clean up the data those tools rely on through our HubSpot onboarding and setup, data migration, and AI agent implementation services.

Key Takeaways

• HubSpot Work Tables store operational data, such as onboarding stages, owners, and deadlines, inside HubSpot next to your CRM records.
• Every HubSpot Work project is built around tables, and its documents, forms, and AI agents use those tables as their data source.
• Columns can hold CRM record lookups, dropdowns, dates, statuses, files, and links to Work documents.
• HubSpot Work is in public beta, so a Super Admin has to enroll the account before anyone can build a table.

What Are HubSpot Work Tables?

HubSpot Work Tables are structured tables that hold the operational side of your CRM: the tasks, stages, and handoffs your team uses for each customer.

Each table sits inside a three-level structure.

• Workspaces hold every project and asset for a team or process, such as client onboarding or IT management.
• Projects track one initiative inside a workspace and contain their own tables, documents, forms, and AI agents.
• Tables store the rows and columns that every other asset in the project draws from.

You'll find Work Tables in your HubSpot account under More, then Work Management. Pick a workspace from the dropdown in the upper left, and its tables appear in the left sidebar.

Why Move Operational Data Out of Spreadsheets?

Moving operational data out of spreadsheets cuts the time lost to app switching and the errors that creep into manual files. Work Tables handle both by keeping the work in the same platform as the customer data it depends on.

In a Harvard Business Review study of 137 workers at three Fortune 500 companies, people toggled between apps and websites nearly 1,200 times a day. That added up to just under four hours a week spent reorienting, or roughly 9% of their time at work. Every tracker that lives outside the CRM adds a few more of those switches.

Spreadsheets also fail quietly. A literature review published in Frontiers of Computer Science found that 94% of spreadsheets used in business decision-making contain errors, from mistyped inputs to broken formulas.

Work Tables close several of those gaps by design. Dropdowns and status fields keep entries consistent, CRM lookups pull in record details without retyping, and forms write submissions straight into the right rows. Everyone also edits one live table, so there's no "final_v3" copy sitting in someone's inbox.

How Do Work Tables Compare to CRM Objects, HubDB, and Spreadsheets?

Work Tables hold the work your team does around customer records, CRM objects hold the customer records themselves, and HubDB holds structured content for your website. Spreadsheets can hold anything, but they have no live connection to HubSpot.

A simple way to decide where data belongs is to ask what it describes. Facts about a customer go on a CRM record, and the tasks, stages, and handoffs your team works through for that customer go in a Work Table.

One naming detail trips people up. Projects in HubSpot Work are separate from the CRM's projects object and from Breeze Assistant projects.

What Can You Store in a Work Table?

A Work Table stores one row per piece of work, plus the details, files, and CRM links your team needs to finish it. Each row behaves like an action item that teammates can add, edit, mark as done, or delete.

HubSpot currently offers these column types.

• Status for stages like New, In Progress, or At Risk
• Text for notes, blockers, and other free-form details
• Date for kickoffs, deadlines, and handoffs
• Dropdowns for fixed choices like request type or service tier
• CRM reference fields that look up a contact, company, or deal from your HubSpot records
• Document links that connect a row to a playbook or recap stored in the same project

Rows can also hold sub-items for smaller tasks, and groups sort rows into categories like region or client segment.

How Do Views Help Different Teams Use the Same Table?

Views help different teams use the same table by showing its data with their own filters and layouts, while the underlying rows stay in one place. Each saved view sits as a tab above the table, so one onboarding tracker can serve a CS manager, an implementation lead, and an executive at once.

HubSpot's documentation highlights three visualization types.

• Table view shows rows and columns for bulk edits and detailed review.
• Board view groups rows into columns by a field like onboarding stage, which makes stalled items easy to spot.
• Calendar view plots rows by date so deadlines and kickoffs are visible at a glance.

You can build a view by hand with the add view icon or describe it in the prompt bar. HubSpot's own example asks for a board view grouped by onboarding stage that shows the owner, target date, implementation status, and blockers for every active client. Table color, row height, and text wrapping are adjustable per view as well.

How Do Forms, Documents, and AI Agents Use Work Tables?

Forms add rows to a Work Table, documents turn table data into readable guides, and AI agents monitor tables and act on them. That's why the table is usually the first asset to build in a project.

Forms collect information and send each submission to a single Work Table, which keeps rows consistent and can kick off automations. A client intake questionnaire, for example, can create a new onboarding row with the stage already set to New. Work forms show up in the marketing forms tool, but their submissions land in the Work Table you choose.

Documents hold information that doesn't fit in rows, such as playbooks, briefs, and meeting recaps. They can use a table as source material, so an onboarding playbook can pull its stages, owners, and timelines straight from the tracker. Teammates can co-edit, comment with mentions, review line-by-line version history, and export documents as Markdown.

AI agents watch a table and act on it based on rules you write. An onboarding agent can check active rows every weekday morning, create standard sub-items with due dates, flag rows as At Risk when a deadline slips, and notify the owner. You can also set hard limits, like never deleting records or changing client-submitted data. AI workflow actions inside these agents consume HubSpot Credits.

Which Workflows Fit Work Tables Best?

Work Tables fit best with processes that repeat, involve several owners, and depend on CRM records. HubSpot names client onboarding, campaign and event coordination, deal desk routing, content pipelines, and internal request intake among the processes the product is built to run.

A spreadsheet still works for one-off analysis or modeling that never touches a customer record. Once a process repeats every week and depends on deal or contact details, a Work Table keeps that context attached to the work.

How Should Teams Structure a Work Table?

Teams should structure a Work Table around one process, give each unit of work its own row, and keep only the columns people filter or act on. These habits keep a table usable as it grows.

• Build one table per process. An onboarding tracker and an IT request log have different stages and owners, so each deserves its own table.
• Decide what a row represents. One row should equal one client, one request, or one event, with smaller steps tracked as sub-items.
• Use dropdowns and statuses for anything you sort by. Free text works for notes, but stages, priorities, and request types need fixed options to power views and agent rules.
• Link CRM records with lookup columns. A lookup keeps company names, contacts, and deal details current as the CRM changes.
• Name views after the people who use them. A view called CS Weekly Review or Exec Deadlines is easy to find a month later.
• Start lean. Forms and agents depend on your column setup, so a short first version is easier to adjust once real work starts flowing through it.

What Should You Clean Up in Your CRM Before Building Work Tables?

Before building Work Tables, clean up duplicate records, missing owners, inconsistent property values, and broken associations in your CRM. Lookup columns, rows generated from CRM data, and agents that read deal properties all inherit those errors.

Here's what to check in each area.

• Duplicates. Merge duplicate contacts and companies so each lookup links to one clean record.
• Ownership. Assign owners on companies and deals, since agents and routing rules use owner fields to decide who gets notified.
• Property values. Standardize the properties a table will reference, like lifecycle stage, deal stage, and products purchased, so filters and views group rows correctly.
• Associations. Confirm contacts, companies, and deals are linked to each other so a row pulls in the right related records.

Portals with years of migrations and integrations layered on them usually need an architecture review first. Fixing the data model before you build saves you from rebuilding tables and agents later.

Need a hand cleaning up your CRM before getting started with Work Tables? We can help you get everything organized.

How Do You Create a Work Table in HubSpot?

You can create a Work Table by describing it to the HubSpot Work AI assistant or by building it from scratch inside a project. HubSpot Work is available on Starter, Professional, and Enterprise editions of Marketing Hub, Sales Hub, Service Hub, Data Hub, and Content Hub, along with Professional and Enterprise editions of Smart CRM and Revenue Hub.

1. Have a Super Admin enroll the account in the HubSpot Work public beta and turn on the setting that gives users access to generative AI tools.
2. Go to More, then Work Management, and create your first workspace with a name and the people or teams who need access.
3. Pick a starting point. You can write a custom prompt, choose one of HubSpot's template prompts, or start from a blank workspace.
4. Describe the table in the prompt bar. Name its purpose, define each column, explain how rows get created, and say which teams can edit or view it.
5. Review the plan the assistant generates, adjust anything that looks off, and click Approve to build the table.
6. Refine the result with follow-up prompts, then add views, a form, or an agent once the columns are right.

HubSpot recommends being specific in your prompts and adding a line like "Ask me clarifying questions before finalizing the build" to cut down on back-and-forth with the assistant.

Who Can Access and Edit a Work Table?

Access to a Work Table depends on each user's seat and their role in the table's workspace and project. Everyone needs an assigned Core, Sales, or Service seat, and by default a table inherits permissions from its project, which inherits them from its workspace.

Workspaces can also be set to Private, Organization can view, or Organization can edit. The two organization-wide options only reach users whose Work Management permission is switched on in Users & Teams settings. For sensitive data, you can make a project or a single table invite-only, which overrides everything it would normally inherit.

Is Your CRM Ready for HubSpot Work?

Before you start building, it’s worth taking a closer look at your CRM data and architecture to see what’s working well and where a few improvements could make a difference.

Run the HubSpot AI Readiness Scorecard to see how prepared your data and architecture are for AI-first tools like HubSpot Work, and identify areas that may need attention before you get started.

Want a hand turning your results into a working setup? Our team would love to help you sort through the gaps, strengthen your CRM foundation, and get more out of HubSpot Work.