83 results found
-
Additional Process Visibility Option
Currently, for active processes, there are three visibility options: Public, Restricted, and Internal.
Public: Visible to applicants; applicants able to apply when open
Internal: Not visible to applicants
Restricted: Only visible to applicants with the corresponding access codeBased on the use of our applicants & grantees, I would love to see a fourth option added that would allow a process to be visible to applicants, but locked, so that applicants would need an access code to apply. Essentially a restricted visibility where the applicants could still view the process as if it were public, but still requiring a code.
…
9 votes -
Shared Documents for Applicants
We would to have a 'Shared Documents' folder specifically for our applicants/grantees to be able to access.
I.e. This way the Agreement to Grant Terms is available for them to access at any time through their profile.
13 votes -
Jump applicants to part(s) of application that are incomplete
When the universal application lists things that still need to be completed before an applicant can submit, is there a way they can be linked so an applicant can click and be taken to that incomplete section?
28 votes -
Stand-alone LOI
LOI - generally called a Letter of Intent - we call it a Letter of Introduction. It's kind of an 'elevator speech' for applicants where we get a snapshot of some financial needs (we ask for up to 3). We use is as a guide and have a phone conversation with the applicant once the LOI is submitted. depending on our yearly goals, we may pass on this applicant for the year, but want to keep them for the next year.
It would be great to have a 'stand-alone' LOI that can be branched to an application at another date…
2 votes -
Change application language to eligibility for first stage of UA
When using a UA, those first common questions are really for eligibility, at least the way we are using it. So when the potential applicants get to the confirmation page, for either the failure message or to see what scholarships they are eligible for, it says your application has been submitted, but really, it hasn't. They are, at that point, ready to enter the application and its questions. Can there be some terminology changes set for the first stage? I make it clear in my instructions what's to happen, but an applicant as you define it shouldn't really be one…
13 votes -
Allow Copy Previous Requests from Organization (Instead of User)
It would be really useful if the Copy Previous Answers function worked for all requests under an Organizational profile instead of just the specific User profile. This would be helpful for some of our organizations who experience high turnover or for folks who are applying when other colleagues are on leave.
10 votes -
Unnecessary Spacing On Forms
There appears to be unnecessary spacing added below the instruction field when building an application or other form. I suggest removing this formatting so instructions appear more naturally grouped with the relevant questions. If the additional spacing is necessary, I suppose we could add that in by adding a blank question field.
9 votes -
Universal app confirmation page
I find the language on the Universe confirmation page confusing. It says the applicant is eligible for the following opportunities, it's not 100% clear that the applicant must continue to apply. I'd suggest moving the blue "Continue" button to the top, or changing the message to read: "Based on your answers, you may apply for the scholarships listed below. Click the blue Continue button at the bottom of the page to complete the applications."
10 votes -
Question Mark Icons
I'd love the option to add question mark icons next to our application questions that would invite applicants to hover over them if they want information as to why we are asking the question. It would go a long way in making the process more transparent and minimizing the power gap. (Similar to what you offer in the Process Manager)
17 votes -
Add User text restrictions
Please remove restrictions on "Add User" information fields!! Only allowing certain formats for phones/addresses/postal codes restricts inputting accurate information. (Can't input extensions for phone numbers, international phone numbers, international addresses.)
1 vote -
Custom URL capability for SLM and GLM grant processes
It would be nice to be able to create a custom URL for grant and scholarship programs instead of the grantinterface.com address.
12 votes -
Organizing Universes
It would be nice if Universes were ordered alphabetically or if administrators could drag/drop to order. You can drag/drop Processes to order them, but not Universes. Universes show in the order in which they were built, which doesn't make much sense when an applicant scrolls down the page.
10 votes -
Allowing larger file sizes
Our applications typically require a lot of uploads. They also have a lot of conditional logic. For instance, if someone is applying for a smaller amount of money, we ask for less financial documents, It would be nice if the allotment for file size allowance per application took the conditional logic into account instead of making it all cumulative. We bump into the issue of not having enough file size space in our applications all the time, and often steal a megabyte or two from one upload field to accommodate another, only to need to steal from somewhere else, etc.
6 votes -
SLM Flow of Application Questions for Student
So I'm working on YR 2 for our UA. Making edits and trying to get a better handle on it all. I'm in now as an applicant. We have sections of questions: shared by all of the scholarships, shared by some of them, and then ones that are only for one scholarship. Question groups are collapsible, right? Going on the scenario that a kid is eligible for several, wouldn't it be good for those shared question sections that they've already completed to be hidden or collapsed? Now I'm old, but it seems clunky and confusing to even have them there…
6 votes -
Limit Applicant's Draft Applications within a Process
Please consider adding the option in the Process Summary that allows us to limit the number of applications an applicant can begin within that process. We only accept one application for most of our grant programs and would like to be able to set a limit to the number of applications one can start. Currently, applicants can start multiple drafts of an application. This creates lots of abandoned applications.
The Apply button could be deactivated and greyed out once an applicant has reached the limit of applications that can be drafted and submitted within the process.
18 votes -
View History: by all of the organization's people
it's great that within an organization, everyone can view all of the applications that were submitted. Unfortunately, they can not see the followups. this is a challenge when a new person takes over a project and they don't use the same account. as well the primary contact which is usually the executive director can not even see the followups to know if they have been complete or what was shared. this would be so helpful for our non-profits so they can easily share application and followups... thanks
6 votes -
Changing the 'show applicant' a document.
We delay our grantees' ability to see the decision on their application by 14 days. This was set up for us by Foundant. We upload their approval/denial letters into their request documents at the time of the decision, but do not want the grantees to see the letters until after the 14 day period when both the decision and the letter should become simultaneously visible to them. At this point in time, we have only two choices - to never allow the applicant to see their approval/denial letters in their Request Documents, or to wait before posting the letters to…
5 votes -
allow multiple users of an organization to copy applications started by other users
If an organization has multiple users, and user A creates a request, as the product works currently user B can NOT copy over that data when they enter a new application. I'm requesting that all users be able to copy data from all existing requests for an organization no matter who created the request.
8 votes -
Group collapsed on applications
When an applicant returns to the application to resume work, the groups of questions could be collapsed and if all questions within the group are complete - the group could be flagged (with a check or a color change). Or, have an option to allow the admins to create the applications in pages, which can be flagged as complete when all questions are filled in on that page.
21 votes -
alert that applicant has a active grant
It would be great if... there was an alert for applicants notifying them that they have an active grant. With a few exceptions, we do not allow organizations to have more than one active grant (per program) at a time. Recently, I had a couple applicants submit applications who already had active grants. I did not know they had active grants until I looked at each organization's history. It would be great if the active grant was highlighted on their dashboard or they received an alert when applying for a grant notifying them that they had an active grant. This…
4 votes
- Don't see your idea?