# Current opportunity and response instructions

**The immediate opportunity is an RFI, not a request for an awardable proposal.** To compete for a possible later contract, submit a useful, credible market-research response now and build evidence that can survive later evaluation. The live [SAM.gov notice 2027-NLS-0075](https://sam.gov/opp/5e1bed195d704dc189d7a231c4a5ab9c/view), checked October 2, 2026, expressly states that no contract will be awarded from this RFI and that participation is voluntary, with no reimbursement of response expenses.

## Verified response facts

| Item | Live notice as checked October 2 |
|---|---|
| Title | TTS for DTB Pilot - Request for Information |
| Notice type | Sources Sought, updated |
| Agency and office | Library of Congress, Contracts Services |
| Latest displayed update | September 28, 2026, 3:34 p.m. EDT; attachments added |
| Response due | **October 12, 2026, 5 p.m. EDT / 4 p.m. CDT** |
| Requested material | Capability statement, rough order of magnitude pricing, draft-SOW feedback/questions and other useful solution information |
| Response route | The notice directs material to both listed contracting contacts: James Robinson, jarobinson@loc.gov; Brenda Kinlay, bkinlay@loc.gov |
| Classification | NAICS 541511; PSC DA01 |
| Not established | Final solicitation, scored evaluation factors/weights, definitive submission template/page limit, final price structure, confirmed bidders or incumbent |

Use the [live notice](https://sam.gov/opp/5e1bed195d704dc189d7a231c4a5ab9c/view) as the controlling source and recheck for amendments before sending. No page limit or mandatory file format was found in the displayed RFI; absence in this review is not permission to ignore later instructions. The blank set-aside field does not establish the structure of a future competition. Draft-SOW resumes due “with Proposal Submission” are future-proposal preparation items, not evidence that this RFI requests a formal proposal package.

## What to prepare now

Prepare a concise capability-led response with a clear proposed solution, evidence of relevant delivery, a transparent ROM and prioritized SOW feedback. Use [the proposed draft](proposal-draft.md), and attach only verified supporting material. An optional short evidence appendix should make the response easier to assess; it should not bury the capability statement in this entire wiki.

Keep the current RFI response and future proposal as separate artifacts. When a solicitation arrives, extract every instruction and evaluation factor into a new compliance matrix, then restructure the offer to match. The [current coverage matrix](compliance.md) is a preparation aid, not a substitute for those future instructions.

## Proposed response workback

These are internal target dates, not Government deadlines or scheduled automations. The remaining window is short; an unbuilt 16-week prototype cannot become a claimed pre-response accomplishment.

| Target | Work product | Owner role |
|---|---|---|
| October 2–4 | Confirm bidder/prime-or-partner position; collect qualifications, relevant references and actual capability evidence; cost assumptions | Capture lead / business owner |
| October 5–6 | Validate strongest technical claims, identify gaps needing a specialist partner, complete ROM and SOW questions | Technical lead + estimator |
| October 7–8 | Independent review of relevance, evidence, rights language, schedule and price logic | Reviewer independent of the writer |
| October 9 | Approve finished response, contact route and any proprietary markings; target early submission if authorized | Authorized company representative |
| Before October 12, 5 p.m. EDT | Recheck notice/amendments, send through the specified route and retain submission evidence | Authorized sender |

This wiki does not send a response, schedule reminders or contact the Library. A separate explicit instruction is needed to send anything.

## Separate present capability from future work

Use three clear categories in every response: **verified existing capability**, **proposed implementation**, and **dependency or unresolved decision**. At present, this workspace establishes research, a technical plan, diagrams and a draft response. It contains no completed TTS prototype, NLS-player test, benchmark, bidder resume or customer reference. That distinction protects credibility and identifies exactly where to invest before a formal competition.