OutcomeReports and dashboards with defined metrics, reconciliation checks, and documented limitations.

What this covers

System-to-system integrations, one-time and phased data migrations, operational reporting, and executive dashboards. The first deliverable is always a written definition of the decisions the output must support.

Why reconciliation is in the acceptance criteria

A dashboard that cannot be reconciled to its source records gets ignored within a quarter. BCA delivers reconciliation checks with every report so the program can prove the numbers when it is asked.

Where BCA fits

A reporting and visibility work package on top of systems a prime operates.
A bounded integration between two agency systems with an approved interface.
A migration scope with inventory, mapping, dry runs, and a documented cutover.

Outcomes

What changes once the work is accepted.

Every number on a report has a written definition, an owner, and a reconciliation back to source records.
Duplicate data entry between approved systems is removed.
Leadership can answer routine questions from a dashboard instead of a data call.
Known limitations are documented, so nobody over-trusts a figure.

Typical deliverables

Named the way they appear in a scope.

Metric and decision definitions: The decisions each report supports, with metric owners and calculation rules.
Integration or migration build: API integration, data mapping, dry runs, and a documented cutover where data moves.
Reconciliation checks: Source-to-output checks delivered with each report and runnable again.
Reports and dashboards: Built on the agency's approved reporting tools, with usage guidance.
Known-limitations register: Data gaps, refresh timing, and caveats, stated in plain language.

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 metric-definition and reconciliation package for one existing report, or a bounded integration design between two systems, sized under the threshold.
How micro-purchase works with BCA
Subcontract work package
A reporting and visibility layer on top of systems a prime operates, or a defined migration scope with inventory, mapping, and dry runs.
The six-part work-package model
Sources sought and RFI response
BCA responds with the decisions the reporting would support, the reconciliation evidence it would deliver, and the data access and hosting it would need the agency to provide.
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.

BCA works with approved data in the agency's or prime's environment. It does not host federal data.
Data governance, retention, and privacy decisions stay with the agency's data owners.
Enterprise data-warehouse programs are prime-scale. BCA takes a defined integration, report set, or migration.

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.

Other capabilities

For Arizona firms: the commercial version

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.

Contact Teton Wilson Capability statement (PDF)

teton@bechosenagency.com · 602-533-0553

Data integration, reporting & dashboards