Recommendation Audit or Categorisation | Community
Skip to main content
Submitted

Recommendation Audit or Categorisation

Related products:ReportingFin & AI
  • September 8, 2026
  • 0 replies
  • 5 views

Currently Fin Recommendations (content gaps, data gaps and action gaps) only have two options - reject or mark as done/approve. Rejecting removes the recommentation and stops Fin from suggesting it again in the future. In our case this is limiting as a recommendation (in particular or data and action gaps) may not be technically possible today, but as technology changes the recommendation may make sense at some future time. It would be amazing if recommendations had a option for a “soft rejection” where it may be rejected now but we’d like Fin to make the recommendation again (if warranted) at some future time, someting like “remind me again in X months”

It would also be great if: there were an audit trail, where we could see what recommendations were accepted and rejected. In addition to an audit, being able to specify reason for rejection, this would help with identifying the recommendations that may not make sense today but could in the future. 

Currently to overcome this limitation in auditability and tracking we need to keep a running list of recommendations in a spreadsheet, noting the recommendation, when it was suggested and the reason for rejection and review it regularly to see what might be feasbile today that perhpas wasn’t a few months ago. This adds extra overhead to our process and means having to bounce between applications vs having one source of truth within Fin.