Scorecards
Track per-person quality scores for chart audits, coding accuracy, productivity, and quality reviews, then spot below-80 results and coaching priorities in one working register.
Included with every MangoApps plan.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Healthcare Operations · Medical Coding · Revenue Cycle Management · Contact Centers · Quality Assurance Teams
Overview
Scorecards is a working MangoApps register for recording quality and performance results by person and period. Each record requires a Metric, Person, Period, and Score, with optional Target, Reviewer, and Notes fields. The Metric choices are Chart Audit, Coding Accuracy, Productivity, and Quality Review, so managers can keep several recurring review types in one scorecard app without losing the measurement context.
The app is designed for controlled entry: only managers and admins add records, while records can be edited or deleted when a correction is needed. Use it after a chart audit, coding review, productivity check, or quality review has been completed. The This month and This quarter saved views support routine review, while Below 80 this month isolates results that may need coaching. The Overview screen presents metric rows and cards, the Board screen provides a metric-row view for comparison, and the Scores screen provides the full grid and action bar.
Scorecards is not a payroll system, formal disciplinary file, or replacement for a regulated quality-management record. It also should not be used to make decisions from an incomplete score without reviewer context. Define the scoring scale, target conventions, and correction process before rollout. The Low score alert notifies the app owner when a record is added, and the Weekly coaching list sends a Monday 08:00 digest of current below-80 scores to the app owner, creating a clear review point without requiring a separate spreadsheet reminder.
Standards & compliance context
- For healthcare quality or coding programs, use Scorecards to organize internal review results while following the organization’s approved quality, privacy, access, and retention policies.
- If scores support payer, accreditation, or internal audit activity, confirm that the editable and deletable register meets the applicable record-keeping expectations before treating it as the official record.
- Limit Notes to information permitted by your workspace policy and avoid unnecessary patient, employee, or other sensitive details.
- Use the template as a management aid rather than as a substitute for required clinical, billing, employment, or incident documentation.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Add Scorecards to your MangoApps workspace and confirm the Metric choices, score scale, target convention, and app owner before entering live results.
- Keep record creation limited to designated managers and admins, and decide which reviewer is responsible for validating each score.
- Add one record for each completed review by selecting the Metric, Person, and Period, then entering the Score and adding Target, Reviewer, and Notes when they provide useful context.
- Use the Scores screen for record-level review, the This month or This quarter saved view for routine reporting, and the Overview or Board screen to compare metric results.
- Review the Below 80 this month view when the Low score alert arrives and each Monday after the Scores needing attention digest is sent to the app owner.
- Discuss the result with the assigned reviewer or manager, correct incomplete records when necessary, and use Notes and the record status of the review process outside this app to close the coaching loop.
Best practices
- Enter the Period as the date the review or measurement applies to rather than the date someone happened to type the record.
- Use one agreed scoring scale across Chart Audit, Coding Accuracy, Productivity, and Quality Review, or document metric-specific scales before comparing results.
- Enter Target whenever the score is meant to be judged against an individual or role expectation.
- Assign a Reviewer for sampled or audited results so a low score has an identifiable source and follow-up owner.
- Use Notes for concise evidence and coaching context, not conclusions that belong in a formal employee record.
- Review the Below 80 this month view alongside the Metric and Person fields so a low result is interpreted in context.
- Correct duplicate or mistaken records promptly, and retain your organization’s approved history outside this editable register if changes must be formally audited.
- Check the Monday digest recipient and schedule during rollout so the app owner can act on Scores needing attention.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does the Scorecards template track?
It records one person’s score for a selected Metric and Period, with optional Target, Reviewer, and Notes fields. Metric options are Chart Audit, Coding Accuracy, Productivity, and Quality Review. Managers can use the records to compare results with targets and identify scores below 80.
Who should add scorecard records?
Only managers and admins add records in this template, which keeps score entry controlled and consistent. Each record identifies the Person and can also name the Reviewer. People who need to see results can be given access without being allowed to create records.
How often should we enter scores?
Add a record whenever a review or measurement is completed, using the Period field for the applicable date. The This month and This quarter views support regular review cadences, while the weekly coaching list runs every Monday at 08:00. If your organization scores on a different cadence, use the Period field consistently and adjust the workflow during rollout.
What happens when a low score is added?
The Low score alert automation notifies the app owner when a record is added. The Below 80 this month view then gathers current-month scores below 80, and the Weekly coaching list sends the app owner an AI summary digest called Scores needing attention each Monday at 08:00.
Is this template a formal regulatory record?
Scorecards is a performance and quality tracking register, not a substitute for a record system required by a regulator, payer, accreditation body, or employment policy. Use it alongside your organization’s approved retention, access, review, and documentation rules. Avoid entering sensitive information in Notes unless your workspace policy permits it.
What is the common mistake when using scorecards?
A frequent spreadsheet-era problem is entering a score without a clear Period, Metric, or Target, making comparisons unreliable. Require the three key fields—Metric, Person, and Period—and agree whether every metric uses the same scoring scale. Do not treat a below-80 alert as a final performance decision without reviewer context.
Can we customize the metrics and threshold?
Yes, the Metric choices and score threshold can be adapted to your review program during setup. The supplied options cover Chart Audit, Coding Accuracy, Productivity, and Quality Review, and the coaching view is currently based on scores below 80 this month. Confirm that any new metric has a defined scoring method and target before adding it to routine use.
How does this compare with a spreadsheet or clipboard?
A spreadsheet can hold scores, but managers typically have to maintain filters, rankings, and reminders manually. Scorecards provides typed fields, the This month, Below 80 this month, and This quarter saved views, Overview, Board, and Scores screens, plus an alert and Monday digest. The register is editable and deletable, so establish ownership and review history practices if auditability matters.
How should we roll out Scorecards?
Add the template to your MangoApps workspace, decide which managers and admins will enter records, and agree on the score scale and Period convention. Start with a small review group, check that the views show the intended records, and confirm that the app owner receives the Low score alert and Monday Scores needing attention digest. Then expand the process after reviewers can consistently interpret the results.
Related templates
Ready to use this template?
Scorecards runs on a platform app included with every MangoApps plan — pick a suite and it comes along.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
