DOCUMENT REVIEW · UPDATED OCTOBER 23, 2026

Our findings.
The sources. The open questions.

A reading guide to the organizer-supplied Heritage Hills application packet and images. Use it to locate evidence and frame specific requests—not as a substitute for reading the source or describing your own experience.

Scope of this review: the relevant application, narrative, traffic-study text, and scoping pages identified below were reviewed. This is not a legal or engineering opinion, a complete audit of all 304 pages, a Board finding, or confirmation of the latest official submission. Confirm revisions and the case-specific hearing notice with the Township.
Open the original proposal PDF ↗

13.9 MB · 304 pages · References below use PDF viewer page numbers. Printed page numbers may differ. The filename’s “2026-12” label does not independently confirm a case number.

01 / THE APPLICATION

A special exception application, with further review ahead.

The September 14 cover letter submits a special exception application for Heritage Hills Associates. The narrative describes a proposed residential development and says detailed land-development review will follow special exception approval. Those statements describe the applicant’s request and proposed process; the supplied packet does not establish that approval has been granted.

Read: cover letter, PDF 1; narrative, PDF 7.

Ask: Which application version, plans, zoning provisions, and requested special exceptions are before the Board? What details remain for land-development review?
02 / ACCESS & CONNECTIONS

The narrative expressly describes an Alexis Drive connection.

The narrative and traffic study describe access through Shawna Avenue and an extension of Alexis Drive connecting to the existing Bridgewater community. The supplied annotated aerial map separately highlights a route around Duquesne Road toward Springwood Road. The map’s colored marks illustrate a concern; they do not independently establish an approved road, opening date, surveyed boundary, or traffic distribution.

Read: narrative, PDF 8; traffic study printed page 9, PDF 52; supplied annotated context map.

Ask: Which current and planned connections are modeled, when are they expected to open, and how are trips through Bridgewater and the Alexis/Duquesne/Springwood network assigned?
03 / VERSION RECONCILIATION

The packet contains differing unit figures.

The narrative on PDF 7 describes 27 detached, 120 attached, and 300 multifamily units, totaling 447. The opening paragraph on PDF 8 instead describes 25 detached, 121 attached, and 300 multifamily units; later on that same page it returns to the 447-unit study description. These are document descriptions, not independently established current or approved totals.

The earlier July 23 scoping letter describes another development mix. Different versions may explain some differences; the packet alone does not establish which version controls or why each figure changed.

Read: narrative, PDF 7–8; July 23 correspondence, PDF 67.

Ask: Please reconcile the narrative, sketch, and traffic-study revisions and identify the current unit mix, total, and plans being evaluated. A difference is a reason to seek clarification; it does not by itself prove an error, omission, or motive.
04 / TRAFFIC STUDY & BRIDGEWATER

The applicant’s forecasts, and the Project 3 question.

Exhibit E contains TPD’s Transportation Impact Study dated August 31, 2026. Table 6 forecasts 3,080 average weekday vehicle trips generated by the site, including 198 trips in the weekday A.M. peak hour and 241 in the P.M. peak hour. These are forecast trip movements across the site, not unique vehicles, observed increases, or the totals at every intersection.

PM peak-hour delay at Chestnut Hill & Camp Betty Washington

Table 10 (printed page 15 / PDF 58) forecasts the following overall intersection control delay for Chestnut Hill Road & Camp Betty Washington Road (SR 2005). The 92.5% comparison uses the same 2035 year, without the modeled improvements:

Applicant’s weekday PM peak-hour forecast at Chestnut Hill Road & Camp Betty Washington Road
ScenarioAverage delay (sec/vehicle)Overall level of service
2035 no-build17.3C
2035 build, without improvements33.3D
2035 build, with modeled improvements23.9C

Calculated change without improvements: 33.3 − 17.3 = 16.0 additional seconds per vehicle; 16.0 ÷ 17.3 × 100 ≈ 92.5%. This percentage is our calculation from the applicant’s delay forecasts, not an applicant-quoted traffic-volume increase. Control delay includes slowing, queueing, stopped time, and acceleration; the overall average is not an exact wait for each driver or each approach. The existing-condition overall delay in Table 10 is 15.3 seconds; that is a different baseline from the 2035 no-build value used here.

Improvement assumptions and the traffic-light question: the study describes a planned westbound left-turn lane/road widening and the Township CIP’s recommended conversion from two-way to all-way stop control (printed page 16 / PDF 59). It forecasts 23.9 seconds per vehicle with the modeled improvements, still 6.6 seconds above the 2035 no-build delay. Table 10 rates the northbound left turn F in the existing, no-build, and build-without-improvements scenarios. These approach-level results differ from the overall intersection rating.

The applicant’s signal-warrant analysis says the tested four-hour volume warrant is not satisfied: two hours exceed the threshold, where four are needed (printed page 19 / PDF 62). This guide does not establish that a traffic light is required. Ask the applicant and reviewing agencies to explain the warrant analysis, turning-movement delays, safety evidence, alternatives, and whether future development or updated counts change the result.

Read: Table 10, printed page 15 / PDF 58; improvement discussion, printed page 16 / PDF 59; delay methodology, printed page 12 / PDF 55; signal-warrant analysis, printed page 19 / PDF 62.

Ask: Which improvements produce the 23.9-second forecast? Who is responsible for funding, approvals, and construction, and will they be operating before the development adds traffic? What happens if those improvements are delayed? Explain the PM northbound left-turn results and the basis for the signal-warrant conclusion.

A separate measure: vehicle trips at Chestnut Hill & Shawna

The Appendix E worksheet dated August 26, 2026 for Chestnut Hill Road & Shawna Avenue (Synchro Node 1) compares the same 2035 design year with and without the proposal. Its intersection totals are:

Applicant’s forecast vehicle trips at Chestnut Hill Road & Shawna Avenue
2035 scenarioA.M. peak hourP.M. peak hour
Without proposal (no-build)339607
With proposal (build)451745
Site trips added112138
Calculated increase33.0%22.7%

How we calculated the percentages: (451 − 339) ÷ 339 × 100 = 33.0% in the A.M.; (745 − 607) ÷ 607 × 100 = 22.7% in the P.M., rounded to one decimal. The percentages are our arithmetic from the applicant’s forecasts, not an overall rate quoted by the applicant. They apply to this intersection’s total peak-hour movements. Other intersections and individual turning movements have different changes; do not add intersection totals together as unique trips.

The study’s printed page 7 describes August traffic counts, seasonal adjustment, and 0.33% annual background growth (3.01% compounded to 2035). That background-growth assumption is separate from the proposal’s added trips. The listed nearby development is a 150-unit Bridgewater Age Restricted Community. The worksheet’s background-development row reads “Bridgewater (Remaining Build-Out) Age Restricted” and adds six trips in each peak hour at this intersection. Neither of these pages separately identifies remaining Project 3 development.

The June 26 scoping memo lists “Bridgewater (Remaining Build-Out).” The July 23 scoping correspondence specifically refers to Projects 1, 2, and 3 when discussing school-in-session traffic data, describes Project 3 as in early construction, and separately describes Project 4 as an age-restricted development of 135 homes. The differing labels and unit figures need reconciliation; they do not by themselves prove that Project 3 was omitted from the final analysis.

Read: Table 6, printed page 11 / PDF 54; Appendix E intersection worksheet, PDF 166; background assumptions, printed page 7 / PDF 50; June 26 scope, PDF 71; July 23 scoping comments, PDF 67–68.

Ask: Show where remaining Bridgewater Project 3 trips and planned road connections are included in the final 2035 assumptions. Which trips are already in the existing counts, which are added for future build-out, and which studies were incorporated? Reconcile the age-restricted development’s labels and unit counts. If remaining development or connections are absent, provide an updated analysis and explain the effect on forecast volumes and intersection operations.
05 / SCHOOL QUESTIONS

School capacity & student population need their own evidence.

The July 23 scoping letter discusses an Ore Valley school expansion and reports no increase to the school’s stated 600-student population in that plan. This is an assertion in the scoping correspondence about that school project. It is not independent confirmation of present enrollment, building capacity, available seats, or students generated by the proposed housing.

Read: July 23 scoping letter, item 2(c), PDF 68.

Ask: What current district enrollment/capacity records, attendance-area assumptions, projected student yields, and district comments apply to this development? Describe school conditions you personally experienced separately. Do not infer enrollment or capacity from a busy event, or include children’s names, records, individual learning needs, or routines.
06 / USING THIS GUIDE

Make the distinction clear in your statement.

The application packet and two images were supplied by the organizer; their status as the latest official record was not independently authenticated. No claim about Phase 3’s home count, a missing analysis, illegality, or anyone’s intent should be inferred from this guide. Questioning witnesses, party status, and admission of statements remain subject to the applicable procedures.

View all supplied materials · Confirm official hearing information

Bring your experience into the record.

Build my statement →

To print this summary, use your browser’s Print command. To print your own statement, use the builder’s reviewed letter output.