How Docuivo tests its tools
We test the same user-facing workflows people rely on: entering data, checking calculations, generating documents, exporting files and verifying that browser-local editing behaves as described.
Document-generator checks
For each document tool we test required and optional fields, line-item totals, tax and discount behavior where present, numbering fields, long text, empty states and the exported PDF. We compare the final output with the values shown in the editor.
Calculator checks
We verify calculators against independently worked examples. Margin uses gross profit divided by selling price; markup uses gross profit divided by cost; rate calculations are checked against the stated assumptions. Edge cases such as zero cost or zero billable hours are reviewed separately.
Privacy checks
Docuivo is designed so working document information remains in the browser. We review the application flow to ensure document-entry fields do not require an account or intentional server upload. Browser-local storage behavior is documented when used.
Cross-device review
We review core pages and editors at desktop and mobile widths, with attention to form usability, readable previews, navigation, export controls and accidental horizontal overflow.
Editorial verification
Guide examples are checked against the tool behavior and formulas they describe. Legal, tax and accounting statements that vary by jurisdiction are qualified rather than treated as universal requirements.
See our Docuivo Lab for reproducible worked examples and our editorial policy for publishing standards.