Repair negotiations create a trail of inspection findings, estimates, approvals, invoices, receipts, credits, and amendments. Estate files are especially vulnerable to confusion when an executor, buyer, contractor, and closing agent each hold a different version. A reconciliation identifies which record supports each amount and obligation. It does not determine whether work was adequate, whether a credit is enforceable, or whether a party has a remedy. Those decisions belong with the authorized professional.
Define the repair question
Specify whether the review concerns completion, cost allocation, a credit, a holdback, a warranty, or a closing condition. Identify property, contract version, inspection date, and closing date. A single request to “check repairs” mixes factual and legal questions. Separate the requested output into document inventory, amount comparison, completion evidence, and open questions so the result is useful to the person deciding what happens next.
Inventory the repair trail
Collect inspection reports, repair amendments, estimates, work orders, invoices, receipts, permits, photos, contractor correspondence, final walkthrough notes, and closing statements. Record source, date, provider, property area, amount, and signature status. Keep estimates distinct from invoices and invoices distinct from proof of payment. A folder full of attachments is not a completed record unless the relationships between them are documented.
Match each item to a finding
Create a finding identifier for every inspection or disclosure issue. Link the proposed repair, approved scope, invoice, payment, and credit to that identifier. If an invoice combines several jobs, split the review into line items without changing the invoice. Record items that have no corresponding finding and findings with no later evidence. This method exposes scope drift without pretending that an invoice proves the work addressed the original condition.
Compare amounts and dates
Record estimate, approved amount, invoice total, tax, deposit, payment, credit, holdback, and balance with source dates. Put these beside amendment deadlines and closing milestones. Differences can result from scope changes, tax, rush work, or duplicate billing. Describe the arithmetic and preserve the source. Do not label the difference unauthorized or reasonable unless the responsible professional has reviewed the governing documents and facts.
Check amendment language
Extract who must perform the work, by when, to what standard, using which provider, and what evidence must be supplied. Note whether the amendment changes price, credit, possession, closing, or release terms. A later email may clarify logistics but may not amend the contract. Capture the email and flag the relationship. The review should show the wording and sequence so the professional can assess its significance.
Verify completion evidence
List permits, paid receipts, photographs, warranties, inspection sign-offs, and walkthrough notes separately. Record what each item actually demonstrates. A photograph can show an installed fixture without showing code approval; a receipt can show payment without showing quality or completion. Mark unsupported assertions as assertions. This protects the handoff from turning a contractor’s statement into an unexamined completion conclusion.
Review credits and holdbacks
Tie each credit or holdback to a clause, amendment, invoice, or closing statement line. Record payer, recipient, timing, and release condition. Compare the stated amount with the settlement record and flag rounding or allocation differences. Keep post-closing obligations visible. A credit on a statement does not prove that the underlying work was accepted, and a holdback line does not establish who controls release.
Create an exception log
Use issue, source page, finding, compared value, missing evidence, deadline, and owner fields. Common exceptions include a repair invoice exceeding the approved amount, an invoice for a different address, an absent permit, a credit with no amendment, an unsigned change, or a payment with no receipt. Distinguish not found from not provided. A clear status tells the next person whether to search, request, compare, or decide.
Handoff and privacy
Deliver the source inventory, finding crosswalk, amount ledger, timeline, completion evidence register, credit crosswalk, and exceptions. Keep personal and banking details in the controlled matter repository. Preserve original filenames and retrieval dates. If a corrected invoice arrives, add a version note rather than deleting the old one. State the limits of the review and route legal, construction, and tax questions to the appropriate professionals.
Recheck after closing changes
Repeat the affected rows when the inspection changes, repair scope expands, closing moves, a new invoice arrives, or the parties sign an amendment. Confirm that the final contract version and settlement statement are the ones being compared. A reliable reconciliation remains useful after handoff because it preserves the evidence sequence and makes clear which amounts are documented, which are disputed, and which still require judgment.
Include a final source checklist for every repair line: original finding, approved scope, provider record, payment record, completion evidence, and contract treatment. A blank field is more informative than a guessed entry. When the matter is transferred, the next reviewer can request precisely the absent item and avoid duplicating searches. This also keeps a corrected invoice or new walkthrough from being mistaken for evidence that existed at signing.
Preserve the party’s stated position when a repair is disputed. Record whether the concern is scope, timing, amount, workmanship, access, or documentation, then attach the message or report that supports the description. Avoid converting a negotiation position into a factual status. When the parties later sign a new amendment, compare only the affected findings and retain the earlier analysis so the file shows how the obligation changed.