Creating a Decision Log for Multifamily Capital Work

From document to ownership decision

Capital work produces more than invoices. It produces a sequence of judgments about urgency, scope, access, materials, budget and the risks of waiting. When those judgments remain scattered across email, proposals and text messages, a later reviewer can see what was spent but may not understand why the work took its final form.

A useful decision log begins with the condition being evaluated. Identify the location, date observed, available photographs, inspection findings, service history and any immediate operational concern. Separate direct observation from a vendor recommendation or an estimate. That distinction preserves the quality of the evidence without suggesting more certainty than the record supports.

Build a usable operating record

Record the alternatives that were actually considered. A temporary repair, component replacement and complete system renewal may carry different cost, access and interruption consequences. The log should explain which alternative was selected, who approved it and which assumptions influenced the choice. Rejected options need only a short, accurate explanation.

Scope changes deserve their own entry. Concealed conditions, unavailable materials, code requirements or coordination with adjacent work can change a project after it begins. Note the new information, revised price, schedule effect and authorization before the change disappears into the final invoice.

Put the finding into practice

Close the record with completion evidence. Link final photographs, permits or inspection results where applicable, warranties, invoices and unresolved follow-up. If the project was intended to address a recurring condition, schedule a later check and compare the result with the original observation.

The objective is not to turn every repair into a lengthy report. A concise log creates continuity between the physical property, the financial record and the people responsible for the next decision. Over time, it also makes patterns easier to see: repeated temporary work, scopes that routinely expand, systems nearing the end of useful service and vendors whose documentation remains complete.

Read the quarterly property-records audit →