What is a Feature Request?
A feature request is a suggestion for new functionality not yet in Clipboard - as opposed to a bug, which is when something already built isn't working as expected.
Our Approach
While we can't guarantee your feature request will make it onto our roadmap, we want you to know that your suggestions genuinely matters to us. For those features we develop, we will work to make sure they are done well.
We love hearing ideas from our schools - your feedback is one of the most valuable inputs we have, and it plays a real role in shaping Clipboard. That said, we want to be upfront with you: we have a full and ambitious roadmap, and we're intentional about what we take on so we can do each thing well. We'd much rather be honest about that than leave you wondering.
To make sure every request is considered fairly - for all schools, including yours - there's a process each one goes through before it can be picked up for development.
Our guiding principle remains: Build the features that provide the greatest benefit to the largest number of schools and associations.
The Process
Add your feedback directly to our Product Portal.
The Clipboard product team will review.
Requested features that we assess to have a potential benefit across many schools enter formal review. Those that have niche benefits will sit in the backlog - we hold onto everything, we just can't promise timelines.
Your School Success Manager will follow up to let you know when something's been picked up and worked on.
What to Expect
We want to set honest expectations:
Timelines are hard to promise: Even requests we're excited about may not have a date we can share yet.
Demand really does matter: Requests that are raised by multiple schools carry more weight and are more likely to be reviewed for development, where they align with Clipboard's Vision and Mission.
Not everything will be built: We focus where we can make the broadest impact. Some requests may not be developed for various reasons, others may stay in the backlog for a long time, and we think you deserve to know that. You’ll be informed and provided explanations where this is the case.
Frequently Asked Questions
What detail should I provide?
The more context the better - particularly the problem you're trying to solve, how often it comes up, and who's affected. That detail helps our product team understand the real need behind the request.
Why can't this be built straight away?
We're releasing improvements every day, but our team works to a planned roadmap so we can maintain quality across everything we build. Feature requests sit outside that roadmap unless they gain enough traction or fit strongly with where we're headed.
Can I have a meeting to discuss it?
Any feature request must go through the due process at Clipboard. To pursue building functionality:
There must be sufficient demand among multiple schools.
The Clipboard development team must have bandwidth/capacity (note that the team works on pre-planned functionality to ensure a high standard of quality)
Additional meetings are usually not the most constructive way of pushing features through the above-mentioned process. The exception is when the Clipboard development team is researching what a proposed feature would address and how it could look.
Can I see what’s on the Clipboard Roadmap?
Our high-level roadmap can be found here - our Product team updates this regularly, and while there is more being worked on than is displayed there, these items are some of our key priorities: Clipboard Community Roadmap