How it works

Checked listings, delivered to the tools you already use.

Here is what a listing looks like, how it changes over time, and what your technical colleagues will want to know.

What a checked listing looks like

Illustrative example, not a live listing

Anytown Peer Support Network

Anytown Community Room
123 Example St, Anytown, CO 80000

Weekly peer support group

Phone
555-0142
Hours
Tuesdays, 6:00–7:30 pm needs confirmation
Intake
Walk in. No referral needed.
How urgent
Routine and community T4
Confidence
High How complete, valid, fresh, and well-sourced this listing is. It describes our information, not the organization.
Checked
Provider call · 12 days ago

Confidence describes our information, not the organization.

How thoroughly a listing is checked depends on how urgent the service is and how costly an error would be.

One listing over time

Checking once is not the point. Keeping evidence as things change is.

Illustrative example, not a live listing

  1. First check

    Details recorded

    Phone, address, and hours confirmed by a provider call. Hours marked as needing confirmation because the message on the line differed from the website.

  2. Later

    Still uncertain

    The hours could not be confirmed. The listing stays in the directory, with the uncertainty visible, rather than being hidden or deleted.

  3. Later

    A detail changes

    A re-check finds the intake line changed. The listing is updated and its check date recorded.

  4. Then

    Your tools receive the update

    The updated listing reaches the systems connected to CommonLight through the supported delivery.

Intervals are illustrative.

How listings are organized

Every listing is stored as an organization, the locations where it operates, and the services offered at each location. One agency with five sites and twenty programs is one organization, five locations, and the services offered at each, every time. That structure is what lets other systems use the listings without re-mapping them.

Based on HSDS v3.0, the open standard for community-resource directories.

How carefully each listing is checked

How thoroughly each kind of listing is checked

  • How urgent
    Crisis and immediate response T1
    Examples
    Crisis hotlines, suicide prevention
    How it's checked
    Checked most carefully and most often.
  • How urgent
    Urgent care T2
    Examples
    Inpatient, detox, psychiatric emergency
    How it's checked
    Checked carefully and more often than routine listings.
  • How urgent
    Ongoing support T3
    Examples
    Outpatient therapy, counseling
    How it's checked
    Checked on a regular schedule.
  • How urgent
    Routine and community T4
    Examples
    Support groups, information and referral
    How it's checked
    Checked on a regular schedule, with lighter checks where an error costs less.

The more urgent the service, the more thorough the check. Listings that fall below our confidence bar are flagged, not deleted.

How it reaches your tools

  1. Bring listings togetherWe gather resources in your service area, including your own list if you have one.
  2. Check the detailsWe confirm the details people need, such as phone numbers, locations, hours, payment options, and who can use each service.
  3. Share the informationWe tailor verified listings for your team’s tools or send them as a file.
  4. Check againServices change, so we validate listings on a schedule and show when each was last verified.

For the colleague evaluating the data

The shareable summary. Specifics beyond this are shared during evaluation; you don't need an NDA to understand what you're buying.

Available through our API and webhooks in HSDS v3.0. Other delivery paths by agreement.

Delivery
API and webhooks; other delivery paths by agreement.
Format
HSDS v3.0 records: organization, location, service, service-at-location.
What "checked" covers
Contact details, address, hours, and intake, checked with more care for more urgent services. Each listing records how and when it was checked and its current tier.
Updates
Listings are re-checked on a schedule and updated when a check finds a change.
Your side of the integration
Your platform decides how to display and act on listings. We confirm together whether and how your tools can receive them.
What's available and what's by agreement
Available: API and webhooks delivering HSDS v3.0 records. By agreement: other delivery paths and partner-specific scoping. Anything not listed here, ask us during evaluation.

Illustrative API response

GET https://api.example.com/services/<id>
Authorization: Bearer YOUR_API_KEY

{
  "name": "Weekly peer support group",
  "status": "active",
  "organization": {
    "name": "Anytown Peer Support Network",
    "description": "A volunteer-run network of peer support groups."
  },
  "service_at_locations": [
    {
      "location": {
        "name": "Anytown Community Room",
        "addresses": [
          {
            "address_1": "123 Example St",
            "city": "Anytown",
            "state_province": "CO",
            "postal_code": "80000"
          }
        ]
      }
    }
  ],
  "phones": [
    {
      "number": "555-0142"
    }
  ],
  "schedules": [
    {
      "description": "Tuesdays, 6:00–7:30 pm"
    }
  ],
  "x_commonlight": {
    "tier": "T4",
    "confidence_band": "high",
    "verified_at": "<date>",
    "verified_method": "provider_call"
  }
}

Fields under x_commonlight are CommonLight fields, not part of HSDS. Illustrative response; field names are subject to confirmation against the current API.

Start with the resource list you use today

We review the resource list you use today and show you which listings look solid, which look out of date, and where information is incomplete.