Rating Responses
Rating responses allow reviewers to provide numeric assessments on customizable scales, making them ideal for quality evaluations, performance reviews, and any scenario where you need quantifiable feedback that can be easily aggregated and analyzed.When to Use Rating Responses
Rating responses are perfect for:Quality Assessment
Evaluating content quality, product ratings, service assessments, or any subjective quality measurement
Performance Evaluation
Rating employee performance, AI model outputs, system effectiveness, or process efficiency
User Experience Rating
Collecting feedback on user experience, satisfaction levels, or preference measurements
Risk Assessment
Scoring risk levels, threat assessments, or priority ratings where numeric scales provide clarity
Configuration Options
Rating responses support flexible scale configuration with custom labels and increments:Required Parameters
number
required
Maximum value on the rating scale
Optional Parameters
number
default:"1"
Minimum value on the rating scale (must be less than scale_max)
number
default:"1"
Step increment for the rating scale (e.g., 0.5 for half-star ratings, 1 for full-star ratings)
boolean
default:"false"
Whether a rating is mandatory for completion
Implementation Examples
Content Quality Rating
Five-star quality assessment with descriptive labels:Risk Assessment Scale
Ten-point risk assessment with threshold labels:User Experience Satisfaction
Net Promoter Score (NPS) style rating:Response Format
When a reviewer provides a rating, you’ll receive the numeric value:Use Case Examples
1. Content Quality Evaluation
- Configuration
- Sample Response
- Processing
2. AI Model Performance Rating
- Configuration
- Sample Response
- Processing
3. Customer Satisfaction Survey
- Configuration
- Sample Response
- Processing
Validation and Error Handling
Automatic Validation
The mobile app automatically validates rating responses:- Range validation: Ensures rating falls within scale_min and scale_max bounds
- Step validation: Verifies rating aligns with scale_step increments
- Required validation: Prevents submission when required=true and no rating provided
- Numeric validation: Ensures only valid numeric values are accepted
Server-Side Validation
Your application should validate received ratings:Best Practices
Scale Design
Choose Appropriate Scale Range
Choose Appropriate Scale Range
- 1-5 scale: Best for simple quality assessments, easy to understand
- 1-10 scale: Good for detailed evaluations, allows more granularity
- 0-100 scale: Ideal for percentage-based ratings, performance metrics
- Custom ranges: Use negative values for scales like -5 to +5 for sentiment
Set Meaningful Steps
Set Meaningful Steps
- Whole numbers (1.0): Simplest option, good for most use cases
- Half points (0.5): Adds precision without overwhelming complexity
- Decimal precision: Use sparingly, mainly for calculated scores
- Larger steps (5): Good for percentage-based scales (0, 5, 10, 15…)
Label Key Points
Label Key Points
- Always label the endpoints (minimum and maximum values)
- Include middle anchor point for context
- Add labels at natural breakpoints (quarters, thirds)
- Use descriptive labels that explain the meaning, not just “poor/good”
Consider Context
Consider Context
- Match scale complexity to reviewer expertise
- Use familiar scales when possible (5-star, 1-10, percentage)
- Consider cultural differences in rating interpretation
- Test scales with actual users to ensure clarity
Processing Best Practices
Threshold-Based Actions
Threshold-Based Actions
Aggregate Multiple Ratings
Aggregate Multiple Ratings
Trend Analysis
Trend Analysis
Analytics and Reporting
Rating Distribution Analysis
Performance Benchmarking
Next Steps
Number Responses
Learn about numeric input with validation and formatting
Boolean Responses
Implement simple true/false decision workflows
Response Analytics
Advanced techniques for analyzing and aggregating rating data
Mobile Experience
See how reviewers interact with rating scales on mobile devices