Checklists that come back as a report
Most inspection tooling stops at collecting the answers, leaving somebody to assemble the findings into something a client will read. On Faldaro the same submission that captured the visit produces the score, the PDF and the paper trail.
-
Checklists that branch
A roof inspection and a kitchen inspection ask different questions. Conditional logic shows only the section that applies, so an inspector answers what matters and nothing else — one form, not eleven near-identical PDFs.
-
Scores the field cannot fudge
Weighted items, defect counts, a pass threshold — all calculated on the server from the submitted answers. The device shows the result; it does not decide it, and it has no way to send one of its own.
-
A report, generated
A document template turns the finished inspection into a PDF: findings, photos, the score and the sign-off, laid out the same way every time. Generate it on the closing transition and email it in the same step.
-
Evidence that holds up later
Photos stay attached to the submission that captured them, and the audit log is append-only — so when a finding is challenged six months on, who inspected what and when is a matter of record, not recollection.
Built from the same parts as everything else: the builder for the checklist, documents for the report and workflows for what happens when something fails.
Questions
Inspections on Faldaro, plainly
Can an inspector attach photos from a phone?
Yes. Add a file field and the form accepts photos — including on a public link, where the file field is itself the opt-in. Uploads are stored against the submission and served as attachments only, never rendered back into the page.
How is a pass or fail decided?
By your formulas, evaluated on the server on every save. A score derived from the answers cannot be edited in the browser, because the engine recomputes it from the submitted data rather than trusting a number the page sent.
What if the checklist changes next quarter?
Edit the form and publish a new version. Every inspection already filed keeps the version it was filled against, so last quarter’s reports still say exactly what they said — and you can run test cases before publishing to see what the change would move.
Put your checklist in a browser
Build the form, add the scoring rule, design the report once — and every visit after that files itself.
No card required.