EXPONDIST in Zoho Sheet: Exponential Waiting-Time Probabilities

EXPONDIST models the time or distance until the next event under an exponential waiting-time assumption. Its third argument chooses between probability density and cumulative probability. The documented Zoho signature is EXPONDIST(x; lambda; mode); all three arguments are shown as required in the official English reference. For example, assuming a steady arrival rate of 2.5 events per minute, =EXPONDIST(0.4;2.5;TRUE) predicts approximately 0.632120559, or a 63.21% chance that a wait ends within 0.4 minute. This numerical result is independently calculated, not a tested Zoho response.

The key distinction is that FALSE gives a density per unit of time, whereas TRUE gives the probability that the wait is no longer than x. The density can legitimately exceed 1 when measured in small units; it is not a percentage. Both modes share the same rate parameter lambda, which has reciprocal units of x (for example, events/minute if x is measured in minutes). The mathematical average waiting time is 1/lambda, not lambda.

EXPONDIST(x; lambda; mode)

Zoho displays no optional bracket around any argument; no omitted-argument default is documented. Do not omit mode and assume Excel or Sheets will fill it in. The documentation says lambda must be greater than zero, while its error summary says a negative lambda produces #NUM!. This discrepancy does not prove what a native Zoho workbook does when lambda equals exactly zero: treat the zero-rate boundary as prohibited by the parameter description and test the app’s specific error if needed. The same error section says negative x causes #NUM!. Z1

Mathematically for x≥0,lambda>0, the waiting-time distribution has f(x)=lambda·exp(−lambda·x) and F(x)=1−exp(−lambda·x). This model assumes a stable event rate and independent exponentially distributed intervals. If arrivals cluster, rates shift over the day, or recorded times are rounded, first inspect the data; otherwise the confidence implied by the formula can be misleading.

Suppose a fictional queue receives events at a constant modelled rate of 2.5 events per minute, hence average wait 1/2.5=0.4 minute. Put labels in A1:C1: Wait (min), Rate (/min) and PDF; label D1 CDF. Fill A2:A5 with 0.2, 0.4, 0.8 and 1.5; put 2.5 in B2:B5. Enter =EXPONDIST(A2;B2;FALSE) in C2, =EXPONDIST(A2;B2;TRUE) in D2, then fill down.

The predicted CDF increases from about 39.35% at 0.2 minute to 97.65% at 1.5 minutes. It is not the chance of an event occurring at precisely those continuous-valued times. Use FALSE when plotting a probability density curve and TRUE when answering a deadline question. Because the density carries reciprocal units, do not compare density numbers directly to percentages.

Independent mathematical cross-check: at 0.4 minute, =1-EXP(-2.5*0.4) should predict 0.632120558829. At the same input, =2.5*EXP(-2.5*0.4) predicts density 0.919698602929. These are independently derived cross-check formulas using a separate mathematical expression; their execution and parsing inside Zoho remain untested.

For the modelled chance that the event happens after 0.4 minute but by 1.5 minutes, subtract cumulative probabilities: =EXPONDIST(1.5;2.5;TRUE)-EXPONDIST(0.4;2.5;TRUE). Independent expected answer: 0.344361695315 (34.44%). Subtracting densities instead would be an error; differences between CDF values, not PDF values, represent interval probabilities.

For the chance a customer waits more than 0.8 minute, the survival probability is 1−F(0.8); worksheet proposal: =1-EXPONDIST(0.8;2.5;TRUE) ≈ 0.135335283237, or 13.53%. Because the model is memoryless, the mathematical conditional probability of an additional wait over 0.8 minute is the same after a positive amount of waiting as at the start. That is a property of the exponential model, not a universal queue fact.

If a planner wants the 90th-percentile wait, the theoretical inverse formula is -LN(1-0.9)/2.5 ≈ 0.921034037197 minutes. This uses the mathematical exponential inverse and ordinary spreadsheet arithmetic as a proposed cross-check, not a documented Zoho EXPONDIST inverse function. It matters operationally because a mean wait of 0.4 minute does not mean that 90% of customers wait 0.4 minute or less.

When modelling equipment repairs or service interruptions, inspect whether the failure rate is reasonably constant: a Weibull model (WEIBULL) can represent increasing or decreasing hazard when data justify it. For count-of-events questions in a fixed interval, use a count model such as Zoho’s documented POISSON function rather than a waiting-time density. Those are distinct questions even when they originate from a Poisson-process assumption.

• #NUM! and invalid rates: Zoho lists x<0 or lambda<0 in its error summary, while requiring lambda>0 in the argument description. Correct a negative input; do not promise a specific native response to lambda=0 without testing.
• #VALUE!, #NAME! or #REF!: The official help provides general invalid-type, misspelled-function and broken-reference meanings. Check that input cells contain numbers, the formula name is spelled EXPONDIST, and copied cell references still exist; Zoho may display error markers differently by locale.
• Density above one: Not an error. =EXPONDIST(0;2.5;FALSE) independently evaluates to 2.5 per minute, a density, whereas the CDF at zero is 0.
• Unrealistic results: Confirm that x and the inverse of lambda share units. A rate of 2.5 per hour applied to x in minutes will be off by a factor of 60.
• Very large lambda*x: The CDF may display exactly 1 at ordinary cell precision. Display precision and software limits are not specified by the official function article, so do not claim a particular threshold.
• Blank, text and fractional inputs: x may be fractional by design; error reporting for blank/text inputs is generic in the Help article. Do not invent additional coercion rules. Validate the real sheet with trial data before treating any such edge behavior as documented.

Zoho’s documented formula uses EXPONDIST(x;lambda;mode) and semicolon separators. Microsoft’s current documented EXPON.DIST(x,lambda,cumulative) performs corresponding density/CDF calculations in Excel, and the legacy EXPONDIST name is retained by Excel for compatibility. This is a function-identity comparison, not a promise of identical native numeric tolerances, treatment of invalid inputs or automatic translation after import. Zoho EXPONDIST · Microsoft EXPON.DIST. The exact default mode is not stated for Zoho; specify TRUE or FALSE.

The WEIBULL function generalizes shape-dependent reliability models; at shape one, its mathematics matches an exponential waiting-time distribution with rate 1/scale. The POISSON function concerns counts rather than waiting times; NORMDIST concerns a normal distribution on both sides of its mean. All three links are official Zoho Help references, not assurances that the corresponding pages exist on Spreadsheet-Tutorials.

Zoho Sheet evidence: This guide covers the English-language Zoho Sheet function documented in the linked official Zoho Help article, inspected 13 October 2026 (UTC). Zoho describes Sheet as an online spreadsheet product and publishes function reference pages without always specifying a function’s first supported release, rollout cohort, plan, device, mobile app edition, numerical precision guarantees or offline calculation support. Accordingly, none of those compatibility details is asserted here. Check the target account and client before claiming parity across web, Windows, macOS, Android, iOS or iPadOS. The Help knowledge base currently lists those client sections, but their existence does not establish function-level equivalence. Zoho Function Catalogue · Zoho Product Help.

Formula delimiters: The English reference writes arguments separated by semicolons (;), as do the examples here. Zoho’s workbook settings let the author change locale, decimal separator and digit grouping, and changes are shared with collaborators. Confirm parsing with the workbook actually used; do not assume formulas copied from comma-delimited Excel examples parse unchanged. Zoho Locale Settings. Dates and workbook numeric displays can also vary by locale.

Validation classification: OFFICIAL_DOCUMENTATION_RESEARCH establishes the vendor’s published names, argument order, stated modes and documented errors; INDEPENDENT_CALCULATION establishes the mathematical expected results on this page; NATIVE_ZOHO_EXECUTION_NOT_PERFORMED means no Zoho workbook/account was used to execute or screenshot these examples. A mathematical identity is not evidence of undocumented coercion or of how a particular Zoho release rounds or displays a cell.

Is this a native Zoho Sheet formula? The function name and documented signature come from official Zoho Help. The example results are independently calculated predictions; they have not been run in a Zoho session.

Can I paste the Excel version of this formula? Compare both the function name and required argument count. The compatibility paragraph below gives an evidence-based Excel distinction, and the actual workbook’s syntax and separators must be checked.

Why does an answer display as 0 or 1? Probabilities may be close to a boundary, or the cell’s number format may be rounding away significant digits. Increase displayed decimal places, verify the data scale and use a mathematically suitable model; do not equate displayed rounding with proof of exact 0 or 1.

Where do these examples come from? The worksheet inputs are invented, openly disclosed practice datasets. The outputs come from independent SciPy calculations and mathematical formulas—not from the illustrative, potentially different, private input cells in Zoho’s official screenshots or embedded demo.

• Z1 Official Zoho Sheet documentation for this function, inspected 13 October 2026: purpose, syntax, argument descriptions, examples and vendor error entries.
• [Z2] Zoho Sheet statistical functions catalogue, inspected 13 October 2026: placement in its statistical reference; catalogue page is not a native execution log.
• [Z3] Zoho Sheet spreadsheet locale and calculation settings, inspected 13 October 2026: workbook locale and separators.
• M1 Microsoft Support documentation for the named Excel counterpart, inspected 13 October 2026: Excel-specific comparison only, not proof of Zoho behaviour.