Stop populating the Recommended Amount field when an application is considered.
There are several old ideas for this same change, but i'm adding another one. This needs changed. It is very inconvenient for many of us who use the Reviewer portal and ask the reviewers to enter a Recommended amount. Currently I have to zero out the Recommended amount field so my Reviewers don't see that amount in their review. I want them to enter that amount and not skip over it just because they see a number there. Additionally, I tried to use Set Value in the application form for the Recommended Amount field and that does not appear to have worked. It still populated the field with the Requested Amount.
-
Carol Greco
- Mar 3 2025
Related ideas
I agree with James Pike for the same reasons.
In our most current round, we received over 600 applications. Only about 10% of them will be awarded and few of them at the requested amount. Having the Recommended Amount populate at $0 is the most efficient for us. Or if there was a way to adjust the Recommended Amount field in bulk, we could more easily work around this new autopopulate feature.
it is an incredibly presumptive approach (rarely do we award grants exactly the same as what is being requested) and exposes us to a lot of risk in terms of errors being made.
Agree. This is an inconvenience. We work with several Funds and for some, the workflow is such that we rely on the recommended amount being $0 until we manually change it with a grant approval. Since multiple team members work on the Funds, if someone sees a recommended amount populated they might think it's been approved when it hasn't been.
This is an urgent need.
Unfortunately, this issue becomes more critical in the new application portal. The Recommended Amount field now automatically populates with the amount applied for, meaning we have to zero this out for every application.
This is a problem for us. We use the reviewer portal and want our reviewers to see $0 and enter their recommended amount. I'm going to have to zero out the recommended amount manually for every request. I am becoming more and more disappointed with this new system. We're going backwards on way too many things.
Highly upvoted. Huge inconvenience.
Thanks Carol for creating this idea, and I completely agree. In the legacy portal, our considered applications did not have the recommended amount default to the request amount so it's frustrating that the behavior is different in the new portal. It is extremely inconvenient and makes room for human error.