Skip to content

Main content

Construction Pay Item Quantity Variance

Compare explicitly recorded contract, installed and paid quantities in one common pay-item unit without determining payment entitlement.

Loading tool…

Description

Compare supplied installed, contracted and paid quantities.

Construction records combine revisions, dates, dimensions, rental periods, claims and financial balances. Revision numbers need not be consecutive, calendar offsets differ from business days, and recoverable length can depend on a strict cutoff. A supplied approval or readiness label is a record assertion rather than an engineering inspection or contractual determination.

Compare supplied installed, contracted and paid quantities.

When to use this tool

Use Construction Pay Item Quantity Variance when you already have contractQuantity, installedQuantity, paidQuantity and need to compare supplied installed, contracted and paid quantities.

How to use the tool and how it works

  1. Enter contractQuantity, installedQuantity, paidQuantity. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read installedMinusContract, unpaidInstalledQuantity. Use the output convention below.

Require all quantities>=0; return installed-contract and installed-paid.1

Input fieldMeaning and unitsAccepted input
contractQuantityContract QuantityRequired. Finite number; minimum 0.
installedQuantityInstalled QuantityRequired. Finite number; minimum 0.
paidQuantityPaid QuantityRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
installedMinusContractInstalled Minus ContractRequired. Finite number.
unpaidInstalledQuantityUnpaid Installed QuantityRequired. Finite number.
json
{
  "input": {
    "contractQuantity": 100,
    "installedQuantity": 110,
    "paidQuantity": 80
  },
  "output": {
    "installedMinusContract": 10,
    "unpaidInstalledQuantity": 30
  }
}

Limitations and assumptions

  • Signed discrepancies are retained. No completed work, payment, overrun, claim or contract interpretation is established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check controlled drawings, site measurements, schedules, approvals and the complete contract. Use the appropriate engineering assessment and actual billing or claim terms when a local scalar calculation or date comparison cannot establish suitability or entitlement.

References

  1. Calculation and input contract: construction-management/construction-pay-item-quantity-variance — tool.io

Similar or alternative tools