Community Design Review --- Building Together, Building Well

In professional construction, design review exists as a formal regulatory mechanism: building permits, plan checks, inspections. These mechanisms enforce minimum standards but are not primarily designed to build community knowledge or capability. The community design review process described here has a different purpose: it is both a quality control mechanism and a capacity-building institution.

Every design review conducted well transfers knowledge between community members. The experienced builder who identifies a drainage problem in a proposed floor plan teaches the design proposer and everyone else in the review meeting something about how water behaves on a site. The future user who points out that the window placement makes the interior unusable in afternoon heat teaches the builder something about the relationship between building orientation and thermal comfort. The person responsible for maintenance who notes that the proposed roof connection detail will be impossible to inspect or repair once built teaches everyone something about maintainability as a design criterion.

Over time, a community that conducts regular design reviews develops a shared technical vocabulary, a common set of standards and expectations, and a reservoir of design knowledge that resides in people rather than in documents. This is the community equivalent of what professions call institutional knowledge — tacit understanding that is acquired through practice and peer review rather than formal instruction.

Composition:

The review committee should include:

Technical members: The most experienced builder or builders in the community. Where available, anyone with formal training in construction, civil engineering, or architecture. For complex structures, a technical advisor from outside the community may be appropriate — a district engineer, a development organization's technical staff, or a university extension service.

User representatives: People who will regularly use the proposed facility. For a school, this means teachers and ideally older students. For a health post, a community health worker and mothers who will bring children for care. For a grain store, the farmers who will use it and the person responsible for managing the stored grain.

Maintenance representative: The person or household responsible for maintaining the facility after construction. This person's perspective is systematically underweighted in design processes — they are not present during design, not present during construction, and only encounter the building when problems have already been embedded in the structure. Including them in design review explicitly gives maintainability a voice at the right moment.

Community authority: A respected community member, not necessarily with technical expertise, whose role is to ensure that review decisions are understood by and acceptable to the broader community, and to facilitate resolution when technical recommendations conflict with community preferences.

Mandate:

The committee's mandate should be defined before any specific project is reviewed. It should include: - Authority to require design modifications before construction approval - Authority to recommend halting construction if significant deviations from the approved design are discovered during the build - A defined escalation path when the committee's technical assessment is disputed - A record-keeping responsibility that produces a written summary of each review

Defining the mandate in advance prevents the common failure mode where the review committee makes recommendations that are ignored because it was never established that the committee's findings carry authority.

A systematic review checklist ensures that all relevant dimensions are assessed for every project. The checklist should be adapted to the community's context, but the following framework covers the core issues:

Site and orientation:

- What is the site drainage pattern? Where does water go during heavy rain? Will the proposed building impede natural drainage and cause flooding of the site or neighboring properties? - What is the prevailing wind direction? Is the building oriented to take advantage of natural ventilation (for climate-appropriate comfort) or is it oriented against prevailing wind? - What is the solar orientation? For structures where daylighting and thermal comfort are important, is the building oriented to admit appropriate light without excessive heat gain? - What are the soil conditions? Has a test pit been excavated to confirm soil bearing capacity and to check for seasonal high groundwater that would affect foundation design? - Is the site free of problematic trees (roots affecting foundations, branches creating fall risk) and clear of any rights-of-way, easements, or community infrastructure?

Functional layout:

- Does the floor plan support the way the building will actually be used? Walk through typical use scenarios — opening time, peak use, cleaning, emergency egress — and check whether the layout enables or impedes each scenario. - Is the circulation pattern logical? Are there unnecessary bottlenecks, dead ends, or conflicts between different user flows? - Are storage provisions adequate for the operational needs of the facility? - Are toilet and sanitation facilities appropriately located, adequate in number for the peak user load, and designed to be maintainable? - For schools: is the classroom to circulation ratio appropriate? Can the teacher see all students from the teaching position? Is there a teacher preparation area? - For health posts: is there a space for consultation that provides visual privacy? Is there a space for examination? Can supplies be stored securely? - For grain stores: is the access designed for the vehicles or equipment that will deliver and remove grain? Can fumigation gases be retained during treatment? Is the ventilation design appropriate for the stored crop?

Structural assessment:

For non-engineers conducting structural assessment, the review should focus on pattern recognition from known good and bad practices rather than attempting calculations.

Roof structure: Is the span-to-depth ratio of roof members consistent with established local practice for similar spans? (Timber purlins spanning more than 2.4m on 600mm spacing without support from a ridge beam or intermediate purlins are a common failure pattern.) Are the connections between roof members and the wall plate adequate to resist wind uplift? (A common failure in rural construction is rafters that are simply rested on the wall plate without positive mechanical connection.) Is the roofing material appropriate for the structural design? (Corrugated iron sheets are relatively light; clay tile is significantly heavier and requires a stronger roof structure.)

Wall structure: Are wall thicknesses appropriate for the height? (For unreinforced masonry, a rule of thumb is minimum wall thickness of one-tenth of the unsupported height — a 3m high wall should be at least 300mm thick.) Are wall openings (windows and doors) limited to a total width that leaves adequate solid wall for lateral stability? Are lintels provided over all openings, of adequate span and bearing length?

Foundation: Is foundation depth appropriate for the soil type and any frost or expansive soil considerations relevant to the local climate? Are foundation dimensions adequate for the wall load? For sites with any seismic risk, is there a continuous foundation connecting all walls, preventing differential movement during ground shaking?

Materials and construction method:

- Are all specified materials available locally in adequate quantity and quality at the time construction is planned to begin? - Are the construction methods specified within the skill set of the community builders, or does the design require subcontracting for specialized work? - Are material quantities estimated realistically, including allowances for waste and breakage? - Is the construction sequence logical — does the design allow for staged construction that produces a weather-tight structure at each stage, or does it require the entire structure to be complete before it can be occupied?

Maintenance provision:

- Are all structural connections accessible for inspection and repair? - Is roofing material replaceable without requiring complete removal of the roof structure? - Are plumbing and drainage systems accessible for cleaning and repair? - Are paint and surface finish specifications appropriate for the maintenance capacity of the community (i.e., regular lime-wash that community members can apply versus specialized coatings requiring professional application)? - Has a maintenance schedule been prepared and a responsible party designated for ongoing maintenance after construction?

The review process will inevitably produce required modifications. How those modifications are managed determines whether the review process builds trust or erodes it.

Minor modifications (changes to window sizes, material substitutions for equivalents, minor layout adjustments) can be approved by the committee and documented in the meeting record without requiring a full revised drawing.

Major modifications (structural changes, significant layout changes, changes to site location or orientation) should require revised drawings or sketches before construction begins. The cost of producing revised drawings is small compared to the cost of constructing from a flawed design.

Disputes between the design proposer and the review committee should be resolved through a defined process. If the committee recommends a modification and the proposer disagrees, the escalation path might be: a second meeting with the full community present; a request for external technical opinion from a district engineer or technical organization; a final binding decision by the community authority member of the committee. What should not happen is that disputes are resolved by simply proceeding with the original design, which defeats the purpose of the review.

Design review and construction supervision are two points on the same quality assurance arc. A design that has been reviewed and approved should be constructed according to that approval. This requires:

Construction drawings or documentation: Reviewed designs should be documented in sufficient detail to guide construction — not necessarily professional engineering drawings, but dimensioned sketches with material specifications and critical detail drawings for connections and foundations. The person building should have access to this documentation throughout construction.

Stage inspections: For significant community buildings, the review committee (or a nominated member) should conduct inspections at critical construction stages: foundation before pouring or backfilling, wall plate installation before roof structure begins, roof structure completion before cladding, and a final inspection before the building is commissioned.

As-built documentation: A record of any deviations from the approved design, made during construction for legitimate reasons, should be documented as the building's as-built record. This record supports future maintenance decisions and potential renovations.

There is a deeper function to design review beyond quality control. It is a community governance practice — a demonstration that collective resources require collective oversight, and that individual projects within the community's shared space are subject to community standards.

This is most visible when private construction affects community interests: a building that blocks a shared pathway, a drainage change that diverts water onto a neighbor's plot, a tree removal that affects shade or windbreak for surrounding households. Without a review mechanism, these conflicts are resolved ad hoc, often poorly, after damage has been done. With a review process that includes consideration of impacts on neighbors and shared resources, these conflicts are addressed in planning rather than in disputes.

The community that practices design review as a regular discipline is building something beyond physical structures. It is building a culture of accountability, a practice of collective stewardship, and a reservoir of technical competence that makes every subsequent building project more likely to succeed than the last. That compounding of capability over time is what distinguishes communities that build well from those that build repeatedly and poorly.