Educational guide

Maryland Hicks workflow turns the 180-day rule into a reviewable matter record.

Maryland circuit court trial timing under Criminal Procedure section 6-103 and Rule 4-271 is commonly handled as Hicks deadline review. Defense workflow needs the first appearance or counsel event, trial setting, postponement orders, good-cause findings, and motion posture visible in one place.

Direct answer

A Hicks workflow should preserve the triggering event, every postponement, and the judicial finding.

Maryland Criminal Procedure section 6-103 and Rule 4-271 make the 180-day trial-date framework central to circuit court criminal workflow. A system can track dates, court settings, postponements, good-cause records, and attorney review status. It should not decide whether Hicks was violated, whether dismissal is required, or whether a postponement order is sufficient.

Regulatory framework

The Maryland deadline sits in both statute and rule.

The Maryland Legal Core and Baltimore Legal Core pages cite Hicks context. This guide narrows to the practical workflow a defense firm should maintain.

Criminal Procedure section 6-103

The statute sets the circuit court trial-date framework. The matter should show the earlier triggering event, trial-date setting, any request to change the date, and the authority for the change.

Maryland Rule 4-271

Rule 4-271 implements the trial-date framework and identifies how circuit court trial dates are set and changed. The workflow should preserve the rule source, any administrative judge action, and the reason for postponement.

Hicks case law informs remedy review

The Hicks label comes from Maryland case law, but this page avoids reducing the doctrine to a software answer. Counsel reviews waiver, good cause, consent, postponement history, and remedy.

Local court structure matters

Baltimore City is an independent city with Circuit Court and District Court layers. The system should identify whether the matter is in circuit court, district court, or federal court before any deadline review begins.

Procedure walkthrough

Create a timeline counsel can audit.

The risk in Hicks workflow is not lack of a date. It is losing the procedural reason a date changed.

01

Capture the first relevant triggering event

The matter should identify counsel appearance, defendant appearance, transfer from District Court if applicable, circuit court docketing, and the date the firm is using as the starting point for review.

02

Record the trial date and every change

Each postponement should show who requested it, what order or docket entry supports it, whether an administrative judge or designee acted, what good cause was stated, and the new trial date.

03

Separate defense consent from court findings

Consent, waiver, party request, and good-cause findings are not interchangeable. A workflow should preserve the facts so counsel can analyze them rather than applying a generic Hicks label.

04

Tie deadline review to motion practice

If counsel is evaluating a Hicks motion, the matter should link the timeline, postponement orders, transcript notes, draft motion, client advice, and upcoming hearing.

05

Preserve District Court and federal separation

Baltimore practices may handle District Court misdemeanors, Circuit Court felonies, and District of Maryland federal matters. Hicks review belongs to Maryland circuit court criminal timing, not every criminal matter in the firm.

Local variation

Baltimore City structure is part of the workflow.

Maryland's statute and rule are statewide, but the educational page goes deeper by making Baltimore City's independent-city court structure explicit.

Circuit Court for Baltimore City

Baltimore felony workflow centers on the Circuit Court for Baltimore City. Hicks review should tie the timeline to that circuit court record, not to a generic county court template.

District Court of Maryland in Baltimore City

District Court matters can affect how a case reaches circuit court, especially where jury-trial demands or charging posture change the path. The matter should preserve transfer or docketing context.

District of Maryland federal matters

Federal criminal matters use a different timing framework. A Baltimore defense firm should separate federal speedy-trial context from Maryland Hicks review.

Maryland professional responsibility

Deadline tracking is a professional workflow issue as well as a procedural issue. The system should make review responsibility visible without becoming ethics advice.

Implementation check

A Hicks implementation should make postponement authority auditable.

The Maryland Legal Core page names Hicks context; this page turns it into the specific records a defense practice should preserve before relying on a deadline workflow. The review is deliberately evidence-oriented: a lawyer should be able to open the matter and see why each date exists, who changed it, and what source supports the change.

01

Identify the triggering event explicitly

The test matter should show counsel appearance, defendant first appearance, transfer or docketing details, and why the firm selected the starting date. The system should not hide that reasoning behind a single deadline field.

02

Attach every postponement source

Each trial-date change should include the motion, order, docket entry, transcript note, administrative judge involvement, and good-cause explanation if present. The reviewer should be able to audit the chain without searching email.

03

Separate consent and good-cause notes

A continuance may involve defense consent, party request, court initiative, or an administrative finding. The implementation should preserve those categories separately so counsel can analyze waiver, authorization, and remedy.

04

Test Circuit Court and District Court transitions

Use a Baltimore matter that moved between District Court and Circuit Court or changed procedural posture. The workflow should preserve where the matter was docketed and which court's timing framework counsel is reviewing.

Practitioner review limits

The Hicks answer is not software-determined.

A date calculator that hides waiver, consent, or good-cause details can mislead the practice. The matter record has to support attorney analysis.

01

Eligibility and strategy stay with counsel

Maryland Hicks deadline workflow can be represented as status, documents, assignments, and review notes. It should not be treated as software-determined legal advice. Counsel decides the triggering event, whether a postponement was authorized, whether good cause exists, and whether dismissal or another motion is appropriate.

02

Court orders and local rules control the file

Circuit court orders, docket entries, administrative judge action, and Maryland Rule 4-271 control the file. 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.

03

Sensitive 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.

04

Migration 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 the Hicks record visible without deciding it.

Legal Core can track triggering events, trial dates, postponements, order references, good-cause notes, responsible attorney, motion drafts, client communication, and migration validation. It does not calculate a binding Hicks answer, determine waiver, or decide dismissal. Maryland firms should test the workflow with a real matter that includes more than one postponement.

Related Butler pages

Move from Hicks procedure to Maryland and Baltimore Legal Core context.

FAQ

Common Maryland Hicks workflow questions.

Is this guide legal advice about Maryland Hicks deadline workflow?

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 Maryland Hicks deadline workflow 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 Maryland?

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 Maryland Hicks deadline workflow guide?

Start with Maryland Legal Core for geographic context, then review Legal Core pricing if user count, trial timing, founding cohort eligibility, and migration are the buying questions.

Sources checked

Maryland Hicks claims are tied to statute, rule, court, and local sources.

Sources include Maryland Criminal Procedure section 6-103, Maryland Rule 4-271 materials, Maryland court resources, Baltimore City court resources, federal court context, and professional resources.

Next step

Test deadline workflow with a postponement-heavy matter.

The system should show the trigger, trial setting, every postponement, the stated reason, the authorizing judge, and the draft motion record. That is the useful Hicks workflow test because the audit trail matters as much as the date itself.