The morning list
One queue of everything approaching or past its window, across every client and every contract. Filter to one staff member, copy their list, and send it from your own inbox. This is the screen your team opens first and closes last.
EVDNT holds client requirements, recurring deliverables, and audit results against the agreement that created them, and turns them into an audit preparedness score you can see before anyone audits you.
No protected health information stored. Clients are tracked by your own internal identifier.
Needs attention
Audit preparedness, average of contracts
Housing services grant
County Housing Authority
Behavioral health services
County BH
Plan A services
Plan A
These sit in spreadsheets, EHR reports, email threads, and institutional memory. The organization only discovers the gap when someone outside it goes looking.
Deadlines that differ by funder, by program, and sometimes by the characteristics of the client in front of you. Miss a window and the record cannot be repaired after the fact.
Recurring submissions on schedules your funders set independently of each other. The one that gets missed is almost always the one only a single person knew about.
A funder samples client files against a written element list and scores you on what they find. You usually learn your score after it is final rather than before it is set.
Not a fixed program template. Your contracts, your rules, your element lists, your columns.
Payer, county, state agency, or foundation. One contract in EVDNT is one agreement with one funder.
Nothing in EVDNT identifies a client. That keeps your risk profile, and your technology review, short.
A working copy of the review surface with sample data from a sample framework. Click a response on each element and watch the weighted score, the progress bar, and the critical element rule resolve live. Your own framework would carry your funder's elements, not these.
Each one answers a question a compliance officer gets without warning, and currently answers by opening four files and hoping the last person updated them.
One queue of everything approaching or past its window, across every client and every contract. Filter to one staff member, copy their list, and send it from your own inbox. This is the screen your team opens first and closes last.
Every contract holds its own requirements, recurring deliverables, rate reference, and amendment history. Schedules that differ from one funder to the next are held per funder rather than in someone's memory.
Pull a sample, walk the elements once per file, and score each one in a single click. Criteria and review procedure sit one tap away. Weighted scoring, critical element handling, and the gap list assemble themselves as you go.
Audit results, client requirements, and deliverables roll into one audit preparedness score per contract. When a funder calls, you already know which agreement is exposed and which element is dragging it down.
Most compliance software encodes one funder's rules and asks everyone else to pretend those rules fit. EVDNT holds no opinion about what your contracts require. Every layer that defines compliance is authored by you.
Define a requirement once, set the window it must be met in, and scope it to the contracts it applies to. Shared starting points exist for some programs. You are free to ignore them and build from nothing.
Choose which requirements appear as columns on your client roster. A column that would be permanently empty for your organization never has to appear at all.
Add any payer, county, agency, or foundation you contract with. Some entries come prefilled where a shared registry exists, including California managed care plans, and the rest are yours to create.
Build an element list from your funder's actual monitoring tool. Set weights, mark which elements are critical, and decide what is scored and what is recorded only.
Most compliance tools ask you to hand over client records and then spend six weeks proving they can hold them. EVDNT takes a different route: it never holds anything that identifies a client, so the conversation starts and ends somewhere much simpler.
Plain language references written cautiously and pointed back at the source documents. Requirements described here are general and should always be confirmed against your executed agreements.
In progress The library is being written now. If one of these would help you this month, say which one and it moves up the list.
What each published guidance letter changed, when it took effect, and which programs it touches. Organized by funder and program, starting with California Medicaid.
Enter an enrollment date and a program. See the assessment, plan, and reassessment windows that generally apply, with the source noted.
Twelve questions drawn from common monitoring tools. Returns a score band and a gap list you can act on today.
The acronyms a new program manager hits in week one, across Medicaid, county behavioral health, and federal grant programs, defined without the circular jargon.
How sampling usually works, what reviewers commonly ask for, and where documentation gaps tend to appear.
How to inventory recurring submissions across several funders at once and catch the ones only one person knows about.
Monthly, with a one time implementation fee and no annual commitment. Every plan includes every module. Seats are not capped, because charging per seat encourages shared logins and shared logins destroy the audit trail.
Implementation is done by hand, not by a setup wizard. It covers loading your contracts, authoring your requirements against your executed agreements, building your audit frameworks from your funders' monitoring tools, configuring your client list columns, and training your team on the surfaces they will use daily. You are working in the product with your own data before the first monthly charge.
I am a compliance manager at a community based organization. I have spent full shifts reconstructing what was due and when, from spreadsheets that disagreed with each other, days before a review. Nothing on the market was built for an organization our size, and nothing was built by anyone who had done the work.
EVDNT is the tool I wanted. The reason it does not assume your program is that I got tired of software that assumed mine.
Compliance Manager · founder of EVDNT · building in California
No. You author your own requirements, your own audit frameworks, and your own funder entries. Shared starting templates exist where a common standard is published, and you can ignore all of them and build from nothing. A contract in EVDNT is an agreement with one funder, whether that funder is a payer, a county, a state agency, or a foundation.
No. Clients are tracked by an internal identifier your organization assigns. EVDNT holds dates, statuses, and the compliance record. It does not hold names, addresses, clinical notes, or client level documents.
Onboarding is done by hand rather than through a wizard, because at our size a conversation configures a contract better than a form does.
No, and it is not meant to. Your record system holds the file. EVDNT holds the obligations, the deadlines, and the audit trail that sit on top of the file and that a record system was never designed to track.
Requirements are edited in place, and the correspondence announcing a change is kept in that contract's communications archive. Completed audit reviews are frozen, so a past review still reads exactly as it was scored.
Both. Access follows role, from read only through administrator, so a front line staff member sees the clients and deadlines relevant to them without seeing contract or rate detail.
Compliance queues can be copied or downloaded at any time. If you leave, we export your records for you.
Thirty minutes, screen shared, no slides. Bring one agreement and we will build your actual requirements in front of you.
Prefer email? Write to [email protected]