⚖️CASE MANAGEMENT

Property management operations teams automate non-payment-of-rent case filing — with complete output visibility as everything executes.

Case intake, defendant entry, document filing, court-date tracking — the work your team runs by hand between your property management system and your case management platform, every filing cycle. Celeron automates the pipeline without removing your team from the process.

Start Free — $200 in credits, Buildium integration ready

The Problem

Case filing is manual because a missed defendant or a missing document delays the case.

Property management operations teams filing non-payment-of-rent cases know the drill: every case needs every contact on the lease listed as a defendant, the right documents attached before the case is accepted, and the status tracked against a court date that doesn't move. Get a defendant wrong, miss a document, or lose track of a hearing date, and the case gets delayed or dismissed.

So teams do it by hand — one lease, one case, one document at a time. It works, but it doesn't scale past a handful of cases without adding headcount, and every manual step is a place a case can fall through.

Celeron is built on a different premise. Automation handles the lookups and the data entry — pulling lease and contact data from Buildium, filing the case, attaching documents, tracking status. Every write surfaces in the Queue with full context as it executes: which lease, which defendants, which documents. Your team reviews the batch in a fraction of the time — everything visible, nothing filed without the right information attached.

Workflow 1

Create Non-Payment of Rent Cases

The manual version

A batch of delinquent leases comes in for filing. Someone on the ops team opens each lease in Buildium, pulls the 7-day notice, the signed lease agreement, and the current ledger, logs into the case management platform, enters the case and every defendant by hand, uploads each document one at a time, then goes back to Buildium to leave a note that the case was filed. Multiply that across every lease in the batch, every filing cycle.

Manual time

20–35 min per case — lease lookup, document collection, case entry, document upload, note back in Buildium.

With Celeron

Workflow runs against the full case list at once. Review each case before it files, or run fully automated.

How Celeron handles it

Step 1 — Read the case list

Each row of the case list your team provides becomes an item — the lease reference and filing type are read directly from the file, no manual re-entry.

Step 2 — Get lease data from Buildium

Celeron retrieves the full lease record from Buildium, including every contact on the lease. All contacts are included as defendants — not just the primary tenant.

Step 3 — Get lease documents from Buildium

Celeron retrieves the documents required for filing: the 7-day notice, the signed lease agreement, and the current lease ledger.

Step 4 — Create the case

Celeron creates a non-payment-of-rent case, listing every lease contact as a defendant and using the property address as the defendant address.

Step 5 — Upload documents to the case

The lease documents retrieved from Buildium are uploaded and attached to the newly created case.

Step 6 — Update lease notes in Buildium

Celeron writes a note back to the Buildium lease recording the case number and filing date, so the case status is visible without opening a second system.

Workflow 2

Case Updates and Reminders

The manual version

The case management platform sends update emails with a table of status changes ahead of every court date. Someone reads each row, matches the defendants back to a lease in Buildium, checks whether new documents were added to the case, logs the update as a note, and — on the day of the hearing — pulls the current ledger and uploads it to the case. Miss a row, and a case shows up to court without current documentation.

Manual time

10–20 min per update — read the email, match the lease, check documents, log the note, prep hearing documents.

With Celeron

Runs automatically as update emails arrive. Hearing-date ledger uploads happen on schedule — no one has to track court dates by hand.

How Celeron handles it

Step 1 — Read the update email

Each row in the status table included in the update email becomes an item — defendants, case number, and status change are read directly from the email.

Step 2 — Find the matching lease in Buildium

Celeron searches Buildium leases by the defendants listed in the update row and resolves the correct lease record.

Step 3 — Retrieve new case documents

If new documents have been added to the case since the last check, Celeron retrieves them for reference and attachment.

Step 4 — Update lease notes in Buildium

The status change is written back to the Buildium lease as a note, so the lease record always reflects the latest court status.

Step 5 — Upload new documents to the case

Any new lease documents available since the last update are uploaded and attached to the case.

Step 6 — Upload the ledger on the hearing date

On the date of the court hearing, Celeron pulls the current lease ledger from Buildium and uploads it to the case, so the file carries final balance figures into the hearing.

The Queue Experience

What the queue experience looks like.

Your team's daily workflow in Celeron is built around the Queue — not a spreadsheet, not an export.

Item View

Each case or case update appears as a card showing the primary identifier — lease, defendants, case number — alongside the key data needed to make a decision. Status is live: processing, ready for review, filed, completed.

Bulk review

Your team selects all cases that look correct and files them in one action. The write executes for every selected item. Cases with questions stay in the queue for individual handling.

Step-level detail

Every item can be expanded to show the full step-by-step output — what Buildium returned, which defendants were included, which documents were attached. If a case looks wrong, your team sees exactly where it came from.

Step View

Switch to Step View to see the workflow's steps as tiles — how many cases are ready at each step, how many are blocked, how many need attention. One view to understand where the entire batch stands right now.

Audit trail

Completed items are permanently logged — source data, step outputs, reviewer, filing timestamp, write confirmation. If a case is questioned, your team opens the completed item and has the complete record immediately.

Integrations

Integrations used in case management workflows.

IntegrationRole in case management workflows

Buildium

Source and write target for lease and contact data. Celeron reads lease records, contacts, and documents — and writes lease notes and the current ledger back after every case update.

Case Management

Write target for case intake and document filing. Celeron creates non-payment-of-rent cases, uploads required lease documents, and retrieves case documents and status updates as they change.

Gmail / Mailgun

Parses incoming case update emails and triggers the Case Updates and Reminders workflow for each row in the status table.

Microsoft Excel

Source for the initial case list. Each row in the uploaded file becomes an item in the Create Non-Payment of Rent Cases workflow.

ROI Framework

The ROI is immediate — every filing cycle.

Every workflow Celeron automates returns a compounding portion of your team's time. The more cases you run through it, the more time compounds back.

WorkflowWithout CeleronTime savingsYour team reviews

Create Non-Payment of Rent Cases20–35 min per case~85% fasterReview before filing, your choice

Case Updates and Reminders10–20 min per update~90% fasterNone required

Manual process time eliminated

~85%

across both workflows

Team effort returned

~85%

to higher-value work per cycle

vs. equivalent headcount

~10%

of annual ops analyst fully-loaded cost

Getting Started

The trial runs against your real Buildium environment.

$200 in free credits, valid for 30 days. Buildium integration is available on day one — connect your credentials, configure a workflow, and run your first case batch in the same session.

A recommended first workflow: Create Non-Payment of Rent Cases. Bring a real case list, connect Buildium and your case management platform, and see the first batch of cases filed with documents attached and notes written back automatically.

No card required to create your account.

Configure Buildium and Case Management credentials

Navigate to Integrations and connect both systems.

Add a payment method

Required before building your first workflow. Your $200 in trial credits cover the cost — nothing is charged until you exceed them.

Create a new workflow

Describe it in plain English: "Read each row of the case list, pull the lease and documents from Buildium, and file a non-payment-of-rent case with those documents attached."

Celeron drafts the workflow steps

Review the spec, approve it, and the Automation Agent builds the steps.

Run the Setup Queue

Validate each step against a real case from your list. When the output looks right, move to production.

Implementation timeline: most teams have their first case-filing workflow in production within their first week of trial.

Your case filing should be automated. Every write should be visible as it executes.

Start with $200 in free credits. Connect Buildium. Run your first case-filing workflow. See exactly what Celeron does as every step executes.

Start Free Trial