If you've installed the Excel add-in, you can edit the pro-forma in Excel and push your edits back to Relm. The model in the cloud is updated; the property's history records the round-trip.
This page is the conceptual overview. For the step-by-step Excel UI flow, see Push-back to cloud.
Why round-trip?
Most acquisition teams have someone who lives in Excel, even when the rest of the team works in Relm Pro. Push-back lets that person stay in Excel without forking the model.
What gets synced back
- Edited input cells. Year-1 R&M, Year 4 capex, exit cap rate — anything that's an input to the model.
- Edited assumptions. Rent growth, expense growth, vacancy.
- Edited debt terms. Interest rate, LTV, IO period, amortization.
- Per-year overrides. A planned $50K capex in Year 3.
What does not sync back
- Edits to derived cells. EGI, NOI, NCF — those are formulas; if you hard-code over them, the add-in surfaces a warning during sync but won't push the value (it would corrupt the model).
- Cells outside the standard pro-forma layout. A note you added in column Z is preserved locally but not synced.
- Charts, conditional formatting, macros. Excel-only artifacts; Relm doesn't represent them.
Conflict handling
If someone edited the same property in Relm while you were editing in Excel, the add-in detects the conflict and presents a side-by-side:
- Your Excel edit on the left.
- The Relm cloud value on the right.
- For each conflicting cell, you pick which wins.
You can pick all-mine, all-theirs, or per-cell. The merged result is what gets saved.
Lock during push-back
When the add-in initiates a sync, it acquires the property's edit lock for the duration of the push. If someone is in Edit Mode in Relm at that moment, the sync fails with a clear "[user] is editing this property; sync canceled" message — you can retry once they save.
See Property locks.
Audit trail
Every push-back creates entries in Version history tagged "Push-back from Excel" with your name. You can see exactly which cells changed and revert if needed.