Most state UCC systems are built for one job: checking a specific debtor before a deal closes. You type a name, you get that name's filings, you leave. Colorado does that too — but it also does something most states do not: it publishes the UCC index itself as open data, refreshed daily. That one decision changes what the dataset is good for. A search interface answers "what has been filed against this company?" A daily feed can answer "what financing activity was recorded across every registered business in the state yesterday?"
This is a field guide to that dataset — where it lives, which fields it carries, how to read it entity by entity, and where its limits are.
Two ways into Colorado UCC records
A Colorado UCC search and Colorado UCC filings data are two different products of the same office, and it pays to keep them straight.
The first is the Secretary of State's UCC search: point lookups by debtor name or filing number, with certified search reports available for diligence. This is the tool for verifying a known name before funding — it is authoritative, current, and built for one-debtor-at-a-time questions.
The second is the state's open-data portal, where Colorado publishes the UCC filing index as a dataset, updated daily. Same underlying records, transposed: instead of one debtor's history on demand, you get every new filing as rows of data. For anyone whose question is "what changed this week?" rather than "what does this one file look like?", the portal is the entry point — and it is the reason Colorado makes an unusually good first state for filing-based prospecting.
The fields in the feed
Each record in the Colorado data carries the fields that matter for reconstructing financing history:
- Filing number and file date — the anchors that let you thread related records together and order events in time.
- Filing type — an initial UCC-1 financing statement, or one of the UCC-3 family: continuation, amendment, assignment, termination.
- Debtor name and address — the business the security interest is filed against.
- Secured party name and address — the party of record claiming the interest. Read it literally: it is the secured party on the filing, which may be a finance company, a bank, an assignee, or a filing agent acting for one of them.
- Collateral description — as text, in the data itself.
Why the collateral text is the rare part
That last field deserves its own section. In many states, the searchable index stops at names, dates, and filing types; the collateral description lives inside the filing image, retrieved one document at a time. That makes any collateral-level question — is this an equipment lien, a blanket "all assets" filing, a titled-vehicle filing? — a per-record retrieval job.
Colorado puts the collateral description in the data as text. You can read, at feed scale, whether a filing covers specific machinery, all assets of the debtor, or accounts and inventory — and that distinction is most of the analytical value. A blanket lien and a single-machine equipment lien are different events with different timing behavior, and Colorado lets you tell them apart without opening a single image.
Reading it entity-only
UCC filings can name individuals as debtors — consumer transactions, sole proprietors filed under a personal name. A responsible prospecting dataset excludes them. The practical reading of Colorado's feed is entity-only: keep filings whose debtor resolves to a registered organization, drop the rest.
Colorado makes this reconciliation unusually tractable because the same office runs both records. The Secretary of State maintains the business entity registry and the UCC index, so a debtor name on a filing can be matched against the state's own register of entities — including the name-variation work that collapses "ACME LLC" and "Acme, L.L.C." into one company. And because a registered organization is treated under the UCC as located in its state of organization, filings against Colorado-organized entities belong in Colorado's index in the first place: the feed approximates the secured-financing history of the state's registered businesses, not a random slice of it.
The rhythm: a daily flow you can actually review
Raw filing volume is larger than usable signal volume. After excluding individuals, resolving debtors against the entity registry, and threading UCC-3s onto the UCC-1s they modify, Colorado's feed settles into a workable rhythm: a stream of entity-grade financing events landing on weekdays as the state processes filings — you can watch it arrive on the portal yourself.
That rhythm matters for how you work the data. The daily flow is small enough to review seriously, account by account — and steady enough that a weekly manual sweep of the raw portal misses the timing that makes a filing worth calling about. The filings themselves are a mix — new UCC-1s recording fresh financing activity, continuations extending liens approaching lapse, terminations closing filings out, amendments and assignments adjusting the record — and each type means something different on a timeline.
What the data does and does not say
This is where most readings of UCC data go wrong, so it is worth being precise.
A UCC-1 is evidence that financing activity occurred — a secured party perfected an interest in described collateral on a dated filing. A financing statement is effective for five years unless continued, and a continuation can be filed only in the six-month window before lapse; those mechanics create observable timing structure. A filing aging toward the end of a typical equipment-finance term, or entering its continuation window, is a timing signal: a potential refinance window worth a conversation, grounded in a dated public record.
What the data never tells you is what the business wants. A termination says a lien was released — not that the obligation was prepaid, not that the debtor is debt-free, not why. The secured party on the filing is the party of record — the record does not tell you the present state of the relationship behind it. Anyone selling you "intent" derived from UCC records is selling an inference the filings cannot support. The honest product of this dataset is observed financing history and detected timing patterns — which, worked consistently, is worth more than manufactured intent, because every claim in it can be checked against the state's own record.
What Trace layers on top
The gap between Colorado's daily feed and a usable prospecting motion is reconciliation work: resolving debtor names against the entity registry, threading each UCC-1 and its UCC-3s into one per-business financing history, reading collateral text, and watching each timeline for the timing patterns above. That is the layer Trace builds — reconciled histories, detected timing signals, and matching against the credit box you actually fund — with every signal linking to the public filing behind it, so the verification standard stays the state's own registry. Colorado is live today; more states spin up on request.
Colorado publishes its UCC index as daily open data with collateral text included — read entity-only and threaded into timelines, it is observable financing history you can verify filing by filing.
See the record on your own credit box
Tell Trace what you fund — it shows the accounts it would look at first, every signal linked to the public filing behind it.