Before planning a Kentfield renovation, establish what the existing house and parcel records actually support. A seller may supply plans, a planning status or an earlier permit without showing the complete route to the work the buyer hopes to build. Keep the present property and future proposal separate. The Kentfield guide provides local context; this walkthrough follows one actual county project to show how the documents connect.
The example is P6135 at 17 Cedar Avenue. The county page identifies an approved design-review application and a prior parcel merger, making it useful for both property-identity and project-stage questions. No full operative approval, private inspection or current construction file was supplied here. The example therefore establishes a research sequence, not permission to build at another property or certification that the proposed addition is complete.
Match the current parcel to the older history
The P6135 page identifies current APN 074-011-90 and former APNs 074-011-88 and 074-011-89, merged under P5963. Those references explain why searching only today’s identifier can leave relevant earlier material disconnected. Retain the merger reference and former numbers with the current address when investigating the existing house and site.
Do not assume that multiple numbers mean multiple independently usable properties are being offered. Establish the actual current land interest through the relevant records and professional review. Conversely, an old plan may use a former identifier while still being relevant to the site’s history. The task is to connect the documents through the change, not discard a file solely because its APN differs.
Use the county’s records-search gateway to investigate the planning and building material separately. Record what each search returned and which identifiers were used. If a key approval or completion sheet is missing, make that a specific follow-up item. A partial result should not become a broad conclusion that the entire house is either fully documented or undocumented.
Read the project description as a proposed scope
P6135 describes a multi-story residential addition and associated exterior changes. The page’s status is Approved when checked, but the narrative continues to describe the requested project. Read the status and scope together. The meaningful question is which design was approved, under what operative conditions and with what later history, not whether every improvement visible at the property is covered by one favorable label.
The page links plans dated January 15,2026 and a Kentfield Planning Advisory Board hearing notice for February 25,2026. Those are actual steps in a dated local file. Obtain the relevant final decision and plan set for any reliance on the approval. A hearing notice, submitted design and status summary each contribute information without necessarily containing the complete operative permission.
Marin County’s design-review board guidance explains that advisory boards make recommendations rather than issue project decisions. For a Kentfield file, distinguish the advisory discussion from the county action. A favorable board recommendation should not be described as the building permit or the final answer to every remaining agency requirement.
Separate design approval from construction and completion
For an actual purchase relying on approved plans, retrieve the operative decision, conditions, referenced plans and any later changes. Ask the responsible office about current validity and the proposed owner’s intended scope. Do not invent a universal transfer or expiration rule from another town’s process. The answer should be tied to the specific approval and current county information.
Then investigate the building stage. A planning status does not establish that a building permit has issued, that construction has begun or that inspections are complete. Obtain the actual building-file scope, revisions and relevant completion evidence. If the proposal affects site work or another agency’s facilities, identify those separate dependencies before treating the project as ready to start.
Compare the existing layout with the documents rather than assuming the latest proposed plan depicts current accommodation. Mark present rooms and structures, approved but unbuilt work and ideas the buyer would change. This gives the designer and reviewers a clear starting point. It also prevents a purchase description from counting a future space as a current room.
The Cedar Avenue summary also distinguishes the proposed addition, resulting floor area and lot-based calculation. These are different measures with different purposes. Keep the source definition attached when information moves into a purchase comparison or design brief. Ask the appropriate professional to establish the existing measurements and applicable calculation, rather than adding unlike figures together or treating a proposed total as the size of the home already available to the buyer.
P6135: connect parcel identity, design review and construction evidence
| Research step | Actual public-file anchor | What it contributes | Evidence still required |
|---|---|---|---|
| Current versus former parcel | APN 074-011-90; former 88/89; merger P5963 | Search continuity across identifiers | Actual current land interest and relevant historical documents |
| Submitted addition | P6135 links January 15,2026plans | Documented proposal and plan-version lead | Operative approved set and actual existing-layout comparison |
| Advisory review | February 25,2026KPAB notice; county board-role explanation | A recommendation stage separate from county decision | Actual action and later history; no approval inferred from notice alone |
| Planning status | County page status Approved | A design-review research result | Decision, conditions, validity and scope-specific confirmation |
| Building and completion | Separate county records routes | Where to investigate construction-stage evidence | Actual permit, revisions and relevant completion/inspection records |
| Related obligations | RVSD project/compliance route | Separate wastewater question where applicable | Actual property status and review of the buyer’s defined proposal |
Original public-file walkthrough checked October 25,2026. No current building approval, completed addition, private condition or transferable permission certified.
Investigate the actual site affected by the changes
Give the designer or relevant specialist the desired footprint and the existing drainage, retaining and access information. A plan can look plausible while leaving a site dependency unresolved. Ask which records and qualified findings are needed for that specific conflict. A neighboring property’s approval does not establish that the same alteration will work on this parcel.
Tree and grounds changes need their own scope. The county’s separate Redwood Drive P5831/P5593 file combines design and tree-removal requests and is Under Review when checked. This actual contrast shows that the subject and stage matter. It does not provide a shortcut to classifying a tree or approving work at the buyer’s property.
Keep current condition separate from project permission. An inspection may identify a repair need without designing a renovation, while an approved design may leave the existing building’s condition to another assessment. Give each professional the relevant records and ask what their engagement does and does not answer. The resulting scopes should fit together without being treated as interchangeable assurances.
Bring service and ownership duties into the proposed scope
RVSD’s compliance page identifies property-transfer and certain remodeling circumstances that require a lateral inquiry. For the actual property, establish existing compliance evidence and submit the defined project through the relevant district route where needed. Do not assume a county planning approval answers the separate private-lateral question or establishes the condition of the owner’s line.
Likewise, obtain actual water-account and private-equipment information before assuming a proposed change has no service consequence. If access or a shared facility is involved, collect the governing documents for appropriate review. These are property-specific dependencies, not reasons to assume every Kentfield remodel is unusually complex. The record should show which issues actually apply.
Separate the budget for establishing feasibility from the later construction budget. A contractor’s early price may assume a design, access and approval path that the file has not yet confirmed. Retain those assumptions and exclusions. A buyer can then see whether a revised proposal changes the price, the sequence or the essential reason for buying the house.
Make the current home and future project clear in the purchase decision
Maintain a register with three descriptions: what exists, what operative documents support and what the buyer proposes. For each difference, identify the missing evidence and responsible reviewer. If the current home meets the household’s needs independently of the project, say so. If the purchase depends on the alteration, identify which unanswered question must be resolved before relying on it.
The existing Marin renovation and design-review guide supplies the broader jurisdiction and process background. This Kentfield walkthrough adds the local file sequence rather than repeating town-by-town thresholds. Use current county guidance and the actual approval for the subject project; a general guide should not substitute for scope-specific confirmation.
The Marin County guide provides area context, and the buying-process guide organizes timing. A useful renovation purchase file makes it possible to understand the existing house without borrowing certainty from a future idea, and to evaluate that idea with the correct parcel, decision and construction evidence.
