CaseLink MDT

The problem it exists to solve

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

• 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 we have not proven

How to judge any product in this category — ours included

• 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).

Frequently asked