Creating Follow-on Actions and Decisions

Modified on Fri, 21 Apr, 2023 at 12:06 PM

Follow-on actions and decisions form part of assigning activities based on existing pieces of work. As a project manager, you might have an impact/change request that requires evaluation and discussion in a project meeting. A follow-on action/decision can be created from the change request and be assigned to the meeting for the team to discuss.

In this article, we will go through a series of steps on how to create follow-on actions/decisions by using the above example. 

You'll learn how to apply the follow-ons to activities/work - as well as track the updates/key developments associated with these follow-ons.

NOTE: Follow-on actions and decisions can be created directly from all action/task dialogs across all modules in Fluid. Each action/task created in Fluid will have the Follow-On section on the task dialog, from where the follow-on actions/decisions can be created and tracked.

Step 1. Initiate a follow-on action/decision 

Follow-on actions and decisions can be created from any action/task dialog. 

  • Simply begin with creating an initial action/task (example - using a new action request below).

  • Once the action is created, open the action's dialog. The action will now have additional sections that can be populated including the Follow-on section where the follow-on actions/decisions can be created.

  • Click on +Action/Decision to create a follow-on Action or decision from this task.

Step 2.  Create a follow-on action/decision

Using the example of an impact/change request requiring discussion in a project meeting, the following steps will show you how to create the follow-on action/decision and how to track the updates/developments. 

  • From the project workspace, navigate to Impacts, and click to create an impact/change request. 

  • Open the change request's dialog and navigate to the Follow-on section to create the action/decision by clicking on "+ Action/Decision".

  • Once the dialog opens, select the Request Type (either Action or Decision) and assign it to either a person, or module in Fluid. In this example, we'll assign it to a meeting. The filter on the Assigned To field will allow you to search by module to assign the action/decision.

  • Now the decision has been created and assigned to the meeting for it to be discussed and approved. 
  • The decision will be displayed under the actions and decisions dashboard of the meeting.

  • The team will now discuss the scope changes and as part of an approval process; 
  • The updates shared in the discussion will be available in the comments section of the decision; and 
  • The follow-on can be tracked by the project manager directly from the initial impact/change request it was created from, in the Follow-On section. 

In the follow-on section of the impact's dialog, the project manager can also review the status of the decision ("Approved" in this decision example) along with the due date to assist with audit details.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article