Some of the other answers suggest that the actual values used are not that important, as long as they are mapped properly to their "meaning" when shown in forms or queries or reports.
I'm going to strongly suggest that is not true, or at least won't be true for long.
Why? Because I guarantee someone is going to ask you for a report that shows an "average" condition rating:
- Is our average road condition (over all roads) better today than this day last year?
- Which roads have the worst and best average rating along their entire length?
- Which areas of town have the worst and best average condition rating?
- Are there inspectors that consistently rate the same roads worse or better than other inspectors?
and a hundred other questions that management loves to be able to ask. Unless your ratings are numeric (and held in either strict ascending or strict descending order), you won't be able to perform these calculations.
That said, I'm not aware of any industry standard for doing so, you just have to be as consistent as you can in your methodology.
For example, it is confusing to take a survey that constantly flip whether 5 is "good" vs "bad":
- How satisfied were you with your meal? (1=very satisfied, 5=not at all satisfied)
- Was your server friendly? (1=Not very friendly, 5=very friendly)
So pick one and stick with it.