Firms already write their procedures down: intake criteria, conflict checks, filing checklists, review thresholds. Helixor turns those procedures into versioned packs with a closed set of outcomes and a receipt for every decision, and leaves professional judgment with professionals.
These are examples, not a complete list. A decision usually fits when it has written criteria, pulls from several systems, happens often, and someone may later ask why it went the way it did. Pick one to jump to it.
A new matter brings the client, adverse parties, related entities, the practice area, estimated fees and the responsible partner. Intake staff run conflict searches, check the firm's criteria on fee size, credit and risk, and send the file to committee when something looks off. Every firm has a story about the matter that should never have been taken.
Intake criteria become a pack. Each matter comes back accept, refer to the intake committee, or decline, and the conflict pre-check flags the specific party or relationship that needs a look. The conflicts attorney still makes the call. Reversals and committee decisions are captured, and they shape the next version of the criteria.
{
"matter": "2026-NY-004812",
"receipt": "hx_proof_4be09d1a7c35f2e8a60b9d13",
"pack": "firm.intake_criteria v6",
"action": "refer_intake_committee",
"rules": ["INT-ADVERSE-AFFILIATE-CLIENT"],
"input_sha256": "c3e7...5a82",
"remedy": ["signed waiver from affected client"],
"logged_at": "2026-09-28T13:07:59Z"
}A prepared return comes with the prior year return, wage and 1099 forms, schedules and the preparer's notes. Firms decide how much review each return gets based on complexity, dollar changes and risk areas. In busy season that decision often comes down to whoever has capacity.
Helixor applies your review thresholds to every return: ready to file, preparer self-review, senior review, or partner review, with the reasons listed. Returns that can't be filed yet (missing authorization, identity check pending) are held with exactly what's needed. Review findings come back as outcomes for next season's thresholds.
Before a filing goes out, someone checks that every required document is present, dates line up, and the deadline has been computed correctly under the procedural rules. Most of it is checklist work, and the misses are expensive.
Each filing type gets a pack. The filing comes back ready, missing items (listed), or date conflict, before anyone signs.
In tax season, managers assign returns to preparers and reviewers from a spreadsheet. They weigh credentials, independence, client relationships, capacity and deadlines. The work piles up on the same few senior people, and extensions get filed that didn't need to be.
Credential requirements, independence rules and deadlines go into the pack. The solver assigns each return to a preparer and reviewer, balancing load, and reassigns when someone is out or a client sends documents late. Review routing from the pack decides how much review each return needs; the solver decides who does it. The pack holds the hard rules and the goal. The solver searches for the best plan that satisfies every hard rule, working from the same typed state the decision core uses. If no plan can satisfy them all, it tells you so instead of quietly breaking one. The solvers are built for GPUs, and that's where large plans solve fastest. Solvers are in Preview today.
| Decision | What Helixor decides |
|---|---|
| Team routing | Assign practice group, office and seniority, with reasoning for complex matters. |
| Privilege decisions | Not automated. These stay with people. |
| Workload | Pattern |
|---|---|
| Intake and docketing | Core runtime next to the practice management system |
| Firm-wide policy | Shared decision service behind an authenticating gateway |
| Unclear matters | Hybrid escalation, as engagement terms allow |
Pick one procedure, like the document checklist for a single filing type, and write it as a playbook. Capture corrections from the first week (reversals, reassignments, rejections). They become proposed improvements to the procedure.
Go deeper on helixor.dev: Industry guide ↗ • Deployment patterns ↗ • Core concepts ↗ • Receipts ↗
Bring a written policy and a handful of past cases. We'll turn it into a pack and run it next to your current process so you can compare.