-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate consistency of findings between general
and findings
forms
#4433
Comments
@Leighdiddy @James-Paul-Mason @analynd Would this be something you guys could assist with? |
Hi @phildominguez-gsa, sorry I missed this in my inbox! This actually sounds relevant to something that was brought up during our call with HHS today. I'm still unfamiliar and learning about findings so gonna pass this to @danswick and @Leighdiddy for guidance. Thanks! |
Still looking for assistance here @Leighdiddy @analynd @danswick |
@phildominguez-gsa I can confirm that this is correct, we just reviewed this with HUD last week :) Regardless of pushback from auditors, this should be a set if/than rule. We will keep an eye out for edge cases after implementation, but this can move forward. |
Spinning this off of this ticket
The relevant text from that ticket:
Before implementing this validation, we first need to confirm that this restriction is in fact "real" and isn't going to cause problems for auditors in the future. It seems this validation idea came from HHS/Federal audit reviewers, so we want to run it by those who actually submit audits.
The text was updated successfully, but these errors were encountered: