Ground Floor PM / System study
2021Recorded work
Lease-renewal CSV intake and contact preparation
Transform an uploaded renewal export into working spreadsheet rows with practical rules for missing and multiple contact emails.
- Noah’s contribution
- Data preparation, workflow testing and document-template prototyping
- Historical stage
- Configured workflow and narrated upload test
- Part of the business
- Ground Floor PM overview ↗
- CSV exports
- Submission form
- Google Sheets
- Integromat / Make
01 / Workflow
The records.
The transitions.
- Renewal export
An operator obtains the lease-renewal CSV from the source software. - Upload intake
A submission form puts the file into the watched folder. - Read renewal rows
Process the export into individual working records. - Contact email fallback
Use the alternate email when the primary/login email is missing. - Multiple-email formatting
Separate multiple email values with commas in the recorded setup. - Working renewal sheet
Populate rows for the next operational follow-up step.
02 / Implementation detail
Connect the export to a repeatable intake
The client’s process began with an assistant downloading lease-renewal information. The configured intake accepted the export through a submission form and a linked folder, providing a consistent input for downstream processing.
In the demonstration Noah selected the uploaded file manually to avoid waiting for the folder timer. This verifies the narrated test path, rather than an independently observed unattended schedule.
03 / Implementation detail
Make contact fields usable for follow-up
The workflow uses an alternate email when the primary or login email is absent. Multiple emails are formatted with commas. These choices make the working sheet more useful without requiring an operator to repair each row by hand.
The walkthrough notes that destination values might still need adjustment to match the client’s preferred layout. An earlier idea for aggregating phone numbers was described but was not part of the demonstrated behavior.
04 / Implementation detail
Resolve tenant identity before extending the flow
A related walkthrough identified multiple tenant records with the same building and unit IDs. Noah asked whether these represented multiple occupants or another data condition before joining records into renewal information.
A unit identifier may refer to more than one tenant. Resolving those matches was necessary before using the data for renewal communications.
Project scope
What this example demonstrates.
The lease-renewal data flow was configured and demonstrated with a manually selected test upload. The document work shows prototypes and template preparation. Multiple tenant matches, final field mapping and an integrated inspection workflow were not resolved in the recordings. No inspection decisions, deposit calculations or legal outcomes are claimed.
Back to the business