For a property-management collection, separate the property, unit, request and work order before connecting related records. They identify different levels of work. AppFolio can be the source of useful operational context, but the inventory needs to say which account view and record groups were actually inspected, rather than borrowing one portal’s capabilities for another.
The documented scope to preserve
AppFolio’s public Owner Portal guidance describes report exports to Excel or CSV. That is guidance for owners using the portal, not a statement about every manager report. Its maintenance product page describes an activity-and-edit history; that feature statement does not establish your export contents or retained period.
Sources: AppFolio, Inc. · AppFolio, Inc.
Map a repair at the work-order level
Fictional property P-8 contains unit U-3. Request R-63 leads to work order W-92, contractor visit V-14 and bill B-40. Property identity gives context, but the work-order reference is needed to distinguish this repair from other activity at the same address.
If several requests are combined into one work order, preserve the request identities and the relationship. If one bill covers several work orders, inspect the allocation or supporting reference rather than attaching the full bill to each repair.
| Group | Reference to inspect | Why it matters |
|---|---|---|
| Property/unit | Property and unit IDs | Avoid address-only joins |
| Request | Request ID | Original reported issue |
| Work order | Work-order and request reference | Operational unit of repair |
| Visit/activity | Work-order reference and date | Sequence and follow-up |
| Bill | Bill and work-order reference | Cost relationship |
| Completion evidence | Note, inspection or attachment reference | Recorded result |
Keep portal and account context with the output
Record whether you inspected a manager screen, Owner Portal report or another available route. Keep the output name, filters and selected period. An export format documented for the Owner Portal should not be described as a guarantee for staff reports or attachment downloads.
Inspect a reopened repair
Choose a request that needed another visit. Can you identify the first work order, the follow-up and the completion evidence? Check whether activity timestamps, authorship and attachments survive in the output you can inspect. Do not infer a complete repair history from the current closed state.
Photos or contractor documents may live separately from report rows. Inventory their actual availability and work-order relationship. A URL or portal reference is different from an included file, and a property folder can contain several unrelated repairs.
Write a bounded maintenance collection description
Name the record groups, account view and observed dates. Keep ownership or authority questions tied to the particular proposed records when they arise, rather than assuming all material in the account has the same scope. The provider matrix can then support a specific maintenance or property-record question.
- Account view and output route
- Property/unit identities kept separate
- Request-to-work-order references
- Activity and follow-up history observed
- Bill allocation and completion evidence
- Attachment contents, links and unresolved gaps
Questions about this comparison
Can Owner Portal export guidance be applied to every manager report?
No. Preserve the portal scope and inspect the route available to the actual account.
Does a property address identify one repair?
No. A property can have many requests. Inspect request and work-order references.
Does an activity feature establish years of retained history?
No. Record the period actually observed and what the chosen output contains.
Sources
- Owner Portal Help & FAQsAppFolio, Inc. · Checked 2026-10-06
- Property Management Maintenance Software | AppFolioAppFolio, Inc. · Checked 2026-10-06