Systems and records
Property management maintenance approval data: linking report, approval and invoice
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Connect the three documents through the work order: the tenant's report opens it, the owner's approval (or the management agreement's not-to-exceed authority) is attached to the estimate before dispatch, and the vendor's invoice is matched back to that work order. Then check the outcome against evidence such as invoice lines, photos and the absence of a repeat request, not the status field, and privacy-review the packet before any AI use.
Provenance trail
Property management
Key takeaways
- The work order id is the spine: every report, estimate, approval, invoice and follow-up should carry it.
- Approval is a record with an approver, a time, a scope and a ceiling, not a status value; when it came from standing authority, say which clause.
- A completed status is a claim; the invoice lines, photos and the absence of a repeat request are the evidence.
- Operating rules such as entry notice, emergency timeframes and lead-safe work change what the right decision was, so record which rule applied.
- Strip tenant identities, interior photos and accommodation requests before records leave the company; keep the decision structure intact.
How do you connect tenant reports, owner approvals and repair invoices into tasks?
Use the work order as the spine and attach each document to it in the order the decision happened: the tenant's report, the triage and estimate, the approval or the standing authority that replaced it, the dispatch and entry, the vendor's invoice, and the follow-up that shows whether the problem stayed fixed. One repair becomes one task record with a starting state, evidence, a decision and a verified outcome.
Most property management systems already hold these pieces, but in different places. The tenant's report sits in the resident portal or a phone log, the owner's approval sits in an owner portal, an email or a text message, and the invoice sits in accounts payable. The linking work is mostly about finding the approval and proving which invoice belongs to which report.
The result is useful twice. Operationally, it shows where approvals stall and where vendors bill for work that did not hold. As AI training or evaluation data, it shows a model a real decision with its constraints and consequences, which a bare request text or a closed status cannot.
What does each document prove, and what can it not prove?
Each of the three documents proves one part of the story and is silent on the rest. Treat them as evidence for specific fields, not as interchangeable summaries of the repair.
| Document | Where it usually lives | What it proves | What it cannot prove |
|---|---|---|---|
| Tenant report | Resident portal request, call log, email | What the tenant observed, when, and in which unit | The cause, the severity or what was actually fixed |
| Triage note and estimate | Work order notes, vendor bid | The proposed scope and expected cost band | That anyone with authority agreed to it |
| Owner approval | Owner portal, email, text, signed estimate | Who agreed, to what scope, when and within what ceiling | That the work matched the approved scope |
| Entry and dispatch record | Work order history, notice log | When the unit was entered and on what notice | That the repair succeeded |
| Vendor invoice | Accounts payable bill linked to the work order | What the vendor says was done and charged | That the problem stayed fixed |
| Follow-up evidence | Completion photos, tenant confirmation, later requests | Whether the same problem came back | Why it came back, without a second investigation |
Where does the owner's approval authority come from?
Approval authority comes from the management agreement, and it takes one of two forms: standing authority to spend up to a not-to-exceed limit without asking, or an explicit owner approval for anything above it, with emergency exceptions defined in the same agreement. The packet has to record which form applied, because a model that learns from repairs without that field learns that managers simply dispatch.
At a glance
Where does the owner's approval authority come from
Software vendors build their guidance around this split. Buildium advises a workflow that checks the not-to-exceed limit before dispatching so the manager knows whether owner approval is needed. Its bill approval policies can be set across the account or per property, and a bill above the policy limit prompts the user to record or request approval before it is paid. AppFolio says managers can send and log work order estimates through the owner portal for owners to approve.
In practice, approvals also arrive by phone or text and never reach the system. When the only evidence is a status change to approved, record the approval as unverified rather than inferring it. A packet with a missing approval is still useful if it says so; a packet with an invented approval teaches the wrong rule.
- approval_basis: standing authority under a named clause, explicit owner approval, or emergency exception.
- approver: owner, owner's representative or manager acting under authority, as a role, not a name.
- approved_scope and ceiling: the scope text and the limit, stored as a band if the amount is sensitive.
- approved_at: timestamp, and the channel the approval came through.
- evidence_ref: pointer to the portal record, email or signed estimate.
Which entry, hazard and lead-safe rules change the right repair decision?
A generic example misses the rules that change the right decision for this unit on this day: how much notice entry needs, how fast a hazard must be corrected, whether the building's age changes who may do the work, and whether the request is really an accessibility modification. Each packet should name the rule that applied, or say none did.
In California, Civil Code section 1954 requires reasonable written notice of entry stating the date, approximate time and purpose, presumes 24 hours to be reasonable, and lets tenant and landlord agree orally to entry for agreed repairs within one week. In HUD-assisted housing, the NSPIRE standards treat life-threatening and severe deficiencies as needing correction within 24 hours, which overrides a routine wait for owner approval. Rules differ by state and program, so the packet stores the jurisdiction and program rather than assuming one rule.
Building age matters too. EPA's Renovation, Repair and Painting rule covers paid work that disturbs paint in housing built before 1978: firms must be certified and must give occupants the Renovate Right pamphlet before work starts, while minor repairs that disturb six square feet or less of paint per interior room are excepted. A drywall repair in a 1960s building and the same repair in a 2010 building are different tasks.
Some requests are not repairs at all. Under 2008 HUD and Justice Department guidance, a housing provider must permit reasonable modifications a person with a disability needs, generally at the tenant's cost. A request for grab bars or a ramp follows that process, involves sensitive information, and should be excluded from a general maintenance dataset.
Which fields does the privacy-reviewed maintenance packet hold?
Build one packet per repair with these ten fields. Each row names the source record and the privacy treatment, so the same packet can be used internally and, after review, as a dataset record. Fields marked keep are the decision structure; do not strip them in the name of privacy, or the record stops being a task.
At a glance
Which fields does the privacy-reviewed maintenance packet hold
Keep a separate review log for records you withhold. Each excluded repair gets its case id and a reason, such as an accommodation request, a dispute or a photo that could not be cleaned, but none of its content. That log is what lets a reviewer, or a later buyer of the dataset, see which kinds of repairs are missing and why, instead of mistaking a gap for a building that never had that problem.
| Field | Content | Linked source | Privacy treatment |
|---|---|---|---|
| case_id and work_order_id | Stable ids for the repair | Work order | Replace with random ids; keep the link |
| property_context | Building type, unit count band, year-built band, jurisdiction, program | Property record | Bands only; drop street address |
| tenant_report | Reported problem, time, channel, tenant's own words | Resident portal or call log | Remove names, phone numbers and unit numbers from text |
| triage | Category, severity, emergency flag, rule applied | Work order notes | Keep |
| estimate | Scope, vendor trade, cost band | Vendor bid | Vendor as trade category; cost as band |
| approval | Basis, approver role, scope, ceiling band, timestamp, evidence pointer | Owner portal, email or agreement clause | Owner as role only |
| entry_and_dispatch | Notice given, entry time, access result | Notice log, work order history | Times shifted consistently per case |
| invoice | Line items, labor and parts, match to approved scope | AP bill linked to work order | Remove vendor tax and bank details |
| photos | Before and after images | Work order attachments | Remove faces, belongings, documents and location metadata, or exclude |
| outcome_check | Repeat request within a set window, tenant confirmation, inspection result | Later work orders, notes | Keep, with window stated |
Worked case: a leaking water heater, start to finish
This case is illustrative; the property, times and counts are invented to show the method. A tenant in a 24-unit building built in 1968 reports water pooling under the water heater closet on a Tuesday evening through the resident portal. Triage marks it urgent but not an emergency because the leak is slow and contained.
A plumber inspects the next morning, at a time the tenant agreed to when the manager called back that evening, and the manager confirms the visit in writing; the plumber quotes replacement of the heater. The estimate is above the manager's standing limit in the management agreement, so the manager sends it through the owner portal. The owner approves the scope on Wednesday afternoon. The packet records approval_basis as explicit owner approval, the approver as owner, the scope as replacement with new expansion tank, and the evidence pointer to the portal record.
The replacement happens Thursday. Because the closet wall must be opened in a building that predates 1978, the triage field records the lead-safe check: the painted area to be disturbed was expected to exceed the minor-repair allowance, so a certified firm did the work. The vendor's invoice lists the heater, the expansion tank, labor and a wall patch. The patch is outside the approved scope, so the packet flags a scope variance rather than hiding it.
The outcome check looks 30 days ahead, an illustrative window: no new request from the unit, and the tenant confirmed hot water on Friday. The packet's verified outcome is resolved, with one scope variance.
How do you prove the repair actually solved the problem?
Prove it with evidence that would look different if the repair had failed: invoice lines that match the approved scope, completion photos, tenant confirmation, and no repeat request for the same problem within a stated window. The status field alone proves only that someone closed the ticket.
Here is the counterexample. In another illustrative unit, a work order for a dripping kitchen faucet shows completed. The invoice has a single line for a trip with no access, the photos are of a locked door, and the same tenant reports the same drip nine days later. A dataset that trusts the status labels this a success. The packet labels it failed attempt, with the reason, and links the repeat request as the next case.
Software can help with the matching step. Buildium describes a Bill Review Assist feature that compares bill details against attached invoices, bids and contracts on related work orders and alerts on mismatches in property, vendor, amount and service. A mismatch alert is a lead for review, not a verdict on outcome.
What should be removed before maintenance records leave the company?
Remove what identifies people and homes, and keep what explains the decision. Tenant names, phone numbers and unit numbers appear inside free text, not only in structured fields, so redaction must cover notes and messages as well. Interior photos are the hardest part: they show belongings, documents, family photos and sometimes people, and their files often carry location metadata.
Keep four questions separate. The property manager may have access to the records; that is not the same as the tenants' privacy expectations, the owners' rights in records about their buildings, or a contractual right to license the records to anyone. The management agreement and any owner instructions decide the last two, and de-identification does not settle them.
Exclude whole categories where review would not be reliable: accommodation and modification requests, records tied to disputes or legal claims, and anything involving minors or medical equipment. Record each exclusion's reason so the dataset's coverage is honest.
Can a property manager license its repair packets?
Packets assembled this way are the kind of operating record AI developers look for, because each one carries a decision, its authority and a checked outcome. Packets like these can be licensed through SourceX, whose work for the property management company covers the rights review, contract, preparation and delivery. Whether its maintenance history could qualify is answered by a brief company questionnaire with nothing uploaded, and owner rights and exclusions are settled before any record moves.
Frequently asked questions
What is a not-to-exceed limit in property management?
It is the spending ceiling in the management agreement up to which the manager may authorize a repair without asking the owner. Above it, the manager needs explicit owner approval, except in emergencies as the agreement defines them. Recording which applied is what makes a maintenance record show a real approval decision.
What if the owner approved by phone and nothing was recorded?
Record the approval as unverified and note the channel if known. Do not infer approval from a status change. A packet that admits a gap is still useful; one that invents an approval teaches a model the wrong rule.
Is a completed work order enough to label a repair successful?
No. Completed is a claim made by whoever closed the ticket. Check the invoice lines against the approved scope, look for completion photos or tenant confirmation, and look for a repeat request for the same problem within a stated window.
Should interior photos be included in maintenance data for AI?
Only after review. Photos are valuable evidence of the problem and the fix, but they often show belongings, documents or people and carry location metadata. Crop or blur, strip metadata, or exclude the photo and keep a note that it existed.
Who decides whether a property manager may license maintenance records?
The management agreements and any owner instructions govern rights in records about the owners' buildings, alongside tenant privacy obligations. Having access to the records in the property management system does not by itself give a right to license them; counsel should review the agreements.
Sources
- Buildium advises checking the not-to-exceed limit before dispatching so the manager knows whether owner approval is needed. Source
- Buildium bill approval policies apply account-wide or per property and prompt for approval before paying bills above the limit. Source
- AppFolio managers can send and log work order estimates through the owner portal for owner approval. Source
- Buildium Bill Review Assist compares bills against attached invoices, bids and contracts on related work orders and flags mismatches. Source
- Under NSPIRE, life-threatening and severe deficiencies need to be corrected within 24 hours. Source
- California Civil Code 1954 sets written entry notice content, presumes 24 hours reasonable, and allows oral agreement to entry for agreed repairs within one week. Source
- EPA's RRP rule requires certified firms and the Renovate Right pamphlet for paid paint-disturbing work in pre-1978 housing, with a minor repair exception. Source
- HUD and DOJ guidance says providers must permit reasonable modifications for people with disabilities, generally at the tenant's cost. Source
See if your company qualifies
A short company assessment. No data uploads are needed.