Applied Kinesiology Flowchart Manual
I've spent years building and refining AK flowcharts for clinic use. The original ones people find online are mostly copy-pasted from old seminars with no real clinical context. What follows is what actually works when you're seeing patients back to back. The core of any applied kinesiology flowchart manual comes down to decision trees. You start with a baseline muscle test, usually the arm or leg, and based on the response you branch into different pathways. Each pathway leads to questions about organ systems, structural alignment, emotional states, or nutritional deficiencies. The trick is making it linear enough to follow under time pressure without oversimplifying what's happening. I built my first real one around 2014 after watching colleagues waste twenty to thirty minutes per patient trying to remember the hierarchy of tests. They'd skip steps, double back, and end up with inconsistent results depending on which way they happened to approach the case. The flowchart cuts that down to roughly five to eight minutes for a standard screening after you've memorized it.
Building Your Own Applied Kinesiology Flowchart Manual
Start with the basic testing sequence. Graded muscle testing against resistance at about three pounds of force, applied for one to two seconds, is the foundation. If you're testing weaker than that, you're just guessing. If you's harder, the patient compensates and the signal gets muddy. From there, organize your branches in this order: structural first, then chemical, then emotional. Most people skip straight to chemical or emotional because those are flashier. Structural problems cause the majority of false positives on chemical tests. I had a case last year where a guy tested positive for six food sensitivities and negative on every structural branch. Turns out his sacrum was fixated. Once I cleared that, five of the six reactions flipped negative. The sixth was borderline and held steady, which pointed to a real issue. Include branching logic for weak baseline tests. A weak baseline doesn't mean nothing to work with, but you have to adjust your whole approach. Check the vital points on the hand first, then move to the cranial reflex points. If those come back normal while the arm test is still weak, you're dealing with either a very deconditioned patient or a compromised nervous system state. Either way, keep your testing pressure lighter and your interpretation more conservative.
The most useful addition most people skip is a reverse confirmation step. After you've identified a dysfunction through the flowchart, test the correction before you commit to any intervention. If you say "this is a spleen issue, let's do this protocol," test the spleen again while applying the correction simultaneously. If the muscle strength returns, you're on the right track. If it doesn't, your flowchart branch led you to the wrong conclusion and you need to backtrack.
Get the Full Details

Where This Approach Falls Apart
Applied kinesiology flowcharts don't work well for acute injuries where the body is in an inflammatory cascade. During acute phases, every muscle tests weak regardless of what you're probing for. I learned that the hard way with a patient who came in after a sports concussion. We spent forty minutes running through the entire flowchart and everything came back compromised. No usable data. Waited two weeks and retested. Within ten minutes we had a clear picture of what was actually going on versus what was just noise from the acute injury. Dehydrated patients also throw off the whole system. Muscle tissue requires adequate hydration to maintain its electrical properties. If someone hasn't drunk water in twelve hours, their responses will be blunted and inconsistent. It's not a major issue in practice because people show up dehydrated constantly, but you need to factor it in. I usually just note it in the chart and flag any borderline results as potentially influenced by hydration status. The biggest limitation is probably the learning curve. You need about two hundred confirmed test-correction pairs before the flowchart stops feeling like a puzzle and starts feeling like pattern recognition. Before that threshold, you're reading the chart instead of running it. That's normal. Don't rush into using it for complex cases until you're past that point.
How I Organize the File
My current working version is organized around a central decision node with six main branches coming off it. Each branch has sub-branches that narrow down the specific intervention. I use color coding in the margins because when you're testing at speed, visual cues matter more than text. Green means structural, red means chemical, yellow means emotional, blue means nutritional. It takes less time to scan colors than to read words mid-session. The file itself lives as a laminated reference sheet at the clinic and as a searchable PDF on my phone. The laminated version is what I glance at during testing. The phone version has expandable sections with notes on edge cases I've encountered over the years. Those notes are worth more than the flowchart itself in some cases.