Skip to main content

How do I use project name variables?

Cassandra Yost
Updated

Project name variables let you automatically generate consistent, standardized project names when you create projects from templates by pulling data from your client, engagement, and project settings.

Using Project Name Placeholder Variables

You can build dynamic project names that automatically populate when a project is created from a template.

Project name variables are added to the Project Name Pattern field within a project template, and each variable is replaced with live data at creation time.
All variables must be wrapped in double curly braces, and static text and variables can be combined in any order.

For example, {{client.name}} inserts the client’s name into the project title.

  • Updating a project template does not rename existing projects.
  • Missing variable data is replaced with a blank space.
  • Generated project names can be edited manually after creation.

Configuring A Project Name Pattern

You can define how project names are generated directly from a project template.

  1. Select Settings in the bottom-left corner of the screen.
  2. Navigate to Project Templates.
  3. Open the project template you want to update.
    • Project name variables apply only when a project is first created.
  4. In Details, locate the Project Name Pattern field.
  5. Enter your static text and project name variables, or select variables using the picker if available.
  6. Preview the generated project name, and then save your changes.

Available Client Fields

You can insert client-specific data into your project name to ensure consistency across engagements.

  • client.name inserts the client name.
  • client.group_name inserts the client group name.
  • client.office inserts the client office location.

Available Engagement Fields

You can reference engagement details to align project names with fiscal or calendar periods.

  • engagement.fiscal_year inserts the engagement fiscal year.
  • engagement.calendar_year inserts the engagement calendar year.
  • engagement.id inserts the engagement ID.

Available Project Fields

You can include project-specific information that reflects timing or service details.

  • project.start_year inserts the project start year.
  • project.start_month inserts the project start month.
  • project.service_line inserts the service line.

Example Project Name Patterns

You can combine variables and static text to match your firm’s naming conventions.

  • Tax services: Fiscal Year {{engagement.fiscal_year}} - {{client.name}} - {{project.service_line}}
  • Bookkeeping services: {{engagement.calendar_year}} - {{client.name}} - Monthly Bookkeeping
  • Audit services: FY {{engagement.fiscal_year}} Audit - {{client.name}}

Related articles