Clarizen Project Setup and Budget Allocation


Table of Contents





Components of a Project

  • A budget
  • A defined goal and completion point
  • A planned Start Date and Due Date
  • Tasks with planned Work hours and Resources to complete them
  • A Project Request for Resources to follow


Clarizen "State" Definitions & TSL Usage






              BEST PRACTICE


For newly assigned transfers yet to be scoped; on-boarding is in progress – full project plan is yet to be finalized but client is engaged with TSL for next steps. Move these new funds from requested to active/ draft as quickly as possible. These funds are transferred in as soon as a client signs SOW so the client is still actively engaged. Make sure to look out for lack of scope in project transfer. Schedule an internal intake call as soon as a new transfer is received.

 Ask for SOW prior to kick off and confirming payment terms to verify work can start during call.

Ensure collective approval of SOW and go-forward plan at the onset of project to avoid likelihood of derailing.



Project that is not necessarily scoped, but confident that these funds can activate in the CURRENT quarter. Ex: perhaps there is $60,000 in Requested funds as long-term plan is TBD but if you know that $5k of this will activate this quarter, move $5k to Draft, leaving $55k in Requested. in the planning stage (campaign will move from requested to draft). Draft stage should not last long – 3 months max. This will need to be monitored on a regular basis as we want this to represent work that will activate in CURRENT quarter. Be sure to update Holding Notes as well with details about the Draft funds. Make you sure reconcile the funds – if pulling from Requested, be sure that you move the appropriate amount from Requested to Draft and that the overall total in Clarizen matches Salesforce. Responsibly plan for Draft and work to activate as soon as possible within the quarter. Evaluate Draft projects on a very regular basis, ensuring that move into Active Status within the quarter.


When project is ready for work to begin. It is fully scoped, budgeted, resourced, and ready to execute. Start/end dates are set and resources will begin tracking hours against the project.  It is important to schedule work out as far out into the future as possible. It is also important to allocate all budget and resources on the onset of a campaign.


For retainer projects, set up  monthly/quarterly sub-projects in active status
Not fully planning a campaign at the beginning makes it more difficult to spend the full budget later often requiring a rescope. Create campaigns in Clarizen using the full budget transferred in Salesforce at the beginning of a project.

On Hold

Project that is held up by client, waiting for payment, in process of re-scope; no real direction for clear path forward. 


When a project is on hold, make sure to notify the sales person and accounting. They can help get the project back on track. Not keeping in constant communication with the client.

Check in on the status of an on-hold project weekly until it is back on track.


Project that will not continue; customer or TSL has decided to not move forward with the engagement. Reconciliation of funds spent (if applicable) will need to take place with sales to ensure payment for services rendered up to until point of cancellation as well as adjustments in Salesforce. Talk to sales person and customer experience to determine why project was cancelled. Project needs to be canceled in both Salesforce and Clarizen. N/A When cancelling in Clarizen, make sure that the main project is canceled as well as the sub-projects (canceling at main project level does not propagate to sub-projects). 


<<<<<Insert content from Holly PROC. Include Required Fields>>>>


Roles & Responsibilities


The functional manager in scenarios outlined below is responsible for managing projects and required data inputs from the assignment of a campaign and through closure of the campaign. 

Project Phases & Functions in Clarizen Creative/Digital Campaign Integrated Campaign Customer Journey Campaign

New Project Transfer:

  • Load Tactics or Budget Placeholders
  • Enter pricing as noted on transfer
  • Assign to Project Lead and/or CJ PM
Operations Operations Operations

Project Assignment: 

  • Load, remove, revise projects based on scope updates (all service types)
  • Edit financial fields
Project Lead Project Lead CJ PM

Ongoing Management:

  • Scheduling: Update timelines, add tasks, assign resources
  • Manage Expenses: Request POs, monitor spends, reconcile Expense Sheets when final cost numbers are available
  • Edit financial fields based on scope changes
Project Lead Project Lead CJ PM
  • Outbound projects' weekly lead goals, lead progress/delivery, and time entry


Project Work Breakdown Structure

Following standard Work Breakdown Structure (WBS) is critical to properly report on project progress and budget data points. If this hierarchy is not followed we will omit data or incorrectly report on budget available, revenue earned, project completeness, etc. for the campaign transfer and individual tactics.

Parent Projects: [Briefcase icon] There should be one Parent Project per Project Transfer Number (Ex. “Solutions II | MS-2565”). This is created by Operations.project_work_breakdown_structure_1

Subprojects: [Briefcase icon] There should be at least one subproject for each budgeted service category or deliverable. This is the project level we report on for tactic progress and revenue. There should not be a subproject indented beneath an existing subproject.

Milestones: [Diamond icon] Milestones should be indented within subprojects.

Tasks: [Clipboard icon] Tasks should be grouped within related subprojects, and may be grouped/organized within milestones. No tasks should be "floating" outside of a subproject.


Project Plan Setup

The following steps review TSL’s unique requirements for creating a project plan and entering necessary information.

  1. On the Project Details page, navigate to the “Financial View”.
  2. Create or Edit subprojects to match each tactic or budget line item corresponding to the project transfer or Strategy Canvas scoping document.
    1. Note that Digital Advertising requires two templated subprojects:
      1. “[Facebook, Google, LinkedIn, or Twitter]Ads: $x Setup | $x Management” 
      2. “[Facebook, Google, LinkedIn, or Twitter]Ads: $x Click Spend | $x Pass Through”project_plan_setup_1
    2. Note that if you have an outbound program with variable Price Per Lead for different numbers of leads, you must create a subproject for each Price Per Lead & SQL Goal combination to properly calculate revenue. 
    3. Create New Projects: Open the "Add a New Project" editor, choose the tactic from the Template picklist (recommended) or Enter Name and create tasks later.
    4. Edit Existing Projects: On the Work Plan, hover over the project Name and click the Edit pencil icon that appears to the right. project_plan_setup_2project_plan_setup_3
  3. Complete fields in the project editor window per the following guidelines: 
Field Name Complete the Field for Earned Value Type Definition
Revenue Department Both

Which department reports this project's earned value?

  • Creative/Digital
  • Customer Journey
  • Data
  • Consulting
  • Service Income Other

Templated projects have field pre-set

Custom projects require entry. For list of categorization see Appendix

Earned Value Type Both

How should earned revenue be reported for this project type?

  • Effort-Based: Value is accrued based on time spent
  • Lead-Based: Value is accrued based on SQLs

Template Projects have field pre-set

Custom projects require entry

Fixed Price Effort-Based The fee for a service offering, including any expenses/costs
Lead-Based Program Price Lead-Based The total fee for outbound program that have a price per lead
Billable Both

Any project or expense-related subproject that is within the scope of work and has an associated budget is billable. All projects and tasks will be Billable by default. 

Billable Projects: Most tasks and meetings are billable to the customer, including project management, strategy management, client consulting/training calls & meetings, production execution, data analysis, reporting are all examples of billable project time. 

Non-Billable Projects: May include internal discussion about customer management, account ramp-up/training for new team members, etc. By choosing non-billable, all tasks/time within the project will have $0 budget dollars associated and progress will not count toward Revenue Earned Value. Enter $0 in the project's Fixed Price field on Non-Billable subprojects.

Total SQL Goal Both

In Lead-Based programs, enter the total number of SQLs promised to the customer

In Effort-Based program, enter the total numbers of SQLs estimated/expected to deliver

 4. Plan projects’ related tasks, Work hours planned, Duration, Start Date, Due Date, and assign Resources. If your project has a Customer Journey program, go to Step 5. If not, go to Step 8.

5. Navigate to the “CJ Performance View” on the project.

6. Expand the project and enter lead targets into the “Weekly SQL Goal” field on the row of the corresponding weekly milestones. On Lead-Based projects, you will see the weekly milestones’ “Expected Revenue” amount recalculate to “Price Per Lead” X “Weekly SQL Goal”. Continue until “Weekly SQL Goal Totals” (planned SQLs) equals the “Total SQL Goal”.

Field Name Use for Earned Value Type Definition
Weekly SQL Goal Both Number of SQLs TSL plans to deliver within the week

Enter on the weekly Milestones under the related subproject

7. If there are extra weekly milestones, delete them. You are complete with the Lead-Based program setup when the “Expected Revenue” on the subproject equals the “Lead-Based Program Price”.


8. You are complete with full campaign setup when the budget has been allocated to scoped service projects, unscoped budget placeholder projects, and expense-related line items.

9. Change the Parent project State per the following guidelines:

a. Requested: Campaign just transferred

b. Draft: You are editing the project Work Plan, budget, etc. and the kickoff call/meeting has not occurred

c. Active: Internal kickoff call/meeting has occurred

10. Change individual subprojects’ State per the following guidelines:

Engagement Model Project Status Scenario State
All Have not confirmed with the client, and have not confirmed start/due date needs Requested
All Custom Funds that require strategist recommendations, sales support, or client confirmation on scope Requested
System Advanced System Recommended by strategist/in canvas but do not have confirmed start/due date. May need more discussion about how it relates to other work and/or client approval.  Requested
System Advanced System Recommended by strategist/in canvas and do have confirmed start/due date, but may need more planning details confirmed before we are ready to schedule for execution Draft
Campaigns/Tactical Tactics defined pre-sale that have been confirmed with the client on initial kickoff call Draft
All Production is ready to be scheduled for execution by the assigned resources Active
System Advanced System Funds that are time-bound/TSL is accountable to execute & earn in future months/quarter that have been scoped Active


Related Financial Fields for Reference (Not Editable Fields)

Field Name Definition
Expected Revenue

Planned Work on tasks multiplied by assigned resources' billing rate

On Lead-Based projects: Expected Revenue will automatically calculate with (Price Per Lead x Weekly SQL Goal)

Revenue EV (Earned Value) Completed work expressed in terms of Expected Revenue
Actual Revenue

Revenue amount that will be recognized

  • Effort-Based projects: Will only show value when 100% complete
  • Lead-Based projects: Will show per-lead revenue earned value progress
Price Per Lead

Price charged per lead; what TSL will earn for each SQL

On Lead-Based projects, automatically calculate as (Lead-Based Program Price / Total SQL Goal)

% Complete
  • Effort-Based projects: Progress calculated based on Work planned, Actual Effort logged, and Remaining Effort estimate from resources
  • Lead-Based projects: Progress calculated as Weekly or Total SQLs compared to Total SQL Goal ("% to SQL Goal")
Opportunity Amount Budget amount for the entire SOW related to the transfer number. The total of all subprojects and expenses (captured in the parent Expected Revenue field) should never exceed this amount.


Data Accuracy

It is the responsibility of the work plan Owner to set up and manage projects according to these best practices, to ensure financial data is accurate and reported properly. To that end we have "Quality Assurance/QA" reports in Clarizen that highlight any missing information or discrepancies with budget. They are sent via email every Friday morning and the manager must take required actions by the end of the day.

Report: QA Budget Field Values: Projects Missing Revenue Department, Earned Value Type, Fixed Price, Lead-Based Tactic Price

  • Interpreting the report and making corrections:
    • Review and take action on the data on each tab of the report in the following order: Revenue Department, Earned Value Type, Fixed Price, Lead-Based Program Price.
    • Locate your name on the bar chart.
      • If you do not see your name, there are no project items to take action on.
      • If you do see your name, click the bar to display your project items to take action on.
    • Scroll to the table below the bar chart and review the field highlighted in yellow that is missing the value.
    • Double-click the field highlighted in yellow to open the drop-down picklist.
    • Click the correct field value and hit the "Enter" or "Return" key on your keyboard to save.

Report: QA Budgets Expected Revenue Does Not Equal Opportunity Amount

  • Interpreting the report:
    • No highlight - ignore; amounts are off by fraction of cents and are virtually equal
    • Orange highlight - Expected Revenue is too low. The fees for the projects planned do not reflect the full amount that the customer is contracted for.
    • Red highlight - Expected Revenue is too high. The fees for the projects planned exceed what the customer will pay TSL.
  • Identifying errors and making corrections:
    • Enter all field values referenced in the "QA Budget Field Values" report above; it will pinpoint those issues that might be contributing to overall planned budget differences.
    • Check that you have any related Expense amounts budgeted for and entered into Fixed Price (ad click spend, fulfillment, pass-through, etc.).
    • Check Lead-Based projects - If you do not have all SQLs planned in the Weekly SQL Goal fields, the project's Expected Revenue will not match the Lead-Based Program Price.
    • Check that you have "Remaining/Unscoped Budget" placeholders and the amounts are current.