Which of the following is NOT a best practice for configuring performance templates?

• A. Avoid version control
• B. Use modular sections
• C. Standardized rating scales
• D. Test with sample data

Answer: (A)

Version control is essential for managing performance templates because it provides a history of every change, who made it, and when. This governance lets you roll back to previous states if a configuration causes issues, track why updates were made for audits, and coordinate edits across teams without overwriting each other. Avoiding version control breaks this safety net and makes changes hard to trace, revert, or collaborate on.

Other best practices—building templates from modular sections, using standardized rating scales, and testing with sample data—all support consistency, reusability, and quality. Modular sections let you assemble templates from reusable parts, so updates apply cleanly across multiple templates. Standardized rating scales ensure uniform interpretation and easier calibration and reporting. Testing with sample data helps verify that calculations, routing, and workflows behave correctly before going live.

So, avoiding version control is not a best practice; version control should be part of the configuration process.