Why This Episode Matters
Here’s something that might ruin your day: that little © symbol you’ve been putting on your CAD files, technical reports, and survey drawings? It’s doing almost nothing to protect you.
Most professional consultants — surveyors, engineers, architects, GIS specialists — operate under the assumption that copyright law protects their deliverables. But under US law, you cannot copyright facts. And if you’re delivering coordinates, measurements, boundary information, or technical data to clients, that’s exactly what you’re producing: facts. Which means when your digital files end up in the wrong hands (and they will), copyright law won’t save you.
In this episode, Landon Blake tackles the uncomfortable realities of digital deliverable liability head-on. He breaks down what copyright actually protects (and doesn’t), explains why your contract language and licensing terms are your real protection, and shares practical file management strategies that can keep you out of court. If you’ve ever emailed a PDF to a client and wondered what happens when it gets forwarded to someone you’ve never met, this is essential listening for protecting your small business.
Key Takeaways
Here are the most actionable insights from this episode:
📌 Copyright doesn’t protect facts — and most consultant deliverables ARE facts. Survey coordinates, boundary lines, measurements, and data points are not protectable under US copyright law. The 1991 Supreme Court case Feist Publications v. Rural Telephone Service made this crystal clear: no matter how much sweat, time, or money went into collecting the data, facts themselves cannot be copyrighted.
📌 Your real protection lives in your contract language and licensing terms. If you want to control how clients use, share, and modify your digital deliverables, you need explicit licensing provisions in your contracts. Copyright won’t do it. A well-drafted scope of use clause will.
📌 Government contracts play by different rules — and they’re not in your favor. Federal, state, and local government contracts typically include “unlimited rights” provisions, meaning the agency can use, modify, reproduce, and redistribute your data however they want. Your work can end up on a public website where competitors and third parties can access it freely. Price this risk accordingly.
📌 The legal doctrine of “privity of contract” is being eroded. Traditionally, you couldn’t be sued by someone you don’t have a contract with. That protection is weakening in US courts, which means third parties who access your digital files secondhand may still be able to bring claims against you.
📌 Add non-reliance language directly to your deliverables. Include a statement like: “This document is for the exclusive use of [Client Name]. Third parties may not rely on it without express written permission. Unauthorized reliance is at the third party’s own risk.” It’s not bulletproof, but it creates a meaningful barrier.
📌 File management is liability management. Implement checksums to verify file integrity, establish version numbering systems, track all revisions with dates, and document exactly what was delivered and when. If you ever end up in a dispute, this paper trail is your best friend.
📌 Know your state’s file retention requirements. In California, the statute of limitations is 10 years — which means you need systems to back up and organize potentially terabytes of data over that timeframe. Check your state law and build retention policies into your client agreements.
📌 Coordinate system mismatches cause real problems (and real liability). When digital files get moved, transformed, or mashed together with third-party data, things stop lining up. Clear documentation of your project coordinate reference system and physical control points on-site can save you from costly rework disputes.
Timestamps
Use these to jump to the sections most relevant to you:
- 0:00 — Introduction and what we’re covering today
- 2:06 — Why digital deliverables create more liability than physical documents
- 4:46 — Real story: A six-figure rework dispute caused by CAD/PDF mismatch
- 6:18 — The copyright misconception most consultants have
- 8:30 — Part 1: What copyright actually protects under US law
- 9:35 — The Supreme Court case that changed everything (Feist v. Rural Telephone, 1991)
- 13:45 — Part 2: How licensing and contract language protect your work
- 18:22 — Key contract clauses every consultant should include
- 25:16 — Part 3: Practical file management for liability reduction
- 26:14 — Checksums, versioning, and change tracking systems
- 28:03 — File retention requirements and what your state law says
- 30:17 — Part 4: Common problems with digital deliverables
- 30:43 — Coordinate system mismatches and why they cost you money
- 32:32 — When your deliverables enable unlicensed practice (a California issue)
- 35:05 — Part 5: Special rules when working for government agencies
- 36:28 — Understanding “unlimited rights” and the Federal Acquisition Regulation
- 39:42 — California SB 496: Protections for licensed professionals
- 42:56 — Using non-reliance letters to limit third-party claims
- 44:34 — Wrap-up and honest reflection on what Landon still needs to improve
Resources Mentioned
Here are the tools, references, and legal citations discussed in this episode:
- Feist Publications, Inc. v. Rural Telephone Service Co. (1991) — The Supreme Court case that established facts cannot be copyrighted under US law.
- Federal Acquisition Regulation (FAR) Part 27 — Governs data rights in federal government contracts
- FAR 52.227-14: Rights in Data—General — The specific clause covering unlimited data rights for government contracts
- California Senate Bill 496 (2017) — Provides liability protections for licensed professionals working on government contracts in California
- Episode 36 & 37: Understanding Contract Basics for Consulting Land Surveyors — Previous episodes in this series covering contract fundamentals
Leave a Reply