Set up your team for consistent, reliable project delivery

Run projects consistently and reliably from the start. With the right foundations in place, every project, from setup to delivery, begins with accurate data, the right people, and a repeatable structure your team can trust.

Getting startedDelivering projects

Read time

10 minutes

Goal

Set up your site

Primary Tool

Teamwork.com

Why this matters

The quality of every project decision you make, from who works on what to how work is tracked and whether a project is profitable, depends entirely on the foundations you put in place at the start.

Task completed

Outcome

Every project starts on solid ground

Setup decisions made here shape everything downstream: billing, reporting, workload, and profitability.

Life preserver

Helps you

Deliver consistently across clients

Roles, templates, and structure mean your team follows the same reliable process every time, regardless of who's running the project.

Unlocked padlock

Unlocks

Intake, delivery, and reporting

Without this foundation, time data is inaccurate, reports can't be compared, and intake routes to the wrong place.

Key actions

01 - Bring in the right people with the right access

Who can see and change things determines how reliable your project data stays as projects scale.

  • Invite team members who will actively contribute (assign tasks, log time, or manage the project).

  • Assign Project Administrator access to anyone managing financials, settings, or project structure.

  • Set site-level permissions to define what each person can see and do across your account.

  • Configure project privacy to protect sensitive client or financial information.

02 - Give everyone a role so work can be assigned by discipline

With roles, you can filter, assign, and report by function across every project, making resourcing and reporting more consistent.

  • Create role types that reflect your team's functions (e.g. Designer, Developer, Project Manager).

  • Assign a role to every team member — people without roles are invisible to role-based filtering.

  • Keep role names consistent across your account to ensure accurate reporting.

03 - Organize people into teams

Teams turn your people view into a planning and reporting layer. You can filter work by team, compare workloads across groups, and report on delivery by unit.

  • Group people into the delivery units that reflect how your organization works (e.g., Design, Engineering, Client Services).

  • Use teams as a filter across projects, workload, and reporting views.

  • Keep teams updated as your organization's structure changes.

04 - Add people to projects with the right project-level permissions

Project-level permissions control who can manage a project versus who simply works within it. Setting these correctly keeps financial data, settings, and reporting in the right hands.

  • Add only the team members who will actively contribute to the project.

  • Assign Project Admin access to anyone who needs to manage project settings, budgets, or financials.

  • Set project privacy to control whether the project is visible to all site members or restricted to assigned people only.

05 - Add billable and cost rates for your team

Rates connect your people to your project financials. Once set, every hour logged carries a cost and revenue value so you can see whether a project is on track to be profitable before it is too late to act.

  • Add a site-level billable and cost rate for each team member.

  • Set project-level rates before any project work begins.

  • Review and update rates whenever compensation or billing terms change.

Key concepts

  • Site permissions vs. project permissions

    Site permissions control access across your whole account. Project permissions control access within a specific project. Both layers are needed: one sets the ceiling, the other sets the detail.

  • Project Admin vs. team member

    A team member contributes to assigned work. A Project Admin manages settings, financials, and structure. Anyone who needs to edit the project itself should be a Project Admin.

Best practices

  • Do this

    • Assign roles to every team member before creating projects.

    • Add cost and billable rates upfront.

    • Keep permissions and project roles consistent across teams to avoid reporting issues later.

    • Only add people to a project who will actively contribute to it.

    • Keep teams and roles updated as your organization evolves.

  • Watch out for

    • Skipping billing setup. Every hour logged without it creates financial data you can't trust.

    • Adding too many people to a project. It creates noise and blurs accountability.

    • Leaving permissions unconfigured. The wrong people editing settings cause compounding problems.

Next steps