Custom Automation for Affordable Housing Waitlists

Property management systems like RealPage and AppFolio are databases of record, not workflow engines. Their built-in reporting can show you a list of expiration dates, but they cannot automatically trigger a 90, 60, and 30-day follow-up sequence. Leasing teams default to exporting CSVs to Excel, using conditional formatting to highlight dates, and manually sending emails from Outlook. This manual process is slow and error-prone.

Consider a leasing manager for a 450-unit new construction property with a 3,000-person waitlist. Each month, 250 applicants are due to expire. The manager spends the first week of every month exporting the list, sorting by date in Excel, and sending templated emails one by one. If they miss someone, that applicant is purged unfairly. If they email the wrong person, it creates confusion and adds to their support workload. This one task consumes nearly 25% of their time.

The core problem is that the data (expiration date) is disconnected from the action (send email). Manual processes create a gap where human error thrives. A sick day, a competing priority, or a large influx of new applications can cause the entire follow-up system to collapse for a week, leading to expired applicants and potential compliance issues.

Syntora's approach begins with a comprehensive discovery phase to understand your specific waitlist management rules and existing property management software configurations. The technical implementation would start by connecting to your RealPage or AppFolio instance via their APIs. We would develop a Python service, designed to run on a daily schedule using an AWS Lambda cron job, to pull all active waitlist applicants and check for key fields like application date, last contact date, and AMI tier. All retrieved data would be stored temporarily in a Supabase Postgres database for processing.

The core logic would be housed within a FastAPI application. This application would evaluate each applicant against your defined waitlist rules, calculating expiration dates (e.g., 365 days from application) and identifying applicants within custom notification windows (e.g., 90, 60, or 30 days prior to expiration). For layered properties with HOME funds, it would trigger additional checks for asset verification as required.

Once an applicant is flagged for follow-up, the system would utilize an email service such as AWS SES to dispatch templated messages. These messages could include unique links for applicants to securely update their information. All communications would be logged back to a custom field in RealPage or AppFolio via an API call, ensuring a permanent record of interactions.

For enhancing the applicant intake process, we would integrate the Claude API to parse income documents like pay stubs and offer letters. This capability allows for the extraction of hourly wages, calculation of anticipated 12-month income using standard methodologies, and automated sorting of applicants into the correct AMI buckets (e.g., 30% to 80%). We have successfully built similar document processing pipelines using Claude API for financial documents, and the same robust pattern applies to affordable housing income verification. This pre-screening capability reduces manual file review and helps identify non-qualified applicants earlier in the process.

A typical engagement for this type of system development involves an initial requirements gathering phase, system architecture and design, a development period of approximately 8-12 weeks, and a deployment and testing phase. Key client deliverables would include the deployed codebase, technical documentation, and training for your operational team. Clients would need to provide API access credentials for their property management software and define their specific waitlist rules and communication templates.