EPLE cheat sheet

EPLE denotes the Engineering Professional Licensing Examination framework; licensing boards derive authority from provincial or state statutes, not from professional associations.

A professional engineer license is granted by a regulator; membership in a society such as a technical institute is voluntary and confers no independent practice right.

Core ethical duties rank public safety, health, and welfare above employer, client, and personal interests when these conflict.

Conflict of interest exists when a professional's private interest could bias judgment; disclosure plus recusal is the standard remedy, not silence.

Confidentiality obligations survive the end of an engagement; exceptions include legal compulsion, imminent public harm, and quality-assurance review.

Signing and sealing work outside one's demonstrated competence is misconduct even if the seal is legally valid; competence is a separate test from licensure scope.

Practising or offering to practise without a current licence is an offence; firms that offer engineering services must typically hold a certificate of authorization and name a responsible licensee.

Continuing professional development is a licence-maintenance condition in most jurisdictions; record retention of CPD evidence is the licensee's responsibility.

A contract requires offer, acceptance, consideration, and intention to create legal relations; a signed proposal alone may not bind if acceptance is conditional.

Standard of care in tort is what a reasonably competent professional would do in similar circumstances, not perfection and not the industry's best practice.

Limitation periods set the deadline to sue; they run from the date of the act or from discovery depending on the statute, and they are shorter than contractual warranty periods.

Negligence requires duty of care, breach of the standard of care, causation, and proven loss; missing any element defeats the claim.

Privity of contract limits claims to contracting parties, but tort duties can extend to foreseeable third parties who rely on the work.

Regulatory compliance is a legal floor, not a ceiling: meeting a code does not by itself defeat a negligence claim.

Statutory duties to report unsafe conditions or environmental releases override contractual confidentiality clauses.

Records created during a dispute may become producible; privilege is narrow and jurisdiction-specific, so assume adverse records will be disclosed.

Design documents must be sealed only by the licensee who supervised and reviewed the work; delegated work remains the seal holder's responsibility.

Codes and standards are adopted by reference in regulation; the edition cited in the permit governs, not the newest edition available.

A field review confirms general conformance with design intent; it does not certify contractor means, methods, or workmanship quality.

Shop drawings are contractor submittals reviewed for design intent; review does not transfer design responsibility to the reviewer.

Delegation is permitted when the delegate is competent and supervised; the delegating licensee retains accountability for the output.

Change orders must be documented with technical justification, cost and schedule impact, and the approver's authority level.

As-built records reflect actual construction; they are a separate deliverable from design drawings and must be marked as such.

Peer review is a quality gate independent of the design team; its findings are advisory unless the regulator or contract makes them binding.

Scope definition precedes fee negotiation: deliverables, exclusions, assumptions, and client-supplied inputs belong in writing before work begins.

A written record of client instructions protects both parties; verbal direction should be confirmed by email or memo within a defined interval.

Informed consent requires disclosing material risks, alternatives, and cost implications in language the client can act on.

Capacity to instruct is assessed by the professional when the client is an organization: confirm the signatory's delegated authority.

Bad news should be communicated early and in writing; delayed disclosure of a defect increases both liability and remediation cost.

Documented assumptions are a risk-transfer tool: if the client supplies wrong data, the assumption record shifts responsibility.

Communication plans should name a single point of contact per party to prevent conflicting instructions reaching the field.

Client confidentiality and public-interest disclosure can conflict; escalate to the regulator or legal counsel rather than deciding alone.

Risk is assessed as likelihood times consequence; controls should target the highest product, not the most familiar hazard.

The hierarchy of controls runs from elimination and substitution to engineering controls, administrative controls, and finally personal protective equipment.

Independent checking of calculations and drawings by a second competent person is the core defence against single-point design error.

Quality assurance covers process; quality control covers inspection of output. Both are required for a defensible QA program.

Error and near-miss reporting should be non-punitive for the reporter, otherwise reporting rates fall and latent errors accumulate.

Insurance transfers financial risk but not regulatory or ethical accountability; a claim still requires defence and disclosure.

Lessons-learned reviews should be closed with assigned owners and dates, otherwise corrective actions decay.

Residual risk after controls must be documented and accepted by an authorized party, not assumed away.

Fee proposals should separate labour, disbursements, and contingency; blending them hides scope creep until the project is unprofitable.

Professional liability exposure is not limited by the fee; low-fee work carries the same standard of care as high-fee work.

Trust or client funds must be held in a separate account; commingling with operating funds is a regulatory and ethical breach.

Cash flow forecasting uses committed costs and expected billing dates; a profitable project can still fail on timing.

Contract terms on payment, retainers, and interest on late payment should be negotiated before mobilization, not after.

Subconsultant agreements must flow down insurance, confidentiality, and standard-of-care obligations from the prime contract.

Budget variance analysis compares earned value against actual cost; a positive variance signals under-billing or scope growth.

Succession and key-person risk planning protects clients when a sole practitioner retires, becomes incapacitated, or dies.

A document control system should enforce version numbering, approval status, and a single authoritative copy per deliverable.

Digital signatures must be backed by identity verification and an audit trail; a scanned image of a seal is not a valid signature.

Data classification tiers (public, internal, confidential, restricted) drive encryption, access, and retention requirements.

Access should follow least privilege and be revoked at role change or contract end, not only at termination.

Backup strategy is defined by recovery point objective (acceptable data loss) and recovery time objective (acceptable downtime).

Model-based delivery requires defined levels of detail and information delivery plans, otherwise downstream users cannot rely on the model.

Retention schedules must satisfy statutory record-keeping periods and litigation holds; deletion during a hold is spoliation.

Third-party software and cloud vendors require due diligence on data residency, breach notification, and exit provisions.