Each row is a project. Rows are grouped by stage: Under construction, Pre-construction, Leads, and a collapsed Permit Issued group at the bottom. Projects with an active follow-on permit pull up into a Supplemental Permits group.

The dot columns read left → right through the permit pipeline, split into phases by the faint gray vertical dividers: Pre-submission (Soils, Survey, Title, Arch, Eng) → Review (Planning, DWP, DBS, Fees, Client Update, Corrections) → Closeout (UA, Field set, Clearances, Resub, RTI) → Pre-construction (Precon, Verify, Issued). The date columns (Contract, Permit submitted, Corrections, Resub, RTI, Construction start) carry the real dates.

Planning / DWP use a review cycle: Submitted · PC Issued · Approved. Fees: Pending · Issued · Paid.

Hover any dot to see its label and current status.

A blank dot turns red Need on its own as soon as the step before it is done, so the next action is always visible. It never overwrites a status you set, and it clears the moment you pick any status. Hover an auto-flagged dot to see why it lit up.

• Contract signed → Arch
• Arch complete → Eng
• Permit submitted → DBS
• Corrections complete → UA, Field set, Clearances
• RTI complete → Precon, Verify, Issued
• 3 weeks after permit submitted → Client Update

Auto-flags don't show on completed / in-warranty projects. The three closeout dots (Precon, Verify, Issued) keep flagging into early construction; the earlier dots stop once a project starts construction.

✓ green = document attached (opens Drive). ✗ red = step done but no document yet (click to attach). Used on Soils, Survey, Field set, and Permit issued (stamped plans).

red ring = behind / priority (an overdue supplemental, or DWP needs powerline verification).

Empty date cells show an Est. line with a proj badge: a date auto-projected from the cadence (admin panel above) so you can see where a milestone is heading before it happens. Type into the Est. line to set your own estimate; the badge changes to M (manual). Clear it to fall back to the auto proj. Enter the real date in the cell above once it's known.

The list at the top is your daily worklist: Overdue supplementals, Behind (past a cadence deadline), Due within 7 days, Needed / in progress (every red or amber dot, including auto-flags), Verify DWP, Missing documents, and Address # needed (the ADU's assigned address number, which turns red once RTI is set until you enter it). Click any item to jump to that project.

To work the board: click a dot to set its status, click a date cell to enter a date, and use + Add in the Supplemental column to log a follow-on permit. The Stage column shows the most recent milestone reached plus days left or over vs the cadence target.

The Authority Having Jurisdiction is whoever reviews the permit. It is derived from the project address, not typed in: City of LA neighborhoods (Woodland Hills, Northridge, Westchester, Sherman Oaks…) all roll up to Los Angeles (LADBS), and unincorporated pockets like Altadena roll up to LA County. Click Set AHJ on any project row to override it; an override wins permanently.

Submitted → RTI is calendar days from permit_submitted_date to rti_date, over the projects that have reached RTI. That population is the n next to it, and it is small — read n before you read the average.

In review counts projects submitted but not yet RTI, with how long they have been waiting. Today that is where most of the signal is.

AR/AP is gross COGS - Permits & Fees from the ledger, from the same cost lines the project page shows (Brex, ad-hoc reimbursables, manual entries). Gross — what the jurisdiction charged, not what the customer was billed after the permit allowance.

sheet is the hand-kept Permit Fee Index tab of the Pricing & Pre-Con Database. It is reference, not truth: the ledger decides money. But it covers projects the ledger never got, and it is the only place the fee is broken down — hover a sheet figure for Fire / Planning / BOE / Plan check / Impact / School / Grading / Permit.

The two are never added together. Where both exist and disagree the row shows the variance; that is a flag to look at, not something the page reconciles for you.

Why the two figures differ, and it is not a bookkeeping gap. The sheet records what the jurisdiction charged. AR/AP holds what Buildoly paid. On 37 of 61 projects the contract sets the permit allowance to none, so the owner pays the city directly and that bill correctly never touches our ledger. Where Buildoly does cover the fees in full, coverage is 7 of 7. So the sheet is the right source for “what does a permit cost here” and AR/AP is the right source for “what did we spend” — they answer different questions and are never added together.

Which one the Permit fee column shows, and why. It shows the sheet figure when we have one. Measured against real data: across the 26 finished permits that appear in both sources, AR/AP holds $41,564 where the sheet records $279,370 — the ledger captures about 15% of what the jurisdictions actually charged, and six projects show $0 booked despite paying $6.8k–$15.3k. Leading with AR/AP printed “$283” as the cost of an LADBS permit. That is not a statement that the sheet outranks the ledger for money — it does not, and the financials use the ledger — but this column answers “what does a permit cost in this city”, and a 15%-complete number is the wrong answer to that. The Booked in AR/AP tile shows the accounting figure and the capture rate.

Only finished permits inform an average. Fees are billed in stages — plan check up front, then issuance, impact, school and grading at the counter when the permit is pulled. A permit still in review has paid a subtotal, so it is marked so far and left out of every average, median and range. It still counts in Fees total, which is cash out, and its share shows as “still in review” underneath. A project already in construction counts as finished even with no RTI date typed in — you cannot break ground without a pulled permit.

Every project is listed, including ones with no submission date and no fees booked. An AHJ can show n 0 on cycle time and still have projects in it.

Most blanks are normal: a lead or a freshly signed job has not submitted anything. The Gaps column counts only the blanks that should not exist — a project already in construction or later with no permit date, or no permit fee in AR/AP. You cannot build without a permit, so those are un-entered records, not un-done work. A pre-construction job whose contract is over 90 days old with nothing submitted counts too.

Tick Data gaps only to work that list. In an expanded group those rows read MISSING instead of a quiet dash.

Model, sqft and beds/baths come from the project's model code (M2, M2C, M3+…) resolved against the model catalog; a custom build reads its own scope. Nothing is inferred — a project with no model set shows no model, and the size filters have an Unknown option so you can pull exactly those up.

Click any column header to sort the jurisdictions by it; click again to flip. Blanks always sort last, in both directions.