ZTEST in Zoho Sheet: One-Sample Z-Test Probabilities

ZTEST is a statistical test of a sample mean against a hypothesized population mean. Zoho Sheet officially documents the syntax ZTEST(data; μ; [σ]), where data is a sample of numeric observations, μ (mu) is the hypothesized mean, and σ (sigma) is an optional standard-deviation argument. The function returns a probability, not the z-score itself. The example below makes the population standard deviation explicit, rather than silently relying on unspecified missing-argument behaviour.

Evidence status: The public Zoho help establishes its syntax and purpose. Exact example probabilities below are independent mathematical predictions calculated with Python/SciPy using the specified known population standard deviation. No Zoho Sheet formulas were executed and no native screenshots, mobile compatibility tests or performance claims were produced. English documentation does not establish a universal first-supported version or identical locale rules.

ZTEST(data; μ; [σ])

The brackets in [σ] denote an optional parameter in Zoho’s documentation; they are not typed into the cell formula. Zoho’s help page identifies sigma as optional but does not fully specify the substitute estimator or arithmetic it uses when sigma is omitted. Therefore, this page intentionally uses an explicit value in its worked examples and does not import the omitted-sigma rule from another spreadsheet application. The documented English formula separator is a semicolon; another locale’s interface may display something else. Z1

A z-test is generally framed for a population standard deviation known independently, suitably random independent sample observations and either a normally distributed measurement or a justified sampling approximation. A claimed “population” standard deviation estimated from the same small sample changes the inferential assumptions; often a one-sample t-test is then more appropriate. The statistical assumptions and one-/two-sided question should be written down before looking at the data.

Suppose a company historically knows its process’s population standard deviation is 5 units and asks whether a new random sample suggests a mean above its established benchmark of 100. Enter these eight observations in J1:J9:

Request the explicitly specified-sigma test in a separate cell, say L2:

=ZTEST(J2:J9;100;5)

Independently modeled expectation: approximately 0.008104770705 for the conventional upper-tail normal z probability with sigma=5 and null mean=100. It is not a value captured from Zoho Sheet. The sample size is n=8, the sum is 834, and the sample mean is 104.25. With known population standard deviation 5, the normal-theory statistic is:

z = (sample mean − null mean) / (σ / √n)
  = (104.25 − 100) / (5 / √8)
  = 2.4041630560342617

For the independent statistical model, the upper-tail probability is P(Z ≥ 2.4041630560342617) = 0.008104770704612714. The corresponding left-tail area is 0.991895229295. The official Zoho NORMSDIST reference specifies a standard-normal left-tail cumulative function, so an unexecuted cross-check formula for the same upper-tail model is:

=1-NORMSDIST(2.4041630560342617)

The source supports the meaning of NORMSDIST; it does not prove that Zoho ZTEST returns our predicted upper-tail number for this particular newly invented dataset. That equivalence requires an explicit in-app comparison.

Interpret the one-sided result

If the planned alternative was that the mean exceeds 100, the mathematical model gives a one-sided p-value around 0.0081, which would constitute evidence against a mean exactly 100 at a predeclared α=0.05 under its assumptions. It does not prove that the process improved, that all observations exceed 100, or that the null hypothesis is 0.81% likely. The mean difference is 4.25 units; operational importance is a separate question from statistical significance. Outliers, serial dependence and non-random recruitment can invalidate naive probability interpretation.

The public Zoho ZTEST reference documents a probability and a comparison with μ but is not a complete specification of a one- versus two-tail contract. Consequently, the tail direction above is identified as a conventional normal-theory model, not a verified native-Zoho guarantee. A native reviewer must confirm the intended direction with both positive and negative sample differences.

If the real question was “different from 100 in either direction” rather than “greater than 100”, the conventional two-sided normal-theory p-value is twice the smaller tail:

2 × min(0.008104770704612714, 1 − 0.008104770704612714)
= 0.01620954140922543

For a hypothetical Zoho calculation after verifying the returned tail convention, a proposed two-tail wrapper is:

=2*MIN(ZTEST(J2:J9;100;5);1-ZTEST(J2:J9;100;5))

This composition was not executed and should not be published as a guaranteed native equivalence without testing. It is meaningful only if the inner ZTEST uses the conventional continuous single-tail probability assumed here. Preselecting one-sided versus two-sided hypotheses is a scientific design decision, not a formatting convenience to obtain a smaller p-value. If the sample mean had been below 100, a given one-tail p-value might be near one instead of near zero depending on the implementation’s directional definition.

The official Zoho signature marks σ as optional, so syntactically it permits:

=ZTEST(J2:J9;100)

Do not attach the value 0.008104770705 to this different formula. The public article does not spell out the missing-σ estimator. The sample standard deviation of these observations is approximately 3.882193783343, not the independently known population sigma of 5. If a different estimator is substituted, the statistic and probability will change. The exact omitted-argument handling, treatment of empty or text cells and error boundaries must be checked in Zoho’s own formula editor. Another application’s explicit rule cannot fill a missing Zoho documentation detail.

Microsoft’s current Excel Z.TEST documentation explains Excel’s own fallback to a sample standard deviation if sigma is omitted. That reference is Excel evidence only; it neither proves Zoho’s behaviour nor licenses assigning an equivalent output without testing. A reviewer should run both variants in Zoho with controlled ranges and compare the results against an independently defined estimator.

A traceable results table might record the data range, the test’s benchmark, the externally known sigma, numeric sample size, sample mean, z-score under the specified model, and p-value. For the sample above, useful independent cross-check formulas using Zoho-documented basics are:

=AVERAGE(J2:J9)
=STDEV(J2:J9)
=AVERAGE(J2:J9)-100
=(AVERAGE(J2:J9)-100)/(5/SQRT(8))

These express independently checkable arithmetic but were not run in Zoho in this research. STDEV estimates the sample spread and can be reported as a descriptive statistic; do not automatically substitute it for a truly known population sigma. If sigma is unknown and n is small, seek an appropriate t-based method. Zoho’s TTEST documentation is for two samples, not automatically an identical drop-in one-sample test. A scientifically justified one-sample t statistic can be calculated from sample summaries and the t distribution separately where appropriate.

Practical examples include testing whether average fill weight exceeds a specified nominal level (assuming random independent units and known sigma), analyzing a long-established measurement process, or comparing a standardized batch mean with a specification. Do not claim the mean passed a regulatory standard solely from p<0.05; confidence intervals, measurement reliability and the exact decision rule are essential.

If the values are correlated across time or grouped subjects, √n may be an inappropriate independence-based standard error. If the true population standard deviation is uncertain, the normal approximation can understate error. Do not replace an independently measured sigma with a convenient guessed number in a production decision.

The Zoho ZTEST article was checked on 2026-10-13, as were its related function references below. It is English public documentation for a rolling cloud service, not an account-specific execution report or a per-release compatibility matrix. It does not establish that the function was present in any particular historic desktop release, or that all localized implementations use identical separators. No paid service, Zoho account, browser automation or third-party workbook was used to execute the formulas.

Excel’s Z.TEST article M1 has different punctuation and explicit sample-sigma fallback details. Avoid equating its behaviour with Zoho’s undocumented edge cases. For native validation, test explicit known sigma, omitted sigma, negative/zero sigma, empty/text arrays, sample mean below μ, and locales with different separators. Record software, locale, plan, date and actual output, then decide if additional claims are justified.

• Z1 Zoho Sheet ZTEST official help, signature, descriptions and stated errors; checked 2026-10-13: ZTEST.
• Z2 Zoho Sheet NORMSDIST official help, standard normal CDF meaning; checked 2026-10-13: NORMSDIST.
• Z3 Zoho Sheet TTEST official help, two-sample t-test types; checked 2026-10-13: TTEST.
• Z4 Zoho Sheet STDEV official help, sample standard deviation; checked 2026-10-13: STDEV.
• M1 Microsoft Support Excel Z.TEST, other-product rule when sigma omitted; not native Zoho evidence; checked 2026-10-13: Excel Z.TEST.