Colorado Revised Statute 38-22-117
What Colorado Revised Statute 38-22-117 Covers
Why this Colorado statute matters in lien and title workflows
Understanding CRS 38-22-117 helps contractors, suppliers, owners, and title professionals comply with procedural rules that protect lien rights and mitigate title risk by clarifying notice, filing, and enforcement steps under Colorado law.
Primary users and stakeholders
Typical users need to follow timing and formality requirements precisely to preserve or challenge lien rights under Colorado law.
- Contractors and subcontractors responsible for labor or materials on Colorado projects who may need to assert or defend lien claims.
- Property owners and developers who must respond to notices, verify charges, and protect title during and after construction.
- Title companies, lenders, and closing agents that evaluate recorded claims and require compliant documentation to clear title.
Who can sign or certify lien-related filings
Project Manager
A project manager or authorized company officer may sign statements or affidavits attesting to work performed, dates, and amounts; ensure signatory authority is documented in company records to avoid disputes.
Property Owner
An owner or authorized representative typically signs acknowledgments and responses to notices; an accurate, dated signature helps establish service and response timelines relevant to enforcement and title clearance.
Practical steps to prepare and file a compliant claim
-
01Review statute: Confirm CRS 38-22-117 applicability and timing
-
02Gather documents: Contracts, invoices, delivery tickets, and lien waivers
-
03Serve notice: Deliver required notices per statute and local rules
-
04Record claim: File with county recorder or clerk as required
Where to file, serve, and record documents
-
Prepare instrument: Assemble claim, exhibits, and affidavits
-
Serve parties: Use certified mail or statutory method
-
File locally: Record with the county recorder's office
-
Retain copies: Keep originals and proof of service
Configuring an online workflow for claim documents
| Field | Configuration |
|---|---|
| Authentication | Email plus SMS code or advanced ID |
| Document format | PDF with embedded signature audit trail |
| Retention | Store signed PDF and audit log |
| Notifications | Email and certified mail as needed |
Digital signing and technical compatibility
Use a platform that supports secure PDF signatures, audit trails, and standard integrations to keep workflow auditable and interoperable.
- File formats: PDF, DOCX supported
- Integrations: Salesforce, NetSuite, Microsoft 365
- Authentication: Email, SMS, or advanced options
Timing considerations and statutory windows
Statutory filing window:
Consult CRS text; requirements vary by claim type
Notice deadlines:
Deliver notices within statutory intervals
Service proof:
Retain certification and tracking evidence
Recording time:
File promptly with county recorder
Challenge period:
Owner response windows vary; consult counsel
Representative scenarios showing typical outcomes
Contractor Claim — Denver
A subcontractor documents unpaid invoices and prepares a claim with attachments and proof of service
- They serve the owner and file with the county recorder
- Accurate dates, full legal names, and proof of service allowed the claimant to pursue negotiations and preserve lien rights while title issues were resolved.
Owner Response — Colorado Springs
An owner receives a notice and audits invoices before responding
- They request verification and contest part of the amount
- Timely, documented responses and moving to challenge the claim limited exposure and enabled quicker resolution at closing.
Common preparation and filing errors to avoid
- Using inconsistent or abbreviated claimant names that do not match contracts or tax records causes recording rejection or title clearance problems.
- Failing to include precise work dates or legal property descriptions can make a claim vulnerable to dismissal or challenge.
- Serving incorrect parties or missing a statutory notice window frequently results in forfeiture of lien rights and loss of remedies.
- Relying on informal signatures or missing notarization where required undermines enforceability and invites procedural challenges.
Key legal risks and consequences of noncompliance
Practical tips for accurate, defensible filings
eSignature vendor comparison for lien and filing workflows
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Frequently asked questions about CRS 38-22-117 and eSigning
-
What does CRS 38-22-117 require?
The statute contains procedural language relevant to construction lien matters; practitioners should read the text for exact requirements and consult counsel for fact-specific application to ensure compliance.
-
Can lien documents be e-signed?
Electronic signatures are generally valid under ESIGN (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met; exceptions may apply for certain notarizations.
-
Is notarization required for filings?
Notarization depends on the document type and local recording rules; some instruments need acknowledgement or notarization before recording, so verify county requirements before submission.
-
How do I prove service?
Use certified mail, statutory personal service, or documented delivery methods and retain receipts or affidavits of service to establish the date and method of notice.
-
What should I do if a filing is rejected?
Promptly review the rejection reason, correct defects (names, descriptions, signatures), and refile or seek counsel to address substantive disagreements or potential deadlines.
-
How long keep signed records?
Retain signed instruments and audit trails for several years—follow federal baselines such as IRS three years and HIPAA six years where applicable; industry or state rules may require longer retention.