1. Reporting settings and targets
Set the reporting context and performance targets used to interpret your metrics. Targets are illustrative; replace them with your site's approved goals.
Lower review time and deviation rates are generally preferable, but all targets should reflect your process, product risk and approved quality objectives.
2. Add batch record data
Enter one row per batch. For the right-first-time metric, mark “Yes” only when the record met your defined first-pass acceptance criteria without corrections or rework that count as a first-pass failure.
3. Batch data table
Edit a value directly in the table. Metrics update automatically.
| Batch / lot | Product / line | Date | Status | Required steps | Completed steps | RFT | Review days | Deviations | Rework hours | Notes | Action |
|---|---|---|---|---|---|---|---|---|---|---|---|
| No batches added yet. Enter a batch above or load the sample data. | |||||||||||
4. Performance dashboard
Metrics are calculated from the batch rows currently in the table.
Target performance
Bars show progress toward a target for completion and RFT. For review time and deviation rate, the bar shows how much of the target threshold is being used; lower is better.
5. Generated performance report
Generate an updated summary before exporting or printing.
5. Generate and export
When you are satisfied with the batch entries, create a report. You can then export the underlying data or print the report to PDF.
CSV files can be opened in spreadsheet software for further analysis. Review exports according to your organization's data-handling procedures.
How the metrics are calculated
| Metric | Calculation | How to interpret it |
|---|---|---|
| Step completion | Total completed steps ÷ total required steps × 100 | Shows the proportion of entered required steps marked complete. It is a weighted aggregate across the listed batches. |
| Right-first-time (RFT) | Batches marked Yes ÷ batches assessed Yes or No × 100 | Shows the proportion of assessed batches meeting your defined first-pass criteria. “Not yet assessed” rows are excluded. |
| Average review cycle | Sum of review days ÷ number of entered batches | Shows the mean cycle time for the values entered. Ensure all teams use the same start and end points. |
| Deviation rate | Total deviations ÷ number of batches × 100 | Normalizes the entered deviation count to a rate per 100 batches. It is not the percentage of batches with a deviation. |
| Record rework | Sum of entered correction / rework hours | Shows the total hours entered. Divide by batch count to estimate average hours per batch. |
Using batch record metrics to improve eDHR performance
Batch record metrics help manufacturing, quality and operations teams understand whether production documentation is being completed consistently and reviewed efficiently. When tracked over comparable periods, the measures can highlight recurring delays, documentation errors, rework and potential opportunities to improve electronic workflows.
Completion rate and outstanding steps
Completion rate compares completed steps with required steps across the entered batch records. A high overall rate can still hide individual batches with overdue or incomplete steps, so aggregate metrics should be paired with batch-level exception review. Do not treat a high completion rate as evidence that every batch is ready for release.
Right-first-time performance
Right-first-time performance is useful for identifying how often batch documentation passes the defined first review without corrections. To compare sites or periods fairly, document what counts as a correction, how repeated reviews are handled, and which batches are included in the denominator.
Review cycle time and deviations
Review cycle time can reveal bottlenecks between production completion, record review and final disposition. Deviation rates provide a normalized view of recorded deviations per 100 batches, but they should be interpreted alongside severity, recurrence and product risk. A lower count is not automatically evidence of a stronger quality system.
From reporting to process improvement
Use the results to identify specific causes, assign owners and monitor corrective actions over time. For example, repeated missing fields may suggest a need to improve electronic form design, instructions, role permissions or training. Repeated review delays may point to queue management, staffing, escalation rules or integration issues.
For regulated manufacturing, establish documented metric definitions, controlled data sources, access controls, review responsibilities and change-management procedures. If the report is used in a validated process or a quality decision, assess the tool and its outputs under your organization's applicable procedures.