<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TrueNext Global</title>
    <description>The latest articles on DEV Community by TrueNext Global (@truenextglobal).</description>
    <link>https://dev.to/truenextglobal</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4256228%2F46d63222-ede8-4790-b25c-f8ff6d5e9067.png</url>
      <title>DEV Community: TrueNext Global</title>
      <link>https://dev.to/truenextglobal</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/truenextglobal"/>
    <language>en</language>
    <item>
      <title>Designing a ticket triage rubric your support team will apply the same way every time</title>
      <dc:creator>TrueNext Global</dc:creator>
      <pubDate>Sun, 22 Nov 2026 04:57:53 +0000</pubDate>
      <link>https://dev.to/truenextglobal/designing-a-ticket-triage-rubric-your-support-team-will-apply-the-same-way-every-time-3klg</link>
      <guid>https://dev.to/truenextglobal/designing-a-ticket-triage-rubric-your-support-team-will-apply-the-same-way-every-time-3klg</guid>
      <description>&lt;p&gt;Most support queues have a priority field. Far fewer have a shared definition of what the values mean. The result is predictable: one agent marks a password reset "High" because the customer sounded upset, another marks a broken checkout "Normal" because it came in through a low-priority channel. Your SLA reports then measure mood, not urgency.&lt;/p&gt;

&lt;p&gt;A triage rubric fixes that. Here's how to build one that two people, in two time zones, will score the same way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Score two dimensions, not one
&lt;/h2&gt;

&lt;p&gt;"Priority" mixes two separate questions. Ask them separately:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Impact: how many people or how much money is affected?&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Score&lt;/th&gt;
&lt;th&gt;Definition&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;All customers, a whole tenant, or anything touching payments, security or data loss&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;One customer's team, or one feature broken for several customers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;One user, with a workaround available&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Urgency: what happens if this waits until tomorrow?&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Score&lt;/th&gt;
&lt;th&gt;Definition&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Work is stopped now, or a deadline lands within 4 hours&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Work is slowed; a deadline lands within 2 business days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Inconvenient, no deadline&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Every definition is something an agent can check from the ticket, not a feeling. "Customer is angry" isn't in either table on purpose.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Map the scores to a priority
&lt;/h2&gt;

&lt;p&gt;Multiply or use a lookup grid. A grid is easier to read at 2 a.m.:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Urgency 1&lt;/th&gt;
&lt;th&gt;Urgency 2&lt;/th&gt;
&lt;th&gt;Urgency 3&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Impact 3&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;P2&lt;/td&gt;
&lt;td&gt;P1&lt;/td&gt;
&lt;td&gt;P1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Impact 2&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;P3&lt;/td&gt;
&lt;td&gt;P2&lt;/td&gt;
&lt;td&gt;P1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Impact 1&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;P4&lt;/td&gt;
&lt;td&gt;P3&lt;/td&gt;
&lt;td&gt;P2&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Then attach a response target and an owner to each level, for example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;P1:&lt;/strong&gt; acknowledge in 15 minutes, page the on-call engineer, update the customer every hour.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;P2:&lt;/strong&gt; acknowledge in 1 hour, assign to a named agent, escalate to tier 2 if not resolved in 4 hours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;P3:&lt;/strong&gt; first response same business day.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;P4:&lt;/strong&gt; first response within 2 business days; candidate for a help-center article.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use your own numbers. The point is that each priority triggers a specific action, not just a colour.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Add override rules, and keep the list short
&lt;/h2&gt;

&lt;p&gt;Some tickets should skip the grid. Write these down explicitly so nobody has to judge it on the spot:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Any suspected security incident or data exposure → P1, regardless of scores.&lt;/li&gt;
&lt;li&gt;Any report that a payment was taken twice or not refunded → at least P2.&lt;/li&gt;
&lt;li&gt;A ticket reopened for the second time → raise one level and assign to a lead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three to five overrides is plenty. If the list grows past that, your impact and urgency definitions need work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Write five worked examples
&lt;/h2&gt;

&lt;p&gt;Definitions alone leave room for interpretation. Real examples close it. Pick tickets from your own history and score them in the rubric document:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;em&gt;"I can't log in, reset link isn't arriving."&lt;/em&gt; One user, workaround (support can resend or verify manually), no deadline → Impact 1, Urgency 2 → &lt;strong&gt;P3&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"Our whole team gets a 500 error on the dashboard."&lt;/em&gt; One customer's team, work stopped → Impact 2, Urgency 3 → &lt;strong&gt;P1&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"Export to CSV puts dates in the wrong format."&lt;/em&gt; Several customers, workaround exists, no deadline → Impact 2, Urgency 1 → &lt;strong&gt;P3&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"Payroll export fails and payroll runs at 3 p.m. today."&lt;/em&gt; One team, deadline within 4 hours → Impact 2, Urgency 3 → &lt;strong&gt;P1&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"Can you add dark mode?"&lt;/em&gt; Feature request → route out of the incident queue entirely.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Example 4 is the one that teaches the most: the same feature as a routine bug becomes P1 because of the deadline. That's what the urgency axis is for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Calibrate before you roll it out
&lt;/h2&gt;

&lt;p&gt;Pull 20 recent tickets. Have three agents score them independently with the rubric, without discussing. Then compare:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where all three agree, the definitions are working.&lt;/li&gt;
&lt;li&gt;Where they disagree, find the word that caused it ("several", "slowed", "deadline") and tighten it.&lt;/li&gt;
&lt;li&gt;Repeat with a fresh 20 until disagreements are rare and explainable.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This takes an hour and saves weeks of arguing about SLA breaches.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Put the rubric where the decision happens
&lt;/h2&gt;

&lt;p&gt;A rubric in a wiki nobody opens doesn't exist. Practical placements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Make Impact and Urgency required dropdowns on the ticket form, and compute priority from them with a helpdesk automation.&lt;/li&gt;
&lt;li&gt;Pin the grid and the overrides as the first macro or saved reply agents see.&lt;/li&gt;
&lt;li&gt;Include the five worked examples in onboarding for every new agent, including contractors and offshore team members, who often join without the hallway context everyone else picked up.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 7: Review it monthly
&lt;/h2&gt;

&lt;p&gt;Once a month, pull every ticket where the priority was changed after triage. Each change is either an agent error (coaching) or a rubric gap (edit the definitions). Track the count; it should fall.&lt;/p&gt;

&lt;h2&gt;
  
  
  A one-page template
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;TRIAGE RUBRIC v1 (owner: ____, reviewed: ____)
Impact:   3 = all customers / payments / security / data loss
          2 = one team, or one feature for several customers
          1 = one user, workaround exists
Urgency:  3 = stopped now, or deadline &amp;lt; 4 h
          2 = slowed, or deadline &amp;lt; 2 business days
          1 = no deadline
Grid:     see table; P1–P4
Overrides: security → P1; double charge → ≥P2; 2nd reopen → +1 level
Targets:  P1 15 min / P2 1 h / P3 same day / P4 2 days
Examples: (paste your five)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A consistent rubric is what makes a distributed support team work: when everyone scores tickets the same way, a hand-off between shifts doesn't change what "urgent" means. We set up this kind of structure when we &lt;a href="https://www.truenextglobal.com/how-it-works/" rel="noopener noreferrer"&gt;build dedicated support teams&lt;/a&gt;, and it's the first document we ask for.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Written by the TrueNext Global team. Drafted with AI writing tools for TrueNext Global.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>management</category>
      <category>productivity</category>
      <category>support</category>
    </item>
    <item>
      <title>How we built a no-signup calculator that runs entirely in the browser</title>
      <dc:creator>TrueNext Global</dc:creator>
      <pubDate>Sun, 22 Nov 2026 04:57:11 +0000</pubDate>
      <link>https://dev.to/truenextglobal/how-we-built-a-no-signup-calculator-that-runs-entirely-in-the-browser-1m5p</link>
      <guid>https://dev.to/truenextglobal/how-we-built-a-no-signup-calculator-that-runs-entirely-in-the-browser-1m5p</guid>
      <description>&lt;p&gt;We publish two small calculators for home care agencies: one estimates what claim denials and slow collections cost in a year, the other estimates what electronic visit verification (EVV) exceptions cost in staff time and held billing. Both had the same requirements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No account, no email gate, no "book a demo to see your result".&lt;/li&gt;
&lt;li&gt;Nothing the visitor types leaves their browser.&lt;/li&gt;
&lt;li&gt;The math is visible, so a finance person can check it.&lt;/li&gt;
&lt;li&gt;Results can still be shared with a colleague.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those requirements turned out to shape the architecture more than any framework choice did. Here's the pattern, in case you're building something similar.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Put the formula in one pure function
&lt;/h2&gt;

&lt;p&gt;The whole calculator is a single TypeScript function: inputs in, numbers out, no DOM, no network.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;EvvInput&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;visits&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;        &lt;span class="c1"&gt;// EVV-covered visits per week&lt;/span&gt;
  &lt;span class="n"&gt;exceptionRate&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// % of visits needing manual correction&lt;/span&gt;
  &lt;span class="n"&gt;fixMinutes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;    &lt;span class="c1"&gt;// minutes to correct one exception&lt;/span&gt;
  &lt;span class="n"&gt;hourlyCost&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;    &lt;span class="c1"&gt;// loaded hourly staff cost&lt;/span&gt;
  &lt;span class="n"&gt;visitValue&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;    &lt;span class="c1"&gt;// billable amount per visit&lt;/span&gt;
  &lt;span class="n"&gt;openAtBilling&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// % of exceptions still open at billing&lt;/span&gt;
  &lt;span class="n"&gt;neverPaid&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;     &lt;span class="c1"&gt;// % of held visits never paid&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;pct&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;min&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;pos&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Number&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isFinite&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;n&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;n&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;evvCost&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;EvvInput&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Object&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;fromEntries&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nb"&gt;Object&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;entries&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;k&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;v&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;k&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;pos&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Number&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;v&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="kt"&gt;unknown&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;EvvInput&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;exceptions&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;visits&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nf"&gt;pct&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;exceptionRate&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;exceptions&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;fixMinutes&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;60&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;held&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;exceptions&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nf"&gt;pct&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;openAtBilling&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;visitValue&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;staffAnnual&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;hourlyCost&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;52&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;lostAnnual&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;held&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nf"&gt;pct&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;neverPaid&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;52&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;exceptions&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fte&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;40&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;staffAnnual&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;lostAnnual&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
           &lt;span class="n"&gt;total&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;staffAnnual&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;lostAnnual&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two small helpers do a lot of work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;pos()&lt;/code&gt; turns &lt;code&gt;NaN&lt;/code&gt;, &lt;code&gt;Infinity&lt;/code&gt;, negatives and empty strings into &lt;code&gt;0&lt;/code&gt;. A half-typed input never produces &lt;code&gt;NaN&lt;/code&gt; on screen.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;pct()&lt;/code&gt; clamps percentages to 0–100. Someone typing &lt;code&gt;150&lt;/code&gt; into a rate field gets 100%, not a result that's impossible on its face.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because the function is pure, it's trivial to unit test with a table of inputs and expected outputs, and the same function can run on both the server and the client.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Render a worked example at build time
&lt;/h2&gt;

&lt;p&gt;The page is static (Astro, but any SSG works). At build time we call the same function with a set of example inputs and render the result into the HTML. That gives us three things for free:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The page shows a real answer before any JavaScript runs.&lt;/li&gt;
&lt;li&gt;Search engines and people using reader mode see a complete worked example, not an empty form.&lt;/li&gt;
&lt;li&gt;The "method" section can quote the example numbers, so the explanation and the calculator never drift apart.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On the client, a small script imports the &lt;em&gt;same&lt;/em&gt; module and recalculates on every &lt;code&gt;input&lt;/code&gt; event. There's one source of truth for the math.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Show every formula in plain language
&lt;/h2&gt;

&lt;p&gt;Under the form we list each formula in words, for example:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Staff hours per week = exceptions per week × minutes to fix ÷ 60&lt;br&gt;
FTEs = staff hours per week ÷ 40&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This matters more than it sounds. The audience is operations and billing people who will reasonably distrust a black-box number. If they can redo the arithmetic on paper, they'll use the number in a budget conversation. We also say which inputs are assumptions (the 40-hour FTE, the 52-week year) so they can adjust.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Keep state in the URL, not in storage or a backend
&lt;/h2&gt;

&lt;p&gt;"Nothing is stored" rules out saving results to a database. But people still want to send a result to their manager. The answer is the query string:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;writeUrl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;HTMLFormElement&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;params&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;URLSearchParams&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;el&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelectorAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'input'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;params&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;el&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;el&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;history&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replaceState&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sb"&gt;`?${params}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(Simplified here.) On load, the script reads &lt;code&gt;location.search&lt;/code&gt;, fills the form, and recalculates. A "Copy a link to this result" button puts the URL on the clipboard. Nobody's numbers are stored by us; the link holds them, and the visitor decides who gets it.&lt;/p&gt;

&lt;p&gt;Two cautions if you copy this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use &lt;code&gt;replaceState&lt;/code&gt;, not &lt;code&gt;pushState&lt;/code&gt;, or every keystroke becomes a history entry and the back button breaks.&lt;/li&gt;
&lt;li&gt;Validate everything you read from the URL through the same &lt;code&gt;pos()&lt;/code&gt;/&lt;code&gt;pct()&lt;/code&gt; helpers. A URL is user input.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Make the privacy claim true, then say it
&lt;/h2&gt;

&lt;p&gt;"Runs in your browser" is only honest if it's literally true. Our checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No &lt;code&gt;fetch&lt;/code&gt;, XHR or beacon in the calculator script.&lt;/li&gt;
&lt;li&gt;Inputs aren't written to &lt;code&gt;localStorage&lt;/code&gt; or cookies.&lt;/li&gt;
&lt;li&gt;If you run analytics, check what it captures: many tools record the full URL, query string included, so strip or exclude the calculator parameters.&lt;/li&gt;
&lt;li&gt;Open DevTools → Network, type into the form, and confirm no request fires. Do this before every release, not once.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then state it in one short sentence near the form. Vague privacy copy ("we respect your data") is worth less than a specific, checkable claim.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Accessibility basics that are easy to miss
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;type="number"&lt;/code&gt; with &lt;code&gt;inputmode="decimal"&lt;/code&gt; gives a numeric keyboard on phones.&lt;/li&gt;
&lt;li&gt;Each input has a real &lt;code&gt;&amp;lt;label&amp;gt;&lt;/code&gt; and an &lt;code&gt;aria-describedby&lt;/code&gt; hint explaining the unit.&lt;/li&gt;
&lt;li&gt;The result container has &lt;code&gt;aria-live="polite"&lt;/code&gt;, so screen readers announce updates without interrupting typing.&lt;/li&gt;
&lt;li&gt;Prefixes like &lt;code&gt;$&lt;/code&gt; and suffixes like &lt;code&gt;%&lt;/code&gt; sit outside the input, marked &lt;code&gt;aria-hidden&lt;/code&gt;, so the label carries the meaning.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What we'd tell anyone building one
&lt;/h2&gt;

&lt;p&gt;Start from the formula and the trust problem, not the UI. A pure function, a build-time worked example, formulas in plain words and URL-only state get you a tool that loads instantly, works without JavaScript for reading, and makes a privacy promise you can actually keep.&lt;/p&gt;

&lt;p&gt;If you want to see the pattern in practice, both calculators are on our &lt;a href="https://www.truenextglobal.com/tools/" rel="noopener noreferrer"&gt;free tools page&lt;/a&gt;. Open DevTools while you use them; the Network tab should stay quiet.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Written by the TrueNext Global team. Drafted with AI writing tools for TrueNext Global.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>frontend</category>
      <category>javascript</category>
      <category>typescript</category>
    </item>
  </channel>
</rss>
