GSA · SCHEDULE · MAS · COMPLIANCE
Charles Trinh — GSA Schedule Preparation | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Preparing a GSA Multiple Award Schedule offer: the solicitation structure, pricing disclosure, the commercial sales practice that underpins the price, and the administration that follows award.
The offer is a disclosure, not a brochure
A GSA Multiple Award Schedule offer is a structured submission in which the company states what it sells, at what price, on what terms, and how that price relates to what it charges commercial customers. The disclosure obligation is the heart of it: the price offered to the government must be consistent with the company's commercial practices, and the commercial sales practices narrative is where the company explains the basis.
This makes the offer a different exercise from a proposal. There is no evaluator to persuade with narrative; there is a reviewer checking whether the offer is complete, whether the pricing is supported and whether the terms are consistent with the representations. A brochure-style submission is returned for information rather than evaluated.
Read the current solicitation in full before drafting anything, because the structure changes and the legacy experience of someone who prepared an offer years ago is often wrong in the details that cause rejection.
Pricing that survives the basis-of-award analysis
GSA evaluates whether the offered price is fair and reasonable relative to commercial practice, and the analysis depends on the data the company provides about its commercial sales. Incomplete or inconsistent commercial data produces a request for more information and a longer negotiation, and in the worst case a price reduction awarded unilaterally.
Build the pricing file before drafting: the rate card, the discount structure, the most-favoured-customer treatment and the evidence for each. The file should show the relationship between the commercial price and the government price rather than assert it, and it should be internally consistent with the offer's terms.
Where the company offers services at varying rates by customer size or volume, describe the tiers accurately rather than simplifying them into a single number. Simplification is discovered when a commercial invoice contradicts the disclosure, and the consequence falls on the schedule.
The administrative obligations begin at award
A schedule award brings ongoing obligations: the catalog in the government marketplace, the price adjustment clauses, the reporting of sales, and the modification process for changes. Each is administrative and each is a compliance item with a deadline, and the organisations that treat the award as the end of the project discover the obligations during their first audit.
Name an owner for schedule administration and give them the calendar. The catalog is the government buyer's view of the company, and a stale catalog produces orders for products that no longer exist and misses products that do.
Price adjustments are the clause most often mishandled, because a commercial price reduction generally must be passed through, and the timing matters. Establishing a process for capturing commercial price changes and reflecting them in the schedule is cheaper than correcting the record later.
Sales reporting and the data behind it
Sales under the schedule are reported, and the data has to reconcile with the company's own accounting. The reconciliation is where the errors appear: orders attributed to the wrong contract, discounts not reflected, returns not netted. Build the reporting from the accounting system rather than from a separate spreadsheet, so there is one source of truth.
Where a reseller sells under the schedule, the reporting obligation and the flow of information are defined by the terms, and the reseller relationship needs to be set up to produce the data. A reseller who cannot report is a gap in the company's own compliance.
Reconcile the reported total against the accounting total each period and investigate differences rather than adjusting them. The pattern of differences is the information, and it usually points at a process rather than at an error.
Team and the decision to pursue it
A schedule is a route to a market, not a guarantee of demand, and the analysis before applying should include whether the agency buyers the company targets actually buy through the schedule. For many services they do; for some they use other vehicles, and a schedule that nobody orders from costs administration without producing revenue.
Assess the competition on the schedule for the specific labour categories or products, and price against that rather than against the commercial market. The government buyer compares you to the other schedule holders, and the comparison is visible in the marketplace.
Finally, plan the maintenance. A schedule requires periodic review, catalog updates and compliance with the clauses; the organisations that succeed treat it as a product line with an owner rather than as a credential to be obtained once.
The catalog as the product
On the schedule, the catalog is what the buyer sees and what they order from, and a catalog that is stale, incomplete or hard to search costs orders without producing a complaint. Build it deliberately: the labour categories or products the company can actually deliver, the descriptions in the buyer's vocabulary, the price list consistent with the schedule, and the terms that apply. Review it quarterly against what has actually been sold, because the catalog that reflects the last year's business is the one that produces the next year's.
Where the company sells services, the labour category descriptions matter more than the titles, because the buyer searches by the category and compares by the description. Write them to describe the work rather than the grade, and keep them consistent with the price list so the comparison is possible.
Finally, keep the record of catalog changes. When a buyer asks why a category disappeared, the change log is the answer, and it is also the evidence that the catalog is maintained rather than abandoned.
Modifications and the discipline of change
Once on schedule, every change to products, prices or terms is a modification, and modifications have their own process, documentation and review. The discipline is to batch changes rather than submit them one at a time, keep the supporting documentation with the request, and record what changed and when. A schedule holder who submits frequent small modifications without documentation accumulates a pattern that invites scrutiny, and the scrutiny costs more than the batching would have. Where a modification is refused or returned, the reason is usually a documentation gap rather than a substantive objection, and the second submission is faster if the first one's feedback is read carefully. Organisations that treat the schedule as a maintained product line have modifications that are routine; the ones that treat it as a credential have modifications that are emergencies.
Review the schedule's performance annually against what it was expected to produce. A schedule with no orders for a category is either a category the agencies do not buy on this vehicle or a catalog that nobody can find, and the two have different fixes. The review should compare orders against the target agencies, the categories against the market, and the price against the competition visible in the marketplace. The output is a short list of changes, which is also the input to the next year's modifications and the honest answer to whether the administration cost is producing anything.
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 — gsa schedule preparation — 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.