Clinical documentation that survives utilization review
The reviewer deciding your request has never met the patient and cannot see your chart. They see the documentation you attached. Everything true but unsent is, for this purpose, not true. That single fact explains a large share of denials that clinicians experience as arbitrary.
#What to send
The note that establishes the indication- Usually the office visit where the decision was made. It should state the diagnosis, the findings supporting it, and the clinical reasoning. A note that records the plan without the reasoning tells the reviewer what you decided and not why.
Evidence of what was tried- Conservative management is in almost every criteria set. Medication trials with dates and outcomes, therapy with duration and response, prior procedures. Duration is the element most often omitted and most often required.
Objective results- Imaging reports, laboratory values, pathology, validated functional scores. The report, not a reference to it.
Relevant history- Prior related procedures and dates, particularly where an interval requirement exists.
#Write for the reviewer
A short cover summary stating the request, the indication, the criteria you believe are met and where in the attachments each is evidenced costs a few minutes and changes outcomes. It is not a substitute for the records; it is a map to them.
This matters most where the clinical picture is genuinely complex. A reviewer who has to reconstruct a two-year history from unordered notes will default to the criteria, and the criteria will say no.
#The documentation problem is upstream
When a practice denies repeatedly for missing conservative management, the failure is usually not in the authorization team. It is that the clinical note did not record the duration of the medication trial, because nothing in the visit workflow prompted it.
The durable fix is upstream: identify the three or four elements the policies for your common procedures require, and make sure the visit captures them as a matter of routine. This converts a recurring authorization problem into a template change made once.