Manager App Detailed Analytics

Handoff documentation for the RentOk Manager App analytics suite: nine screens, one self-contained handoff sheet per screen. Each sheet defines every number, every window, every tap and every empty state in plain language. No code references anywhere; a developer builds from it, a designer works from it, a non-technical reader follows it.

Contents

• Start here, by role
• The screens
• Jump straight into a sheet
• The rules every sheet follows
• How this repo stays current

Start here, by role

You are	Open this	Then
Building a screen	Its handoff sheet, below	The engineering reading map tells you which sections are yours and what will bite
Designing	The design reading map, below	Every fix for your screen sits in one numbered list
Running the project	The tracker	Every locked rule, the backfill queue, the next action. Read it first, every time
Writing a new sheet	The template	The canonical spine. Copy it; never start from a blank page

The screens

#	Screen	Handoff sheet	Engineering map	Design map	Status
1	Dues	DA-01 sheet	read me first	design map	✅ v12 · the current reference
2	Collection	DA-02 sheet	read me first	design map	✅ v13 · the toggle screen
3	Expense	DA-04 sheet	read me first	design map	✅ v3
4	Inventory	DA-08 sheet	read me first	design map	✅ v2 · uplifted to template
5	Tenants	DA-09 sheet	read me first	design map	✅ v2.1 · voice exemplar
6	Old Tenants	—	—	—	🟡 next up
7	Bookings	—	—	—	⬜
8	Complaints	DA-10 sheet	read me first	design map	✅ v1.1 · audited
9	Leads	—	—	—	⬜ newest addition

Jump straight into a sheet

Deep links into the sections readers ask for most.

Section	Complaints (DA-10)	Tenants (DA-09)	Inventory (DA-08)	Expense (DA-04)	Dues (DA-01)	Collection (DA-02)
What every number counts	§3	§3	§3	§3	§3	§3
How the screen behaves	§4	§4	§4	§4	§4	§4
What each number opens	§17	§19	§14	§11	§15	§13
Build guidance	§21	§23	§18	§15	§19	§17
Open items	§22	§24	§19	§16	§20	§18
Design file fixes	§23	§25	§20	§17	§21	§19

Every sheet also opens with its own What is in here table: the full section list with a reading map per audience.

The rules every sheet follows

Rule	Meaning
Self-contained	One sheet is the whole spec for its screen. No other document needed to build
Plain language	The team's own words. No code, no file paths, no internal numeric codes
Outcome plus test	Anything that must hold carries a Test it: line QA can run
One grammar	Same spine, same section names, same table shapes across all sheets, from the template
Two kinds of number	Live always shows now; Time-scoped counts inside the filter window. Every sheet carries the grid
Honest gaps	A number that cannot open its own records says so; nothing silently opens a wrong list

How this repo stays current

Source of truth	The Obsidian vault. This repo carries the closed deliverables only
What lands here	Each screen's handoff sheet and reading maps, at close-out, plus the tracker and template
What never lands here	Briefs, formula maps, archives, superseded PRDs. They stay in the vault
Wikilinks	[[Like this]] resolve inside Obsidian, not on GitHub, and are kept as written