Navigating Utah Legal Eligibility Tools
Mycase is a practice management platform used by legal professionals across the country. When people search for Utah eligibility features within MyCase, they are usually trying to set up automated eligibility screening for legal aid cases or self-help clinic intake workflows. This is a specific use case, and the implementation is more tedious than most users expect. The core of this setup revolves around custom fields, conditional logic rules, and sometimes integrations with Utah's LSS (Legal Services) income threshold tables. MyCase does not ship with a pre-built Utah eligibility module. You have to build it yourself using the platform's workflow engine. Here is what the actual process looks like once you sit down to configure it.
Building the Eligibility Framework Inside MyCase
First, create a document type or matter subtype specifically for eligibility screening. This keeps your main practice area views clean. I recommend tagging these matters with "ELIG_SCREEN" so they are easily filterable. Next, you need custom fields for income thresholds. Utah legal aid programs typically use Federal Poverty Guidelines as a baseline. Most programs cap eligibility at 125% or 200% of FPG depending on the program type. Set up numeric fields for household size, gross monthly income, and calculated income-to-poverty ratio. The ratio field uses a formula: divide monthly income by the monthly FPG amount for the corresponding household size, then multiply by 100. The conditional logic is where this actually becomes useful. You can set up rules that auto-assign or flag matters based on the ratio. For example, if the ratio falls below 125, the matter gets tagged as "ELIGIBLE_LSC" and routed to your legal services team. If it is between 125 and 200, it might go to a sliding-scale fee program. Above 200, the matter gets flagged for referral to private pro bono or denied.
I spent about three weeks getting this right on my first attempt. The main problem was that MyCase's formula fields do not support dynamic lookups against a poverty guideline table. The FPG amounts change annually, and there is no native way to import that table and reference it in a formula. I ended up building a workaround by creating a separate tabbed form with hardcoded FPG values for the current year, then referencing those values in calculated fields using a series of IF statements. It is not elegant, but it works. When the new FPG numbers came out in 2024, I had to manually update roughly fourteen formula fields across three document types. That took about an hour and a half, and I almost missed a threshold adjustment because I forgot to update the 6-person household row.
Get the Full Details
Common Pitfalls and What They Miss in the Documentation
Most guides skip over the fact that MyCase's conditional logic rules do not re-evaluate when a field value changes retroactively. If you enter a client's income as $3,000 per month and the system correctly flags it as ineligible, then later correct the income to $1,800, the original assignment and tags stay in place until you manually trigger a re-evaluation or edit the record again. This caused a real problem in my office where two clients who should have been accepted sat in a denied queue for nearly three weeks. The fix is to set up a recurring task reminder for your intake staff to review and re-run the eligibility screen whenever income fields are edited after initial entry. Another issue that nobody talks about is user permissions. Eligibility screening often involves sensitive financial data. MyCase lets you set field-level permissions, but the default configuration gives most staff view access to all matter fields. You need to explicitly lock down the income and asset fields so that intake coordinators who are not authorized to make eligibility decisions cannot see or modify them. This took me about forty-five minutes to configure properly across five user roles, and honestly, it should be the default setting.
Alternative Approaches Worth Considering
If you are running a high-volume legal aid clinic, building this inside MyCase is feasible but it is not the most efficient path. Third-party eligibility screening tools like Esure or various Utah-specific intake platforms can connect to MyCase via API and handle the income calculations, annual FPG updates, and multi-program threshold matching automatically. The tradeoff is cost and integration complexity. For a small firm or solo practitioner doing occasional eligibility screens, the native MyCase build is fine. For an organization processing more than fifty eligibility determinations per month, the manual maintenance burden starts to outweigh the software cost. The bottom line is that MyCase can handle Utah eligibility screening, but it requires deliberate configuration work and ongoing maintenance. The platform gives you the tools. It does not give you the policy knowledge or the automation that comes with a purpose-built screening product.
