Feature Requests

Once students have joined an experience page, they can view the project marketplace and upvote open projects (not projects already matched to Experience). This would not notify the employer in any way, but is visible for the educator and Riipen team to clearly guide matchmaking candidates where students are expected to find their own project. Employer isn't notified. This is about the educator / EdSM seeing the students' interest / initiative and acting on it so everyone is aligned Benefit: Stops matchmaking getting bogged down by educator objections "the students are supposed to find projects" "I cant pick the projects for the students" and having to share URLs from educator to students. Crucial for data: minimise the "I matched the projects and showed students but nobody was interested" which causes a big data grey area after the fact Incentive for students to join platform, something for them to do and push their educator into action Give educator confidence that projects will be used and popular Student initiative particularly common at senior capstone classes which usually have best results Could lead to more "market share" in experiences where students can find project from their own sources. Guardrails: Could be disabled by default unless the course/module requires students' input in project selection Maximum number of 'votes' students can make per experience they're part of.

Problem: FuturePath project applications expire after 10 days if an employer does not act, which can disrupt the matching process: * Employers may need more time to review candidates, conduct interviews, and make decisions. * Students may be invited to interviews scheduled after the application expires, requiring them to reapply. While there may be functionality or workarounds to extend application deadlines, employers and students still lack a clear way to indicate which applications are moving forward to the next stage such as those shortlisted or selected for interviews. Proposed Solution: Introduce a status option beyond "Accept/Decline" such as “Shortlist,” “Finalist,” or “Pending Interview", that * Signals continued interest to students * Gives employers a way to track candidate progress * Optionally pauses or extends the expiration clock for applications at this stage

Though I understand WHY this is not a thing we allow for scoping purposes when a project is accepted, I am wondering if for Signature Programs we can think of a way to bring it in? Employers and students will begin working together and jointly decide that the scope of work has changed based on the students abilities and I am wondering if there is a way to introduce scope changing mid-project that includes sign off from both the student and the employer (and maybe even the educator/us) in order to allow for this to happen in a controlled way when the scope changes legitimately

This was brought up for FuturePath, but the ability to close a project to applications and provide a reason that can be something along the lines of reached maximum applicants needed for this project found matches elsewhere/no longer looking for matches pausing applications to interview We are losing FP projects to LU and to outside applicants and the ability to communicate that to both the students in the cohort, and to us to understand the drop off would be hugely helpful

As an experience admin, I’d like the option to post (scheduled) updates to specific employers or students, not everyone at once. For example, at UNF, students might start applying while we’re still adding employers. We need a way to message just those new employers. Same with students: some teams may be falling behind, but it wouldn’t make sense to send that reminder to all 10 teams. Also, joining their teams to follow up directly could raise privacy concerns.

Presently, an employer can select their own number of teams wanted and it will lock this in and it has to be changed in forest if it is not caught before accepting - I have had to go back and change this numerous times for Ascent, and am seeing it happen elsewhere. I do not anticipate Ascent being able to remember to check for this and request the change, and it will cause them to become frustrated. It would be nice to disable this feature if we know our experience does not let employers select team sizes. (this is most of PPD - employers select 1-3 teams, but we upload 5-6 people as teams)

Hello, When inviting teams the prompt says you can invite existing folks, or you can add an email to invite, which is fairly clear to those familiar, but lately I've had numerous partners not realize they can enter emails into that box and reach out for help lately. Im wondering if the text can change from "search" to "search user or enter email address for new user" (or similar) so it is extra clear for partners.

Allow survey respondents to order options based on a ranked criteria, such as least to most importance. Could be a version of the multiple choice grid which only allows one response per value option. e.g. If you hired or would consider hiring a participant who completed your project work, what would make the candidate a good fit for your organization? Please rank the following, 1 being the most important, 4 being the least important: (Respondent would then only be able to select '1' once) Technical Skills Durable Skills Relevant Experience Domain/ Industry knowledge

A partner asked if they could export summary data. At this moment we are only able to export replies to CSV format. This would allow for a more streamlined user experience. Is it possible to include the option to export survey summary data? Screenshot from user attached.

In Staging: When filling out a work log, we should limit the learner from entering alpha characters in the hours worked field. If not, we should at least fix the validation message to instruct the learner to only enter numerical values