You told us what was slowing you down. We listened. Here's what we built.
This is our third Customer Love Sprint—and every feature on this page exists because you asked for it. Over the past two weeks, we've knocked out 30+ updates that save you time, reduce frustration, and make KickUp work the way you actually work.
Legacy platforms don't do this. They don't pause their roadmaps to focus on the small fixes that make a massive difference in your day-to-day. We do. Because when you waste less time fighting your software, you have more time to support educators.
These five updates were the most urgent requests we heard from districts across the country—covering 35% of all Customer Love Sprint requests. If you've been waiting for any of these, you're about to have a much better week.
Stop clicking through hundreds of registrants one by one. You can now confirm attendance for entire groups at once—saving facilitators hours every week. — KickUp Learning
When you approve or deny a submitted event, you can now leave a comment explaining why. No more back-and-forth emails or confused staff wondering what happened to their submission. — KickUp Learning
Filter entire dashboards by facilitator, opportunity, or collection at the dashboard level. No more filtering every block individually or creating 20 versions of the same dashboard. — Platform-Wide
Users can now delete their own submissions across Learning and Foundations—including PD Feedback, Coaching Logs and Walks, Coaching Cycle Steps, and Evaluation Cycle Steps. No more waiting for support to fix mistakes. — Platform-Wide
Complete waitlist control: export waitlists to CSV, reorder them with simple controls, add people directly to waitlists, and override waitlists for series. Everything you needed for managing full sessions. — KickUp Learning
See a feature you love? Let us know.
.png)
Why:
Previously, Illinois districts couldn't generate a single series certificate that shows total professional learning hours. The Illinois certificate displayed 0 hours, forcing educators to print multiple certificates for each session just to prove their hours for ISBE audits. This created confusion for staff and extra work for admins who had to create manual workarounds or custom credit types just to stay compliant.
Update:
When you generate an Illinois certificate for a series, KickUp now automatically sums all published learning hours within that series and displays the total on the certificate.
Impact:
Educators get one clean compliance certificate at the end of a series. Admins save time, reduce audit errors, and stop building workarounds.
.png)
Why:
Previously, district leaders had to manually go into every event, scroll down, and uncheck "allow users to confirm their own attendance" to close the confirmation window. If they forgot, staff could technically confirm attendance months—or even years—after an event. This was especially problematic for districts in states like Michigan that upload attendance to state systems, because late confirmations got lost and admins had to hunt them down.
Update:
You can now set a confirmation close date for an event. After that date, staff can no longer confirm their own attendance.
Impact:
No more manually tracking down events to close confirmation windows. No more late confirmations messing up your state reporting. And if you're worried about confirmation codes being shared, this eliminates that concern—expired codes don't work.
Why:
When districts have hundreds of staff members submitting events, keeping track of why an event was approved or denied becomes impossible without a paper trail. Previously, there was no way to leave a comment when approving or denying, which meant more emails, more confusion, and more resubmissions.
Update:
When you approve or publish a submitted event—or when you deny it—you can now add feedback that shows up when the submitter gets their response.
[Image/GIF placeholder: Screenshot of feedback field when approving/denying submitted events]
Impact:
Clear communication. Less back-and-forth. Staff understand why their event was denied and what to fix before resubmitting. This brings parity with other features where you can leave comments (like submitted assignments or out-of-district requests).
Why:
Facilitators who manage events with hundreds—or thousands—of registrants waste hours confirming attendance one person at a time. It's tedious, time-consuming work. And for districts coming from PowerSchool, this is a feature they're really missing.
Update:
You can now bulk confirm attendance for multiple people at once—no more clicking through registrants individually.
[Image/GIF placeholder: Screenshot of bulk confirm attendance action on event attendance tab]
Impact:
Facilitators save hours every week. Large events no longer mean large administrative burdens. This matches the ability to bulk register people, giving you full bulk capabilities for managing attendance.
Why:
Waitlist management has been a pain. You couldn't export waitlists as CSVs (making it impossible to quickly reassign staff to other sessions or email everyone at once). You couldn't reorder waitlists without impersonating every single person, unregistering them, and re-registering them in the correct order. You couldn't add people directly to a waitlist—your only option was to override seat limits, even when you just wanted someone on the waitlist. And you couldn't override waitlists for series the way you could for individual opportunities, which meant facilitators couldn't ensure the right staff were registered for multi-session series.
Update:
Four new capabilities make waitlist management actually work:
Export waitlists to CSV: Download your waitlist just like you can for registered participants.
Reorder waitlists: Move people up, down, to the top, or to the bottom with simple controls—no more impersonating dozens of people.
Add people to waitlists: When adding attendees to a full event, you can now add them directly to the waitlist instead of being forced to override seat limits.
Override waitlist for series: Users with attendance management permission for a series can now register staff for that series, overriding the waitlist just like they can for individual opportunities.
[Image placeholder: Export waitlist to CSV]
[Image placeholder: Reorder waitlist controls]
[Image placeholder: Add staff to waitlist & override for series]
Impact:
When sessions fill up, you can quickly reassign staff, communicate with waitlisted people, manage the order, and ensure the right people get into series—all without frustrating workarounds. Full control over waitlists in seconds, not hours.
Why:
When districts create learning content with quizzes that include scenarios, they were stuck putting those scenarios in the directions section. This forced users to open two different windows—one with the scenario, one to answer the question. It was clunky and broke the learning flow.
Update:
You can now add read-only rich text elements directly within quizzes. This means scenarios, instructions, or context can appear right on the same screen as the question.
[Image/GIF placeholder: Screenshot of quiz with read-only text element showing scenario on same screen as question]
Impact:
Better learning experience for staff. No more toggling between windows. Everything they need is in one place.
Why:
On the Attendance tab of an event, there was no way to sort or filter staff by their attendance status. If you wanted to quickly find everyone who hadn't confirmed attendance yet, you had to scan through the entire list manually.
Update:
You can now sort and filter the attendance list by status, making it easy to find staff without confirmed attendance.
[Image/GIF placeholder: Screenshot of attendance status column with sort/filter options]
Impact:
Faster follow-up with staff who haven't confirmed. Less time hunting through lists.
Why:
Series still used the old "search to add" field for registration, which was clunky and inconsistent with how you register people for individual opportunities. You couldn't use the streamlined "Add attendees" modal that lets you add multiple users and groups at once. And if you wanted to search for existing registrants, the search field didn't work for that—it only added new people.
Update:
Series registration now matches the experience for individual opportunities. The "search to add" field now functions as a search bar for existing registrants, and clicking "Add attendees" opens the familiar modal where you can add individuals and groups in bulk.
[Image/GIF placeholder: Screenshot of new series "Add attendees" modal matching individual opportunity experience]
Impact:
Consistent experience across all event types. Faster registration. Less confusion about how to add people to series.
Why:
If you use Tracks to organize professional learning (like tracking progress toward a standards-based grading initiative), every time you create a new event, you have to go back and manually add it to every relevant Track. For districts with dozens of Tracks copied across multiple schools, this means opening each Track individually and adding the event—a process that can take hours.
Update:
When creating an event, you can now select which Tracks it should be added to. No more going back to update Tracks individually.
[Image/GIF placeholder: Screenshot of Track selection when creating an event]
Impact:
Massive time savings for districts using Tracks. Principals see accurate, up-to-date progress without you having to manually update dozens of Tracks.
What else would make your work easier? Share your ideas.
Why:
Right now, you can turn off anonymous submissions in coaching, but not in walkthroughs. This lack of parity causes confusion—why can I control this in one tool but not the other? Some districts want to allow anonymous walks at the beginning of the year for calibration, then turn them off once principals start doing walks connected to specific teachers.
Update:
You can now disable anonymous walk submissions, just like you can in coaching.
Impact:
Smoother workflows. Less confusion for principals. Better parity across tools.
Why:
On the roster page, you can filter to open cycles in coaching, but there's no way to view closed cycles. This forces coaches and leads to click into individual teachers to see completed cycles—which becomes incredibly time-consuming when you support dozens of teachers.
Update:
You can now filter to view closed cycles directly from the roster page.
Impact:
Coaches and leads can quickly review completed work without clicking through every single teacher on their roster.
Why:
Some districts (like New Teacher Center clients) need to report time metrics in minutes, not hours. But dashboards, data tables, and exports previously showed hours, which meant admins had to manually convert every number to minutes before reporting.
Update:
In admin settings, you can now choose how duration is displayed: "Hours and minutes (e.g., 2:30)" or "Total minutes (e.g., 150 min)." This setting applies to dashboards, in-context tables for time data, and exports.
Impact:
No more manual conversions. Reports match your district's format automatically.
Share feedback on these Foundations updates.
Why:
In Foundations, users with managed permissions can import leads, giving certain staff access to specific data without universal permissions. But this capability didn't exist in Growth, which meant admins had to manually set up observers one by one—a time-consuming process, especially in large districts where principals need access to specific staff data but shouldn't see all data in the Growth instance.
Update:
You can now import supervisors for Growth, just like you can import leads in Foundations.
[Image/GIF placeholder: Screenshot of import supervisors functionality in Growth]
Impact:
Huge time savings for both CSMs and district admins during rostering. Better parity across tools.
Why:
When adjusting steps in multiple teachers' evaluation cycles, you had to add or remove steps one person at a time. And when bulk assigning steps, if some selected users didn't already have those steps added, those users would be disabled in the interface—forcing you to assign steps separately. Both workflows required far too many clicks.
Update:
Two new capabilities speed up step management:
Bulk add/remove steps: Adjust steps across multiple teachers' cycles at once.
Add steps during bulk assignment: When bulk assigning steps, a modal now lets you add steps to users who don't already have them, instead of disabling those users.
[Image placeholder: Bulk add/remove steps]
[Image placeholder: Add steps during bulk assignment]
[Image placeholder: Modal showing step options]
Impact:
Fewer clicks. Faster cycle adjustments. More flexibility when managing evaluation steps across your staff.
Share feedback on these Growth updates.
Why:
Right now, if you want to create a dashboard filtered by facilitator, opportunity, or collection, you have to manually filter each individual block. If you want dashboards for different facilitators or collections, you end up creating tons of duplicated dashboards—one per facilitator, one per collection—which makes it impossible to manage and overwhelming for viewers to navigate.
Update:
You can now filter entire dashboards at the dashboard level by:
Impact:
No more filtering every block individually. No more creating 20 versions of the same dashboard. One dashboard, multiple filter options. Faster dashboard creation, less clutter, more flexibility.
Why:
Users can edit their past submissions, but they couldn't delete them. This happens all the time—someone submits the wrong walk, coaching log, PD feedback, or cycle step by mistake. Previously, the only option was to message Intercom or email their CSM and wait for manual deletion. It was one of the top 10 most popular support requests, and it created stress for both users and support teams.
Update:
Users can now delete their own submissions across Learning and Foundations:
Deletions require confirmation (including typing "delete" to proceed), and the system tracks the deletion as an activity. Raw submissions are preserved on the backend in case recovery is needed.
[Image placeholder: Delete button in submission modal]
[Image placeholder: Confirmation modal with "delete" typing requirement]
[Image placeholder: Success state after deletion]
Impact:
Users can fix their own mistakes immediately. Fewer support tickets. Less time spent on deletion requests for CSMs and support teams.
Share feedback on these platform-wide updates.
Sometimes the smallest changes make the biggest difference in daily use. Here are a few refinements that improve the experience across devices and workflows:
The issue: The calendar widget took up so much space on tablets and mobile that you couldn't actually see the events you were trying to browse.
The fix: We've updated the calendar component to be more compact and responsive. On tablets, we've moved the calendar to a Date filter in the filter area. On mobile, the Date filter is now the primary way to navigate events, with other filters accessible as needed.
The issue: When hovering over dates to see edit history, the tooltip appeared too far away from the trigger, making it hard to read.
The fix: Tooltips now appear closer to their triggers for better readability and a cleaner user experience.
Noticed something we could polish? Let us know.
These technical improvements make KickUp more stable, reliable, and easier to support—even if you don't see them directly:
When you delete a submission and trigger a confirmation modal, modals now replace each other instead of stacking on top of each other. This prevents visual clutter and makes the flow feel smoother.
When a coaching log submission is deleted, related coaching activities are now soft-deleted automatically. This keeps your activity history accurate without losing data.
We've added the ability to restore raw submissions if needed. While deletions are permanent from the user's perspective, this backend capability gives us a safety net for edge cases.
Have technical feedback? Share it with us.
Legacy platforms don't pause their roadmaps to focus on the small fixes that make your life easier. We do. Because when you spend less time fighting your software, you have more time to actually support educators—which is the whole point.
This is our third Customer Love Sprint, and it won't be our last. We're already tracking what you're telling us for the next one.
Have feedback on these updates?
Your Client Success Manager wants to hear it. Reach out and let them know which features made the biggest difference for your team.
Want to enable any of these features?
Contact your CSM—they'll get you set up.
What should we build next?
Keep the feedback coming. These sprints exist because you speak up.
Schedule a demo with one of our friendly team members.
.png)