Checking your numbers: what Clavoz does and doesn't guarantee

What Clavoz does for you — arithmetic, templates, records — and what stays yours: the site visit, the quantities, the code, the permit, the price and the promise you make.

Draft for legal review.

Checking your numbers: what Clavoz does and doesn't guarantee

Clavoz is a fast, honest tool for turning a site visit into a proposal. It is not the
licensed contractor, and it does not take over the parts of the job that belong to you.
This page is the plain-language version of that boundary: what the software checks, what it
only helps you check, and what has always been yours.

This guide explains how the software behaves. It is not legal advice, and it does not
change the Terms of Service.

What Clavoz does for you

  • The arithmetic. Subtotals, tax, contingency, margin and markup, per-line and per-quote
    totals. It does this consistently, which is more than can be said for a spreadsheet at
    6pm.
  • The records. Every quote keeps its line items, its costs, its photographs, its
    signatures and its timestamps, so "what did I agree to, and when" has an answer.
  • The paperwork you asked for. Proposals, PDFs, material takeoffs, contract attachments
    and your own terms — rendered from what you entered.
  • The second look. Flags on things worth re-checking (a quantity to verify, a price to
    set, a margin below your target) and a section for the carrier's own notes, kept separate
    from your scope.

What stays yours

Everything that requires judgement about a real building and a real promise:

  • The site visit and the measurements. A takeoff from photographs, a walkthrough
    transcript or a carrier's PDF is an input, not a verification. Somebody has to have looked
    at the thing.
  • The quantities and the scope. The app will happily price a wrong number without a
    complaint.
  • Code, permits, licensing and inspections. No code lookup, no permit-fee database, no
    jurisdiction rules. Whether the work is legal, permitted and within your licence is your
    question to answer, every time.
  • The prices you charge and the promises you make. Including lead times, warranties,
    start dates and anything you typed into a line item's description.
  • Safety and execution. How the work is done on site is not in this software.
  • Your client relationship. Who you tell, when you tell them, and what you agreed
    verbally outside the app.
  • Tax and accounting. Clavoz shows a tax line you configure; it is not your tax advice
    and it does not file anything.

Where the app will disagree with you — and why that is on purpose

The app nudges; it does not decide. A margin under your target is flagged rather than
blocked, a parsed line is marked Verify Qty rather than trusted, and a price it could not
match from your catalog is marked Set Price rather than guessed. Those flags are the
software saying "look at this one" — they are not a guarantee that everything un-flagged is
right, and they never carry your approval for you.

Two habits that make the flags worth having:

  • Read the summaries before you send. A wrong unit, a missing line or a doubled one is
    easier to catch in a short proposal than in a long takeoff.
  • Keep the carrier's notes where they belong. They are kept separate from your scope so
    that a carrier's assumption never quietly becomes your promise.

Signatures, and who is bound by what

A signed proposal is between you and your client. Clavoz stores the signature, the name
typed, the timestamp and the version of the terms the client agreed to — the record of the
moment, not a party to it. When a signature happens, the app also stops being a draft: jobs,
draws and payment tracking hang off that one act, so know what you are sending before you
send it.

If a guide and the app ever disagree

Tell us. The guides live in the repository beside the code, and a guide that describes a
different app is treated as a bug rather than a wording preference — that is the whole point
of keeping them there.

Found something out of date? The guides live in the repository's docs/ directory — fixing the guide is part of fixing the feature.