I thought about that too, but, somehow, I forgot to add it in the OP. I also don't understand the 300 good reports "barrier".
It's more of a milestone IMO. To incentivize users to reach a minimum of X good reports to receive a certain perk.
If every user here would have at least 300 good reports things would definitely look different
Additionally, I remembered also another suggestion which I forgot to mention in the OP: maybe there should be more resolutions for the reports, not just "good" and "bad". For easier understanding of the bad reports, maybe these could be classified in more types: one of them could be "duplicate". Another status could be "will not handle" - this can be used for those reports which, for one reason will never be handled.
The "duplicate" sounds fine but not that common to implement. It doesn't happens more than 0.1% of the time (100% guesstimated stats, so don't quote me on this)
Besides, maybe the mod's username could be added for each solved report. Thus, in case of bad reports, the reporters could ask the mod why the respective report was considered as bad. This way, the reporters would also understand why some reports are considered as being bad.
Mod's username = more drama. Also last time you received a feedback you opened a thread about it so at the end it still boils down to that (discussing in a thread).
Also an additional field where mods can leave some feedback sounds nice but would be very time consuming and in some cases would be the spark that lights the flame to more drama.
For example, I reported several shilling of some members and all the reports were good. Then I reported the exact type of posts of other members and all were marked as bad. Thus, as a reporter, I'm wondering: why was post X considered good and post Y was considered bad, if both have the same pattern?
Different mod, different board, different post in the thread (some OP some just regular posts), on-topic shilling
(jk) ... there are lots of variables.
Might also wanna give reporting spam, low value, repetitive sig spam bs, bumps, malware etc a try. They tend to grow on you!
I recommend (re)hacking it to add in a few particulars that are missing from the original:
1) priority text within reports (e.g. [P1], [P2], etc. prefixes)
- I order it from 1 (malware) being maximum priority to 5 (2+ bumps/day) being minimum priority
2) page-wide report for spam
A prefix method is highly prone to abuse and pretty subjective. Things some users might feel they should have max priority: "paid for X and did not get product", "doxxin", "insulting/swearing", "defaming me and my business", etc IMHO just writing "malware" in that comment box would give it enough priority.