CaseLink MDT

What it is

A case spine that dispatch, evidence, EMS, and K9 all attach to, so a suspect's history, the linked custody chain, and the medical report live in one file instead of five resources that never met. Authority is resolved on the server per job and grade. For owners running a law faction that keeps losing the thread between scene and court. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. Escrow split publishes at release. In development; no runtime proof published — pending Shadow bench.

The problem it exists for

An MDT is the piece every police department touches every shift, and it's usually the piece that knows the least. It doesn't know what the evidence system logged, the dispatch call it was attached to, or the charge history sitting in another resource's table. So officers narrate the record to each other over voice, the story lives in someone's memory instead of the database, and the scene dies while three people type the same information into three places.

Why we're building it

MDT is the most expensive single script we recorded in our July 2026 survey of 13 stores — $69.99, though that's a single observation and a thin sample rather than a market rate (see /guides/fivem-script-prices). Something that costs the most and integrates the least is the definition of a category worth rebuilding. We're building it as one record the whole justice chain shares rather than another silo with a nicer interface.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed to share one record across the law-and-order pillar — the same case a dispatcher opens, an officer amends, and an evidence entry attaches to.
• Designed around append-only history: an amended report should show that it was amended, by whom, when — not silently overwrite what was there.
• Designed to be readable during a scene, not after it, because a system that requires you to stop roleplaying to use it doesn't get used.
• Designed to run through the same ForgeCore bridge as everything else we ship, so your framework choice stays reversible (see /guides/fivem-framework-lock-in).

What is not proven

The section every product page should have and almost none do.

• It is not released. There is nothing to buy, nothing to download, and no server of ours you can join to watch it work.
• No runtime proof published — pending Shadow bench. Nothing about it has been demonstrated under load in front of anybody, and until that happens every capability above is design intent.
• No performance figure exists. resmon reads [MEASURED-PENDING] and will keep reading that until a real client produces a real number on a real server.
• The $44.99 planned price is a target against the bands in our own survey, not a commitment, and it can move before the studio pricing lock.
• We have not published a release date because we do not have one. A date we invented would be the first thing we'd break.

What we're building toward

A case file assembling itself as evidence, an EMS report, and a K9 hit snap into place.

Current status, stated exactly

• resmon [measured-pending]
• escrow manifest — at release
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any law & order resource

This applies to every product in this category, ours included, whenever it arrives. Hold CaseLink MDT to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask what happens to a report when it's edited. If the answer is that it changes, there is no audit trail — you have a document, not a record.
• Ask what it shares with the evidence and dispatch systems. 'Integrates' means nothing; ask which table, which export, which event.
• Ask for the measured resmon figure with its method and its date. An MDT with an open NUI is a UI that can idle expensively (see /guides/fivem-resmon-script-performance).
• Ask which files ship escrowed. An MDT you can't extend is an MDT that will never match your department's actual procedure (see /guides/fivem-asset-escrow-explained).
• Ask whether every net event validates the source. An MDT is a database write endpoint exposed to every client on your server (see /guides/fivem-server-security-net-events).

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.