An export containing rows of rental data may still leave important attachment records behind. Before relying on a property manager’s handover process, test whether an authorized recipient can connect each exported document to the correct property, unit and operational record. The goal is a usable evidence package, not merely a folder that contains some files.
This Chicago edition is an original planning worksheet for the specific decision in the title. It does not report a local survey, a property inspection or a completed software test. Use your own confirmed documents and observations for the inputs. Every amount in the worked example is hypothetical and is included to make the method reviewable, not to suggest a local price or a promised result.
Define the records you need to preserve
Choose a small fictional sample that represents your actual attachments: a work request photograph, a vendor invoice, an approval note and a revised document. Give each sample a known property, unit and parent record. Do not upload resident information or live financial documents merely to discover how an export works.
List which relationships must survive the export. A file name alone may not reveal whether an invoice belongs to one property or another, and a photograph may be meaningless without its work request reference. Record the minimum index fields needed by the authorized person receiving the package.
Clarify the manager’s actual authority and the agreed handover scope before requesting live records. This worksheet does not establish ownership, access rights or retention duties. The practical test should operate within the arrangement you have and help identify what needs to be clarified in that arrangement.
Test the file and the relationship separately
Ask the manager or software provider to export the fictional sample using the process it proposes for a real handover. Record the steps, the role used and any limits disclosed. If a manual download is required for some attachments, include that step in the test rather than describing the process as fully automated.
First verify that each expected file is present and can be opened in an appropriate application. Then verify that an independent reviewer can connect it to the correct parent record. Passing the first test does not establish the second. A readable invoice with no reliable property association remains an incomplete operational handover.
Check whether the package contains actual files or references that still depend on the original account. A link can be useful, but it is not equivalent to possessing a usable copy. Ask about access conditions and test within the permitted environment. Do not bypass account restrictions to make a failed export appear complete.
Include revisions and ambiguous filenames
Create two fictional attachments with the same simple file name but different parent records. The export should preserve enough distinction to avoid one overwriting the other or becoming impossible to identify. Record how the process handles the collision instead of assuming that an export folder will always rename files safely.
Include a revised document and identify which version is current. The receiving person should be able to understand the history without accidentally treating both versions as current instructions. If the export omits prior versions, record that limitation and decide whether the available process meets your requirements.
Test a document removed from daily view if your actual workflow uses an archive and the provider supports it. Keep the exercise within normal authorized functions. The purpose is to understand the scope of the export, not to retrieve material beyond the access granted to your role.
Use this practical worksheet
| Record | Evidence to retain | Completion question |
|---|---|---|
| Expected manifest | Known list of fictional files and parent records | What exactly should the package contain? |
| File usability | Opened sample documents and format notes | Can the recipient read the actual content? |
| Record association | Export index or other reliable mapping | Can the recipient identify the correct property and work? |
| Version history | Current and earlier sample documents | Can obsolete instructions be distinguished? |
| Delivery security | Authorized recipient and agreed transfer method | Who can access the exported package? |
Review expected manifest
Write the expected list before running the export. Include a unique test reference, broad document type and the intended parent record. A manifest built only after downloading cannot reveal what was omitted. Keep the test small enough that someone can inspect every file and relationship directly rather than relying on a summary count alone.
Review file usability
Open each file using an appropriate ordinary reader and check that the expected content is present. A file extension or a successful download message does not establish readability. Record any dependency on a special viewer or active account. Do not claim universal compatibility from one test environment; state what was actually inspected and what remains untested.
Review record association
Give an authorized reviewer the package without a verbal explanation and ask them to locate a specific attachment from its parent record. Then reverse the exercise by asking which record a particular file belongs to. Both directions matter. A folder arrangement that works only when its creator remembers the original screen is a weak handover method.
Review version history
Check how revised files are named and whether the export identifies dates or status sufficiently for your needs. Preserve the original sample expectations so that the test does not rely on memory. If earlier versions are intentionally excluded, record that scope decision plainly. The problem is an unexplained omission, not necessarily the absence of every document ever uploaded.
Review delivery security
A successful export can still be an inappropriate handover if it is sent to the wrong person or shared too broadly. Confirm the intended recipient and use an appropriate transfer process. Keep the package limited to the authorized scope. Record receipt and any unresolved access problem without copying private attachment contents into a general status message.
Work through a hypothetical example
Build a fictional test containing twelve attachment records: four invoices, three approval notes, three photographs and two versions of one service document. The expected file count is twelve. Suppose the first export contains eleven readable files, while its index lists twelve records. The count difference is one, but the manifest is needed to identify which file is absent.
After the missing file is supplied, all twelve files open. A reviewer can map ten to their parent records, while two identically named photographs remain ambiguous. File completeness is now twelve out of twelve, but relationship completeness is ten out of twelve. Those are separate results and should not be combined into a single passed status.
If the manager supplies a reliable mapping that resolves both photographs, the relationship result becomes twelve out of twelve. Record the additional manual step as part of the observed process. This invented test does not report a completed evaluation of any named product or a finding about Chicago property managers.
Ask another reviewer to reconstruct the sample package
Give an authorized colleague the fictional export and its index without showing the original application. Ask them to find the latest approval for a named work request, the invoice associated with that approval and the photographs linked to the same job. Record the steps they use and any point where they must ask you to explain a file name or folder convention.
A question from the reviewer is useful evidence about the package. If the relationship is present but poorly described, improve the index. If the file is absent, ask for the missing material through the agreed process. Do not solve every question verbally and then mark the export complete. The handover must remain usable when the person who created it is unavailable.
Test a second retrieval starting from the file rather than the parent record. Select an attachment and ask which property, unit and work request it belongs to. This reverse lookup can expose a folder scheme that supports browsing in one direction but loses identity once a file is copied elsewhere. Decide what embedded or accompanying reference your operational process needs, without claiming that one naming convention is universally required.
Record the package’s dependencies. If some documents require the manager’s active account, identify that limitation and ask what supported alternative exists. If a special viewer is necessary, verify that the authorized recipient can use it under the actual arrangement. A handover that works only during the demonstration may not meet the purpose for which you requested the records.
For a larger eventual export, preserve the small sample’s acceptance criteria and add a manifest suitable for the actual scope. Do not assume that passing twelve files proves every later file is present. Reconcile counts and investigate exceptions, using proportionate review appropriate to the records. Keep any decision about retention or deletion separate and based on your actual obligations.
The final evaluation should state what was exported, what relationships were preserved, what manual steps were needed and what remained unavailable. Avoid reducing those findings to a broad claim that the manager has good exports. A precise result lets an owner judge whether the observed process supports a future handover and what additional arrangements must be settled before relying on it.
Optional software evaluation resources
Affiliate disclosure: Homzora may earn a commission through the following links. Referral relationships do not establish that a product supports the workflow in this article. Ask the provider to demonstrate current capabilities, charges and export options using your own fictional exercise.
Explore Buildium and explore Rentec Direct as possible evaluation candidates. Neither product is ranked or reported as having passed a test here. Your existing process may already satisfy the requirement.
Record observed results in the Homzora software scorecard and return to the Chicago edition for related resources. Keep each open exception assigned to a person and a next action. Closing an exercise means that the evidence supports the conclusion, not merely that every field contains some text.