How BonusPayCalc builds formulas, separates intent, and reviews pages

This page exists because calculator sites often hide the most important part: how the result was framed, which assumptions were chosen, and where the estimate stops being trustworthy. BonusPayCalc now documents that openly.

Intent first

STIP, commission, OTE, year-end bonus, and broad bonus payout pages are separated on purpose.

Formula transparency

The key payout drivers should be visible on-page instead of hidden in abstract output language.

Scope control

Pages are estimates for planning only, not payroll approval or legal interpretation.

What this fixes

Too many generic pages answering different intents badly.
Thin calculator pages with no explanation or trust layer.
Confusion between formula help, terminology help, and software-buying intent.

1. Formula selection logic

Start from the compensation language

A page should match the plan wording such as STIP, annual incentive, commission rate, OTE, retention bonus, or year-end bonus.

Use the narrowest useful formula

A broad page is only appropriate when the query itself is broad. Exact plan types should have exact entry pages.

Expose the assumptions

Target bonus, weighting, attainment, proration, caps, and modifiers should all be visible and explainable.

2. Why the site separates calculators, guides, and software pages

Calculators

Used when the main job is to estimate a payout and pressure-test a few variables.

Guides

Used when the real blocker is terminology, payout mechanics, or plan interpretation.

Software pages

Used when the real problem is governance, approvals, exceptions, forecasting, or audit trail.

This separation is deliberate. It reduces search intent mismatch and makes internal linking more useful.

3. What gets reviewed on important pages

Review area	What gets checked	Why it matters
Formula fit	Whether the page matches the compensation language and payout structure.	A generic formula on the wrong page creates bad trust and bad SEO signals.
Inputs and output wording	Whether the page explains target bonus, multipliers, proration, attainment, or caps clearly.	Users need to understand what moved the number.
Support links	Whether the page connects to guides, methodology, and other relevant cluster pages.	This reduces orphaning and improves user path depth.
Trust language	Whether the page says when the estimate is useful and when it should not be treated as final.	Important for sensitive pay and payroll topics.

4. Sensitive topics and source notes

Some topics need extra care because people confuse a gross estimate with a real payroll result. BonusPayCalc uses source notes and disclaimers in these areas rather than pretending a quick formula can answer everything.

U.S. Department of Labor — bonuses under the FLSA

Useful for overtime questions involving nondiscretionary bonuses.

U.S. Department of Labor — regular rate overview

Helpful when commissions or bonuses affect overtime treatment.

IRS Publication 15

Helpful when readers confuse gross bonus estimates with payroll withholding outcomes.

Methodology FAQ

How does BonusPayCalc choose formulas?

Pages are organised by plan type and decision stage. The goal is to use the narrowest formula that matches the wording in the compensation plan, not the broadest generic keyword.

Are the calculator results official payroll figures?

No. Results are planning estimates. Users still need to confirm plan rules, payroll treatment, eligibility windows, and withholding through their employer or advisor.

Why does the site separate calculators, guides, and software pages?

Because the searcher’s problem is not always the same. Some people need a formula, some need interpretation, and some teams really need process software rather than one more calculator.