Educational guide
Texas Article 39 discovery is statewide law applied through county criminal practice.
Texas defense teams work with Article 39.14 discovery obligations, eFileTexas context, local court rules, and major-county variations. The workflow should keep statutory references and county practice visible without claiming automated legal analysis.
Direct answer
Article 39.14 discovery needs a request, receipt, review, and gap-tracking workflow.
The Michael Morton Act expanded Texas discovery through Article 39.14, but defense practices still need disciplined matter-level tracking: request status, prosecution production, law enforcement materials, witness or exhibit categories, missing items, supplemental production, local rules, and motion strategy. Legal Core can organize this record; attorneys decide compliance and response.
Article 39.14 is the core disclosure statute
Article 39.14 is where Texas practitioners commonly start for modern discovery. The matter record should preserve the request, production, item categories, review status, and any exculpatory, impeachment, or mitigation issue counsel identifies.
Court rules and local practice shape execution
Texas trial courts are local in practice. District courts, county courts at law, municipal courts, and local rules affect the filing packet, hearing, and follow-up workflow even when the discovery statute is statewide.
eFileTexas is filing context, not discovery analysis
eFileTexas can matter for motions, notices, and filing packets, but this page does not claim direct eFileTexas integration. Firms should distinguish filing status from discovery completeness.
Ethics and technology review remain lawyer duties
Texas lawyers remain responsible for confidentiality, competence, technology judgment, and any AI-related review. Software can organize the record and audit trail; it does not make professional-responsibility decisions.
01Document the request and statutory basis
The matter should show whether discovery was requested, the statutory reference, responsible attorney, request date, prosecutor contact, local court context, and any related filing packet. That record is separate from the documents later produced.
02Break production into review categories
Reports, videos, lab material, witness statements, digital evidence, prior statements, and impeachment or mitigation material should not collapse into one folder. Review status, assignments, notes, and gaps should be visible by category.
03Track supplemental disclosure and late material
Article 39.14 workflow can continue after initial production. The matter should preserve supplemental items, date received, who reviewed them, whether strategy changed, and whether a hearing or motion issue was created.
04Tie discovery to suppression and dismissal issues
Discovery gaps often feed suppression motions, plea advice, mitigation, dismissal requests, or trial preparation. Legal workflow should connect the missing or disputed item to hearing dates, drafts, and attorney review.
05Keep county context close to the record
A Houston, Dallas, San Antonio, Fort Worth, or Austin practice should not rely on one generic Texas checklist. Court structure, local rules, and prosecutor communication vary enough that implementation should preserve county tags and local rule references.
Harris County and Houston
Houston defense work may involve Harris County district courts, criminal courts at law, municipal context, and Southern District overlap. Article 39 records should stay tied to the court layer and hearing sequence.
Dallas and Tarrant counties
Dallas and Fort Worth share North Texas practice themes but use different county courts, local rules, and bar resources. Discovery workflow should distinguish Dallas County from Tarrant County rather than treating DFW as one court system.
Bexar County and San Antonio
San Antonio practices often need Bexar County local rules and municipal-court context. Discovery packets should be tied to the actual court and prosecutor workflow for that county.
Travis County and Austin
Austin defense work adds capital-region and Travis County practice context. A clean matter record should identify whether the issue belongs to county criminal court, district court, municipal court, or federal separation.
01Keep county tags on every discovery issue
A test matter should show whether the issue belongs to Harris, Dallas, Bexar, Tarrant, Travis, or another county. County tags should affect local rule references, court contacts, hearing notes, and filing packet context without changing the statewide Article 39 source.
02Tie each production to a request and reviewer
The workflow should preserve when discovery was requested, what was produced, who reviewed it, what remains missing, and whether a supplemental production changed strategy. A file upload without request and review history is not enough.
03Treat eFileTexas as filing context only
Implementation should show drafts, notices, exhibits, signatures, review status, and filing notes while remaining clear that Butler is not submitting directly through eFileTexas. Direct filing or court-feed integration would need separate validation.
04Test a late-disclosure scenario
Use a scenario where body camera, lab material, or impeachment information appears after an initial production. The system should connect the late item to attorney review, hearing status, and any motion or plea strategy consideration.
01Eligibility and strategy stay with counsel
Texas Article 39 discovery can be represented as status, documents, assignments, and review notes. It should not be treated as software-determined legal advice. Counsel determines whether production is adequate, whether a disclosure obligation was breached, and how to respond through motion practice, plea advice, or trial strategy.
02Court orders and local rules control the file
County local rules, eFileTexas filing requirements, court orders, and prosecutor-specific procedures control the working record. Software can keep the court, rule, order, hearing, and packet context close to the matter, but the responsible lawyer still reviews the controlling source before relying on it.
03Sensitive records need access decisions
Criminal defense teams often handle discovery, sealed records, witness materials, investigator notes, and privileged work product together. Access, export, search visibility, and migration behavior should be scoped deliberately.
04Migration requires parallel validation
Firms moving from Clio, MyCase, Smokeball, PracticePanther, Filevine, or a custom system should validate active matters, calendar items, documents, custom fields, and sensitive labels before cutover.
Butler workflow relevance
Legal Core can keep Article 39 discovery organized without overclaiming automation.
Legal Core can track discovery requests, production categories, packet status, county tags, review assignments, missing-item notes, supplemental disclosures, motion drafts, hearing dates, and migration checks. It does not decide whether Article 39.14 was satisfied, file directly through eFileTexas, or replace attorney review of local rules and strategy. Texas firms should test the workflow with their own county discovery history.
Is this guide legal advice about Texas Article 39 discovery?
No. It is an educational workflow guide for criminal defense practices. Statutory interpretation, deadlines, filings, waiver, remedy, and strategy remain attorney-reviewed.
Can Butler automatically determine Texas Article 39 discovery compliance?
No. Legal Core can organize references, assignments, documents, review status, dates, and packet context. It does not determine legal compliance or replace counsel.
Why does this page cite state and local sources for Texas?
The state statute or court rule usually supplies the legal framework, but implementation happens inside local courts, clerk practices, filing systems, and firm procedures.
How should a firm use this page during software evaluation?
Use it to build demo scenarios and migration checks. Ask how the system handles the real documents, court dates, review tasks, sensitive records, and local-rule references the firm already uses.
Does Butler claim direct court filing or court data integration here?
No. These educational pages describe firm-side organization and implementation scoping. Direct court filing, court feeds, and automated submissions would require separate validation.
Where should a practitioner go next after reading this Texas Article 39 discovery guide?
Start with Texas Legal Core for geographic context, then review Legal Core pricing if user count, trial timing, founding cohort eligibility, and migration are the buying questions.
Next step
Evaluate discovery workflow with a county-specific scenario.
Use a Harris, Dallas, Bexar, Tarrant, or Travis County matter with request dates, video, reports, late production, and a motion issue. Generic document storage is not enough for Article 39 workflow.