Sample Florida rental-property underwriting report.
See how a share-safe review can summarize calculated returns, assumptions, warnings, rent support, map context, and next diligence steps without exposing private workspace data.
What a report should preserve
A useful property report should not only show a return estimate. It should show what produced that estimate: rent assumptions, debt terms, reserves, tax and insurance placeholders, data-quality warnings, and the items still requiring human verification.
Example review file
This static sample shows the public shape of a review. In the app, users can assemble property review files, compare candidates, save device-local portfolios, and deliberately export or copy summaries when a deal is ready for another set of eyes.
| Review area | Example output | Why it matters |
|---|---|---|
| Calculated economics | CoC 8.4%, cap rate 6.7%, cash flow $412/mo | Shows the first-pass operating case. |
| Assumption stack | Rent, debt, taxes, insurance, vacancy, repairs, management | Makes the model challengeable. |
| Warnings | Insurance quote needed; roof age unknown; solar/HOA flags checked | Keeps hidden obligations visible. |
| Next step | Verify rent comps, insurance, permits, HOA rules, and inspection scope | Turns a score into a diligence plan. |
Can reports be shared?
Property Rollup supports sanitized summaries and file exports intended for review. Account activity, saved searches, and portfolio context are not published by the app; exported material leaves only when the user chooses to share it.
Why include warnings next to returns?
Strong headline returns can be misleading when insurance, HOA rules, solar financing, flood exposure, repairs, or stale data have not been checked. Warnings keep the underwriting file honest.