<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[QDRO Institute: Weekly Analysis]]></title><description><![CDATA[One QDRO rejection pattern, one upstream mistake, one system fix — every Tuesday]]></description><link>https://qdroinstitute.substack.com/s/weekly-analysis</link><image><url>https://substackcdn.com/image/fetch/$s_!eTVO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3c5bbfe2-a8f0-4ffd-8475-754610e13f70_150x150.jpeg</url><title>QDRO Institute: Weekly Analysis</title><link>https://qdroinstitute.substack.com/s/weekly-analysis</link></image><generator>Substack</generator><lastBuildDate>Thu, 11 Jun 2026 10:26:19 GMT</lastBuildDate><atom:link href="https://qdroinstitute.substack.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Hernsy the Elder]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[qdroinstitute@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[qdroinstitute@substack.com]]></itunes:email><itunes:name><![CDATA[Judge Hernsberger (Ret.)]]></itunes:name></itunes:owner><itunes:author><![CDATA[Judge Hernsberger (Ret.)]]></itunes:author><googleplay:owner><![CDATA[qdroinstitute@substack.com]]></googleplay:owner><googleplay:email><![CDATA[qdroinstitute@substack.com]]></googleplay:email><googleplay:author><![CDATA[Judge Hernsberger (Ret.)]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[TRS Needs to Know Who's Who. You Have to Prove It]]></title><description><![CDATA[The rejection that has nothing to do with your QDRO &#8212; and everything to do with what you forgot to include.]]></description><link>https://qdroinstitute.substack.com/p/trs-needs-to-know-whos-who-you-have</link><guid isPermaLink="false">https://qdroinstitute.substack.com/p/trs-needs-to-know-whos-who-you-have</guid><dc:creator><![CDATA[Judge Hernsberger (Ret.)]]></dc:creator><pubDate>Tue, 12 May 2026 14:02:15 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!eTVO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3c5bbfe2-a8f0-4ffd-8475-754610e13f70_150x150.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The QDRO was drafted correctly. The decree was consistent. The right form was used. Everything looked good.</p><p>TRS rejected it.</p><p>The rejection letter said: *&#8221;The alternate method of verifying the social security numbers has not been provided to TRS.&#8221;*</p><p>This is not a QDRO problem. The order itself may be perfect. TRS simply cannot process it until it can verify who the parties are &#8212; and that verification requires a separate document.</p><p>TRS accepts three methods of SSN verification:</p><p>A letter from the attorney of record confirming the social security number. Or a sworn statement signed before a notary public confirming the social security number, if the party is not represented by counsel. Or the completion of <strong>Form TRS 629</strong> &#8212; the Verification of Social Security Number for Qualification of a Domestic Relations Order. Form 629 must be signed before a notary and can be completed by either or both parties.</p><p>Most attorneys use Form 629. And most attorneys forget to include it.</p><p>Here&#8217;s what makes this rejection particularly painful: Form 629 is not filed with the court. It is not part of the QDRO. It is a companion document that must be included when you mail the certified QDRO to TRS. If you mail the QDRO without it, TRS rejects the submission &#8212; not because the QDRO is wrong, but because TRS can&#8217;t verify the parties&#8217; identities.</p><h3>The upstream mistake</h3><p>Nobody told the attorney about Form 629. Or the attorney knew about it but forgot to arrange signatures and notarization before submitting. Or the paralegal mailed the QDRO package without checking whether Form 629 was included.</p><p>This is a procedural failure &#8212; a Fit 4 (Procedural Misalignment) under the Five Fits Framework&#8482;. The order is substantively correct. The submission is incomplete.</p><h3>The system fix</h3><p>In the Controlled Pipeline&#8482;, Form 629 is surfaced at three stages:</p><p><strong>Stage 1 (intake):</strong> When TRS is identified as the plan, the system adds Form 629 to the document checklist and explains what it is &#8212; signed by both parties, notarized, not filed with the court.</p><p><strong>Stage 5 (negotiation):</strong> The system reminds the attorney that both parties must sign Form 629. If both parties are present at mediation, this is the time to arrange signatures. Don&#8217;t wait until after the decree is signed and the other party has disappeared.</p><p><strong>Stage 10 (submission):</strong> The pre-submission checklist includes Form 629 as a required companion document. The system blocks submission if Form 629 hasn&#8217;t been confirmed as complete, signed, and notarized.</p><p>Three reminders at three stages. The attorney never has to remember it. The system remembers for him.</p><p><strong>A QDRO is not a document. It&#8217;s a system.</strong></p>]]></content:encoded></item><item><title><![CDATA[TRS Can't Read What the Clerk Covered Up]]></title><description><![CDATA[A rejection caused by a certification stamp &#8212; and the one-minute fix that prevents it]]></description><link>https://qdroinstitute.substack.com/p/trs-cant-read-what-the-clerk-covered</link><guid isPermaLink="false">https://qdroinstitute.substack.com/p/trs-cant-read-what-the-clerk-covered</guid><dc:creator><![CDATA[Judge Hernsberger (Ret.)]]></dc:creator><pubDate>Tue, 05 May 2026 14:00:49 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!eTVO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3c5bbfe2-a8f0-4ffd-8475-754610e13f70_150x150.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The QDRO was correct. Every field was filled in properly. The dates of marriage and end date for division of benefits were clearly stated in the order. The attorney did everything right.</p><p>TRS rejected it anyway.</p><p>The rejection letter cited 34 TAC &#167;47.10(b)(9) &#8212; the rule requiring the order to clearly specify the date of the marriage and end date for division of benefits. The explanation:</p><p><em>&#8221;The seal of the clerk of the court obscured all or part of these dates. The dates must be clearly legible for TRS to accurately calculate the amount awarded to Alternate Payee.&#8221;</em></p><p>The clerk&#8217;s certification stamp &#8212; the big embossed seal that proves the document is a certified copy &#8212; landed right on top of the dates. TRS couldn&#8217;t read them. And TRS won&#8217;t guess.</p><p>This is not a drafting failure. It&#8217;s not a negotiation failure. It&#8217;s a submission failure. And it&#8217;s one of the most frustrating rejections an attorney can receive because the order itself was fine.</p><h3>The upstream mistake</h3><p>The attorney (or paralegal) picked up the certified copy from the clerk&#8217;s office, put it in an envelope, and mailed it to TRS without checking whether the certification stamp obscured any text. A ten-second visual inspection would have caught it.</p><h3>The system fix</h3><p>In the Controlled Pipeline&#8482;, Stage 10 (submission) includes a pre-submission checklist. One item on that checklist:</p><p><strong>&#8221;Inspect the certified copy. Confirm that the clerk&#8217;s seal does not obscure any text, particularly dates, names, and identification numbers. If any text is obscured, request a new certified copy from the clerk before submitting.&#8221;</strong></p><p>The fix is simple: ask the clerk to prepare a certified copy without obstructing any portion of the text of the order. Most clerks will do this if you ask. Most attorneys never think to ask &#8212; because they don&#8217;t know TRS reads every character literally.</p><p>The system knows. The checklist reminds you. The rejection never happens.</p><p><strong>A QDRO is not a document. It&#8217;s a system</strong>.</p>]]></content:encoded></item><item><title><![CDATA[TRS Gave You the Language. Use It]]></title><description><![CDATA[The rejection that happens when attorneys try to improve on perfection.]]></description><link>https://qdroinstitute.substack.com/p/trs-gave-you-the-language-use-it</link><guid isPermaLink="false">https://qdroinstitute.substack.com/p/trs-gave-you-the-language-use-it</guid><dc:creator><![CDATA[Judge Hernsberger (Ret.)]]></dc:creator><pubDate>Tue, 28 Apr 2026 14:01:11 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!eTVO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3c5bbfe2-a8f0-4ffd-8475-754610e13f70_150x150.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The attorney reviewed the TRS model order and decided it needed improvement. A paragraph was added to clarify the division method. A sentence was modified to better reflect the decree language. A provision was inserted to address a contingency the model didn&#8217;t cover.</p><p>All reasonable instincts. All wrong.</p><p>TRS rejected the order.</p><p>The rejection didn&#8217;t say &#8220;your added language is incorrect.&#8221; It said the order did not comply with the required format. Because TRS has a bright-line rule that most attorneys don&#8217;t know:</p><p><strong>Nothing may be added to the TRS model form. Nothing may be removed.</strong></p><p>The model order language is prescribed by Chapter 804 of the Texas Government Code and the administrative rules developed by the TRS Board of Trustees. TRS created its model by closely following the terms of state law. When you add language, you introduce the possibility of conflict with the statutory provisions the model was designed to implement. When you remove language, you eliminate a provision TRS requires.</p><p>The attorney who &#8220;improved&#8221; the form created a rejection that didn&#8217;t need to exist.</p><h3>The upstream mistake</h3><p>This one is a knowledge gap, not a process failure. The attorney didn&#8217;t know about the bright-line rule because nobody told him. It&#8217;s not intuitive &#8212; most ERISA plan administrators accept custom QDRO language as long as the required elements are present. TRS is not an ERISA plan. TRS does not accept custom language. Period.</p><h3>The system fix</h3><p>In the Controlled Pipeline&#8482;, this rule is enforced at two points. At Stage 8 (drafting), the system generates the QDRO from the TRS model template &#8212; not from a blank document. The attorney fills in the variable fields. The model language is locked. You can&#8217;t add to it or modify it because the system doesn&#8217;t let you.</p><p>At Stage 9 (pre-submission review), the system confirms that the generated document matches the TRS template exactly. If anything has been altered outside the approved fill-in fields, the system flags it and blocks submission.</p><p>The QI Advisor&#8482; knows this rule. Ask it: &#8220;Can I add a paragraph to the TRS form addressing early retirement?&#8221; The answer comes back immediately: &#8220;No. TRS requires exact use of their approved form. No language may be added or removed. Any modification will result in rejection.&#8221;</p><p>The attorney doesn&#8217;t need to memorize the rule. The system enforces it.</p><p><strong>A QDRO is not a document. It&#8217;s a system.</strong></p>]]></content:encoded></item><item><title><![CDATA[She Was Already Retired. Nobody Checked.]]></title><description><![CDATA[The most preventable TRS rejection &#8212; and the one intake question that would have stopped it.]]></description><link>https://qdroinstitute.substack.com/p/she-was-already-retired-nobody-checked</link><guid isPermaLink="false">https://qdroinstitute.substack.com/p/she-was-already-retired-nobody-checked</guid><dc:creator><![CDATA[Judge Hernsberger (Ret.)]]></dc:creator><pubDate>Tue, 21 Apr 2026 17:09:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!eTVO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3c5bbfe2-a8f0-4ffd-8475-754610e13f70_150x150.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A QDRO was submitted to TRS using Form 154 &#8212; the model order for active members.</p><p>TRS rejected it. One sentence in the rejection letter told the whole story:</p><blockquote><p><em>According to TRS records, Participant retired effective May 31, 2021. Since the Participant was already retired as of the date of divorce, the model order for retirees must be used.</em></p></blockquote><p>The attorney didn&#8217;t know the member was retired. The intake didn&#8217;t ask. The file didn&#8217;t say. So the preparer used the active member form &#8212; Form 154 &#8212; because that&#8217;s what the limited information suggested.</p><p>The fix sounds simple: switch to Form 155 and resubmit.</p><p>It&#8217;s not simple.</p><p>Form 155 is a different world. The retiree has already selected an annuity option &#8212; standard or optional. That selection is irrevocable. The QDRO can&#8217;t change it. She may have elected a Partial Lump Sum Option at retirement. The decree doesn&#8217;t address it, because nobody knew she was retired when the settlement was negotiated.</p><p>The survivor benefit is already locked in. The division options available under Form 155 are fundamentally different from those under Form 154. The decree language &#8212; written for an active member scenario &#8212; may not work for a retiree at all.</p><p>Two rejections. Neither caused by bad drafting. Both caused by a question that should have been asked at intake:</p><p><strong>&#8220;Is the member active or retired?&#8221;</strong></p><h2><strong>The upstream mistake</strong></h2><p>This rejection was born at Stage 1 &#8212; intake. The attorney or paralegal never verified the member&#8217;s employment status against TRS records. They assumed. The assumption was wrong. Everything downstream inherited the error.</p><h2><strong>The system fix</strong></h2><p>In the Controlled Pipeline&#8482;, Stage 1 requires the answer to this question before the case can advance. The system asks: Is the member active, vested, or retired? The answer is verified against plan records &#8212; not the client&#8217;s description, not the attorney&#8217;s guess. The case cannot move to Stage 2 without a verified answer.</p><p>If the answer is &#8220;retired,&#8221; the system routes to the retiree workflow. It loads Form 155. It surfaces the variables that must be resolved before negotiation &#8212; annuity option, PLSO election, current beneficiary. The attorney walks into mediation knowing the constraints. The decree reflects reality. The QDRO uses the right form.</p><p>One question at intake. Verified, not assumed. That&#8217;s the difference between an approved QDRO and two rejections.</p><p><strong>A QDRO is not a document. It&#8217;s a system.</strong></p>]]></content:encoded></item></channel></rss>