F1 score combines precision and recall into one number using their harmonic mean. It's calculated as 2 times precision times recall, divided by precision plus recall.
Why it matters
A plain average can hide a badly unbalanced system. With 100% precision and 10% recall, the simple average is 55%, which sounds decent. F1 comes out around 18%, much closer to the weaker number, which is a fairer picture of a system that misses most of the real cases.
When to use it
F1 is handy when you need one number to compare models quickly and both kinds of mistakes matter about equally. When one is clearly worse, like missing a safety violation, look at precision and recall separately or use F-beta, because F1 alone doesn't show which way the system is failing.
Variants worth knowing
F1 weights precision and recall equally. The more general F-beta score lets you tilt it: F2 puts more weight on recall, and F0.5 puts more weight on precision. For datasets with several categories, macro F1 averages the score across categories equally, while micro F1 pools all the items together, so large categories dominate it.

A concise guide to SaaS customer support, covering team models, SLAs, KPIs, tooling, 24/7 coverage, and when outsourcing makes sense.

A practical guide to building 24/7 customer service, covering staffing, follow-the-sun shifts, escalation, automation, and SLAs without burning the team.

Learn how our managed services are designed to shoulder all operational responsibilities, offering clients streamlined, process-based operations under a flat monthly fee, allowing them to focus on growth.

Build a reliable social media community management operation with clear SLAs, escalation paths, moderation standards and off-hours coverage.

Explore 8 managed services examples across labeling, moderation, support, KYC and AI safety, with scope, SLAs, outcomes and practical lessons.

Scale ecommerce support with BUNCH using automation for routine work and real people for difficult tickets, with 24/7 coverage and order ops.