The customer has requested the ability to bulk import contacts into Accord using a spreadsheet, rather than creating each contact individually. At present, contacts must be entered manually, which can be a time-consuming process, particularly during the initial implementation of the system or when large numbers of contacts need to be added or maintained. The customer would like the ability to upload a CSV or Excel file containing contact details, with the system validating the data and creating the contact records automatically. Customer Benefits Reduces the time spent creating contacts manually. Improves efficiency when onboarding new organisations or maintaining existing contact records. Reduces the risk of manual data entry errors. Simplifies the migration of contact data from other systems into Accord. Suggested Functionality Ability to download a standard import template. Support for CSV and/or Excel file uploads. Validation of mandatory fields before import. Duplicate detection to prevent existing contacts from being created multiple times. Clear import summary showing successful imports and any records that failed, including the reason for failure. Restricted to users with the appropriate permissions.

Kelly Szabo 5 days ago

💡

Feature Request

Current Behaviour: Accord does not currently provide a standard module to support the creation and management of notices required under the Procurement Act. Whilst similar requirements have been discussed previously and may be achievable through bespoke development, organisations currently need to manage these notices outside of the system. Requested Enhancement: Introduce functionality to support Procurement Act notice requirements directly within Accord. This could include the ability to automatically generate, manage, and track notices linked to the contract lifecycle, such as: Contract Details Notices when a new contract is created or awarded. Contract Termination Notices when a contract reaches its end or is terminated. Additional Procurement Act notices as legislative requirements evolve. Configurable workflows and prompts to ensure notices are issued at the appropriate stage. Storage of submitted notices against the relevant contract record. Full audit trails showing when notices were generated, issued, and by whom. Reporting capabilities to demonstrate compliance across all contracts. Benefit: Embedding Procurement Act notice functionality within Accord would help organisations meet their statutory obligations more efficiently and consistently, reducing reliance on manual processes and external systems. It would improve compliance, strengthen governance, and provide greater visibility over procurement activity and reporting requirements.

Kelly Szabo 26 days ago

💡

Feature Request

Current Behaviour: Accord currently provides some tender tracking and pre-tender support capabilities; however, it does not offer a full end-to-end e-tendering solution. Organisations requiring this functionality must utilise separate systems to manage the tendering process. Requested Enhancement: Introduce e-tendering functionality within Accord to support the complete tender lifecycle. Potential capabilities could include: Creating and publishing tender opportunities. Inviting suppliers to participate in tender exercises. Managing supplier submissions securely within the platform. Setting tender deadlines and milestones. Facilitating clarification questions and responses. Recording evaluations and scoring criteria. Maintaining a full audit trail throughout the procurement process. Providing reporting and visibility over tender activity and outcomes. Benefit: A fully integrated e-tendering solution would enable organisations to manage procurement activities from a single platform, reducing the need for additional systems and improving efficiency, transparency, and governance. It would also strengthen Accord's position within the market by supporting a broader range of procurement activities and reducing the likelihood of clients seeking alternative suppliers to fulfil this requirement.

Kelly Szabo 26 days ago

💡

Feature Request

Current Behaviour: Users are required to manually generate reports each time they need to review or distribute information. This process can be time-consuming, particularly for reports that are produced on a regular basis and shared with the same stakeholders. Requested Enhancement: Introduce the ability for users to schedule reports to run automatically at a specified date and time. As part of the setup, users should be able to: Select the report they wish to automate. Define the frequency (e.g. daily, weekly, monthly, or on a specific date). Specify the time the report should be generated. Nominate one or more recipients to receive the report automatically via email. Choose the preferred export format, where applicable (e.g. Excel, PDF, CSV). Benefit: Automated report scheduling would remove the need for repetitive manual tasks, ensuring key stakeholders receive the information they need in a timely and consistent manner. This would improve efficiency, reduce the risk of reports being forgotten or delayed, and provide greater confidence that important operational and compliance data is being shared proactively.

Kelly Szabo 26 days ago

💡

Feature Request

Current Behaviour: Custom exports can be created and used within the system, however they are not easily accessible from the main navigation. Users must navigate through multiple areas of the platform to locate and run the exports they use regularly. Requested Enhancement: Introduce the ability to add selected custom exports directly to the side menu navigation. This could allow organisations or individual users to pin their most frequently used exports for quick access. Benefit: Providing direct access to commonly used custom exports would improve efficiency and reduce the number of clicks required to retrieve key information. It would streamline reporting processes, encourage greater use of custom reporting functionality, and create a more personalised user experience by allowing users to surface the reports most relevant to their role.

Kelly Szabo 26 days ago

💡

Feature Request

Product Suggestion Introduce the ability for users to manually cancel reports or exports that become stuck in an “In Progress” state for an extended period of time. This would allow users to clear failed or stalled report processes without requiring support intervention, enabling them to restart the export or run a new report more quickly. The functionality could include: A “Cancel Export/Report” option Automatic timeout thresholds (e.g. 30 minutes to 1 hour) Status indicators showing stalled or failed exports Confirmation prompts before cancellation Automatic cleanup of failed background processes Problem Statement Currently, when a report or export fails, it can remain stuck in an “In Progress” state indefinitely. While this process remains active: Users may be unable to rerun the export New reports may be blocked Reporting workflows can be delayed Users may need to contact support to clear the process manually This can create frustration and slow down operational reporting activities. Suggested Improvement Add functionality allowing users to cancel reports or exports that have remained in progress beyond a defined time threshold. For example: Reports running longer than 30 minutes or 1 hour could display a cancellation option Stalled exports could automatically move into a failed state after timeout Users could then restart the export without needing support assistance Potential Benefits Reduced reporting delays Faster recovery from failed exports Less dependency on support intervention Improved user control over reporting processes Better visibility of failed or stalled exports Improved reliability and usability of report generation workflows

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Introduce a more detailed amendment history audit log that provides a clearer and more comprehensive breakdown of changes made within the system. The enhanced audit log would allow users to easily view: What was changed The previous and updated values When the change was made Who made the amendment This would create a clearer historical record of amendments and improve visibility of contract or record changes over time. Problem Statement The current audit log does not provide enough detail about amendments made to contracts or records. As a result, users may find it difficult to: Understand exactly what was changed Track the history of amendments over time Identify who made specific updates Investigate historical changes or discrepancies This can reduce transparency and make audits or internal reviews more time-consuming. Suggested Improvement Enhance the audit log to provide a detailed amendment history showing: A full breakdown of each amendment Original and updated values where applicable Date and time of the change The user responsible for the amendment The amendment history should be easily accessible from the relevant contract or record view. Potential Benefits Clearer visibility of historical changes Improved audit and compliance tracking Easier investigation of amendments and updates Better accountability for system changes Reduced time spent reviewing contract history Stronger governance and change management controls

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Introduce consistent button ordering and layout across comparable search pages within Accord, particularly within Contract Search, Supplier Search, and similar data-driven areas of the platform. Standardising the placement of common actions such as: Filter Export to Excel Add New Reset/Search …would create a more predictable and user-friendly experience across the system. Problem Statement Currently, action buttons are not always displayed in the same order across similar search screens. For example: On the Contract Search page, “Export to Excel” appears before “Filter” On the Supplier Search page, “Filter” appears before “Export to Excel” This inconsistency can make the interface feel less intuitive and may slow users down as they adjust between different sections of the platform. Suggested Improvement Standardise the positioning and ordering of common action buttons across comparable search pages and grids throughout Accord. This could include: Consistent button order Standardised alignment and spacing Shared UI patterns across search screens Alignment with wider platform design standards Potential Benefits More consistent user experience Easier navigation across different modules Reduced user confusion and hesitation Faster interaction with common actions Cleaner and more predictable interface design Improved usability for frequent system users

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Introduce indented parent/child formatting for multi-select dropdown lists where options are structured hierarchically. This would align the behaviour of other dropdown fields with the existing Organisation Hierarchy field, which already uses indentation to visually distinguish parent and child options. Applying this formatting to additional areas such as Locations and other hierarchical fields would make larger dropdown lists easier to read, navigate, and understand. Problem Statement Currently, many multi-select dropdown fields display hierarchical data in a flat list format with no visual indication of parent and child relationships. This can make it difficult for users to: Understand the hierarchy structure Quickly identify the correct option Navigate large or complex lists confidently The lack of visual structure can increase selection errors and reduce usability, particularly where similar names exist across different parent groups. Suggested Improvement Apply the same indented hierarchy format used within the Organisation Hierarchy field to other dropdown lists that contain parent/child relationships. For example: Locations Site structures Department groupings Other hierarchical configuration lists Child items should appear visually indented beneath their parent option to improve readability and navigation. Potential Benefits Improved readability of hierarchical dropdown lists Easier navigation of large option sets Clearer visibility of parent/child relationships Reduced selection mistakes More consistent user experience across the platform Improved usability for complex organisational structures

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Introduce the ability to delete or remove additional extension period lines from a contract once they have been added. This would allow users to manage contract extension periods more cleanly and remove any unnecessary or incorrectly added entries without leaving unused lines within the contract record. Each additional extension line could include: A Delete or Remove button Confirmation prompt before removal Automatic reordering/cleanup of remaining lines if required Problem Statement Currently, when additional extension period lines are added to a contract, there is no option to remove them if they are no longer needed or were added in error. This can result in: Blank or unused extension entries remaining visible Cluttered contract records Confusion over whether unused lines are active or intentional Reduced flexibility when managing contract extensions Suggested Improvement Add a Delete or Remove option against each additional extension period line, allowing users to remove unwanted entries directly from the contract. This functionality should: Allow removal of unused extension lines Prevent unnecessary blank entries remaining within the contract Maintain a cleaner and more manageable contract structure Potential Benefits Cleaner contract extension management Reduced clutter within contract records Easier correction of setup mistakes Improved usability and flexibility Clearer visibility of active extension periods Reduced confusion for contract administrators

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Enhance the KPI module to allow KPI requests, notifications, and related communications to be sent to a wider range of contacts, rather than only the main supplier contact. This would allow users to select additional recipients such as: Internal contacts Secondary supplier contacts External stakeholders Operational or departmental contacts Shared mailbox addresses The functionality could support multiple recipients against a KPI workflow, ensuring the relevant people receive KPI-related communications and actions. Problem Statement Currently, KPIs can only be sent to the main supplier contact. This can create limitations where: The supplier contact is not responsible for KPI completion Internal teams also need visibility of KPI activity Multiple stakeholders need to review or contribute to KPI responses Organisations use shared or department-based ownership for performance management As a result, KPI communication may need to be managed manually outside the system. Suggested Improvement Allow users to select additional internal and external recipients when configuring or sending KPI-related communications. This could include: Multiple contact selection Internal and supplier-side contacts Optional CC-style notification settings Contact management directly within KPI workflows Potential Benefits Improved visibility of KPI activity Better collaboration between internal and supplier teams Reduced reliance on manual forwarding of KPI emails Greater flexibility in KPI ownership and management Improved communication across stakeholders More efficient KPI completion and tracking

Kelly Szabo about 2 months ago

💡

Feature Request

Product Suggestion Introduce a transfer audit log within the Transfer Contracts functionality, allowing users to view a history of contract transfers and the details associated with each transfer action. The log would provide visibility of: What changes were made during the transfer Who completed the transfer When the transfer took place Previous and new contract owners or responsible users This would create a clearer history of contract ownership changes and improve traceability when contracts are reassigned between users. Problem Statement Currently, when contracts are transferred from one user to another, there is limited visibility of what changed as part of the transfer process. This can make it difficult to: Track historical ownership changes Understand when transfers occurred Identify who performed the transfer Investigate changes following reassignment The lack of a visible transfer history reduces transparency and auditability around contract management activities. Suggested Improvement Add a transfer history log within the Transfer Contracts functionality that records: Date and time of transfer User who completed the transfer Original contract owner New contract owner Any related changes applied during the transfer process The log should be easily accessible from the relevant contract or transfer history area. Potential Benefits Improved audit trail for contract transfers Clearer visibility of ownership history Easier investigation of historical changes Improved accountability for transfer actions Better governance and contract management oversight Reduced confusion following contract reassignment

Kelly Szabo about 2 months ago

💡

Feature Request