Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Scoring And Deadline topic
No spam. Unsubscribe anytime.
Committee reminded scores due Jan. 28; staff warns software may delay point deductions
Summary
Committee members were reminded to finalize development scores by January 28. Staff said point deductions for application errors may not display on individual scorecards due to a software issue and will be applied after submission; staff comments will document errors in the meantime.
Rowan reminded committee members that development scores must be entered and finalized in Neighborly by January 28. "Your development scores are due on January 28th," Rowan said, and staff will send reminders and Portland-specific CDBG goals to guide scoring.
Rowan also warned of a technical problem affecting automatic point deductions. "Staff has and and will be deducting some points from applications due to errors or missing sections," Rowan said, but a software issue may prevent those deductions from appearing on committee members' individual scorecards. "So you may not see those point deductions counted on your individual scorecards. They may have to be applied after," she added. Staff advised reviewers to check staff comments for errors because deductions may be applied administratively after finalization.
Rowan walked the group through scoring categories including sustainability, capacity to deliver, leveraged funds, and letters of support, and encouraged scorers to add comments where scoring is notably high or low. Committee members agreed to discuss thematic scoring guidance immediately rather than postpone to the next meeting.
