Auto-Calculating Fields: What They Can and Can't Do
Where they genuinely help
Simple arithmetic, quantity times unit price, or a running total across several line items, is exactly what auto-calculating fields are built for, and using them removes a common source of human error in manually totaled documents.
They're particularly valuable on documents that get filled out repeatedly by different people, since a formula doesn't get tired or make an arithmetic slip the way a person filling out their fortieth expense report of the month might.
Where they tend to fall short
Conditional calculations, different formulas depending on which option someone selects elsewhere on the form, are harder to set up reliably and are worth testing extensively before trusting them in a live document.
Formulas also can't validate that the underlying inputs make sense. A calculated total will faithfully add up two numbers even if one of them was clearly mistyped, so calculation isn't a substitute for input validation.
A sensible approach to using them
Use auto-calculation for the parts of a document with a genuinely fixed formula, and leave more judgment-dependent totals as manually entered fields, which keeps the document predictable rather than trying to force every number into a formula.
Always test a calculated field with edge cases, zero values, unusually large numbers, before sending a template out widely, since these are exactly the inputs most likely to expose a formula that was built for the common case only.
Want to try this yourself? Explore the product →