Skip to content
Knowledge
  • Pages
    • Getting Started
      • Welcome to TandemTask
    • Account
      • Understanding TandemTask Records, Objects, and Associations
      • Creating Records
        • Creating a Project
    • Product Knowledge Base
      • Feature
        • About this feature
        • Feature guide
        • Feature FAQs
        • Issue with feature
    • Policies
    • Security best practices
    • Helpful tools
    • Glossary
    • FAQs
Knowledge
/
/
Understanding TandemTask Records, Objects, and Associations
Share
Explore

Understanding TandemTask Records, Objects, and Associations

March 19, 2026

Learn how Your Account, Spaces, Companies, Contacts, Deals, Projects, Tasks, and Subtasks work together

Overview

TandemTask organizes your business using seven connected objects: Your Account contains Spaces (like Sales or Customer Success), which contain Companies (your clients) and their Contacts (people). Deals track sales opportunities, Projects manage work initiatives, and Tasks break down that work into actionable items with optional Subtasks. Understanding how these objects associate with each other helps you structure your data effectively and track everything from initial outreach through deal close and delivery.

Core Objects

TandemTask organizes data using these objects (listed from broadest to most specific):
Account - Your organization's TandemTask instance
Spaces - Departments or functional areas within your account
Companies - The organizations you work with (customers, prospects, partners)
Contacts - Individual people at those organizations
Deals - Sales opportunities associated with Companies
Projects - Work initiatives associated with Companies
Tasks - Actionable work items within Projects
Subtasks - Detailed steps within Tasks

Object Associations

⁠
TandemTask_Hierarchy_v3
⁠
⁠

Your Account

Your Account is the root object. Everything in TandemTask exists within your Account. This is where you manage users, billing, and account-level settings.
Contains: Spaces

Spaces

Spaces organize your data by department, team, or functional area. Each Space operates independently, allowing different teams to work without interfering with each other's data.
Parent object: Your Account Contains: Companies, Contacts, Projects Common uses: Sales, Customer Success, Operations, Marketing
Example: Your Sales team works in the "Sales" Space while your Customer Success team works in the "Customer Success" Space. A Company can exist in multiple Spaces if different teams need to work with the same account.

Companies

Companies represent the organizations you do business with. This is your account-level object where you track organization-wide information, relationships, and deals.
Parent object: Space Contains: Contacts, Projects Associated with: Contacts (one-to-many), Projects (one-to-many)
Example: "Acme Corporation" is a Company record. You can store their industry, company size, contract value, renewal date, and other account-level data here.

Contacts

Contacts are individual people associated with a Company. Each Contact must belong to at least one Company.
Parent object: Companies Associated with: Companies (many-to-one), Projects (many-to-many) Contains: Nothing (Contacts are end-node objects for relationship tracking)
Example: Sarah Johnson (VP of Sales) and Mike Chen (IT Administrator) are both Contact records associated with Acme Corporation. When you create a Project for Acme Corporation, you can assign specific Contacts as stakeholders.

Deals

Deals represent sales opportunities with a Company. Each Deal must be associated with a Company and can be linked to specific Contacts, Projects, and Tasks. Deals bridge your sales pipeline with your execution work.
Parent object: Companies Associated with: Companies (many-to-one), Contacts (many-to-many), Projects (many-to-many), Tasks (many-to-many) Contains: Nothing (Deals are an associative object)
Example: "Acme Corp - Annual Enterprise License" is a Deal associated with Acme Corporation. You might associate Contacts Sarah Johnson (decision maker) and Mike Chen (technical evaluator) with this Deal. As the Deal progresses, you can link it to a "Product Demo - Acme Corp" Project and specific Tasks like "Send pricing proposal" or "Schedule executive briefing."
Common use cases:
Track sales opportunities through your pipeline
Associate revenue forecasts with specific companies
Connect sales activities (Tasks) directly to the deals they support
Link post-sale Projects (like onboarding) back to the original Deal

Projects

Projects represent work you're doing for or with a Company. Every Project must be associated with a Company. Projects bridge your CRM relationships (Companies and Contacts) with your execution (Tasks and Subtasks).
Parent object: Companies Associated with: Companies (many-to-one), Contacts (many-to-many) Contains: Tasks
Example: "Q4 Business Review - Acme Corp" is a Project associated with Acme Corporation and assigned to Contacts Sarah Johnson and Mike Chen.

Tasks

Tasks are individual work items within a Project. They represent specific actions that need to be completed.
Parent object: Projects Contains: Subtasks (optional) Associated with: Projects (many-to-one)
Example: Within the "Q4 Business Review - Acme Corp" Project, you might have Tasks like "Prepare usage analysis," "Schedule review meeting," and "Create presentation deck."

Subtasks

Subtasks break down complex Tasks into smaller, manageable steps. Subtasks are optional and should be used when a Task requires multiple discrete actions.
Parent object: Tasks Contains: Nothing (Subtasks are the most granular object) Associated with: Tasks (many-to-one)
Example: The Task "Prepare usage analysis" might contain Subtasks: "Export usage data from platform," "Calculate key metrics," and "Create visualizations."

How Associations Work in Practice

When you create objects in TandemTask, the associations determine what information you need to provide:
Creating a Space: Select your Account
⁠
Creating a Company
⁠
: Select which Space it belongs to
⁠
Creating a Contact:
⁠
Select which Company (or Companies) they work for
⁠
Creating a Deal
⁠
: Select the Company it's for, then assign Contacts, Projects, and Tasks
⁠
Creating a Project
⁠
: Select the Company it's for, and optionally assign Contacts and associate with Deals
⁠
Creating a Task
⁠
: Select which Project it belongs to, and optionally associate with Deals
Creating a Subtask: Select which Task it belongs to
These associations also determine how you can view and filter your data. For example:
View all Deals associated with a specific Company
See all Projects and Tasks linked to a specific Deal
View all Contacts who work at companies in your Sales Space
Filter Tasks by the Company they're ultimately connected to through their parent Project
Track all work (Deals, Projects, Tasks, Subtasks) related to a specific Contact

Data Flow Example

Here's how the objects work together for a typical customer engagement:
You create Acme Corporation as a Company in your Sales Space
You add Sarah Johnson and Mike Chen as Contacts associated with Acme Corporation
You create a "Acme Corp - Enterprise License" Deal associated with Acme Corporation, with Sarah as the decision maker
During the sales process, you create a "Product Demo - Acme Corp" Project associated with Acme Corporation and link it to the Deal
Within that Project, you create Tasks like "Prepare demo environment" and "Send follow-up proposal"
You associate the "Send follow-up proposal" Task directly with the Deal for tracking
Once the Deal closes, you move Acme Corp to your Customer Success Space
You create an "Onboarding - Acme Corp" Project (also linked to the original Deal for reference)
For the complex "Configure workspace" Task, you add Subtasks like "Set up SSO," "Create custom fields," and "Import data"
Now when you view the Acme Corporation record, you see:
All associated Contacts (Sarah, Mike)
All Deals (Enterprise License)
All Projects (Product Demo, Onboarding)
Through the Deal, you can see which Projects and Tasks contributed to closing it
Through Projects, you can access all related Tasks and Subtasks
This structure keeps your sales pipeline, customer relationships, and work execution connected while maintaining clear data organization.

Best Practices

Use Spaces to separate teams, not customers. Don't create a Space for each customer—create a Space for each team or functional area. Customers are represented by Company records.
Associate Contacts with the right Company. Make sure every Contact is linked to their organization. This ensures Projects, Deals, and communication stay properly connected.
Link Deals to relevant Projects and Tasks. When working on sales activities, associate them with the Deal they support. This creates clear visibility into what work is driving revenue.
Create Projects for distinct initiatives. Don't create one giant Project per customer. Instead, create separate Projects for onboarding, quarterly reviews, support escalations, etc.
Use Tasks for trackable work items. Each Task should represent something that can be completed and checked off. Avoid creating Tasks that are too broad or ongoing.
Reserve Subtasks for complex Tasks. Not every Task needs Subtasks. Use them when breaking down a Task makes the work clearer and more manageable.

Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.