URL: Proposal List
The Proposal List Module in FigsFlow is designed to provide a comprehensive and structured view of all proposals generated, whether sent to clients, saved as drafts, or marked with specific statuses. This module offers a two-level hierarchy for tracking and managing proposals more efficiently. Below is the detailed breakdown of its structure and functionality.
1st Level Hierarchy: Point of Contact Level
At the Point of Contact Level, the main table row displays critical information about the proposal’s primary contact and general status:
- Proposal ID: Displays the unique ID generated for each proposal, which allows easy identification and reference.
- Point of Contact: Shows the individual or entity acting as the main point of contact for the proposal. The contact is responsible for signing or reviewing the proposal.
- Created By: Displays the user who generated the proposal.
- Status: Displays the overall status of the proposal (Draft, Live, Won, or Lost).
- Draft: Proposal has not been sent to the client.
- Live: Proposal has been sent to the client and is awaiting action.
- Won: All signatories have signed the proposal.
- Lost: The client declined the proposal or the proposal was marked as lost.
- Actions:
- View: Previews the Proposal document for the Point of Contact.
- Send Live: Sends the proposal live to the Point of Contact for signing or review.
- Duplicate: Duplicates the entire proposal, allowing the user to quickly generate a similar proposal for a new client or scenario.
- Edit: Allows the user to modify the proposal at the Point of Contact level. Note that only certain details can be edited, and contacts cannot be changed.
- Resend Email: Resends the email to the client, which was initially triggered during the “Send Live” action.
- Delete: Provides the option to delete the proposal. This functionality is available regardless of the proposal’s status but is controlled based on the user’s permissions.
2nd Level Hierarchy: Entity Level
When a row at the Point of Contact Level is expanded, the Entity Level is revealed. Here, details about the specific entities tied to the proposal are displayed.
- Entity Name: Lists the name of each entity/client for whom the proposal was generated.
- Signatories: Displays the signatories associated with the entity at the Entity Level. The signatories’ statuses are colour-coded for easy reference:
- Red: The email to the signatory has not been delivered.
- Blue: The email was sent, but the signatory has not yet signed.
- Green: The signatory has successfully signed the Letter of Engagement (LOE).
- Value: Displays the total one-off and recurring value for each entity. The recurring value can be monthly, quarterly, or annual, based on the proposal setup.
- Status: Reflects the specific status of each entity, allowing for more granular tracking of individual entity progress.
- Actions:
- View: Previews the LOE document for the specific entity (unlike the Proposal preview at the Point of Contact Level).
- Mark as Lost: Marks the proposal as lost at the Entity Level. This action is no longer available at the Point of Contact Level.
- Mark as Won: Marks the proposal as won for that specific entity, finalising the engagement.
Version Control
- If the user edits a proposal where no entities are marked as won, a new version of the same proposal is created.
- However, if a proposal contains multiple entities and at least one has already been marked as won, editing the proposal generates a new proposal ID that includes only the unsigned entities. This ensures the integrity of signed agreements while allowing edits for pending entities.
Export Functionality
- The Export button allows users to export the entire list of proposals or specific data into a CSV format. This feature is helpful for further analysis or reporting needs.
By utilising these functionalities in the Proposal List Module, users can maintain a well-organised, efficient workflow for managing proposals, ensuring timely updates and accurate tracking. The multi-level hierarchy adds flexibility, allowing users to manage both proposals and individual entities within those proposals effectively.sible.