Plans can be rejected and sent back to the user for clarification

Description

This feature enables management to review, provide feedback, and request revisions on submitted plans.

Example Use Case

Scenario: A healthcare company uses CPM software to manage their budget. A unit manager submits a proposed budget plan for the upcoming fiscal year through the software.

Solution: The controller reviews the submitted plan and finds some unclear items and questionable costs that need further justification. They reject the plan, adding comments to outline what areas need clarification or adjustment. The unit manager receives a notification about the rejection, reads the comments, and revises the budget plan accordingly before re-submitting.

Considerations

Rejections can be broad, such as “You're over budget by $X” or can be specific, linking the user back to a cell that requires correction. More specific feedback will always accelerate the process of completing a budget. As such we suggest that, should you implement an approvals process, the software include a way to route the submitter back to a very specific data intersection for correction. If it is unable to do this the user is left to meander through a collection of sheets trying to determine how to address the concern.

Questions to Ask a Vendor

• User Notification: How does your software notify users about the rejection of their plans and requests for clarification?
• Revision Tracking: How does the system document the history of revisions, rejections, and clarifications within the workflow?
• Communication Functionality: Does the system allow for detailed comments when sending back plans for clarification? Does it store all the comments in a message board-like interface for reference?