Overview

ManageBac+ welcomes feedback from schools and users across the platform. Feature requests help inform future improvements and are reviewed as part of the wider product planning process.

Requests are considered based on broader impact across the ManageBac+ community. During review, the team checks whether a feature already exists, whether a workaround is available, whether development is already in progress, or whether the suggestion may be considered for the roadmap.

How to submit a feature request

Share your suggestion through the Product Portal.

1. Open the Product Portal.
2. Submit your feature idea with a clear title and description.
3. Include practical examples, your use case, and the benefit the feature would bring.
4. Explain the problem you are trying to solve and the outcome you would like to achieve.

What happens after submission

• New requests are reviewed on a monthly basis.
• The team may contact you if more information is needed before the request can be evaluated.
• Requests are assessed against the current Product Roadmap and wider product priorities.
• Suggestions are reviewed as product wide improvements rather than school specific developments.
• A request may be identified as not feasible, not currently on the roadmap, aligned with the roadmap, or already in development.

How to follow progress

• A support ticket may be closed for administrative reasons while the feature request remains under internal review.
• When possible, you may be notified if the status of your request changes.
• You can review product updates on the What’s New in ManageBac+ page.
• You can also stay informed through webinars and the ManageBac+ blog.
• To explore past community inspired improvements, see favourite updates suggested by our users.

Tips for a strong request

• Be specific about the feature you need and the problem it would solve.
• Include examples of the workflow or scenario where the feature is needed.
• Check whether an existing feature or workaround may already support your goal.
• Allow time for review, especially where the request would affect schools more broadly across the platform.

Important notes

Frequently Asked Questions

I submitted a feature request. What happens next?

Once your request has been logged, it is reviewed against the current product roadmap and wider ManageBac+ priorities. The team may also contact you if more context is needed.

Are feature requests school specific?

No. Feature requests are reviewed as potential improvements for the wider ManageBac+ community, which is why development decisions may take time.

Why was my support ticket closed if the feature was not implemented?

Feature request tickets may be closed for administrative reasons. This does not mean the request has been forgotten, rejected, or removed from internal review.

How can I stay informed about future updates?

You can monitor the Product Roadmap, the What’s New in ManageBac+ page, webinars, and the ManageBac+ blog for broader product developments.

In summary

• Submit feature suggestions through the Product Portal with clear details and examples.
• Requests are reviewed against the roadmap and wider ManageBac+ priorities.
• A closed support ticket does not necessarily mean the request is no longer being tracked.

Use this guide to understand how feature requests are submitted, reviewed, and tracked over time in ManageBac+.