Qualified Person(s) Statutory Responsibilities
While the regulatory approval process is being redesigned to improve the current user experience to navigate across multiple regulatory agencies, the regulatory agencies’ respective mandate and regime remains unchanged. Hence, the statutory responsibilities of the appointed QPs under the respective Acts and Regulations remains unchanged.
Under the RABW, part of the process requires joint submission by the relevant QPs within the project teams to the relevant regulatory agencies. To ensure clear delineation of responsibilities, the developer (or whoever is required under the respective Acts and Regulations) needs to first appoint the QP for the respective areas of work at the start of a project. The appointed QP will then be responsible for the relevant aspects of the submission.
Roles and Responsibilities of Project Members
In any development project, the developer would need to assemble a team of professionals to design the project and make submission on his/ her behalf to the respective authorities to obtain the necessary approval. As part of the process, the developer will need to appoint and inform the authorities the respective QP overseeing the various aspects. In CORENET 2, this appointment is done via forms and wet ink signature from developer.
Under CORENET X, the process will be digitalised. The Project Coordinator (being the lead QP) will provide the necessary information before having it review and appointed digitally by the developer.
We have prepared the following document for project teams to refer to and plan for the various responsibilities to be allocated to the various registered / licensed professionals required for submissions for your project in CORENET X. After these responsibilities are allocated to the Qualified Persons, you may then proceed to initiate them for appointment by the Developer / Builder.
Please note that once the developer/ builder (for D&B projects) appoints the respective project members, these QPs and members will be given access to the various forms to coordinate with fellow project members involved in the submission, declare and submit. The following document comprises the lists of available responsibilities for the various roles of project members in a CORENET X project.
General Appointment Process in CORENET X
Note: Pre-submission consultations and submission of documents to the agencies can be submitted after Step 2, without requiring appointment by Developer / Builder