Stage 1: What the designer needs from you
A good interpretive signage designer can work from very little, but the more you can provide at the start, the smoother the project runs. What is typically needed:
Panel dimensions and substrate specifications. The designer needs to know exactly what size each panel is and what material it will be printed or fabricated on. These should come from your signage contractor or the project specifications.
Engineering and construction drawings. For parks with rain gardens, bioswales, drainage systems or planted areas, the technical drawings are the primary reference for the content. The designer interprets these to produce diagrams that park visitors can actually understand.
A panel schedule or content brief. If the client or landscape architect has indicated what each panel should cover, that helps. If not, the designer will propose a content strategy based on the site and the project scope.
Site context. Any background on the area, the history, the ecology or the community helps the designer develop accurate and relevant content.
Stage 2: Content development
This is where most of the work happens, and it is the stage that surprises people who have not managed a signage project before.
The designer researches the subject matter: the plant species on site, the history of the area, how any technical infrastructure works. For HDB estate parks, this often means consulting the National Archives of Singapore for historical photographs, reviewing scientific literature on local plant species, and cross-referencing the engineering drawings to understand drainage and ecological systems.
From that research, the designer writes all the copy. Every word on every panel. That includes plant names and descriptions, historical narratives, ecology explainers, and any wayfinding text.
At the same time, any diagrams or illustrations are produced. For parks with rain gardens or engineered planting systems, the designer will typically produce a custom diagram translating the technical engineering cross-section into something a visitor can read at a glance.
Stage 3: Layout and design
With content confirmed, the designer layouts each panel. This involves typesetting the copy, placing images and diagrams, and applying whatever design system the client or project requires. For HDB and NParks projects, there are often established style references that the artwork needs to align with.
All images used need to be either original, commissioned, sourced from appropriate archives with cleared usage rights, or licensed. This is particularly relevant for historical photographs.
Stage 4: Review and approval
Interpretive signage for HDB estate parks and NParks projects typically goes through multiple rounds of review before it is approved for production.
The landscape architect reviews first, checking that the content and design is consistent with the project's broader landscape intent. Then the client, usually HDB or NParks, reviews the panels for accuracy, tone and compliance with their requirements. Revision rounds are normal. A well-managed project will have structured feedback at each stage so that changes are clear, documented and addressed in a single round rather than drip-fed over weeks.
Stage 5: Production files
Once the artwork is approved, the designer prepares print-ready production files to the signage fabricator's specifications. This typically means high-resolution PDFs with correct bleed, correct colour profiles for the substrate, and any special instructions for how the files should be handled in production.
The designer stays available through this stage to answer any technical questions from the fabricator and to make minor adjustments if production constraints require it.
How long does it take
A typical HDB estate park interpretive signage project with eight to twelve panels takes between four and eight weeks from initial brief to approved artwork, depending on the complexity of the content and the speed of the review process. Projects with more panels, multiple stakeholders or complex content take longer.
The most common cause of delays is feedback arriving in instalments rather than as consolidated rounds, and stakeholders being brought into the process late. Both of these are avoidable with a clear process agreed at the start.