BANKRUPTCY · ASSET ACQUISITION · DUE DILIGENCE
Charles Trinh — Bankruptcy Trustee Acquisition Support | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Acquiring assets from a bankruptcy estate: the sale process and its deadlines, what the trustee can and cannot warrant, diligence under time pressure, and the operational risks that survive the closing.
The process is a court process
Assets sold from a bankruptcy estate are sold through a process supervised by the court, which means the timetable, the bidding procedures and the approvals are set by orders rather than by negotiation. Understanding the orders is the first diligence task, because they define what can be bid, when, with what deposit and on what terms, and a bidder who has not read them is a bidder who will be surprised.
The sale order also defines the relief a buyer can obtain: the free-and-clear transfer of assets, the assumption and assignment of specified contracts and the treatment of liens. Each of those is valuable and each is conditional, and the conditions are where a bidder's assumptions usually exceed what the court will grant.
Timing is compressed by design, which is the point of the process and also the principal risk. A bidder who needs six weeks of diligence has to either build a team that can work in two or accept that some questions will not be answered before the bid deadline. Both are legitimate choices and only one of them is usually acknowledged in the bid.
What a trustee can and cannot warrant
A trustee sells what the estate owns and warrants little beyond its authority to sell. There is no seller's representation about the condition of the assets, the accuracy of the records or the absence of undisclosed liabilities, and a buyer who expects the customary private-market package will be disappointed at the worst possible moment.
The consequence is that diligence must establish the facts the buyer would otherwise have been given, and the diligence has to do it with limited access. Records may be incomplete, key personnel may have left, and the systems may have been operated on a skeleton basis for months. The diligence plan should assume a degraded information environment and prioritise the questions that would change the bid.
Where a representation is essential, the mechanism is usually a court-approved carve-out or a specific order, and those are negotiated before the bid rather than after. Ask early which of your assumptions the trustee or the estate's professionals can support, and price the rest.
Diligence under time pressure
Rank the questions by what would change the bid rather than by what would be nice to know. For a technology or clinical business the rank usually starts with licences and certifications that may lapse with the sale, contracts that terminate on assignment, data that cannot be transferred, and key people who have already gone. Each of those can invalidate the asset you thought you were buying, and each is answerable in days rather than weeks if the question is asked directly.
Assign a partner per question with a deadline and a written answer, and accept that some answers will be partial. The deliverable is not a complete picture; it is a list of the risks with their assessed impact and the price adjustment or condition attached to each.
Bring operational people into the diligence, not only financial and legal advisors. The systems that will have to be operated after closing are where the surprises live, and the people who will operate them can often assess them in an afternoon by looking at what is running.
The liabilities that survive closing
A free-and-clear order addresses liens on the assets, not every liability that attaches to the business. Successor liability, tax liabilities in some circumstances, environmental obligations and obligations under licences can follow the assets, and the analysis of which ones do is a legal question with a technical component. Where the business holds regulated data, the obligations attached to that data are a diligence item in their own right.
Employee obligations are frequently the largest category, because the transfer of employees brings accrued obligations, and the treatment of those is a matter of the orders and of employment law. A plan that assumes a clean slate for people is a plan that will be revised.
Insurance for the pre-closing period is usually unavailable, which is why the representation and warranty insurance market rarely covers this kind of transaction. The absence of that protection is a reason to price conservatively rather than a reason not to proceed.
The operating plan for day one
The asset is worth what it can be operated as, and the operating plan for the first day is part of the bid. Who has the credentials, who can sign, which systems stay up, which contracts must be assumed to keep the lights on, and who tells the customers. Each of those needs an owner and a time, and the plan is usually written by the buyer's operators rather than by the deal team.
Assume some systems will not be accessible at closing because the seller's credentials or subscriptions lapse. Have a plan for read-only access to records, and a plan for communicating with customers whose records you now hold but cannot yet reach.
The measure of success is not the closing; it is the first month of operations with no unexpected outage. Write the day-one plan against that measure, and rehearse the handover of credentials and keys before the court date rather than after it.
Working with the estate's professionals
The trustee's professionals are the counterparty for every practical question, and the relationship is transactional rather than adversarial: they need a sale that closes, and a bidder who is organised helps them get there. Ask precise questions in writing, respond quickly when they ask, and keep the record of what was asked and answered, because the estate's professionals are working to a court timetable and their attention is the scarcest resource in the process.
The other bidders change the dynamic, and the knowledge that there is competition should not change the diligence rather than the price. A bid built on an assumption nobody tested is a bid that wins at the wrong number, and the estate will not renegotiate after the auction. Decide in advance what the walk-away number is and what conditions would make the asset worth that number, because the decision is easier before the auction than during it.
Finally, plan for the possibility that the sale does not close: a competing bid, a court objection or an adjournment. The diligence work remains useful and the transaction costs are sunk, which is an argument for bounding the spend before the process begins rather than discovering the boundary afterwards.
What the bid should contain
A bid in a court-supervised sale is a document that has to be both commercially competitive and legally clean, because it will be read by the trustee, the creditors committee and the judge. It should state the purchase price and its components, the assumed liabilities, the contracts to be assumed and the treatment of employees, with the conditions and the timeline clearly expressed. Ambiguity in a bid is resolved against the bidder, because the estate and the court need certainty more than they need the bidder's intentions, and a bid that leaves a question open produces a request for clarification that costs a day nobody has. The bid should also state what the buyer will do if the conditions are not met, because the failure of a bid only one party wants is an outcome the trustee has to manage and would rather not.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — bankruptcy trustee acquisition support — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.