Capability 06

Testing, documentation, training & handoff

The artifacts that let another owner inspect, accept, operate, and support delivered work.

One person handing a navy binder of documentation to another across an ivory table

OutcomeRecorded acceptance results, a complete handoff inventory, and an open-risk register with named owners.

What this covers

Acceptance-test support for systems built by others, documentation for systems that never got any, operator training, and structured handoffs when a contract or a team changes.

Why this is a stand-alone capability

Programs inherit systems. The documentation is missing, the tests were never written down, and the person who knew it has moved on. BCA produces the record: what the system does, how it is operated, how it is tested, and what is still at risk.

Deliverables

  • Test plans and recorded execution against the program’s own acceptance criteria.
  • User guides, operator runbooks, and configuration references in the agency’s required format.
  • Recorded training sessions and a handoff inventory that names every artifact, location, and owner.

Outcomes

What changes once the work is accepted.

  • Inherited systems have a written record of what they do, how they run, and how they are tested.
  • Acceptance is based on recorded results against the program's own criteria.
  • Operators and users are trained, with recordings that survive staff turnover.
  • Every artifact, location, and owner is listed when a contract or team changes.

Typical deliverables

Named the way they appear in a scope.

Acceptance-test plan and recorded execution
Test cases written from the program's acceptance criteria, run, and recorded.
User guides and operator runbooks
In the agency's required formats and repositories.
Configuration reference
Settings, integrations, and environments documented for the next operator.
Training sessions
Delivered live and recorded, for users, operators, or administrators.
Handoff inventory and open-risk register
Every artifact with its location and owner, and every open risk with a named owner.

How engagements work

Three common ways this capability is bought.

Each starts with a written scope, deliverables, and acceptance evidence. Thresholds and authorities are on the federal agencies page.

  • Micro-purchase or simplified acquisition

    A documentation and test package for one system that has none, or a recorded training set for a delivered tool, sized under the threshold.

    How micro-purchase works with BCA
  • Subcontract work package

    Independent acceptance-test support, documentation, or training as a defined package inside a prime's delivery.

    The six-part work-package model
  • Sources sought and RFI response

    BCA responds with the artifacts it would produce, the formats it would follow, and the access it would need to document or test the system.

    What BCA sends back

Capability limits

What BCA will not claim or perform here.

Stated before award so the file, the compliance matrix, and the work all match.

  • Acceptance-test support is not independent verification and validation under a formal IV&V contract unless the awarded scope says so.
  • BCA documents and tests systems. It does not take over operations and maintenance unless an awarded scope assigns them.
  • Training is practical system and tool training, not an accredited course.

Company-wide boundaries

  • No federal contract past performance yet. Commercial delivery and owned-system evidence are labeled on the past performance page.
  • No personnel or facility security clearance. Unclassified work only.
  • No FedRAMP authorization, agency ATO, CMMC certification, ISO certification, or SOC 2 report. BCA works inside the boundary the agency or prime authorizes.
  • Not a GSA Multiple Award Schedule holder.

Source and verification dates for every boundary statement are kept with the evidence records and the capability statement.

Next step

Send the requirement. We reply with a bounded scope and evidence, not a pitch.

A sources-sought notice, a section of a statement of work, or a one-paragraph problem description is enough to start. Expect a written response within two business days.