Educational guide
Maryland private detective firms operate under Maryland State Police licensing, Title 13, COMAR rules, and strict wiretap/electronic-surveillance review. PI Core can organize the record without deciding license status or recording legality.
Direct answer
A Maryland PI file should track Maryland State Police licensing context, agency and individual certification records, assignment scope, evidence and media, Courts and Judicial Proceedings section 10-401 and 10-402 recording review, and attorney delivery status. PI Core can make those checkpoints visible, but MSP licensing status and recording-law analysis remain practitioner-reviewed.
Regulatory framework
The Maryland PI Core page identifies MSP and Maryland's stricter recording-law posture. This guide goes deeper on license records, COMAR implementation, and why recording review should be explicit before field work.
The MSP Licensing Division publishes private detective agency and certification materials. A PI system should preserve agency, employee, certification, renewal, and compliance notes without claiming direct MSP filing.
Business Occupations and Professions Title 13 establishes private detective licensing and regulated work. The case file should identify who accepted, supervised, performed, reviewed, and delivered the assignment.
COMAR materials supply rule-level context for private detectives. These sources belong near the agency compliance record and assignments that depend on license posture.
Maryland is treated as all-party or two-party for covered recording workflow. Audio surveillance, witness interviews, phone calls, and undercover work should be reviewed before capture, not cleaned up later.
Procedure walkthrough
Maryland implementation should make license status and recording review visible before a report leaves the firm.
Record the licensed agency, certified or assigned investigator, responsible reviewer, client, attorney, subject, and scope. The file should make MSP licensing context visible without duplicating every compliance document.
Distinguish surveillance, witness work, locating, background investigation, attorney-requested investigation, and records work. Different assignment types create different recording and evidence-review questions.
Before an interview, call, or covert audio plan moves forward, the file should show consent review, participant role, attorney instruction, and whether the assignment is marked do not record.
Baltimore City, Prince George's County, Montgomery County, and other Maryland practice contexts may change court or records work. They do not change the MSP licensing anchor or the need for recording-law review.
Reports, media, transcripts, raw notes, and exhibits should show whether they are raw field material, attorney-reviewed, client-delivered, or held for legal review.
Local variation
MSP licensing is statewide. Local court, records, and attorney workflows still shape implementation.
Baltimore investigation work often supports criminal defense and civil litigation with city-specific court and records context. The Baltimore PI Core page anchors that local implementation surface.
Prince George's and Montgomery County work may involve cross-border attorney relationships and federal court-adjacent assignments. The case file should preserve local context while keeping Maryland recording review explicit.
License, certification, renewal, and complaint-response records should live in a statewide agency compliance file and be referenced from assignments.
County practice does not make Maryland a one-party workflow state. Audio plans should remain attorney or senior-investigator reviewed.
Implementation check
The implementation goal is not to automate Maryland law. It is to prevent licensing and recording context from disappearing into freeform notes.
Separate agency, certificate, employee, renewal, and reviewer fields make MSP context visible when reports or evidence records are audited.
Statuses like no audio, all-party consent needed, all-party consent documented, attorney reviewed, exception review, or do not record fit Maryland better than a simple recording toggle.
Title 13, COMAR, and wiretap statute references should be available from the compliance file and from assignments that create recording or license questions.
A Maryland migration should include one MSP compliance record, one Baltimore assignment, one witness interview plan, and one attorney-requested report package.
Practitioner review limits
PI Core can organize Maryland licensing and recording-law context. It does not decide Title 13 eligibility, COMAR compliance, section 10-401 or 10-402 recording questions, or report admissibility.
Maryland MSP private detective workflow can be represented as source references, assignment records, license-review notes, audio flags, evidence status, report drafts, and responsible owners. MSP license status, Title 13 role analysis, COMAR compliance, recording-law application, and evidence-use decisions remain reviewed outside the product.
MSP materials, Title 13, COMAR, Maryland wiretap statutes, client instructions, and attorney guidance control the operating record. PI Core can keep those instructions visible near the investigation file, but it cannot convert a firm-side note into an official license, court, or admissibility determination.
Surveillance video, audio, phone calls, witness interviews, undercover work, and third-party media require state-specific review. The file should show who reviewed recording context, what source was checked, and what instruction controlled the assignment.
Firms moving from CROSStrax, Trackops, CaseFleet, spreadsheets, or mixed folders should test active assignments, reports, evidence references, media libraries, billing notes, and attorney delivery records before cutover.
Butler workflow relevance
PI Core can track Maryland assignments, MSP license context, investigator roles, audio flags, consent notes, evidence records, attorney handoffs, report drafts, and migration review. It does not file MSP renewals or decide whether a recording is lawful.
Related Butler pages
FAQ
No. It is an educational workflow guide for investigation firms and adjacent legal teams. Licensing status, scope-of-practice questions, surveillance legality, recording-law analysis, and evidence-use decisions remain investigator, agency, attorney, court, or regulator reviewed.
No. PI Core can track audio flags, consent notes, assignment instructions, legal-review status, and source references. It does not decide whether a recording is lawful under Maryland's all-party recording-law framework or any related exception.
Private investigation work often turns on surveillance, interviews, phone calls, media capture, and attorney handoffs. Licensing explains who may perform the work; recording law helps determine how audio or communications are reviewed before they are captured, stored, delivered, or used.
Use it to build demo scenarios from real work: one surveillance assignment, one witness interview, one attorney-requested matter, one licensing or local-compliance record, and one migrated case. The evaluation should test whether source references, recordings, reports, evidence, and review owners stay together.
No. These educational pages describe firm-side organization. License applications, renewals, court petitions, regulatory submissions, official license status, and disciplinary responses remain outside the product unless a specific integration is separately validated.
Start with Maryland PI Core for geographic context, then review PI Core pricing if user count, trial timing, founding cohort eligibility, and migration are the buying questions. Bring a reviewed sample investigation file into the evaluation so product discussion stays tied to actual practice.
Sources checked
Sources combine Maryland State Police licensing pages, Title 13, COMAR, court and Attorney General context, and Maryland wiretap/electronic-surveillance statutes.
Next step
Bring one MSP license record, one Baltimore or DC-area assignment, one proposed recorded interview, and one attorney handoff into a PI Core evaluation.