Communication, Client Relations and Teamwork
Clear Technical Communication
Write for the reader: lead with the purpose, state findings plainly, and support with data. Use plain language, define acronyms, and keep units consistent. Reports should include an executive summary, methodology, results, conclusions, and recommendations. Emails and transmittals form part of the project record-write them as if they will be read in a dispute, because they may be.
Client Relations
Manage expectations early: confirm scope, deliverables, timelines, and fees in writing. Deliver bad news promptly and with options, not just problems. Distinguish what the client wants from what they need, and be candid when a request is unsafe, non-compliant, or outside your competence. Confidentiality builds trust; discretion about other clients is part of it.
Teamwork and Conflict
Respect other disciplines' expertise. When conflict arises, focus on interests and evidence rather than personalities. Escalate constructively-bring the issue, the impact, and a proposed path forward. Document decisions and action items from meetings.
Traps
Questions reward the answer that "avoids upsetting the client" by concealing a problem-that is never correct. Another trap: agreeing to a scope change verbally without written confirmation. Also watch for the option that cc's everyone as a substitute for direct communication.
Rule of Thumb
Bad news travels fastest and best from you, in writing, with a plan. Worked example: a test result will delay a client's launch. The technologist calls the client the same day, explains the finding, offers options (expedite retest, alternate material), and follows up with a written summary and revised timeline-rather than waiting for the formal report.
Environmental Responsibility and Sustainability
The Duty to the Environment
Environmental responsibility is part of the public-interest duty. Technologists must consider environmental impacts of designs and operations, comply with environmental legislation, and report spills or releases as required. Ontario's Environmental Protection Act and Ontario Water Resources Act impose duties on those who cause or permit discharges; the Environmental Bill of Rights provides public participation tools.
Sustainability in Design
Think lifecycle: energy use, material selection, recyclability, water, emissions, and end-of-life. Design to reduce waste and improve efficiency. Recognize tools such as life-cycle assessment (LCA) and standards for energy performance. Sustainability is not decoration-it is measurable performance over the asset's life.
Spills and Reporting
If a spill occurs, contain it, protect people, notify the appropriate authority, and document. Do not conceal or delay reporting. Waste must be characterized and disposed of through approved routes; hazardous waste requires manifesting and licensed carriers.
Traps
Questions may suggest "dilute to compliance" or "dispose quietly to save cost"-both are improper and often illegal. Another trap: assuming compliance with a permit means no further duty to prevent harm. Also watch for confusing sustainability with mere marketing claims.
Rule of Thumb
Contain, protect, notify, document. Worked example: a technologist notices solvent entering a storm drain during a site visit. They stop the activity, contain the release, notify the site supervisor and the regulator as required, and record the event-rather than assuming someone else will report it.
Professional Development, Competency Maintenance and OACETT Governance
Continuing Competence
Certification is not a one-time event. OACETT expects members to maintain and demonstrate competence through continuing professional development (CPD): formal courses, technical presentations, self-study, mentoring, and participation in professional activities. Keep a record-dates, hours, topics, and evidence. The point is demonstrable currency in your field, not merely accumulating hours.
Governance and Discipline
OACETT is governed by a volunteer board and committees, with a registrar and staff supporting certification, ethics, and discipline. Complaints go through a defined process that may include investigation, a discipline committee, and sanctions ranging from caution to revocation. Members must cooperate with the process. Know that the association sets and enforces standards of practice and ethics for its members.
Staying Current
Track changes to codes, standards, and legislation affecting your work. Participate in technical societies and peer review. Reflect on gaps and target them deliberately.
Traps
Questions may imply CPD is optional or only about classroom hours-self-directed learning and professional service count, but must be documented. Another trap: assuming a complaint is confidential to the complainant; the process requires the member's participation. Also watch for confusion between OACETT's role and the regulator of professional engineering.
Rule of Thumb
If you can't document it, you can't claim it. Worked example: a technologist completes a code-update seminar and mentors a new hire. They log the seminar hours, the mentoring dates and topics, and retain certificates, so a future competency review is supported by evidence rather than recollection.