Visible update context

Regulatory guidance shown here uses Codes of Good Practice, generic estimator profile, as of 2024-12-01.

Open current source reference
Ruled Ledger Calm, South Africa specific

Estimate your B-BBEE position without pretending the rules are static.

ScoreBee starts with enterprise classification, shows the assumptions behind every estimate, and keeps the line between a planning answer and a verification outcome visible the whole time.

As-of dates shown in workflowClassification-first routingSource-backed recognition output

What the estimator gives you

  • Likely enterprise path, EME, QSE, or Generic, before you enter full scorecard detail.
  • Shortcut logic when ownership thresholds support it, instead of forcing unnecessary form fill.
  • Estimated level, procurement recognition, risk warnings, and an evidence checklist for next steps.

Planning estimate only. Use it to prepare a real verification conversation, not replace one.

How ScoreBee works

One path at a time

1

Classify the enterprise

Start with turnover, ownership profile, and the active ruleset date so the calculator routes into the right lane.

2

Estimate with the right logic

Shortcut eligibility is checked before full scorecard inputs. Generic scenarios expand into element-level scoring only when needed.

3

Prepare the real next step

Results explain what moved the estimate, what could discount it, and what evidence a verifier will still ask for.

Choose your path

Router-first, not content-first

Start an estimate

Move straight into classification, live summary, result explanation, and assumption review.

Need depth first?

Review methodology, FAQ, and sources without the homepage turning into a full documentation dump.

Guide routes

Long-tail questions belong on dedicated pages

B-BBEE scorecard explained for operators

A plain-language walkthrough of how ownership, management, skills, supplier development, and SED combine in a practical B-BBEE estimate.

Read guide

B-BBEE levels explained without consultant fog

A practical read on what Level 1 through non-compliant contributor mean, how recognition maps in, and where operators misread the result.

Read guide

EME vs QSE vs Generic, where your estimate starts

Turnover thresholds shape the first branch in the calculator. This guide explains why the same ownership profile can produce very different workflows.

Read guide

How to improve your B-BBEE score without chasing vanity points

Operators usually need a priority order, not a generic checklist. This guide explains how to turn a weak estimate into a focused improvement plan.

Read guide

Priority elements and discount risk

A usable estimate must surface sub-minimum risk clearly. This guide explains what the warning means and how to act on it.

Read guide

Source posture

Nothing hidden in opaque calculator math

Every mutable threshold shown in the app uses an as-of date and source link. That keeps the estimator durable and makes it easier for your team to challenge defaults before someone mistakes them for timeless law.