RFP · RFQ · EVALUATION · COMPLIANCE
Charles Trinh — RFP and RFQ Responses | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Responding to solicitations that are scored rather than read: compliance with the instructions, structure that mirrors the evaluation criteria, and the evidence that turns an assertion into a point.
Instructions are scored before content
Solicitations carry instructions on format, page limits, font, section order and submission mechanics, and a response that violates them can be judged non-responsive before anyone reads the argument. The first act of any response is a compliance matrix that extracts every instruction and marks where the draft satisfies it, and the matrix is checked again before submission by somebody who did not write the document.
The instructions also define what may not be included, and the cheapest way to lose an otherwise strong proposal is to include a past performance narrative where only a reference form was permitted, or to exceed a page limit that exists because the evaluators have a fixed reading budget. Both are common and both are avoidable with a checklist.
Submission mechanics have their own instructions: the portal, the format, the file naming and the deadline in a specified timezone. Build the submission as a rehearsal a week early, because the discovery that a file exceeds a size limit on the final day is the most avoidable failure in the process.
Structure follows the evaluation criteria
Evaluators score against the stated criteria, and a response organised by the criteria saves them work and earns the benefit of the doubt. A response organised by the company's own narrative arc makes the evaluator search for the answer, and searching produces lower scores even when the answer is present.
Use the criteria's language in the headings, including any weighting, and put the strongest evidence first within each section. Where a criterion is technical, state the capability and then the evidence; where it is management-related, state the approach and then the named people who will execute it.
Keep the document navigable: numbered sections matching the criteria, a table of contents, and cross-references that are correct. A well-structured response is read in order; a badly structured one is read selectively, and selectively means the parts that lose points.
Evidence over assertion
Every claim in a proposal is competing with a competitor's claim, and the differentiator is the evidence attached: a reference, a metric, a credential with a date, a document in an appendix. A response that says the team is experienced is graded on the evaluator's belief; a response that names the engagements and the outcomes is graded on the facts.
Where evidence cannot be published, cite it and offer it under the submission's confidentiality provisions, and check that those provisions actually permit what you intend to submit. An appendix marked proprietary that the solicitation does not accommodate is an appendix that gets removed.
Metrics need definitions, because a number without a definition is not evidence. State the source and the period, and keep the definition consistent across the document, since an inconsistent metric is discovered by anyone who reads carefully and it undermines the sections around it.
Pricing that can be defended
Price is scored on a stated basis, whether lowest-price technically acceptable or a best-value trade-off, and the response has to match the basis. A best-value solicitation rewards a price narrative that explains what the money buys; a lowest-price one rewards a compliant, competitive price and penalises narrative that suggests scope was reduced.
Build the price from a cost model rather than from a target, and keep the model. When the buyer asks a question during evaluation, the answer comes from the model, and a price that cannot be explained at that moment tends to be revised downward or upward without justification.
Keep the schedules consistent with the narrative. The most common pricing defect is a schedule that omits a category the technical narrative promised, which is discovered either as an unrealistically low price or as a post-award dispute.
The review that catches the disqualifiers
Run a coloured review with three passes: a compliance pass against the matrix, a technical pass for accuracy and evidence, and a readability pass by somebody outside the team. Each pass has a different reader and each catches a different class of defect. The compliance pass is mechanical and must be done first, because technical excellence in a non-responsive submission scores nothing.
Leave time between the final draft and the review. A document reviewed the hour it is finished is reviewed by people who remember what they meant rather than what they wrote, and the defects that matter are the ones a fresh reader finds.
Finally, debrief every loss and write down what was learned. The scoring feedback is the cheapest improvement available, and organisations that ask for it improve faster than organisations that submit more proposals with the same weaknesses.
Teaming and the gaps you cannot fill
Most solicitations ask for capability that one small company does not have in full, and the answer is a teaming arrangement rather than an overstatement. Identify the gaps from the compliance matrix, decide which are coverable by a partner and which must be addressed by a limitation disclosure, and start the teaming conversation early enough for the partner to contribute to the response rather than merely sign a letter.
The teaming agreement should name the work, the share, the payment terms and the responsibilities, and it should be aligned with what the proposal says about the team. A proposal that describes a partner in glowing terms and a teaming agreement that says something narrower creates a performance dispute after award, and the resolution is more expensive than the drafting would have been.
Where a gap cannot be covered, address it in the proposal with a mitigation rather than leaving it silent. Evaluators score silence as an absence of capability, and a stated plan to acquire or partner is scored more generously than an omission.
After submission
Submission is not the end of the response; clarifications, discussions and oral presentations are often scored and are frequently treated as an afterthought by teams that spent everything on the document. Prepare the people attending the oral session as though it were a scored interview, because it is, with responses rehearsed against the criteria rather than against the proposal narrative. Answer clarifications precisely and within the deadline, and do not use them to introduce new material, since a clarification that contradicts the proposal creates a defect the evaluator must record. If the award comes, read the contract before the first week of delivery, because its terms define what performance means and the first deliverable is judged against them. If it does not, request the debrief and write the findings into the library, because the next solicitation's advantage is usually the intelligence from the last one.
Keep the proposal library after every submission, not only after the awards. The sections that were written, the evidence that was assembled and the pricing that was modelled are the raw material for the next response, and a library organised by section rather than by opportunity is what makes the tenth proposal faster than the first. The library also becomes the record of what was claimed, which matters when a buyer asks whether the company has done the thing it said it would do, and it is the source of the consistency that makes a company recognisable across multiple submissions to the same customer.
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 — rfp and rfq responses — the scope, the failure modes it prevents and how the work is measured. It sits in the Regulatory and Capital Markets 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.