Tasks that span every module
A task can link to a rental unit, a development buyer, a contractor job, or a document, and appear on the record it belongs to. Here is how that works.
Most property-and-construction software tracks the financial record and leaves the operational one somewhere else: in text threads, on a whiteboard in the office, in someone’s head. The bill for the faucet repair is in the system. The faucet repair isn’t.
Tasks in Zeno are built to fix that. A task can be linked to a rental unit, a development buyer, a contractor job, a document in the Inbox, or nothing at all. It has an owner, a status, due dates, and a history. Because every task lives in the same system as the record it points at, a property detail page shows every task tied to that property, open and closed.
What a task holds
A task has:
- Title and description: plain text, whatever you want
- Assignee: a team member, or unassigned
- Status: open, in progress, blocked, done
- Due date: optional
- Linked record: optional; point it at a unit, tenant, buyer, job, property, or document
The detail page shows notes, activity history, and any files attached to the task. Comments thread, so team members can discuss a task without leaving the system.
A repair, from the call to the bill
When a tenant calls about a leaky faucet, that’s a task. Link it to the unit and it appears on the unit detail page next to the lease. When the repair bill arrives through the Inbox, match the bill to the task so the cost ties out. When the tenant asks again two months later, the history is right there on the unit.
The same pattern holds elsewhere:
- Development: “Follow up on closing docs for Unit 4B” linked to the buyer
- Contractor: “Check on material delivery for Smith job” linked to the job
- Property management: “Schedule annual inspection for 125 Main” linked to the property
The task is the same record in each case. The link is what makes it useful.
Recurring tasks
A lot of real estate work repeats on a schedule: quarterly inspections, annual lease reviews, monthly rent reminders, permit renewals. Set up a recurring task once, and Zeno creates the next instance when the previous one closes.
Team assignments
Assign a task to a team member and it appears in their personal task list. They get a notification and can see their queue on the dashboard. Managers see everything across the organization; individual contributors see their own.
On the list for spring
- Maintenance requests from tenants arriving as tasks automatically, pre-linked to the unit and assigned to the superintendent
- SLAs and reminders for tasks with deadlines
- Templates for common workflows: move-in checklist, move-out checklist, job kickoff
Already using tasks? We’d love to hear what’s working and what isn’t. Email [email protected].