Reports
Report packets
Report packets turn one-off saved views into a repeatable reporting product. A packet can carry named saved views, delivery cadence, recipients, and a status model that makes recurring reporting operational instead of manual.
Packet inputs
Saved views with stable parameters
Delivery modes
Manual, weekly, or monthly cadences
Core benefit
Reusable report delivery instead of repeated report assembly
Interactive example
Packet builder preview
Assemble a packet from saved views and see the delivery digest update in real time.
Saved views
Packet digest
April owner packet
- Rent roll#1
- Owner statement#2
Video guide
Report packet guide
A short Remotion walkthrough of creating a packet, scheduling it, and sending a digest.
Duration
0:23
Coverage
Video guide · Create and manage packets · How delivery becomes operational
Guided walkthrough
Create and manage packets
The packet routes validate saved-view ownership and store schedule intent directly on the packet.
/api/dashboard/reports/packetsLists, creates, and deletes report packets built from saved views.
- Authentication
- Management dashboard session with reports access
- Constraint 1
- Saved view IDs are deduplicated before create.
- Constraint 2
- Cadence and schedule fields are normalized when the packet is created.
- Constraint 3
- Packets are stored with recipients, pause state, and delivery status so dispatch can be automated later.
Request examples
{
"name": "April owner packet",
"cadence": "MONTHLY",
"scheduleTimeZone": "America/Chicago",
"scheduleTimeOfDay": "09:00",
"businessDayPolicy": "EXACT",
"recipients": [
"owners@theabode.ai"
],
"savedViewIds": [
"sv_rent_roll",
"sv_owner_statement",
"sv_unpaid_bills"
]
}Response examples
{
"id": "packet_01J8V1VCX2A7D9V0DFW5M7Q3RQ",
"name": "April owner packet",
"cadence": "MONTHLY",
"latestDeliveryStatus": "READY",
"isPaused": false,
"items": [
{ "savedViewId": "sv_rent_roll", "position": 0 },
{ "savedViewId": "sv_owner_statement", "position": 1 },
{ "savedViewId": "sv_unpaid_bills", "position": 2 }
]
}How delivery becomes operational
The value of packets is not just bundling reports. It is making recurring delivery auditable and easy to reason about.
- Packets can be scheduled and paused without redefining the underlying saved views.
- A digest layer can summarize what the packet contains before it is delivered.
- Delivery status keeps recurring packets visible instead of burying them in cron-only infrastructure.
Why packets are high leverage
A property team rarely needs another export button. It needs a stable reporting routine. Packets convert reporting knowledge into a reusable operating workflow.