A vendor proposes several repairs in one quote. The owner agrees to the urgent repair but asks to defer a cosmetic item and wants more information about a replacement. If the whole quote is marked approved, the budget overstates the commitment. If it is left entirely unapproved, the person coordinating the work may overlook the portion that should proceed. The useful unit of control is the individual scope line.
This Nashville edition guide describes an operational record for partial approval. It does not determine which repairs may legally be deferred, establish accounting treatment or replace a qualified assessment of condition. Safety and applicable obligations need their own review. The worksheet helps everyone see which work is proposed, authorized, completed and billed without treating those stages as interchangeable.
Break the quote into identifiable scope lines
Start with the vendor’s actual description and amounts. Assign a reference to each separately understandable task, such as inspect the reported leak, replace the identified component, or refinish the affected surface. Do not divide a bundled quote into invented prices. If the vendor has supplied one combined amount, ask for an appropriate breakdown before claiming that individual parts have known costs.
Keep the original quote as a dated attachment. Your worksheet is an index to the proposal, not a replacement document that silently changes its meaning. Record the version because later quotes may alter both the amount and the technical scope even when the filename looks similar.
Identify dependencies between tasks. A proposed finish repair might depend on resolving moisture first, while a replacement could make another line unnecessary. Ask the qualified vendor to clarify that relationship. A partial approval should not create an impractical sequence simply because the spreadsheet allows each row to be checked independently.
Make the owner decision specific
For each line, record approved, deferred, declined or awaiting clarification. Add the date, the person making the decision and the exact evidence of that decision. A broad message saying proceed with essentials leaves too much interpretation unless the owner and coordinator have already identified the essential lines together.
Record any amount limit separately from the scope approval. An owner may authorize a task only up to a stated amount, or approve a quote subject to a condition. Neither statement should be shortened to approved without retaining its limitation. The person issuing instructions to the vendor needs to see the limitation at the moment of action.
Where an owner’s request conflicts with a safety concern or a possible legal obligation, escalate the concern to an appropriate person. A budget status is not permission to ignore required work. Keep the unresolved concern visible alongside the decision rather than hiding it in an email thread because the owner has not yet replied.
| Scope reference | Quoted amount | Decision | Commitment evidence |
|---|---|---|---|
| Task A | Vendor quoted amount | Approved within stated limit | Written instruction and acknowledgment |
| Task B | Vendor quoted amount | Deferred pending review | No instruction to proceed |
| Task C | Awaiting breakdown | Clarification required | Question assigned to coordinator |
| Change request | Separate proposed amount | New decision required | Link to affected original task |
Distinguish authorization from a commitment to a vendor
An owner approval and a vendor acceptance are separate events. Record when an authorized instruction is actually issued and whether the vendor confirms the scope and price. Your operational budget can then distinguish a decision waiting to be scheduled from work already committed under the relevant arrangement.
Do not assume that a deferred task remains available at the original price. Ask the vendor how separating the work affects the quote, scheduling and any shared visit charge. A proposal for three tasks completed together may not describe the cost of completing just one now and another much later.
If a vendor says the partial instruction cannot be performed as written, return to the owner with the revised facts. Preserve the original authorization, but mark that a new decision is needed. Quietly expanding the task to make the visit convenient undermines both the budget and the approval record.
Use a hypothetical example to reconcile the amounts
Consider a fictional proposal with three separately priced tasks: $480 for Task A, $220 for Task B and $300 for Task C. The full proposal totals $1,000. The owner approves A and B, so the approved amount is $700, while $300 remains unapproved. These invented figures do not describe Nashville repair prices.
Suppose the vendor accepts A at $480 but explains that B would cost $260 when separated from C. Task A can remain recorded as committed at $480 if the actual arrangement supports that status. Task B now needs a decision on the revised $260 amount. The original $220 approval should not be silently stretched to cover the change.
If the owner approves the revised B and the vendor accepts it, the selected committed total becomes $740. The increase over the earlier approved total is $40. The complete revised proposal, if C remained $300, would total $1,040, but that does not make $1,040 the authorized commitment. The unapproved line remains separate.
Now assume A is completed and billed at $480 while B has not yet been performed. The operational register shows $480 billed, $260 committed but not billed, and $300 still unapproved. Adding billed and committed unbilled amounts gives $740. Adding the invoice again to the original $740 commitment would incorrectly produce $1,220 for the same authorized work.
Issue a work instruction that cannot be misread
Name the property, unit, scope references, relevant quote version and approved limits in the vendor instruction. Explicitly identify the excluded lines when a quote contains both approved and unapproved work. A vendor should not have to infer the boundary from a forwarded email containing several conflicting comments.
Ask the vendor to acknowledge the partial scope before scheduling where the arrangement permits. Preserve that acknowledgment with the work record. If there is a technical dependency that changes what can be done, ask for clarification rather than leaving the crew to discover the disagreement on arrival.
Keep access arrangements and resident communications linked to the work but controlled separately. An appointment confirmation does not expand the authorized scope. A resident describing another concern during the visit also does not automatically authorize additional work under the owner’s budget process. Provide a clear route for documenting and escalating new findings.
Handle discovered work as a change request
Create a new change reference when the vendor finds additional work. Connect it to the original task and retain the explanation, revised amount and any supporting evidence. Distinguish additional work from a correction to the original description so that the owner can understand why the budget changed.
Record whether existing work can continue while the change is reviewed. This is a technical and scheduling question for the relevant parties, not something the worksheet can decide. If pausing creates a condition that needs immediate attention, escalate promptly through the appropriate process rather than waiting for a routine budget meeting.
Do not erase a declined change. Retain its status and reason, along with any follow up necessary to address the underlying issue. A declined price does not necessarily mean the reported condition disappeared. The record should support a later reader in distinguishing a commercial decision from confirmation that the property concern was resolved.
Match the invoice to the approved lines
When the invoice arrives, compare its scope references and amounts with the current authorization and completion evidence. If it includes an unapproved line, hold that difference for clarification according to your established process. Do not treat a matching grand total as proof that the invoice contains the correct tasks.
Where the vendor combines approved lines into one description, request enough detail to connect the charge to the work. Preserve the clarification with the invoice. The purpose is not to create administrative work for its own sake, but to avoid paying a plausible amount against the wrong combination of repairs.
Close each line only when the relevant completion, invoice and payment checks are satisfied. A paid invoice and a technically completed repair answer different questions. If a resident reports that the problem remains, link the new observation to the original task rather than reopening every unrelated line in the proposal.
Keep a deferred scope review separate from completion
Give every deferred line a review trigger that reflects the unresolved decision. That trigger might be receipt of a technical explanation, a revised quote or a specified owner discussion. A general deferred status can otherwise remain indefinitely even when the circumstances that justified it have changed.
At that review, ask whether the original proposal is still relevant. The condition may have changed, a different repair may have resolved part of it, or the vendor may need to reassess the scope. Retain the earlier decision for history while marking which evidence supports the current plan. A budget carried forward from an old quote should remain labeled as an earlier proposal until its basis is confirmed.
Test software using the partial approval exercise
Use fictional data in a demonstration. Ask the provider to show the $1,000 proposal, the initial $700 approval, the $40 revision and the final $740 authorized total without losing the $300 deferred line. Then ask for a report that separates billed work from committed unbilled work. Record what was actually demonstrated.
Affiliate disclosure: Homzora may earn a commission through these links. Buildium and Rentec Direct are possible products to evaluate against your own requirements. No feature support, current price or successful product test is asserted here.
Use the software scorecard to record evidence, limitations and unanswered questions. Return to the Nashville edition for related resources. A successful operational record leaves the next reviewer able to explain the authorized work, the remaining exposure and the next decision without reconstructing the entire email history.