Using Workback Workflows

Using Workback Workflows

A "Workback Workflow" is a type of Dynamic Duration workflow where instead of all task dates calculated and flowing forward from the project start date, rather they all calculate and flow backward from the project end date. This is great for events and other projects where you need to hit a specific target date and want all task dates to be automatically calculated/shifted/updated so that you’ll always hit that target.

To create and use a workback workflow, you'll follow basically the same set of steps for creating a Dynamic Duration template, and then projects from that template, as outlined here:

There are two crucial differences from that document for workback workflows:
  1. In Step 3 of "Create Your Workflow Template", when you select the project to use as the template, you'll see there is a new checkbox below it labeled "This is a Workback workflow (dependencies flow backward from the project end date)". Be sure to check that checkbox.
  2. In Step 2 of "Use Your Template", instead of filling in a project start and due date, you'll only enter a project due date. This is the key ending date which everything will calculate back from. Flowsana will assign this ending date as the due date for the bottom task in the project, and it will work up from there.
Also, you can still use lag times in a Workback Workflow. However, conceptually they work a bit differently: if you want to build in a gap between the start of a task and the end of its dependent task (i.e. the task above it), use a negative number for Lag Time.

    • Related Articles

    • Notes and Tips on Using Rule Workflows

      Most Conditions and Actions for Rules are self-explanatory. Here are a few notes on how to use specific Conditions and Actions, that might not be obvious. CONDITIONS    Starts or due... When using any of the date-based rule conditions, you must ...
    • How Dynamic Duration-Based Workflows Work

      CUSTOM FIELDS When you put a project under control of a Dynamic Duration-Based workflow, it attaches three custom fields to the project. (If any of these fields doesn't exist, Flowsana creates it.) Duration : This is a number of days, weeks, or ...
    • How do we handle multiple Flowsana users in an organization?

      Multiple users can be handled in two ways; choose the best fit for your scenario. One option is to create one Flowsana account and share the login among multiple users. In this case, you'll have one list of workflows among the multiple Flowsana ...
    • How to Set Up a Dynamic Duration-Based Workflow

      Following is information on how to get started with a Dynamic Duration-Based Workflow.  Please see How Dynamic Duration-Based Workflows Work for details on how this type of workflow operates. There are two ways to get started.  If you are building a ...
    • How does Flowsana's pricing work?

      Flowsana's pricing works based on the concept of Billable Users. A Billable User is an Asana user who's a member of a team having workflow-enabled projects. Flowsana charges at $2.99/month USD per Billable User. Say you have a Marketing team which ...