A maintenance decision can become difficult to reconstruct when the first estimate, a revised scope and a final invoice all circulate as separate messages. The owner may remember approving one amount while the local contact works from another version. The problem is not solved by keeping every attachment if no one can tell which document authorized the work.
This Atlanta edition guide provides a revision record for a small rental owner. It covers document organization and approval control, not the technical adequacy of a repair or the legal obligations attached to a property. The worked example is fictional. Local requirements, resident communications and the appropriate response to an urgent problem need their own review.
Keep one work request through every revision
Assign a stable reference to the underlying problem. The reference should identify the property and unit where relevant, the reported issue and the date it entered your process. Use that reference when attaching each estimate, approval and invoice. A new quote version should not automatically create an unrelated repair request.
Separate the reported problem from the proposed solution. For example, a resident’s description of an issue is evidence of what was reported, while the vendor’s proposed work is a response that may change after inspection. Do not rewrite the original report to make it match the final solution. Retaining both makes the decision history easier to follow.
Also separate a request for information from authorization to proceed. Asking a vendor to explain an alternative or provide a price does not itself document approval of the alternative. Use an explicit status and an identifiable response so that a later reviewer can see what action was actually authorized.
Give each estimate a version and a date
Label the first estimate Version 1, the next Version 2 and so on in your own record. Retain the vendor’s original identifiers as well. The internal version label makes the sequence clear even if the vendor sends several attachments with the same filename.
For every new version, record what changed. Identify additions, removals, quantity changes, price changes and scheduling changes separately. A lower total may reflect less work rather than a lower price for the same work. A higher total may include a newly identified item that requires its own review.
Keep the original documents intact and add your explanation alongside them. Do not edit a vendor’s estimate in a way that makes your notes look like the vendor’s terms. A simple revision summary can point to the relevant pages or line items while preserving the source material.
| Version | Scope change | Selected amount | Status | Evidence |
|---|---|---|---|---|
| Version 1 | Original proposed work | Record quoted amount | Review, approved or superseded | Original estimate and decision |
| Version 2 | Identify additions and removals | Record revised amount | Separate decision required | Revised estimate and explanation |
| Version 3 | Identify further changes | Record current amount | Current approved scope if confirmed | Final authorization record |
Make the approval refer to a specific version
Record the person approving, the version being approved, the amount and any condition attached to the decision. If only certain line items are approved, identify them explicitly. A message saying proceed can be hard to interpret when it appears below several conflicting documents.
Clarify who is allowed to approve changes in your operating process. If an owner delegates a limited decision to a local contact, document the scope of that delegation in a form appropriate to the arrangement. This guide does not establish legal authority or a universal spending limit. It helps you make your own intended process understandable.
Where approval depends on another piece of evidence, preserve that condition. For example, a proposed replacement may remain under review until the vendor supplies the requested description. Do not move the record to fully approved simply because someone expressed a general preference for the replacement.
Use a fictional sequence to test the arithmetic
Assume Version 1 contains selected work totaling $600. Version 2 adds a $180 item, making its selected total $780. Version 3 removes a $120 item from that revised scope and adds a different $90 item. Its selected total is therefore $750. These invented amounts illustrate revision arithmetic and are not Atlanta repair estimates.
If Version 3 is the authorized scope, do not add all three version totals together. The $600, $780 and $750 figures describe successive versions of one proposed job in this exercise. Their sum would not represent an authorized total. The register should show which earlier version has been superseded.
Now suppose $200 has already been paid against the authorized $750 amount. The remaining amount under these limited assumptions is $550. Record the earlier payment reference and its treatment in the actual agreement. The calculation does not establish that a particular payment is due or that the work has been completed.
Finally, suppose a later invoice is $790. The difference from the selected authorized amount is $40. Mark that difference for explanation rather than automatically adding it to an approved bill. It could represent a documented change, an error or an item treated differently in the source documents. The arithmetic identifies the question; it does not answer it.
Track schedule changes as well as price changes
A revision can change the order or timing of work without changing the total. Record any new appointment, dependency or interruption described by the provider. Identify which household or property arrangements need updating because of that change.
Keep resident communication records separate from internal approval notes, while linking both to the work request where appropriate. Share the information needed for the relevant purpose and avoid exposing unrelated financial or personal material. A vendor may need access instructions without needing the owner’s full financial record.
Do not let a routine approval worksheet delay the appropriate response to an urgent situation. Establish how urgent issues are escalated through the relevant qualified contacts and applicable requirements. The revision register records decisions; it does not diagnose hazards or determine whether waiting for an ordinary approval cycle is appropriate.
Make partial approval visible
When only part of a proposal is approved, split the record into clearly identified approved and unresolved items. Keep their totals separate. A single status label applied to the whole attachment can mislead someone into thinking that every line is authorized.
Ask the vendor to confirm the scope they understand they are being asked to perform. Retain that response with the approved version. If the vendor says the approved subset cannot be performed independently, return that question to the decision maker rather than assuming that a partial approval will work in practice.
When the unresolved part is decided later, record a new authorization that connects it to the existing request. This preserves the sequence without forcing the reader to infer that a later payment must have approved an earlier proposal retroactively.
Compare the final invoice with the current record
At invoice review, identify the current approved version and compare its scope with the invoice description. Match payments already made, credits and any separately documented changes. Keep the supporting evidence beside the bill so that someone else can reproduce the selected total.
If the invoice uses different terminology, ask for an explanation connecting the billed items with the approved work. A terminology difference may be harmless, but it should not require a future reviewer to guess. Record the clarification without replacing the original invoice.
Close the financial review separately from the work completion review. An invoice can match the authorized amount while a practical issue remains unresolved. Conversely, the reported work may be complete while the bill needs clarification. Separate statuses prevent one kind of completion from being mistaken for the other.
Test software with the same three versions
Use the fictional $600, $780 and $750 sequence in a software evaluation. Ask the provider to demonstrate how its current product records revised documents, partial approvals and the current authorized amount. Use test records that contain no real resident information.
Then ask an authorized second reviewer to identify the current version without help from the person who entered it. The reviewer should be able to explain the change history, the $200 prior payment and the resulting $550 balance under the exercise assumptions. If the record cannot support that explanation, identify the missing feature or process step.
Record provider statements separately from observed behavior. A demonstration may show one part of the process while an export or permission question remains unanswered. Use the Homzora software scorecard to preserve both the evidence and the limitation rather than assigning an unsupported overall pass.
Optional provider resources
Affiliate disclosure: Homzora may earn a commission through these links. You can explore TurboTenant and Buildium as candidates for your own workflow evaluation. Confirm current functionality, charges and export options directly.
No product test was performed for this article, and neither link establishes that the provider supports every approval step described. A clear existing document process may be sufficient for your needs. Return to the Atlanta edition for broader housing resources, and retain the actual technical, contractual and legal evidence separately from this operational worksheet.