Feature Requests

I’ve received feedback from Francophone employers who would really appreciate the ability to create projects in French using the AI tool on the platform. Currently, even when they input their project goals in French, the tool generates the project in English. It would be great to make this feature more inclusive by allowing full French-language generation. This would improve accessibility and the overall experience for our French-speaking users.

Say I have an experience with binding dates, and a team has missed the start date of a project, I'd like to be able to re-activate the team and bypass the binding deadline for the start date. Right now if I activate the team, it will go back in incomplete within 10 minutes unless the team starts the project in that window. This same logic would be nice for any other binding date. I can work around this today by setting additional grace period days on the team, but this would also give them those same grace days on the end date too, which I don't want in this case.

In Riipen surveys, to allow clearer reading of questions and response options, Riipen should add rich text formatting to survey questions and response options, allowing for bolding and italicizing of text.

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.

It would be really helpful to have a notes area for teams/individuals that respond to an experience to make it easier to keep track of which one is which and thoughts about their eligibility for the experience.

As a project approver I would love an "in-review" stage/flag for match requests - this would allow employers to know it is being looked at, or for admins/educators to know that revisions are being reviewed, etc. This would also allow for more of a "pipeline" view for programs where multiple people are in the experiences working through match requests (Like Ascent, TCF, or in our own programs where we have PM and PS in there) Although we do try to suggest the notes feature, this would save time and ensure more consistency and transparency.

As per my chat with Emily: As an admin/educator when I click my "requests" inbox at the top of my page I would like to see all matches and requests, which include matches that are imported and bypass the request stage. Currently, only imported matches that go through the request stage show up. This will allow for a more "pipeline" type view for our partners with one source of data.

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

As an employer I should be able to add milestones to teams at any time regardless of who sets dates, etc (maybe with an approval mechanism?) This will help with project planning across teams after kick-off and is an ask from TCF (partner). They would love to know an ETA is possible Discussed with Emily async.