In IDhall, depending on its progress, an initiative can go through different statuses. Each step is visually represented by four quarters of a circle, each one symbolizing a key stage in the processing cycle, allowing users to quickly see the current stage of the initiative in its lifecycle.
You will find in the application pictograms representing the evolution of the initiatives' lifecycle.
Draft
Saving the initiative as a draft in order to come back to it later on to either submit it (once considered as ready) with optional comments for the approver, or delete it.
Awaiting decision
- Registered: as soon as the initiative is registered, it is sent to the approver identified, selected (if manual selection is allowed) or named according to the decisional structure set up.
- Expertised: the expertise carried out by the various experts is added to the initiative sheet. If the expert has not ticked the "Confidential expertise" box, the expertise is available to all users.
- Request for a new approver: when the approver feels that he or she is not the best person to handle the initiative, he or she can transfer it to another approver. This option can also be used in the case of a decision-making structure with multiple approvers. The initiative may also be transferred to another approver after the initiative has been approved. Thus, the approver who approved the initiative is not the one who closes it.
- Put on hold; an initiative may be interesting, but not immediately applicable (lack of resources, waiting for another decision, etc.). It would be inappropriate to reject such initiatives as they are potentially of interest in the near future. On the other hand, leaving them in the pile of initiatives to be analyzed would clutter the approver, especially since delay alerts would be generated once the set processing time had expired. To avoid these problems, IDhall offers the possibility for approvers to put initiatives on hold by specifying their motivations. The initiative joins the temporarily suspended initiatives and does not produce an alert until the waiting period has expired. As for the author of the initiative, he is informed on his homepage and by e-mail that the initiative has been put on hold.
Request further details
The approver may consider that the initiative is not sufficiently developed and that it requires further details. To do this, the approver makes a request for further details. This request is automatically sent to the writer of the initiative. It shall explain the reasons for its request and specify the time limit within which the author must reply. Beyond this time, the application will produce an alert on its homepage.
Request an expertise
The approver may consider that the initiative requires further study on a particular point that goes beyond its scope and that of the author. To do this, the approver requests expertise from one of the experts referenced in the application. If no expert is referenced in the application, the request for expertise is not available. It also specifies the time frame within which it wishes to receive the expertise. Beyond this time, an alert is generated on its homepage.
Approved
The initiative has been validated by the approver who must now plan its implementation.
Rejected
If the approver does not wish to proceed with the initiative, he or she may then reject it. He is then asked to indicate the reason for inadmissibility and the reasons for the rejection on grounds of transparency, in particular with regard to the author. Rejected initiatives are always present in the database and therefore accessible, in particular via the search engine.
Implementation
Define the additionnal informations to the progress in percentage (confidence level, actual workload carried if the "Resources" module is activated) that can be filled in by the person in charge of implementation.
Closed
Successfully or unsuccessfully