Bankruptcy / Restructuring

• A party needs the automatic stay concerns around an action, communication, or proceeding spotted and organized for an attorney.
• A creditor, lender, landlord, or counterparty is unsure whether a step is affected by a bankruptcy filing and needs the facts mapped.
• Post-petition activity must be inventoried before an attorney evaluates stay exposure.

• Debtor identity, the user's party role, and case status.
• Petition date if provided, echoed and marked [deadline verification required].
• The specific actions, communications, or proceedings in question — for example collections, litigation, setoff, foreclosure, repossession, contract termination, payment demands, eviction, lien enforcement, regulatory actions if mentioned, and post-petition communications.
• The timing of each action relative to the petition date, as the user states it.
• Notices received and any responses sent.
• Source documents with citations to docket entries, letters, or pages.

If the debtor, the user's role, or the actions in question are missing, record them as not provided and return the missing-information list first.

• A team needs the bankruptcy dates and notices it has collected organized into a single draft tracker for attorney verification.
• A matter has multiple notices, orders, and hearing dates that must be recorded with sources before an attorney confirms them.
• Internally assigned task deadlines must be tracked alongside court dates.

• The dates the user provides, each with its source — for example petition date, bar date, meeting dates, objection deadlines, plan and disclosure-statement dates, sale dates, and hearing dates.
• The notices, orders, or docket entries that state those dates.
• The user's party role.
• Internally assigned task deadlines, if any.
• If the user wants a draft computed entry: the rule and the date calculation the user supplies, with an explicit request for a draft tracker entry for attorney verification.
• Source references to docket entries, notices, or pages.

If no dates or sources are provided, record that as not provided and return the missing-information list first.

• A distressed M&A deal, a bankruptcy asset sale, creditor or lender diligence, a restructuring transaction, or a plan negotiation needs a diligence request list.
• A diligence team needs requests organized by workstream with priority, rationale, and ownership.
• Diligence follow-ups must be tracked against documents produced.

• The transaction or matter type and stage.
• Debtor profile, the user's party role (buyer, lender, creditor, committee, debtor, or other), and case status if known.
• Court or jurisdiction if known, or [verify jurisdiction].
• The workstreams in scope — for example debtor organization, debt structure, liens and collateral, contracts, litigation, claims, taxes, employees and benefits, environmental if relevant, real estate, intellectual property, financials, cash management, insider transactions, avoidance actions, regulatory issues, and sale or plan documents if relevant.
• Documents already provided, with source references.
• Known debt, lien, contract, litigation, or claim facts the user reports.

If the transaction/matter type, the user's role, or the workstreams in scope are missing, record them as not provided and return the missing-information list first.

• A new bankruptcy, insolvency, or restructuring matter needs structured intake before substantive legal analysis by an attorney.
• A creditor, debtor, buyer, lender, committee, or contract counterparty needs the matter's facts, parties, and posture organized.
• A matter must be routed to the right specialist bankruptcy skill and the issues scoped first.

• Debtor identity and creditor identity (and other key parties), as available.
• The user's party role and posture (creditor-side, debtor-side, buyer-side, lender-side, committee-side, contract counterparty, or other).
• Case status, and the chapter or case type if known, or not provided.
• Court or jurisdiction if known, or [verify jurisdiction].
• Petition date if provided, echoed and marked [deadline verification required].
• Claim type, contract relationship, and any collateral or lien facts.
• Deadlines and notices the user reports, echoed and marked [deadline verification required].
• Litigation status, payments received, and the action the user is considering.
• Source documents with citations to docket entries, pleadings, or pages.

If the party role, the chapter/case type, or the court is missing, record it as not provided and return the missing-information list before substantive intake.

• A cash collateral order, DIP credit agreement, DIP financing motion, or related document must be reviewed and its issues organized for an attorney.
• A debtor, lender, committee, or party in interest needs the financing terms and issues mapped with sources.
• Financing terms must be checked before a hearing or an objection is considered.

• The cash collateral or DIP financing document, with source references.
• The user's party role (debtor-side, DIP lender, prepetition lender, committee-side, or other).
• The lenders, the collateral, and the liens as written.
• The budget as written, with budget-line references.
• Reporting covenants, milestones, and roll-ups if provided.
• Adequate-protection provisions, carveouts, default triggers, use restrictions, releases, investigation periods (including any challenge-period dates), and professional-fee provisions.
• Any milestone, hearing, or challenge-period dates, echoed and marked [deadline verification required].
• Source references to sections, clauses, budget lines, or pages.

If the document, the user's role, or the lenders and collateral are missing, record them as not provided and return the missing-information list first.

• A creditor's claim facts must be organized before an attorney evaluates the claim or a proof of claim is considered.
• A team needs the contract or invoice basis, amounts, collateral, and disputes captured with sources and gaps flagged.
• A bankruptcy matter requires the creditor's position scoped before substantive analysis.

• Debtor and creditor identities, and the user's party role.
• The basis of the claim — contracts, invoices, notes, judgments, or other — with source references.
• The claim amount as stated by the user (recorded as a user-stated figure, never computed or verified).
• Any secured, unsecured, or priority characterization the user provides (recorded as an assertion, never confirmed).
• Collateral facts, guaranties, offsets or setoffs, and payment history.
• Disputes, defenses raised, and notices received.
• Proof-of-claim status (filed, not filed, unknown), and any user-supplied bar date marked [deadline verification required].
• Source documents with citations to invoices, contract clauses, or pages.

If the debtor, the creditor's role, or the basis of the claim is missing, record it as not provided and return the missing-information list first.

• A bankruptcy or distressed asset sale needs its process steps, diligence, and closing deliverables organized for an attorney.
• A buyer, seller, or debtor needs the sale checklist, contract/cure tracker, and closing tracker built with sources.
• A sale process must be scoped before bid procedures or a sale hearing are considered.

• Asset description and the sale process contemplated.
• The user's party role (buyer-side, debtor/seller-side, lender-side, committee-side, or other).
• Court or jurisdiction if known, or [verify jurisdiction].
• Stalking-horse terms if provided, and bid procedures if provided.
• Liens and encumbrances, cure costs as provided, and assigned contracts as provided.
• Employee matters, intellectual property, real estate, taxes, and regulatory approvals if provided.
• Closing deliverables and any sale-order issues the user raises.
• Any sale, bid, objection, or hearing dates, echoed and marked [deadline verification required].
• Source references to sale documents, motions, or pages.

If the asset description, the sale process, or the user's role is missing, record it as not provided and return the missing-information list first.

• A debtor or a counterparty needs the facts of an executory contract or unexpired lease organized for an attorney's assumption/rejection analysis.
• A team needs cure amounts, defaults, assignment rights, and consent issues captured with sources.
• A contract portfolio must be triaged before an attorney evaluates assumption or rejection.

• Contract or lease identity, and the debtor and counterparty roles.
• The user's party role (debtor-side, counterparty, buyer-side, or other).
• Cure amounts as provided (recorded as stated, never computed or confirmed).
• Defaults asserted and notice history, with source references.
• Assignment rights, anti-assignment or change-of-control language, and any consent issues, with clause citations.
• Critical-vendor status if raised (recorded as raised, never confirmed).
• Assumption or rejection status, if any, and any related deadlines echoed and marked [deadline verification required].
• Business impact as the user describes it.
• Source documents with citations to contract clauses, notices, or pages.

If the contract identity, the party roles, or the contract text is missing, record it as not provided and return the missing-information list first.

• A plan and/or disclosure statement must be reviewed and its issues organized for an attorney.
• A creditor, committee, or party in interest needs the classification, treatment, and release provisions mapped with sources.
• A plan draft must be checked for internal consistency before objections or a vote are considered.

• The plan and/or disclosure statement, with source references.
• The user's party role (debtor-side, creditor-side, committee-side, equity, or other).
• Class classification and treatment provisions, as written.
• Voting provisions, and releases, exculpation, and injunction provisions.
• Executory contract provisions and claims-reconciliation provisions.
• Feasibility facts and any liquidation analysis, if provided (recorded as provided, never assessed).
• Governance, equity treatment, and any stated objections or confirmation issues.
• Any plan, disclosure-statement, voting, or confirmation dates, echoed and marked [deadline verification required].
• Source references to plan or disclosure-statement sections, articles, or pages.

If the documents, the user's role, or the classification/treatment provisions are missing, record them as not provided and return the missing-information list first.

• A creditor has received a preference demand and the underlying facts must be organized before an attorney evaluates a response.
• A team needs the alleged transfers, invoice and payment history, and defense-relevant facts captured with sources.
• A preference matter must be triaged before substantive analysis or settlement discussion.

• The preference demand letter, with source references.
• The alleged transfer dates and amounts as stated in the demand.
• Invoice history and payment history, with source references.
• The creditor relationship and its history with the debtor.
• Facts the user provides that may bear on common defense themes — ordinary course of business, new value, and contemporaneous exchange — recorded as facts only, never as a defense conclusion.
• Security interests and any collateral facts.
• Settlement posture and litigation status.
• Any user-supplied response deadline, echoed and marked [deadline verification required].

If the demand letter, the alleged transfers, or the creditor relationship is missing, record it as not provided and return the missing-information list first.

• A creditor is preparing a proof of claim and needs a preparation checklist and document tracker for attorney review.
• A team needs to see what supporting documents exist and what is missing before an attorney drafts a proof of claim.
• A claim's supporting record must be organized before submission is considered.

• Claimant identity and the user's party role.
• Debtor and case information (case name, court if known, case reference).
• Basis of the claim and the amount as stated by the user.
• Supporting documents available, with source references.
• Any secured or priority characterization the user provides (recorded as an assertion, never confirmed).
• Interest and fees as provided (recorded as stated, never computed).
• Assignment or transfer history, if any.
• Redaction needs (personal identifiers, account numbers) and signature-authority facts.
• Any bar date the user supplies, echoed and marked [deadline verification required].

If the claimant, debtor/case information, or basis of claim is missing, record it as not provided and return the missing-information list first.

• A restructuring support agreement, forbearance agreement, exchange offer, workout term sheet, or plan support term sheet must be reviewed and organized for an attorney.
• A negotiating party needs the key terms, issues, and risks mapped from one side's perspective.
• Restructuring terms must be checked for completeness before negotiation or signing.

• The restructuring document, with source references.
• The user's party role and perspective (debtor-side, lender-side, creditor-side, committee-side, or other).
• The parties, the debt instruments involved, and the transaction type.
• The terms to review, as written — for example milestones if supplied, releases, covenants, payment terms, collateral, guaranties, consents, defaults, fees, voting and support obligations, termination rights, exclusivity, confidentiality, and conditions.
• Any milestone dates or deadlines, echoed and marked [deadline verification required].
• Source references to sections, clauses, or pages.

If the document, the user's role, or the transaction type is missing, record it as not provided and return the missing-information list first.