automation.engineer

Ground Floor PM / System study

2021Recorded work

Property-document generation and inspection-template preparation

Prototype reusable text and image placeholders, retrieve image assets and prepare a consistent move-out document template.

Noah’s contribution
Data preparation, workflow testing and document-template prototyping
Historical stage
Document-generation prototypes and delegated template preparation
Part of the business
Ground Floor PM overview ↗
Tools and design context
  • Google Slides
  • Google Docs template
  • Image asset retrieval
  • Integromat / Make

01 / Workflow

The records.
The transitions.

  1. Property fields
    Define the notes, condition values and images a document needs.
  2. Template placeholders
    Give text and image positions consistent replacement tags.
  3. Asset lookup
    Retrieve an image resource by its asset identifier in the test.
  4. Text and image merge
    Replace template placeholders with sample text and images.
  5. Generated document
    Demonstrate document output from the prototype template.
  6. Template cleanup
    Hand off consistent field naming and layout preparation for further integration.

02 / Implementation detail

Separate fixed layout from changing property data

The prototype keeps static document structure in Google Slides and marks the positions where text or images should change. Sample values were placed directly into the automation to demonstrate the merge behavior.

A walkthrough shows replacement text, image placement and document generation. It describes the foundations of a later system, rather than an end-to-end inspection form integration.

03 / Implementation detail

Retrieve the asset before inserting the image

A separate test looks up an attached image by its asset ID and obtains a usable resource for the document. Noah then demonstrates inserting that image into a defined placeholder.

The implemented approach used Google Docs; PandaDoc was considered as an alternative.

04 / Implementation detail

Prepare a consistent inspection template

The move-out walkthrough delegates cleanup of the document’s notes, condition and image fields. Consistent numbering and placeholder names make later mapping easier and reduce ambiguity between different sections.

The source shows template preparation, not completed property inspections. Condition assessment, tenant liability and deposit decisions remain outside the work established by these recordings.

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

Ground Floor PM

Explore the business & all systems ↗