Filing a Complaint Against an Oregon Contractor

Oregon's Construction Contractors Board (CCB) administers a formal complaint process that allows property owners, subcontractors, and other affected parties to seek resolution when a licensed contractor fails to meet legal or contractual obligations. This process carries legal weight: substantiated complaints can result in license suspension, civil penalties, and claims against a contractor's bond. Understanding how the complaint system is structured — and when it applies — is essential for anyone navigating a contractor dispute in Oregon.

Definition and scope

A formal complaint filed with the Oregon Construction Contractors Board is a regulatory action, not a civil lawsuit. Under ORS Chapter 701, the CCB holds jurisdiction over disputes involving licensed contractors performing residential and small commercial construction work. A CCB complaint serves two purposes simultaneously: it initiates a regulatory review of the contractor's conduct, and it can trigger access to the contractor's surety bond — a financial instrument the CCB requires as a precondition of licensure.

Oregon law sets distinct complaint eligibility requirements. Complainants must file within 2 years of the date the defective or incomplete work was discovered, or within 2 years of the contract completion date, whichever is later (ORS 701.145). The contractor named in the complaint must hold, or have held, a valid CCB license at the time the work was performed. Complaints against unlicensed contractors fall outside the CCB's dispute resolution process, though separate criminal penalties may apply to unlicensed activity under ORS 701.055.

Scope limitations: This page addresses Oregon state jurisdiction only. Federal construction contracts, tribal land projects, and multi-state construction operations fall outside CCB authority. The CCB's complaint jurisdiction does not extend to contractors licensed exclusively in Washington, Idaho, California, or Nevada. For work performed by Oregon contractors within the Portland metro area, including Multnomah, Washington, and Clackamas counties, the same statewide CCB complaint process applies — local jurisdictions do not operate parallel complaint intake systems.

How it works

The CCB complaint process follows a structured sequence:

  1. Complaint submission — The complainant submits a written complaint form to the CCB, available through the agency's official portal at oregon.gov/ccb. The submission must identify the contractor's CCB license number, describe the nature of the dispute, and attach supporting documentation such as contracts, photographs, permit records, and payment receipts.
  2. Intake and screening — CCB staff review the complaint for jurisdictional eligibility. Complaints falling outside the 2-year filing window, involving unlicensed parties, or addressing matters beyond CCB jurisdiction (such as fee disputes unrelated to construction quality) may be dismissed at intake.
  3. Investigation — A CCB investigator contacts both parties, reviews documentation, and may conduct a site inspection. The investigation phase can take 60 to 90 days depending on case complexity and investigator caseload.
  4. Mediation or formal hearing — The CCB offers mediation as a lower-cost resolution pathway. If mediation fails or is declined, the matter proceeds to a formal contested case hearing before an administrative law judge under the Oregon Administrative Procedures Act (ORS Chapter 183).
  5. Order and enforcement — If the complaint is sustained, the CCB may order the contractor to pay restitution, suspend or revoke the license, or refer the matter to the Oregon Department of Justice. Bond claims are processed separately after a final CCB order is issued.

The CCB's surety bond requirement — set at a minimum of $20,000 for residential general contractors (ORS 701.068) — serves as the primary financial recovery mechanism for complainants who obtain a favorable ruling. Details on bond structures and coverage limits are addressed in the Oregon contractor bond and insurance requirements reference.

Common scenarios

Complaints filed with the CCB fall into identifiable categories. The most frequently cited grounds include:

Decision boundaries

Not every contractor dispute belongs with the CCB. Understanding the appropriate forum is as important as understanding the complaint process itself.

CCB complaint vs. civil lawsuit: The CCB process is an administrative remedy — it can result in restitution orders and license action, but the CCB does not function as a court. Complainants seeking damages beyond bond coverage, consequential damages, or claims based on breach of warranty must pursue civil litigation independently. Oregon contractor warranty obligations describes the statutory and contractual warranty standards that support civil claims.

CCB complaint vs. small claims court: For monetary disputes below $10,000, Oregon Small Claims Court offers a faster resolution pathway that operates independently of CCB proceedings. A complainant may pursue both simultaneously, though any CCB-ordered restitution is credited against a civil judgment.

Residential vs. commercial scope: The CCB's dispute resolution program applies primarily to residential construction and small commercial projects. Large commercial construction disputes — governed by different bonding requirements and contract structures — are addressed under Oregon commercial contractor regulations. Commercial property owners typically resolve disputes through arbitration clauses embedded in AIA or similar contracts rather than through CCB intake.

Licensed vs. unlicensed contractors: A complainant whose contractor was never CCB-licensed has no access to the CCB's bond claim or dispute resolution program. In such cases, the Oregon Department of Justice Consumer Protection Division and civil courts are the primary remedies. Verifying license status before work begins — through Oregon contractor license verification — eliminates this gap in coverage.

References

📜 2 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log