[{"data":1,"prerenderedAt":211},["ShallowReactive",2],{"\u002Fresources\u002Fservice-documentation-standards":3},{"id":4,"title":5,"accentColor":6,"assetType":7,"body":8,"description":196,"extension":197,"icon":198,"meta":199,"navigation":200,"order":201,"path":202,"readTime":203,"seo":204,"states":205,"stem":207,"type":208,"updated":209,"__hash__":210},"toolkit\u002Fresources\u002Fservice-documentation-standards.md","Service Documentation Standards: What Every Billable Note Must Contain","bg-secondary-500","template",{"type":9,"value":10,"toc":188},"minimark",[11,15,18,23,26,85,89,96,116,120,126,129,143,146,150,161,165,179,182],[12,13,14],"p",{},"A billable service note has one job: to prove, after the fact, that an authorized service was actually delivered to a specific person, by a qualified person, for a documented amount of time, in pursuit of that person's goals. Most documentation problems come from notes that describe a feeling (\"good day\") instead of a service.",[12,16,17],{},"Use this as a team standard. Adapt the labels to your EHR, but keep the required elements.",[19,20,22],"h2",{"id":21},"the-required-elements","The required elements",[12,24,25],{},"Every billable note should answer all of these:",[27,28,29,37,43,49,55,61,67,73,79],"ul",{},[30,31,32,36],"li",{},[33,34,35],"strong",{},"Who received the service",", the individual, clearly identified.",[30,38,39,42],{},[33,40,41],{},"Who delivered it",", staff name and credentials, with a signature.",[30,44,45,48],{},[33,46,47],{},"When",", date, and start\u002Fend time precise enough to support the units billed.",[30,50,51,54],{},[33,52,53],{},"Where",", service location (especially where EVV applies).",[30,56,57,60],{},[33,58,59],{},"What service",", the specific authorized service, named the way the plan of care names it.",[30,62,63,66],{},[33,64,65],{},"What happened",", a specific description of the support provided.",[30,68,69,72],{},[33,70,71],{},"Why it mattered",", how the activity connected to the individual's authorized goals.",[30,74,75,78],{},[33,76,77],{},"Outcome \u002F response",", how the individual responded or progressed.",[30,80,81,84],{},[33,82,83],{},"Signature & date",", signed by the person who delivered the service, at or near the time of service.",[19,86,88],{"id":87},"the-writing-rubric","The writing rubric",[12,90,91,92,95],{},"Train staff to write notes that are ",[33,93,94],{},"Specific, Service-linked, and Signed",":",[27,97,98,104,110],{},[30,99,100,103],{},[33,101,102],{},"Specific",", concrete actions and observations, not adjectives. \"Prompted to brush teeth, completed with two verbal cues\" beats \"good hygiene.\"",[30,105,106,109],{},[33,107,108],{},"Service-linked",", the note describes the authorized service and ties to a plan goal, not just an activity.",[30,111,112,115],{},[33,113,114],{},"Signed",", authored, dated, and attributed to the person who was there. Corrections are added as new dated entries, never written over the original.",[19,117,119],{"id":118},"good-vs-weak-examples","Good vs. weak examples",[12,121,122,125],{},[33,123,124],{},"Weak:"," \"Client had a good day. Went into the community.\"",[12,127,128],{},"Why it fails: no service named, no goal link, no specifics, no time, nothing an auditor can verify.",[12,130,131,134,135,139,140,142],{},[33,132,133],{},"Strong:"," \"Community integration, 10:05–11:35. Supported ",[136,137,138],"span",{},"individual"," on a planned grocery trip toward goal of independent shopping. Provided verbal prompts to locate items from a written list; ",[136,141,138],{}," completed 6 of 8 items independently and used self-checkout with one prompt. Calm and engaged throughout. Next session: practice handling payment independently.\"",[12,144,145],{},"Why it works: names the service, ties to a goal, documents specific support and the individual's response, supports the time billed, and sets up continuity.",[19,147,149],{"id":148},"a-reusable-note-skeleton","A reusable note skeleton",[151,152,157],"pre",{"className":153,"code":155,"language":156},[154],"language-text","Service: [authorized service name]\nIndividual: [name \u002F ID]\nDate: [date]   Time: [start]–[end]\nLocation: [location]\nGoal addressed: [goal from the plan of care]\nSupport provided: [specific actions, prompts, assistance]\nIndividual's response\u002Fprogress: [what happened, how they responded]\nFollow-up \u002F next steps: [continuity]\nStaff: [name, credentials]   Signature: ____   Date signed: [date]\n","text",[158,159,155],"code",{"__ignoreMap":160},"",[19,162,164],{"id":163},"quality-check-before-it-counts","Quality-check before it counts",[27,166,167,170,173,176],{},[30,168,169],{},"Could a reviewer who wasn't there understand exactly what service was delivered and why?",[30,171,172],{},"Does the documented time support the units being billed?",[30,174,175],{},"Is it tied to an authorized goal in a current plan of care?",[30,177,178],{},"Is it signed and dated by the person who delivered the service?",[180,181],"hr",{},[12,183,184],{},[185,186,187],"em",{},"This standard offers general, federal\u002FCMS-level documentation guidance and is not legal advice. Required note elements, signature rules, and billing standards vary by state, waiver program, and payer, confirm the specifics for your programs before adopting.",{"title":160,"searchDepth":189,"depth":189,"links":190},2,[191,192,193,194,195],{"id":21,"depth":189,"text":22},{"id":87,"depth":189,"text":88},{"id":118,"depth":189,"text":119},{"id":148,"depth":189,"text":149},{"id":163,"depth":189,"text":164},"A reusable standard your whole team can follow so every progress note holds up to billing review. Includes the required elements, a writing rubric, and good vs. weak examples.","md","i-heroicons-document-text",{},true,3,"\u002Fresources\u002Fservice-documentation-standards",8,{"title":5,"description":196},[206],"All states","resources\u002Fservice-documentation-standards","Template","2026-06-05","7vuW7_ns5pxYEPAk0JJ7FGxvKs9FLpDndRIQwZ7Xfrs",1790093086461]