> ## Content Index > Fetch the complete content index at: https://www.kevos.com/llms.txt > Use this file to discover other available public pages before exploring further. # Residential Alterations and CDC Design Documentation – NSW - URL: https://www.kevos.com/house-improvement-design-for-complying-development-certificate-cdc/ - Published: 2022-09-25T14:00:00.000Z - Updated: 2026-09-29T07:44:25.000Z - Description: Design Coordination | CAD Documentation | Compliance Support | Client Requirements | Residential Development - Author: K G J - Tags: KEVOS® Projects, KEVOS® Civil Projects **Project Stage:** Design and documentation developed to support the Complying Development Certificate process. This project involved developing architectural and technical documentation for alterations and improvements to an existing residential property in NSW. The proposed works included a residential extension and outdoor deck, requiring the existing property, proposed changes and relevant development requirements to be brought together into a coordinated set of drawings suitable for review as part of the Complying Development Certificate process. My contribution focused on understanding the client's requirements, developing and coordinating the CAD documentation, incorporating structural information and preparing clear technical information that could support review by the relevant building and certification professionals. Although this was a residential project, the underlying capabilities are directly transferable to larger engineering and project environments: requirements definition, technical coordination, documentation control, stakeholder communication and working within regulatory constraints. ## Project Context Modifying an existing building introduces different challenges from designing a completely new structure. The proposed works needed to integrate with an established property where dimensions, levels, existing structures and site boundaries were already fixed. The project therefore required consideration of both the existing condition and the proposed development. The design needed to address several interconnected requirements: - Client expectations - Existing building conditions - Proposed extension - Outdoor deck arrangement - Site constraints - Architectural documentation - Structural information - Planning and development requirements - Certification documentation - Buildability The objective was to translate these requirements into a clear and coordinated design package. ## Understanding the Client Requirement The project began by establishing what the property owner wanted to achieve through the proposed improvements. This required moving beyond a general statement such as "extend the house" and developing a clearer understanding of the intended spaces, access, relationship to the existing building and desired outdoor area. The requirements then needed to be considered against the physical limitations of the property. This requirements-definition stage is important in any engineering or project environment. A design can only solve the right problem when the intended outcome has first been understood. ## Existing Condition Assessment The existing building and available site information provided the baseline for development of the proposed design. Existing geometry, property constraints and interfaces with the proposed work needed to be represented accurately. This is particularly important when working on modifications because inaccuracies in the existing-condition information can affect every later stage of the project. The existing and proposed conditions were therefore considered together rather than developing the extension independently of the current building. ## Design Development The client's requirements were progressively translated into a coordinated CAD design. The proposed extension needed to connect logically with the existing house while maintaining practical movement between spaces. The outdoor deck also needed to integrate with the building and surrounding property. During development, the design considered: - Existing and proposed floor arrangements - Access and circulation - Relationship between internal and external spaces - Building geometry - Structural interfaces - Site limitations - Construction practicality The objective was not simply to create an attractive drawing. The documentation needed to describe a solution that could be reviewed, understood and developed toward construction. ## Architectural CAD Documentation Detailed CAD drawings were developed to communicate the proposed changes. Depending on the requirements of each drawing, the documentation represented existing and proposed conditions, dimensions, layouts, elevations and relevant construction information. Consistency between drawings was particularly important. A change to one area of the design can affect several other documents. Managing these relationships strengthened my experience in coordinated technical documentation and revision control. ## Structural Documentation Coordination Structural information also formed part of the documentation package. My role was to incorporate and coordinate the required structural information within the wider design documentation rather than independently certify structural engineering. This distinction is important. The project involved ensuring that architectural intent, structural information and the proposed building arrangement were represented consistently so that the documentation could support further professional review and certification. This type of multidisciplinary interface management later became increasingly relevant in my mechanical, manufacturing and project work. ## CDC and Compliance Considerations Because the project was intended to proceed through the Complying Development Certificate pathway, the documentation needed to account for the applicable development requirements. The design therefore could not be developed solely around client preference. Planning constraints and certification requirements also influenced the available design solution. This introduced another important project principle: **A successful design sits inside the boundaries of technical, regulatory and stakeholder requirements.** Understanding these boundaries early helps reduce unnecessary redesign later. ## Certification Interface Documentation was prepared to support review through the private-certification process. This required presenting information clearly enough for the relevant professionals to understand the proposed works and identify any additional information or changes required. The role of technical documentation in this environment is significant. Drawings are not simply illustrations. They become communication tools connecting: **Client → Designer → Engineer → Certifier → Builder** Each stakeholder needs enough reliable information to perform their part of the project. ## Design Change Management Residential design also involves iteration. Client preferences may change as the proposed arrangement becomes clearer, and professional review can identify requirements that need to be incorporated. Changes therefore needed to be managed without losing consistency across the overall drawing package. This strengthened my experience in: - Receiving design feedback - Assessing the effect of changes - Updating related documentation - Maintaining drawing consistency - Communicating revised information These same change-management principles apply directly to engineering and manufacturing projects. ## Buildability The proposed design needed to remain practical for eventual construction. This meant considering how the new work would connect to the existing property and whether the documentation clearly communicated the intended outcome. Buildability considerations included interfaces between existing and proposed construction, access, dimensions and coordination between different elements of the design. This helped reinforce the relationship between technical documentation and project execution. A drawing is successful only when the people responsible for the next stage can understand and use it. ## Stakeholder Coordination Several stakeholder perspectives influenced the project. The property owner focused on the desired outcome. Technical professionals focused on engineering and building requirements. The certifier required sufficient information to assess the proposed development. The builder ultimately required practical construction information. My role involved helping connect these requirements through coordinated design documentation. This type of interface management became increasingly important throughout my later career as projects grew more complex and involved manufacturing teams, contractors, suppliers, systems personnel and management stakeholders. ## Project Deliverables The project work included: - Review of client requirements - Existing-condition documentation - Proposed residential-extension layout - Outdoor deck design documentation - Architectural CAD drawings - Coordination of structural information - Plans and elevations - Dimensional and technical documentation - Design revisions - Compliance-related design considerations - Documentation supporting the CDC and certification process Specialist engineering certification and statutory approval remained the responsibility of the appropriately qualified and registered professionals involved in those functions. ## Project Outcome The project produced a coordinated set of design documentation describing the proposed residential alterations and supporting progression through the relevant approval and certification process. From a career-development perspective, the project strengthened capabilities that extend well beyond residential design. It required me to understand a client's desired outcome, evaluate existing conditions, work within physical and regulatory constraints, coordinate technical information and manage design revisions. These are fundamental project-delivery skills. ## Capabilities Demonstrated **Requirements Definition** Translating a client's initial objectives into structured design requirements. **Existing-Condition Assessment** Understanding the current environment before developing proposed modifications. **Design Coordination** Bringing architectural requirements, structural information and project constraints together within one coordinated documentation package. **CAD Documentation** Developing accurate drawings capable of supporting professional review and subsequent project activities. **Compliance Awareness** Understanding that designs must operate within regulatory and approval requirements. **Stakeholder Coordination** Supporting communication between client, technical professionals, certifier and construction stakeholders. **Change Management** Incorporating revisions while maintaining consistency across interconnected technical documents. **Buildability** Considering how proposed changes would integrate with existing construction and eventually be implemented. **Technical Communication** Using drawings and documentation to communicate design intent clearly between different project participants. **Project Development** Supporting progression from an initial client requirement through design development, coordination and approval-stage documentation. ## Career Development This project represents another useful stage in my progression from technical drafting toward broader project coordination. The visible output was a set of drawings, but the actual work involved much more: **Client Need → Site Constraints → Design Requirements → Technical Coordination → Compliance → Review → Revision → Construction Information** That sequence is fundamentally a project-delivery process. The scale and technical discipline later changed as my career progressed into product development, manufacturing, plant engineering and operations excellence, but many of the underlying skills remained the same. Today, those same principles apply when I coordinate an industrial project: What is the required outcome? What already exists? What constraints apply? Who needs to contribute? What technical information is required? What approvals or decisions are needed? What changes need to be controlled? What does the implementation team need in order to deliver the work? Developing this ability to connect technical detail with the wider delivery process has been an important part of my progression toward engineering project and operational leadership roles.