Fee quoting is the rule set that turns the characteristics of an assignment into a number before the work is accepted. Property type sets a base, complexity and geography adjust it, and a rush request multiplies the result. A quoting system applies those layers in a fixed order and records which inputs produced the figure. It prices administration only. No input is a value, a target, or a contract price, and the fee never moves with the conclusion.
What breaks when fees are quoted from memory
The same assignment gets two different quotes
Two people quote the same property on the same day and the numbers differ meaningfully. Neither is wrong by any written rule, because there is none. The client notices the inconsistency before the firm does.
Distance is estimated by whoever knows the county
A property forty minutes out gets quoted at the same fee as one across town, because whoever took the call did not recognize the road. Most of a working day disappears into a fee set for a different job.
Complexity turns up at the inspection
The order said single family. The parcel is eleven acres with a second dwelling, a barn, a private well, and no comparable sale within miles. The fee was agreed a week ago, and the conversation about changing it happens in a driveway.
Rush is a favor rather than a rate
A client asks for a two day turn and gets it. Whether that carried a premium depended on who answered the phone and how the week looked. The precedent outlives the file, and the next request assumes the same answer.
Nobody can reconstruct why a fee was what it was
Months later a client asks why this assignment cost more than the last one nearby. The quote survives as a number in an email, and the reasoning existed only in a phone call.
Fee matrix logic and the order the layers resolve in
Order of precedence is what most firms skip, and it is what makes a quote reproducible. Each layer runs on the result of the one above. We publish the structure; the rates and bands stay yours.
| Order | Layer | What it reads | How it applies | What can override it |
|---|---|---|---|---|
| 1 | Client agreement | Client record and any contracted fee schedule | Selects the schedule everything below runs against | Nothing. Where an agreement fixes a fee, calculation stops |
| 2 | Base by product | Property type with form or report type: interior single family, exterior only, condominium, two to four unit, manufactured, land, narrative | Sets the base. Companion products such as a rent schedule or operating income statement are separate lines | Client agreement only |
| 3 | Complexity tier | Conditions that expand scope of work: acreage above a band, legal non-conforming or mixed use, accessory dwelling, atypical improvements, thin comparable availability, proposed construction, private utilities | Additive. Tiers stack, and each one that fires is recorded with its trigger | A named person, with a reason code |
| 4 | Geographic band | Route distance or drive time from the nominated origin to the geocoded subject, plus a coverage flag | Additive on the subtotal. Outside the service area also raises a geographic competence review | As above |
| 5 | Market data flag | The county or market, flagged where comparable data costs more, including non-disclosure markets | Additive, once per assignment | As above |
| 6 | Rush | Requested delivery date against the standard interval for that product | Multiplicative on the subtotal of layers two through five | Declining the rush; the multiplier is not talked down without a reason |
| 7 | Floor and ceiling check | The computed total against a product floor and an approval ceiling | Changes nothing. Routes the quote for approval when it falls outside the band | The approver’s decision, recorded |
| 8 | Discretionary override | A person with authority to set a different number | Replaces the total, keeping the original beside it with a reason code | Nothing. Last by design, so an exception stays visible |
How the quote engine gets assembled
Address in, geocode and drive band out
The subject is geocoded at entry and matched to a parcel record where county data supports it. Bands run on route distance or drive time from the origin you nominate, because a straight line across a river produces a fee that will not cover the day.
Complexity captured as flags, not prose
Every trigger is a field with a defined condition behind it. That makes a tier reproducible, and it lets you look back across a year to see which triggers fire, so the schedule gets revised on evidence rather than impression.
A re-quote is a new version, not an edit
When a scope change surfaces, the fee recalculates as a new version against the same order. The prior quote keeps its date and its reason. That history is what an addendum to the engagement letter is written from.
The accepted fee reaches the invoice unchanged
We have built this end to end: acceptance of the quote raises the invoice, fee lines and complexity reasons already on it. The invoice and the quote cannot disagree because there is only one number.
Administration only, by design
The engine handles pricing, approval routing, and billing. It has no view of the valuation and no path to one. Nothing in it influences, suggests, or comments on a value conclusion, and no part of the calculation is aware of what that conclusion turns out to be.
What the fee engine talks to
- QuickBooks automation for appraisal invoicing — The accepted quote becomes the invoice with its fee lines intact.
- DocuSign workflow automation — The agreed fee populates the engagement letter, and a re-quote produces the addendum.
- workflow automation services — Quotes outside the approval band route to a named approver first.
Is this a fit for your business?
A good fit when
- More than one person in your office quotes fees
- Drive time across your service area changes the economics
- Complexity is discovered late often enough to be a running argument
- You want to know which complexity conditions actually occur
Probably not a fit when
- Every assignment comes at a fee the client states and you never quote
- You want a benchmark of what other firms charge
- You need advice on customary and reasonable fee expectations
What to have ready
- Your current fee schedule, including the part that exists only in your head
- The complexity conditions you already charge for, in your own words
- Twenty recent assignments with the fee charged and enough detail to explain each
Questions we get asked
Does anything in the fee engine see the value?
No. The engine reads property type, form, complexity flags, geography, market, and the requested delivery date. It does not read a contract price, an estimated value, a loan amount, or the appraiser’s conclusion, and it has no route to any of them. The fee is fixed before development begins and does not change with what the appraisal finds.
We negotiate every fee. Does a matrix still help?
It helps more, not less. The matrix gives the negotiation a starting number anyone in the office would have produced, and the override step records what you agreed and why. Without it you are guessing and then defending the guess.
How does this work for AMC orders where the fee is already stated?
The engine runs anyway and shows the computed figure beside the stated one. Nobody has to act on the difference. But when an order arrives well below what your schedule would produce, that is worth seeing before acceptance.
Where do the bands and multipliers come from?
From your own history. We build the structure, then work through a year of completed assignments to find where the distance bands break, which complexity conditions recur, and what your standard interval per product really is.
Related
- appraisal invoicing and payment collection
- AMC orders compared with direct lender orders
- QuickBooks automation services for professional firms
- workflow automation for appraisal firms
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.