By Chatham Journal staff
Pittsboro, NC – A July 16 Chatham Park work session brought town staff and development representatives together over a series of questions with consequences beyond engineering drawings: how to protect children near stormwater facilities, how to move subdivision paperwork through review, and how to distinguish promised parks from amenities already delivered.
The roughly 94-minute discussion ranged from pavement thickness and maintenance-worker fall protection to traffic modeling and preparations for public presentations. Participants resolved some misunderstandings, identified additional documentation and set tentative deadlines for outstanding submissions.
The session also revealed a recurring difficulty in overseeing a development with many simultaneous projects: the people submitting plans and those reviewing them did not always share the same understanding of a project’s status, the meaning of an approval notification or the information included in a progress tracker.
For residents, those administrative details affect when streets, parks and infrastructure can move forward – and how clearly the public can judge progress. The meeting established a series of next steps, but the video recording itself does not establish whether the proposed deadlines were subsequently met.
Stormwater fencing raises questions about responsibility
An early discussion concerned a stormwater control measure, commonly abbreviated SCM, associated with a project participant called 6.2.
Development representatives sought clarification of a town review comment about fencing and steep slopes. Plans already showed four-foot safety fencing on the high side of retaining walls. Their question was whether the town wanted additional fencing around the stormwater facility.
A town-side participant described concerns arising elsewhere, saying children were playing in a stormwater facility and throwing rocks into its infrastructure. The concern involved both possible injury and damage to the installation.
“We don’t want to repeat that,” the participant said.
A development representative acknowledged the concern but questioned whether the additional enclosure was a project requirement or a measure the town wanted for managing its park.
“That sounds like something the town can do,” the representative said, framing the request as a potential park-management responsibility.
The exchange exposed two different approaches to the same location. One focused on the engineering features shown in the submitted plans. The other considered how children might actually use a stormwater installation within a recreational setting.
Representatives pointed to three-to-one slopes and a vegetated shelf near the normal water level as features relevant to the discussion. Those descriptions were part of their explanation of the design; the session did not independently establish that they resolved every potential public-safety concern.
A participant addressed as Katie joined remotely and was shown the existing wall-fence provisions. After clarification that the retaining walls already included safety fencing, she said she was satisfied with that explanation.
The conversation then moved on. The apparent resolution concerned the scope of the review comment and the fencing already depicted. It should not be read as a broader finding that every stormwater facility near a park requires, or does not require, a perimeter fence.
Pavement dispute requires a clearer engineering record
The next major question involved the pavement section for Parkland Drive and the relationship between an earlier construction adjustment and the design required for another phase.
Participants referred repeatedly to abbreviated pavement sections and an NV5 engineering letter. Development representatives said an earlier Village Center plan had shown a heavier section than originally intended.
According to their explanation, the contractor had already excavated to accommodate that section. Rather than replace part of the excavation with compacted soil, the field solution was to extend the stone base and place the asphalt above it.
A participant reading from an engineering recommendation described three inches of asphalt over 14 inches of base.
The disagreement concerned what that recommendation meant for subsequent work. Development representatives characterized the thicker stone section as a remedy for an already excavated roadway. Town-side reviewers wanted confirmation of the appropriate design for the collector road under consideration.
One participant distilled the request: “A pavement design based on the conditions and the traffic.”
The group agreed to return to the engineering documentation and, if necessary, obtain clarification from NV5. The discussion did not establish that a thinner section was unsuitable, nor did it provide final approval for the proposed alternative.
Instead, it identified a documentation problem: a letter describing how to address one construction circumstance was being read differently by the parties considering another phase.
That distinction mattered because participants were trying to determine when the broader 6.2 package could reach signature. A clear engineering recommendation would provide a common basis for deciding whether the remaining pavement comment had been satisfied.
Maintenance safety remains part of the approval package
Although the fencing and pavement questions received substantial attention, they were not the only outstanding details.
Participants also discussed fall protection at a large stormwater riser structure. A town-side reviewer questioned how workers would secure equipment or tie off while accessing the structure.
The initial response referred to using the stormwater team’s customary procedures, including equipment such as a tripod. The reviewer pressed for a specific connection point rather than an assumption that standard equipment could be used.
The group discussed adding a tie-off or anchor point to the plans.
That exchange brought a different kind of safety into the review. Fencing addressed people approaching the facility from the surrounding park or neighborhood. The anchor-point question concerned workers who would eventually inspect or maintain the structure.
Other comments involved labeling the homeowners association open space and clarifying the status of an electrical transformer. Reviewers wanted to know whether the transformer served only the park or also served other properties, and whether the plans needed to show or note a utility easement.
Participants proposed checking with the relevant project contact and Duke Energy documentation.
An operations and maintenance package also remained necessary. Development representatives believed they could adapt material from an earlier project, but needed to confirm that their team could assemble the required submission.
Together, those items showed why an apparently short list of remaining comments could still involve several people, documents and decisions before a project was ready for signature.
A submission calendar adds pressure
The effort to finish the 6.2 package ran into the town’s intake and signature-routing schedule.
A town-side participant explained that intake occurred on Tuesday and that the next intake opportunity would otherwise be two weeks later. Even a package seeking final signatures remained subject to that schedule at the time.
Development representatives asked whether plans could enter signature routing while the operations and maintenance material followed shortly afterward.
The response allowed that approach: the plans could circulate, with completion held until the supporting material arrived.
Participants discussed getting revised plans and responses to town staff on Monday, July 20, and working toward signatures by the end of that week. July 24 emerged as a desired milestone.
Those dates were targets, not unconditional promises. Completion still depended on acceptable documentation, remaining review items and the availability of people whose signatures were required.
The practical issue was the interaction between technical readiness and administrative timing. Missing an intake window could affect a project even when the remaining changes appeared limited.
Allowing signature routing to begin while a supporting document was completed offered a way to overlap those tasks. The recording does not show that the town waived the missing requirement.
Plat reviews reveal several different bottlenecks
The discussion then turned to plats, the survey documents used to establish or revise such matters as lots, rights-of-way, and easements.
One item involved Asteria’s phase-one roadway right-of-way dedication plat. A development representative said the submission, dated to late April and sought clarification of a comment about dedicating the right of way before approval of the document intended to accomplish that dedication.
The representative explained that the proposed dedication would occur through recording the plat.
Town-side review also identified more routine issues: a missing legend on the cover sheet, inconsistent utility labels and a question about notary certification.
Participants planned to clarify those requirements and determine whether further comments remained.
A separate 6.2 phase 1B correction involved a table on a previously recorded plat. The representative said several lots described in the table as 26 feet wide were actually 35 feet wide.
According to that explanation, the detailed drawing already depicted the wider lots correctly. The correction would separate the two lot-width categories in the summary table.
That distinction is significant: the representative described a correction to the document’s tabulation, rather than a redesign of the lots themselves.
Even so, the corrective plat required its own submission, signatures and recording process. The group searched for the relevant electronic record while trying to determine where it stood.
The result was a discussion in which technically different documents shared a common challenge: locating the controlling submission and identifying the precise action needed next.
A completed review had not produced a shared understanding
The most revealing status discussion concerned a lot 10 easement-related plat associated with 7.1.
Participants initially struggled to locate it. Searches were complicated by differing project names, record numbers and descriptions. A document known to one participant by its lot designation appeared in the system under another name.
Eventually, the group found a record showing completed review activity. Participants said the approvals had been in place since June 30.
The remaining issue was communicating that the document was ready for final signatures and recording preparation.
“I just didn’t realize that you don’t see that,” a town-side participant said during the exchange.
The discussion highlighted a gap between a status visible within the review system and the next instruction understood by the applicant.
Review completion, authorization to prepare the final recording document and delivery of an electronic signature request were separate steps. Participants had not been operating with the same understanding of where one ended and the next began.
They agreed on a clearer notification that a plat was ready for the final recording process. Because the applicant intended to record electronically, the next step would involve sending an electronic signature request.
The recording does not establish that every delay discussed that day resulted from town inaction. Other items still needed applicant revisions, supporting documents or payment. In this case, however, the discussion showed how completed review work could fail to translate promptly into an understood next step.
Standard certification language draws objections
Another plat, for 7.1 phase two, appeared close to moving forward but remained tied to a dispute over certification wording.
Development representatives questioned whether a standard stormwater certification accurately described the requirements applying to Chatham Park.
Town-side participants said the governing ordinance still supplied the underlying authority, including for development operating under its approved framework. Representatives on the other side argued that the actual wording should more clearly reflect that relationship.
The disagreement was therefore more specific than whether stormwater rules applied. It concerned whether the certification accurately stated the applicable standard.
Participants learned during the discussion that updated versions of the certification forms were available. They agreed to review the newer language and consider an additional modification if needed.
That provided a possible route to resolution without settling every interpretive question in the room.
The exchange also illustrated the tension between consistent municipal forms and a development with its own approved requirements. A standard form can simplify administration, but the people signing it still need confidence that its statement is accurate.
Participants indicated that the certification appeared to be the remaining issue for that plat, subject to confirming the record and acceptable wording.
Water recovery expansion and water tank are separate submissions
Confusion also arose between a plat for the water recovery center expansion and a separate water tank site plat.
The group clarified that the expansion plat had been submitted in June. Participants identified a $650 review fee and discussed checking its payment status so the document could enter the appropriate review cycle.
The water tank site plat, by contrast, was described as still being worked on and not yet submitted.
That distinction prevented the conversation from treating both documents as if they were awaiting the same town action.
The exchange matters when assessing infrastructure progress. Discussion of a facility does not establish that every associated document has been filed. Likewise, identifying a plat in the review system does not demonstrate that the underlying construction is approved or complete.
Participants also discussed improving notifications in OpenGov, the electronic system used for submissions.
A town-side participant described working with the county on notices that would tell applicants when a submission had been accepted, when comments were due and when comments had been uploaded.
At the time, the stated review expectation remained 30 business days. A shorter period, potentially 15 business days for plats, was discussed as a future possibility after process improvements.
The shorter period was not presented as an already implemented standard.
Park tracker separates delivery from promises
The parkland tracker brought the discussion from individual submissions to the larger question of how development obligations should be measured and explained.
Development representatives said the town had been looking at an older tracker and that a revised summary had been developed in the spring.
The newer approach separated completed or recorded items from projects that were approved, pending or under construction.
Participants discussed the YMCA greenway and Sixth Street Park as items that should not be portrayed as already delivered merely because they appeared elsewhere in the development pipeline.
The conversation also included differing acreage figures, including 40.1 acres and a revised figure of 36.76 acres. Participants said the accounting needed to be checked.
The recording therefore does not support treating either number as an independently verified final total.
The larger point was the need for categories that readers could understand. An approved park, a recorded dedication and a usable recreational facility describe different stages of progress.
Participants wanted a summary that showed what was actually in place while retaining information about future work.
That approach would make it easier for town officials and residents to compare current requirements with delivered amenities, rather than treating every proposed improvement as equivalent.
It would also reduce the risk that a lengthy spreadsheet obscured the basic question the public wanted answered: what has been provided so far?
Private ownership and public access require different treatment
The park discussion became more detailed when participants considered privately owned mini parks and pocket parks.
Town-side questions focused on language describing private pocket parks as open space and whether such areas could also count toward parkland requirements.
Development representatives distinguished between resident-only spaces and privately maintained spaces open to the public.
They said small areas reserved for a neighborhood’s residents were not being submitted as public parkland. Asteria’s internal spaces were used as an example.
By contrast, they identified the lawn near the YMCA as the kind of privately retained and maintained space that could be proposed for parkland credit because it would be open to the public.
“We aren’t counting that as parkland,” one representative said of the resident-oriented spaces used in the example.
Participants referred to a requirement for 28 mini parks across Chatham Park. The session did not include a complete inventory establishing which locations would satisfy that requirement.
The discussion nevertheless clarified the distinction the parties were trying to draw: ownership alone did not explain how a space functioned. Public access and maintenance responsibility also mattered.
A privately maintained public space could offer recreational value without placing routine maintenance on the town. A resident-only space served a different population.
The meeting moved toward a shared understanding of those examples, but it did not constitute approval of every future request for parkland credit.
Traffic modeling still needs another run
Later discussion addressed transportation modeling associated with South Village section design plans and the annual development update.
Participants indicated that outstanding questions about the no-build model had been resolved. Attention then shifted to the build model and removal of two roads previously discussed.
Town-side participants wanted the updated model before presenting the information to commissioners.
A development representative said the roads’ removal was not expected to materially affect the approved South Village road network, but acknowledged that the consultant could not confirm the result without running the model.
That distinction separated an engineering expectation from a completed analysis.
Participants discussed coordinating with Kimley-Horn and the town’s transportation review team to complete the work in time for September presentation materials.
A mid-August working target and an August 31 final-package deadline were discussed.
The reason for seeking the updated run was straightforward: officials wanted the presentation to reflect the agreed assumptions. Showing a model that still contained roads marked for removal would invite questions about whether the analysis matched the plan being described.
The work session did not report the result of that rerun. It established the desired revision and the timetable participants hoped to follow.
September update intended to show the broader picture
The group also considered how to sequence section design plans, a fiscal impact analysis and the broader annual update.
Participants discussed taking section design plans to the Planning Board in August and commissioners in September, subject to review progress.
The fiscal impact analysis was considered for an August information item, giving commissioners time to review it before September discussion.
The recording did not present the analysis’s numerical findings. Participants described questions that town officials had raised and responses that had been supplied, but that conversation does not establish what the final fiscal conclusions were.
School-site documentation also entered the discussion. A participant said a letter indicating the need for school sites had been uploaded to relevant project records. No construction or opening schedule was established in that exchange.
For the broader update, development representatives argued that commissioners would want information on all of Chatham Park, including North Village activity, even if the presentation arose from South Village requirements.
They anticipated questions about lots, development on the ground, parkland and greenways.
The resulting plan was to assemble information that connected individual submissions to an understandable account of overall progress.
What residents should watch next
The July 16 session ended with a clearer list of tasks than it began with: clarify pavement recommendations, complete safety details, move plats toward signature, resolve certification wording, confirm fee payment, reconcile park accounting and update transportation modeling.
It also showed that progress depends on more than resolving engineering questions. Participants need the same understanding of submission names, review status, recording steps and the difference between planned improvements and completed facilities.
For residents following Chatham Park, the next useful records are the signed plans and recorded plats, revised park tracker, transportation-model update, fiscal impact analysis and subsequent public meeting materials.
Those documents can establish whether the July targets became completed actions and whether the anticipated public presentations answered the questions raised in the work session.
The central measure is whether each proposed action produced a documented result.
This article is based on the July 16 meeting recording of the Chatham Park work session.
Dates discussed in the session are reported as historical targets, not confirmation of subsequent completion.