Supporting others well is dependent on a series of timely interventions.
Any one of our clients will have many actions that need to be completed to successfully conclude support to them. Not all these actions need to be completed by just one user, as time and experience or constraints may define, that help from other users is needed.
Actions – Basic Premise
Actions follow a very simple premise, that is summed up in 3 words Define, Assign & Accept.
- Define the reason, purpose and objective of the action
- Assign the action to a user who is best placed to complete the action
- Accept responsibility for the action
An Actions Features
Actions are designed to inform quickly and be managed easily so here are a list of features each action has:
A Name to help differentiate between actions
A Purpose to define broadly why it is needed
A Deadline that it needs to be completed by
An Urgency to help you prioritise your work load
A User who is responsible for the action
A Description to explain more about the requirements of the action
A Status to define the stage the action is at
A Linking ability to associate to a record or other Adeveam features
A Time detail to the time spent on the action
An automatic Log to capture the user and date the action was set
A Document Tab store to add documents specific to the action
An Updates Tab to show any changes that have been made
The ability to create multiple Further Actions linked to the main action
Each action is colour coded
White/Grey means the action is within the deadline time
Red means the action is outside of the action deadline
Green means the action has been completed
And Finally
Key action details can only be changed by the action setter
Each action has to be accepted or rejected by the user requested to complete the action
Users receive an email notification of new actions assigned to them
This process works the same way no matter which part of Adeveam you are working in.
Continue …
An Action we set for ourselves is easy to accept as we are aware of our commitments, but
Continue …
After accepting responsibility for an action we need to keep our progress on the action up to date to
Continue …
There are many instances when a user takes the responsibility for an action and also acts as the
Continue …
When you have finished working on an action we need to mark the action as being completed. This
Continue …
