Property Tax Appeals: The Right Parcels Filed Within Each County's Capacity
Parcel triage, filing allocation, manifest review, comparable corrections and appeal letters run through one Kylon room. Agents compute each county's median and check every filing against Airtable, and the tax manager approves each change and each letter.
Twenty-eight parcels, four counties and a filing cap for each
An appeal cycle starts when the assessor notices arrive. For each parcel the team compares the assessed value with what the county's comparable sales support, checks the notice for the procedural facts that decide whether an appeal is still open, and estimates the potential saving. Parcels that clear the policy go to appeal. Then each county's filing capacity decides which appeals are filed this cycle and which are deferred.
None of it sits in one place. Parcel records live in Airtable, assessor notices are in Box, and the comparable sales report is a Google Doc that lists sale prices without stating the median. The policy and every notice for the cycle sit in Drive. The filing manifest is generated from Airtable and checked by hand, and when a county's comparables are corrected, someone recomputes the median and re-checks every parcel in that county.
Who works in the room
People
Property tax manager
Approves every disposition, filing status and letter, and signs the cycle summary
Tax analysts
Check assessor notices, gather comparable sales and answer county questions
Asset managers
Weigh in on borderline parcels and use the cycle summary in their budgets
Agents

FinParcel analyst
Reads each assessor notice in Box, computes each county's median from the comparable sales report and proposes a disposition and filing status
Airtable
Box
Google Docs
Google Drive
MycoManifest reviewer
Checks the filing manifest and every re-run against current Airtable records, and runs the fresh sweep before close

AdaAppeal letters
Drafts one appeal letter per filed parcel and the cycle summary in Google Docs once the manager approves
Google Docs
Airtable
Parcel questions go to Fin, the appeals room's default agent. Myco owns the manifest and the sweeps and Ada owns the letters, so a message about either reaches them without a mention. On the first pass Fin splits the twenty-eight assessor notices across parallel helpers and works from the one set of facts they return. When the cycle closes, Fin opens a thread for Ada whose first message lists every filed parcel with its figures, and Ada drafts from that brief.
One appeal cycle, notice to letter
The appeal policy is in Drive and its section order is in the room guidelines. No Airtable write and no letter goes ahead without the property tax manager.
- Agent works
- Person decides
- Arrives or gets recorded
flowchart TD
notices([Assessor notices arrive in Box])
triage["<b>Fin</b> computes each county's median,<br>proposes a disposition per parcel"]
alloc["<b>Fin</b> fills each county's capacity<br>by potential saving, defers the rest"]
ok1["<b>Property tax manager</b> approves each<br>disposition and filing status"]
manifest["<b>Myco</b> checks the manifest and<br>records the correction count once"]
rerun["<b>Fin</b> re-runs only the parcels<br>a correction notice names"]
ok2["<b>Property tax manager</b><br>approves the note"]
ok3["<b>Property tax manager</b><br>approves the changed records"]
reset([A parcel that leaves appeal<br>has its filing status reset])
promote["<b>Fin</b> gives a freed slot to the<br>deferred parcel with the higher saving"]
sweep["<b>Myco</b> lists every parcel's state<br>fresh from Airtable"]
ok4["<b>Property tax manager</b> approves<br>the promotion and the list"]
letters["<b>Ada</b> drafts one letter per filed<br>parcel and the cycle summary"]
ok5["<b>Property tax manager</b><br>approves each letter"]
notices --> triage --> alloc --> ok1
ok1 --> manifest & rerun
manifest --> ok2
rerun --> ok3
rerun -->|leaves appeal| reset
ok2 & ok3 --> promote --> sweep --> ok4 --> letters --> ok5
class triage,alloc,manifest,rerun,promote,sweep,letters agent
class ok1,ok2,ok3,ok4,ok5 person
class notices,reset event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42| Stage | What happens | Who acts | Who decides |
|---|---|---|---|
| Triage | Each parcel is disposed from its own assessed value, its notice and its county's median computed from the listed sales | Fin, from Airtable, Box and the Google Doc | The manager approves before Airtable changes |
| Filing allocation | Each county's capacity is filled in order of potential saving and the rest are deferred | Fin | The manager approves the filing status on every parcel |
| Manifest review | The generated manifest is checked against filing status and potential saving, and the correction count is recorded once | Myco | The manager approves the note |
| Reversals | Corrected comparables, corrected notices and an extended deadline re-run only the parcels they name | Fin, checked by Myco | The manager approves the changed records |
| Escalation and sweep | A freed filing slot goes to the deferred parcel with the higher saving, then every parcel's state is listed fresh from Airtable | Fin, then Myco | The manager approves the promotion and confirms the list |
| Close-out | One appeal letter per filed parcel and one summary are drafted from the final records | Ada | The manager approves each letter before it is filed |
When comparables, notices or capacity change
Corrections arrive as notices in Drive. One county's comparable sales report is corrected, which changes its median and can move every parcel there. Two assessor notices in another county are reissued with new assessed values, though that county's median is unchanged. One parcel's deadline is extended. Fin re-runs each county or parcel a notice names and nothing else, and a parcel that drops out of appeal has its filing status reset in the same change, so the manifest never shows a filing for a parcel that is no longer appealed.
Capacity is the constraint that trips people up. When one of the reissued parcels qualifies again, it can only use the filing capacity its county still has unused this cycle. A later escalation notice frees one more slot, and the deferred parcel with the higher saving takes it. Myco re-reads the current Airtable records before each of these steps rather than relying on an earlier pass, and the manager approves each change.
What the checks catch
- A county median taken from a note or a neighboring parcel instead of computed from the listed sale prices
- A parcel that left appeal while its filing status still says filed
- A reversal that filled more slots than the county had left unused this cycle
- A manifest correction count posted twice, or worded differently from the form the policy sets
- A letter drafted for a deferred parcel, or a filed parcel left without one
What stays with people
- Approving every disposition and filing status before Airtable is updated
- Choosing whether to appeal a parcel whose saving sits close to the policy threshold
- Approving each appeal letter before it is filed with a county
- Signing the cycle summary
Integrations in this workflow
Kylon is not property tax software and it does not replace it. It sits across the tools the tax team already uses and holds the coordination between them.
Airtable
Box
Google Docs
Google Drive
Slack
- Airtable holds the parcels table with assessed value, county, disposition, filing status and potential saving
- Box holds each parcel's assessor notice, read as evidence only
- Google Docs holds the comparable sales report and receives the appeal letters and the summary
- Google Drive keeps the appeal policy, the filing manifest and every correction notice
- Slack is where asset managers outside the room ask about parcels and see the approved summary
Where to start
Run one county through one cycle first. Connect the Airtable base that holds your parcels, point the room at the Box folder with the assessor notices, and write the one rule in the room guidelines: a parcel that leaves appeal resets its filing status in the same change, and the manager approves every change before it is written.
“The median is computed, not copied, and every filed parcel has exactly one letter.”
Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set up our property tax appeals desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Box, Google Docs, Google Drive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the property tax manager, the tax analysts and the asset managers. Help me invite them to this Room. 3. Build a Parcel Appeals App with Parcel, County, Potential saving and Status, one record per parcel. Pull the current records from our Airtable base. 4. For each parcel, read its assessor notice from Box, compute the county median from the listed sale prices in the Google Doc, check the procedural facts on the notice, and estimate the potential saving. Propose a disposition and filing status for each parcel, fill each county's capacity in order of potential saving, and show me every parcel that fails or sits close to the threshold we set. 5. Hold every Airtable write, every appeal letter and every Slack post until the property tax manager approves. Draft one letter per filed parcel and one cycle summary in Google Docs only after that approval, and flag any parcel leaving appeal so its filing status resets in the same change. 6. Write our rules and who approves what into this Room's guideline, starting with the rule that a parcel leaving appeal resets its filing status in the same change. 7. After one clean cycle, offer to turn the manifest sweep and re-run checks into an Automation. Before you start, ask me for our rules one at a time.
Your first company harness. Where humans and agents run your business together.
More Use Cases
View allFacilities Work Orders: A Dispatch Week With No Stale Visits or Double-Booked Slots
Every open work order gets a vendor, a slot and a calendar visit, and keeps them right through field reports, cancellations, re-triage and Friday intake. Agents work ClickUp, Attio and the vendor calendar, and the coordinator approves each visit.
Utility Bill Validation: Every Bill Checked Against Tariff, Meter and Period Days
Each utility bill is checked against the site register, the tariff in force on each day and any meter swap. Agents do the arithmetic and draft the replies in one Kylon room, and the utilities lead approves every disposition and every message.







