research · benefits

Before we recommend a benefit

A benefit claim needs a source and a way to tell when that source no longer supports it.

By Ali Madad · Published November 12, 2026

A caregiver looking for respite finds a program that appears to offer help. Someone still has to check whether it accepts applications. The published application route needs checking too. A family can spend time on an option whose current availability remains unknown.

GiveCare is building a benefits catalog where each published claim carries evidence. An application route can be documented while intake status remains unresolved. The record needs to preserve that difference.

Check the claim separately

A source can establish that a program exists without saying whether it has places available. We attach evidence to the specific fact it supports. This lets a publisher keep a useful application route visible while stating what still needs checking.

Caregiver Respite · Allegany County, New York

Catalog record: ny/allegany-county-caregiver-respite. Checked 12 November 2026.

Claim	Evidence	Limit
Respite support is described	The county’s Office for the Aging describes respite services as a temporary break for caregivers.	The source supports the service description.
Intake is open	The catalog records intake as unknown.	Current intake needs confirmation.
A household qualifies	This record cannot establish an individual decision.	The program must determine eligibility.

Source: Allegany County Office for the Aging. The catalog record is due for review on 9 December 2026. That date schedules a check; it does not guarantee availability until then.

Let uncertainty change the answer

BenefitEvidence is our draft profile for carrying source-backed claims about a program. A claim includes a date checked and a review date or policy. Its state can be supported, unknown, conflicting or expired.

Is this program accepting applications?

Fictional example. These controls do not query a live program.

Evidence in the record

“Applications are open for the current round.”

Illustrative official notice, checked 12 November. Review due 12 December.

What can be published

The program says applications are open. Check the official application page before applying.

This example changes the evidence state by hand. The profile records that state; its schema cannot establish whether a source is true or current.

See the corresponding claim

{
  "id": "current-intake",
  "kind": "availability",
  "value": true,
  "state": "supported",
  "checked_at": "2026-11-12",
  "review_by": "2026-12-12",
  "evidence": [
    {
      "url": "https://example.org/fictional-notice",
      "excerpt": "Applications are open for the current round."
    }
  ]
}

A review date makes the next check visible. Passing that date signals that review is due; the public profile does not automatically verify a source or change the claim’s state.

Build on the standards that exist

Our catalog can export program records using CommonBenefits. It also links selected programs to versioned RuleSpec artifacts from The Axiom Foundation. Those references retain the scope of the policy they encode. A financial test can cover only part of a program’s eligibility requirements.

Format	What it describes	Role here
CommonBenefits	Benefit programs and related application data	Identify the program
RuleSpec	Executable policy rules	Reference selected rules
BenefitEvidence	Claims with sources, review information and evidence states	Explain the support for a claim
Open Referral / HSDS	Organizations, services and ways to access them	Describe a separate directory layer

These projects have distinct scopes. The table describes their roles; it does not claim endorsement or a completed integration.

A service directory can help someone find an organization. A claim that a particular benefit is available still needs evidence about that benefit. BenefitEvidence does not define a services directory or a referral workflow.

Review before a recommendation

GiveCare’s benefits catalog uses a stricter admission process than the portable profile requires. Source captures and claim checks belong to that implementation. BenefitEvidence lets another publisher carry evidence and uncertainty through its own process.

Current support applies to the specific claim being considered. Other facts about the same program can remain unresolved.

GiveCare supports benefits navigation and pre-screening. The administering program makes the official eligibility and enrollment decisions.

BenefitEvidence v0.1 is an MIT-licensed draft maintained by GiveCare. CommonBenefits and The Axiom Foundation have not endorsed or adopted the profile. We are developing it so publishers can preserve the evidence behind their claims when those claims move between systems.

References

BenefitEvidence v0.1: GiveCare’s draft profile and its scope.
CommonBenefits: The shared protocol and program model.
Axiom Rules Engine / RuleSpec: The rule format and execution semantics.
Open Referral / HSDS: The data standard for community resource directories.
GiveCare’s benefits catalog: The public program collection. Consult the record and its official sources for current information.
Allegany County Office for the Aging: The official source for the Caregiver Respite example. Checked 12 November 2026.

← All caregiver answers