Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

Ticket Queues Don't Understand Casework. What Labs Need Instead

11/19/2026

It's Wednesday morning. The toxicology section's instrument stopped sending results to the LIMS after a routine update the night before, and an analyst has testimony on Monday in a case whose batch is stuck. The supervisor opens a ticket. The technician who calls back has never seen the lab, asks what the LIMS is, and suggests a reboot. By the time the ticket reaches someone who can actually help, it's Friday afternoon and the weekend is gone.

Most supervisors have lived some version of that week. The people working the queue are usually capable and stretched thin. They work inside a support model built for printers, passwords, and laptops, and a forensic lab runs on instruments, validated software, accreditation, and court dates. That mismatch is why lab problems take so long to fix, and why the supervisor ends up spending hours explaining the lab to someone new on every call.

At a glance

  • Generic ticket queues start from zero on each call, which costs analyst hours and puts turnaround and testimony dates at risk.
  • Lab IT has to work within validation and change control under ISO/IEC 17025, so even small changes need planning with the quality team.
  • A better model pairs a named advisor and a documented environment with clear escalation, working alongside agency IT.

Why ticket queues struggle with lab work

Help desks are designed for volume. Tickets get a category and a priority, then go to whoever is next. That works well for a locked account or a broken monitor, where any trained technician can follow the same steps.

Lab problems rarely fit a category. A failed data transfer might involve the instrument's vendor software, the workstation it runs on, a network share, the LIMS interface, and a security agent that started blocking a file. Fixing it takes someone who knows how those pieces connect in your lab. When each ticket lands with a different person, that knowledge has to be rebuilt every time, and the supervisor is the one rebuilding it.

What the help desk can't see

Most of what makes a lab different is invisible from a ticketing system. Instrument workstations often run vendor software that's supported only on specific operating system versions, which means they can't follow the standard patch schedule. The data path from an instrument to the LIMS may run through a folder, a script, or middleware that one person set up years ago. Service contracts, vendor contacts, and the rules about who may touch a validated system usually live in a binder or in someone's memory.

Without that context written down, the same conversations repeat. The supervisor draws the same diagram, explains why the workstation can't take the update, and reads off the same vendor support number. Each repetition is time taken away from casework, review, and the supervision the job is supposed to be about.

Change control has to respect validation

ISO/IEC 17025 expects accredited labs to control their data and information management systems. Clause 7.11 covers this area, and it expects software used to collect, process, record, report, store, or retrieve data to be validated before use and again after changes. Commercial software used within its designed range can generally be considered validated, though the lab remains responsible for how it's configured in its own environment. In practice, changes to a LIMS or instrument software need to be authorized, tested, and documented before they go live.

A general IT change process isn't usually built around a quality manager's sign-off. That creates two bad outcomes. Sometimes a routine update reaches a validated system and breaks a workflow nobody tested. Other times the lab, wary of that risk, blocks every change, and its systems age without security updates. Either one leaves the lab with something to explain later, to an assessor or in court.

The fix is a shared change process. Plan changes with the quality team, test them against the validated workflow, record what changed, and keep a back-out plan ready. NIST's guide to security-focused configuration management treats managing and monitoring system configurations as part of security itself, which gives IT and quality a common reason to keep that record current.

Casework deadlines don't wait for escalation

A lab's priorities come from turnaround commitments, discovery requests, and court dates. A help desk's priorities come from its service level agreement, which may treat a stuck instrument batch the same as a slow laptop. When testimony is days away, a ticket waiting in line for its next escalation is a real risk to the case.

Instruments also keep their own hours. Long sequences often run overnight or through the weekend, and a failure at 2 a.m. can cost a full day of analysis if nobody responds until morning. Support for a lab needs an after-hours path for the systems that run unattended, and a priority scheme that reflects casework, so a blocked batch with a court date outranks a new monitor request.

Vendor coordination falls through the cracks

When something breaks between systems, every party has a reasonable claim that the cause is somewhere else. The instrument vendor points to the network. Agency IT points to the vendor software. The LIMS provider asks for logs nobody has collected. The supervisor ends up coordinating three organizations while also running the section.

Someone needs to own that call from start to finish. That person should already have the contract details, the support contacts, the configuration records, and the authority to bring each vendor in. When the owner knows the environment, the conversation with a vendor starts with evidence and moves faster.

What a better support model looks like

The model that works for labs is built around continuity. Each piece below answers one of the problems above.

  • A named advisor
    • What it looks like in practice: One senior person who knows your instruments, LIMS, and staff, and picks up when you call
  • A documented environment
    • What it looks like in practice: Current records of instruments, workstations, data paths, validated configurations, and vendor contacts
  • Change control that respects validation
    • What it looks like in practice: Changes planned with quality, tested, documented, and paired with a back-out plan
  • Clear escalation
    • What it looks like in practice: Priorities tied to casework, an after-hours path for instruments, and named vendor contacts
  • A written split with agency IT
    • What it looks like in practice: Agreement on who owns the network, identity, endpoints, and lab systems

The lab keeps its existing tools, vendors, and contracts. What it gains is one person and one set of records that stay with it over time.

Co-managed support alongside agency IT

Many labs sit inside a city, county, or state agency with its own IT department, and that department usually does a lot well. It runs the network, identity, email, and enterprise systems that the whole agency depends on. Replacing it is rarely the goal. The gap is lab-specific depth: instruments, LIMS interfaces, validated changes, and the escalation paths casework needs.

A co-managed arrangement fills that gap. Agency IT keeps ownership of shared infrastructure, and a lab-focused partner takes on the instruments, lab applications, change coordination with quality, and vendor management. The split is written down, so a problem is routed to the right owner on the first call. You can read more about how a co-managed IT model divides that work.

Start with your last bad week

List the last three lab IT problems your section hit. For each one, note how long it took to resolve, how many people were involved, and how many times someone had to explain the lab from the beginning. That short list usually shows where the time is going, and what a different model would need to change.

At CTP, we support forensic labs with one named senior advisor who learns the environment and stays with it, alongside the agency IT team you already have. See how we structure managed IT for forensic laboratories, or schedule a conversation about how support works in your lab today.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us