M&A · TECHNICAL SCHEDULES · DISCLOSURE SCHEDULES

Charles Trinh — M&A Technical Drafting Support | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading M&A Technical Drafting — schedules and representations
Charles Trinh — M&A Technical Drafting Support

Drafting the technical half of a transaction: the schedules that describe systems, the representations that depend on technical facts, and the disclosure schedule that has to be right rather than complete.

The schedule is a description someone will rely on

Technology schedules in a transaction describe systems, contracts, licences, data and personnel, and they are relied on by the buyer, by the buyer's lenders and often by insurers. The standard is accuracy rather than completeness, and the distinction matters because a schedule that lists everything vaguely is worse than one that lists the material items precisely. A buyer who finds one inaccurate statement reads the whole schedule with suspicion, and the cost of that suspicion is measured in indemnities.

Write each entry so that it can be verified: the system, its purpose, its vendor and contract, its hosting location and its material dependencies. Where a system is being retired, say so and give the date, because a schedule that lists a retired system as live creates an obligation to keep it alive.

The drafting works best when the engineer writes and the lawyer edits for precision, rather than the lawyer writing from a questionnaire and the engineer correcting afterwards. The correction round is where the schedule acquires confident errors.

Representations that depend on technical facts

Several standard representations are technical in substance: that the systems are sufficient for the business, that there has been no material security incident, that the software is owned or licensed as stated, that the data has been handled in accordance with law. Each is a legal statement resting on a factual foundation that someone in the business has to establish, and the establishment is a diligence exercise rather than a drafting one.

For each representation, identify the facts that would make it true and the evidence that those facts hold. Where the evidence is missing, the representation needs a qualification rather than a hope, and a disclosed qualification is survivable where an undisclosed exception is not.

Security incidents are the representation most often qualified after the fact, because small incidents are not always logged. The diligence should reconstruct the incident history from ticketing, from the monitoring system and from the memory of the people who responded, and the reconstruction should happen before the representation is negotiated rather than after.

Disclosure schedules and the exceptions that matter

A disclosure schedule qualifies the representations by listing exceptions, and the quality of the schedule determines whether the buyer's remedies survive. An exception that is described as a category is weaker than one described as a specific item with its facts, and the difference is discovered when a claim is made.

The usual failure is a schedule assembled at the end from a questionnaire answered quickly, which produces exceptions that are either too broad or missing. Assembling it in parallel with diligence, with each exception traced to the document that establishes it, produces a schedule that a buyer's counsel will accept without a negotiation cycle.

Where an exception is material, discuss it before drafting. A material exception changes the price, the indemnity or the structure, and discovering that during the final negotiation is a worse outcome than raising it early with a proposed treatment.

Contracts, change of control and assignment

Every material technology contract needs to be read for change-of-control, assignment and termination provisions, because those clauses determine what happens on closing and which consents are required. A cloud agreement that terminates on change of control can take a system offline at the worst moment, and the consent process takes longer than the closing timetable allows.

Build a consent register: the contract, the clause, the consent required, the party to ask and the status. The register is the artefact that drives the pre-closing workstream, and it is the schedule the buyer will ask for when the closing date approaches.

Where consent cannot be obtained, the options are a transition services arrangement, a renegotiation or a replacement, and each has a cost that belongs in the price. Identifying the issue early is what makes it a cost rather than a surprise.

Data and the transfer question

The transfer of a data set is not the same as the transfer of a contract, and the transaction documents have to address what happens to data, where it lives and under what authority it moves. Where the data is regulated, the analysis includes the lawful basis for the transfer, the obligations that follow the data to the buyer, and the records that must be retained or destroyed.

Drafting the data clause without the engineering view produces an obligation that cannot be performed, which is worse than no clause because it creates a breach on day one. Have the people who operate the systems write the operational description, then let the lawyers shape the obligation around it.

Finally, keep the drafting trail. The version history, the questions asked and the answers given are the record of why a schedule says what it says, and that record is what protects the individuals who signed when a later question is asked.

The diligence trail behind every statement

Every factual statement in the transaction documents should have a source that someone can produce. The trail is a folder per schedule entry with the document, the date and the person who supplied it, and it exists so that a later question about a statement can be answered with evidence rather than with recollection. In a transaction the questions come months after the drafting, from people who were not in the room, and the trail is the difference between an answer and an argument.

The trail also disciplines the drafting, because a statement without a source is visibly unsupported at the moment it is written rather than at the moment it is challenged. Teams that build the folder as they go produce fewer corrections and fewer negotiation cycles, and the cost of the discipline is a filing convention rather than extra work.

Keep the trail after closing. The representation may survive for a stated period, and the evidence behind it needs to survive at least as long.

Closing deliverables and working capital

The deliverables at closing include the schedules, the consents, the assignments, the data transition plan and the evidence that each representation remains true at the moment of closing. Building the deliverable list early, with an owner and a status per item, converts closing from an event that may or may not happen into a checklist that either completes or shows exactly what is outstanding. The items that slip are rarely the ones the deal team worries about; they are the consents nobody chased because the contract seemed routine, and the assignments nobody drafted because the vendor promised to be accommodating. A working-capital estimate belongs in the drafting rather than in the negotiation, because a price agreed without a mechanism for the position on the closing date tends to be reopened afterwards, and the reopening costs more than the mechanism.

Keep the closing binder as a working document rather than an archive. The parties will return to it for years, for warranties, for consents and for the operational assumptions that were made, and a binder assembled from whatever happened to be filed is one that answers questions slowly. A named owner for the binder, a convention for what goes in it and a date for each document turns the closing into a durable record, which is what a transaction of this kind actually needs after the deal team has moved on to the next one and the operators are left running the systems that were described in it.

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 — m&a technical drafting 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh