Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Creating a Project

Your step-by-step guide to creating and configuring a new project in TandemTask

Overview

Projects are work initiatives tied to specific Companies in TandemTask. Whether you're managing a customer onboarding, running an internal initiative, or delivering a service engagement, Projects help you organize related Tasks, track progress, and collaborate with your team. Every Project must be associated with a Company, and you can assign Contacts as stakeholders to keep everyone involved in the loop. This article walks you through creating a Project, configuring its settings, and understanding how it connects to your broader workflow.

Before You Begin

Before creating a Project, make sure you have:

  • A Company created - Projects must be associated with a Company. If you haven't created the Company yet, see Creating a Company (coming soon).
  • Appropriate permissions - Depending on your role, you may need specific permissions to create Projects. If you're unsure, contact your account administrator or reach out to support@tandemtask.com.
  • Contact information (optional) - If you want to assign specific people as Project stakeholders, you'll need Contacts created for that Company. See Creating a Contact (coming soon).

Creating a Project

Follow these steps to create a new Project:

Step 1: Navigate to Projects

Log into TandemTask at app.tandemtask.com and click Projects in the main navigation menu. This displays all existing Projects across your Spaces.

Step 2: Start a New Project

Click the + Add Project button (typically found in the upper right corner or at the top of the Projects list).

Step 3: Select the Company

In the Project creation form, select which Company this Project is for. The dropdown will show all Companies in your accessible Spaces.

Tip: If you can't find the Company you're looking for, it may be in a different Space than you expected, or it may not exist yet. Use the search function in the dropdown or create the Company first before proceeding.

Step 4: Name Your Project

Enter a clear, descriptive Project Name that explains what this initiative is about. Good Project names are specific enough to be meaningful at a glance.

Examples of effective Project names:

  • "Customer Onboarding"
  • "Website Redesign"
  • "Feature Requests"
  • "Quarterly Business Reviews"

Avoid vague names like: "Project 1," "Work," or "TBD"

Step 5: Add a Description (optional but recommended)

In the Description field, provide context about what this Project aims to accomplish, key deliverables, or important background information. This helps team members understand the Project's purpose without needing additional explanation.

Example description:
"Quarterly business review meeting with customer leadership. Goals: present usage analytics, discuss expansion opportunities, gather feedback on roadmap priorities. Deliverables: QBR deck, follow-up proposal, meeting notes."

Step 6: Set Project Dates (optional)

Add Due Date plus Start Date and End Date if your Project has specific timeline requirements. These dates help with planning and can be used to filter and view Projects on timeline-based views (available in Pro and Enterprise plans).

  • Due Date: when the project is actually due. The deadline.
  • Start Date: when you first start work on the project.
  • End Date: when all work is finalized or closed on the project. For example, the "End Date" may be after the "Due Date" if it was delivered overdue.

Note: Individual Tasks and Subtasks within the Project can have their own due dates independent of the Project's overall timeline.

Step 7: Assign Project Contacts, Leads, and Members (optional)

If specific Users or Contacts should be associated with this Project, add them in the fields for: Project Lead, Project Members, or Company Contacts.

  • Project Lead: the contact(s) leading the project. Typically the person who created the project or has the most ownership, work, or guidance over the project.
  • Project Members: anyone who is collaborating on the project, and isn't already assigned as a Project Lead or Company Contact.
  • Company Contacts: contacts at the company (internal or client) who are associated with the project, but aren't necessarily involved with the day-to-day work or deliverables.

These are typically:

  • Customer contacts who need visibility into the work
  • Decision makers for the initiative
  • Key collaborators from the client side

Example: For an onboarding Project, you might assign the customer's implementation lead as the "Project Lead", while their technical administrator might be a "Project Member", and the billing contact or budget holder might be a "Company Contact."

IMPORTANT NOTE: Anyone who is not a "Project Member", "Project Lead", "Company Contact", or the creator of the project may not be able to view or access the project. You must add contacts accordingly. For issues otherwise, please contact to our support team.

Step 8: Associate with a Deal (optional)

If this Project is related to a sales opportunity, you can link it to a Deal record. This creates visibility between your sales pipeline and delivery work.

Common scenarios:

  • Pre-sale Projects (demos, pilots, proof-of-concepts) linked to open Deals
  • Post-sale Projects (onboarding, implementation) linked to closed-won Deals for tracking

See Associating Projects and Deals (coming soon) for more details.

Step 9: Select the Space (if applicable)

Depending on your account configuration, you may be prompted to select which Space the Project belongs to. Spaces organize work by department or team (Engineering, Sales, Customer Success, Operations, etc.).

Tip: If you're creating a Project for a Company that exists in multiple Spaces, choose the Space that matches the team responsible for this particular initiative.

Step 10: Save the Project

Click Create Project or Save to finalize. Your new Project is now created and appears in your Projects list.

After Creating Your Project

Once your Project is created, you can:

  • Add Tasks - Break down the Project into actionable work items. See Creating a Task (coming soon).
  • Assign team members - Add internal collaborators to specific Tasks within the Project. See Adding Team Members to Projects and Tasks (coming soon).
  • Track progress - Use Board View, List View, or Table View (depending on your plan) to monitor Task completion and Project status.
  • Update Project details - Edit the Project name, description, dates, or associations at any time by clicking into the Project and selecting "Edit" or the settings icon.

Project Fields Explained

Here's what each field does and when to use it:

Space (Required) - The department or functional area this Project belongs to. Required to help you distinguish which workspace the project belongs to.

Company (required) - The organization this Project is for. Projects cannot exist without a Company association. This ensures all your work stays connected to your customer relationships.

💡Pro Tip: You can include a single or multiple companies and spaces.

The "Company" could be the same as the "Space", such as for internal projects.

  • Example: "Feature Releases"
    • Project name: Feature Releases
    • Space: TandemTask
    • Company: TandemTask

Or, the "Company" could be different than the "Space", such as for partnership projects. 

  • Example: "Partnerships"
    • Project name: Acme + TandemTask Partnership
    • Space: TandemTask
    • Company: Acme Corp, TandemTask

Project Name (required) - The title of your Project. Make it descriptive and specific so team members can identify it easily in lists and reports.

Description (optional) - Context about the Project's goals, scope, or background. Particularly useful for Projects where multiple people will be collaborating or where context might otherwise live in scattered emails or notes.

Start Date / Due Date (optional) - Timeline boundaries for the Project. These don't enforce anything automatically but provide visibility and structure for planning purposes.

Contacts/Stakeholders (optional) - People from the Company who should be associated with this Project. These might be decision makers, collaborators, or anyone who needs visibility. Note: These are external stakeholders, not your internal team members (those get assigned at the Task level).

Deal Association (optional) - Links the Project to a sales opportunity. Useful for tracking which Projects support active deals or which post-sale work originated from a specific sales engagement.

Best Practices

Be specific with Project names. Future you (and your teammates) will thank you when the Projects list is easy to scan. "Feature Requests" is infinitely more helpful than "Product."

Use Projects for distinct initiatives, or ongoing work. Each Project should have a defined purpose or deliverable. For ongoing support or maintenance, consider creating an open-ended Project with no definitive Due Date or End Date. (Recurring projects coming soon.)

Add descriptions for context. A two-sentence description now saves multiple Slack messages or emails later when someone asks "what's this Project about?"

Associate relevant Contacts. Adding project members, leads, and company contacts to the Project level means they're automatically visible when you create Tasks within that Project, making it easier to loop them in on specific work items.

Link Projects to Deals when appropriate. If a Project is part of a sales cycle or post-sale delivery tied to revenue, linking it to a Deal creates better visibility for forecasting and reporting.

Don't over-structure at the start. You can always add dates, descriptions, and associations later. Get the Project created, start adding Tasks, and refine details as the work evolves.

Need Help?

  • Starter Plan: Email us at support@tandemtask.com
  • Pro Plan: Email, chat, or call us—plus schedule time with our team for setup assistance
  • Enterprise Plan: Contact your dedicated Project Manager for hands-on help creating Projects and structuring your workflows

Next Steps