Designing a faster bankruptcy intake process

A bankruptcy intake process is the pipeline that carries a person from a first phone call to a filed petition. In a consumer practice it is the operational core of the firm: the fee is largely fixed and the forms are standardized, so the only real variable is how many days and how much staff time each file consumes between signing and filing.

Most firms try to improve intake by working harder inside the existing steps. The durable gain comes from mapping the pipeline, naming an owner for every handoff, setting a target per stage, and attacking the two places where files reliably sit: waiting on client documents, and re-keying the intake packet into petition software.

Map the pipeline before you try to speed it up

Write the stages down as they actually happen, not as they are supposed to. A typical consumer pipeline has eight, each with a named owner and a definition of done someone else can verify.

The value is not the diagram. Once every stage has a definition of done, “where is this file?” has one answer, and “why has it been there eleven days?” becomes answerable.

Where cases actually stall

Stage 4: the client has the documents and you do not

This is almost always the longest stage and the one you control least. A client who signed and left with a packet has no deadline and a strong incentive to avoid the paperwork. The stage ends only when they act, so the levers are making the ask smaller, more specific, and more frequent.

• Split the request into a gating wave and a completion wave, short enough to finish in one sitting
• Give counts rather than categories — “four pay stubs,” not “recent pay stubs”
• Accept legible phone photos with a stated quality floor instead of scans that never arrive
• Book the follow-up before the client leaves, so the next contact is an appointment rather than a chase
• Track a specific missing-item list, never a general “waiting on client” status

Stage 5: re-keying the intake packet

The second stall is entirely internal and therefore fixable. When the packet comes back, someone reads the questionnaire and types it field by field into petition software — names, addresses, employers, dozens of creditor lines, balances, dates. It is hours of skilled attention spent on transcription, and it produces the defects catalogued in common petition data entry errors: a transposed account number, a creditor address copied from a stale statement, a joint case where one spouse’s income landed in the other column.

Fixing it means reducing how many times a fact is handled. Order the questionnaire to match the software’s entry screens, and enter creditors once, from statements, rather than again from a credit report. Then question whether transcription must be manual at all — handwritten packets can be read automatically, which is what Casewell does: it reads the completed paper form, flags low-confidence fields for staff to confirm against the original handwriting, and produces a verified file that imports into Best Case.

Set stage-level targets

A single signed-to-filed number is too coarse to manage. Give each stage a target in business days, publish them, and review exceptions weekly, starting from what your best files already achieve. A file past its stage target then becomes visible on a list instead of invisible in a drawer.

• First call to consult scheduled: same business day
• Consult to engagement: the same visit where possible, otherwise a fixed follow-up window
• Engagement to packet returned: the stage to manage hardest, with a defined check-in cadence, not an open wait
• Packet returned to draft complete: measured in days, because it happens under your roof
• Draft to review complete: a fixed queue interval, so attorney review does not become the new bottleneck

Emergency filings need a parallel track and a named attorney, since a sale date compresses everything and the schedules can follow within 14 days of a skeletal petition. Do not run those on the standard cadence.

Own every handoff

Delay accumulates in the gaps between people, not inside their work. Every transition needs three things written down: who hands off, who receives, and what the receiver is entitled to expect. If a paralegal can receive a file missing the employment section, that handoff has no standard.

• Attorney to paralegal after the consult: chapter direction, known complications, and any deadline constraining the filing date
• Client to paralegal on packet return: a completeness check the day it arrives, not the day drafting starts
• Paralegal to attorney: a draft that already passed the internal checklist, so review is judgment rather than proofreading
• Attorney to filing clerk: signed documents, explicit go-ahead, and the counseling certificate confirmed in the file

Same-day completeness screening is the highest-leverage item on that list. A gap found on arrival costs one phone call; the same gap found mid-draft costs a context switch and a second wait. How the receiving side should be organized is covered in the paralegal workflow guide.

Paper, portal, or hybrid

Hybrid is the honest answer for most consumer practices. The mistake is treating paper as a fallback nobody maintains: if a real share of clients return paper, that path deserves the same field order, version number, and defined route into the file.

Measure cycle time

Instrument the pipeline with the fewest timestamps that answer a real question: consult, engagement, packet returned, drafting complete, filed. Those five yield total cycle time and every stage length — enough to find your own bottleneck instead of borrowing someone else’s.

• Report the median and the slowest quartile — averages hide the files that are actually hurting the firm
• Count business days only, so weekends do not disguise a stalled stage
• Track the number of files past their stage target as one visible number
• Track rework separately: amendments filed, and how many trace to an intake omission
• Review the exception list weekly with the stage owners, changing one thing at a time

Current versions of every form the pipeline produces are published at uscourts.gov. Everything upstream is yours to design, so start with the document the pipeline depends on — the client intake form.

This guide is general information for law-firm staff, not legal advice for any particular case.