Fill Rate

Plauti Context Analysis Types

Last published at: May 19th, 2026

The Fill Rate measures data completeness. It calculates the percentage of records that have a non-empty value for a certain field.

 

The Fill Rate measures data completeness by calculating the percentage of records that have a non-empty value for each field. A fill rate of 100% means all analyzed records have a value filled in for that field; 0% means the field is empty on all records. 

Use for identifying data completeness issues, and evaluating field readiness for reporting and automation. Decide which fields to improve completion for, or deprecate.

Configuration

Set a threshold for what constitutes a good, warning level, or critical fill rate. For most fields that you apply a Fill Rate analysis to you'll want to have as much fields filled as possible. This would mean for example a good fill rate is 90% or more, warning level would be between 80-90%, and anything less than 80% filled would be critical. 

For those cases where having empty fields is good, you can reverse the threshold signalling by clicking the Reverse button. 

Detailed Job Results

In the Context Job Results, the doughnut chart groups all analyzed fields into fill rate ranges (0-20%, 20-40%, etc.) to show overall data completeness at a glance. Hover over the different ranges to see the number of records in that range. 
The bar chart sorts the fields by their fill rate; the fields with the number of records containing a value are listed at the top. 
In the Field Details table, "Fill Rate" is the percentage of records that have a non-empty value, and "# Records Without Value" shows the absolute count of empty records per field.

Key Insights

  • Data completeness: which fields are well-populated vs. mostly empty
  • Reality check on ‘Required’ fields: shows whether they’re really filled in practice
  • Trust level for analytics/AI: which fields are reliable for use in reports and AI models
  • Field usage patterns
    • High Fill Rate = actively used, important in process
    • Very low Fill Rate = candidate for clean-up or removal
  • Trend monitoring: Are key fields silently degrading? Is completeness improving after a change? 
Scenario Actions
Key fields with low Fill Rate
  • Make field required where appropriate (layouts, flows)
  • Add validation rules so all channels enforce it (UI, API, imports)
  • Fix integrations to populate the field
  • Run cleanup/enrichment for records where it's empty
  • Re-run Fill Rate analysis to confirm improvement
Non-essential fields with very low Fill Rate
  • Decide whether to keep and fix, or to retire the field, thereby simplifying the user experience.
Required fields not near 100% Fill Rate
  • Audit all entry points (forms, API, flows, imports)
  • Align rules so entry points cannot bypass the field
Preparing for AI/reporting
  • Define a minimum Fill Rate threshold for analytics (e.g. ≥ 80% or 90%)
  • Only use fields that score above that threshold in AI models, dashboards and KPIs
  • Regularly review Fill Rate for fields used in key reports