Digital delivery modules

Separate the work before assigning the owner.

Each package starts with the same questions: what can BCA own, what inputs are required, what evidence demonstrates acceptance, and what authority stays elsewhere?

Separable work package

Content, architecture & migration

BCA can own

Content inventory and disposition model
Information architecture and page mapping
Redirect matrix and migration QA

Inputs, acceptance, and retained authority

Inputs required: Approved source inventory
Target platform constraints
Content owners and review windows
Acceptance evidence: Approved inventory and mapping artifacts
Traceable redirect coverage
Documented migration QA results
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Separable work package

Accessibility assessment & remediation support

BCA can own

Accessibility risk review
Remediation backlog and pattern guidance
Accessible UX and content acceptance testing

Inputs, acceptance, and retained authority

Inputs required: Approved URLs or builds
Applicable accessibility requirements
Access to content and component owners
Acceptance evidence: Reproducible issue records
Prioritized remediation decisions
Dated retest evidence and remaining-risk log
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Separable work package

CRM, intake, routing & workflow

BCA can own

Workflow and decision mapping
Intake, routing, and status configuration
Exception queues and operating documentation

Inputs, acceptance, and retained authority

Inputs required: Approved process owners
Current forms and status definitions
System access and integration constraints
Acceptance evidence: Tested happy and exception paths
Role and routing matrix
Operating guide and handoff record
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Separable work package

Dashboards, reporting & visibility

BCA can own

Metric and decision definition
Data mapping and report implementation
Reconciliation checks and report guidance

Inputs, acceptance, and retained authority

Inputs required: Approved data sources
Metric owners and definitions
Access, retention, and refresh constraints
Acceptance evidence: Traceable metric definitions
Source-to-output reconciliation evidence
Known limitations and operating instructions
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Separable work package

Bounded AI assessment & prototype

BCA can own

Use-case and risk framing
Synthetic or approved-data prototype
Evaluation criteria and observed-result record

Inputs, acceptance, and retained authority

Inputs required: Named user and decision
Approved data boundary
Human review and failure-handling rules
Acceptance evidence: Reproducible prototype demonstration
Evaluation record against agreed cases
Deployment gaps and decision memo
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Separable work package

Documentation, testing, training & handoff

BCA can own

Acceptance-test planning and execution support
User and operator documentation
Training sessions and handoff inventory

Inputs, acceptance, and retained authority

Inputs required: Current build and scope baseline
Named operators and reviewers
Required artifact formats and repositories
Acceptance evidence: Signed or recorded acceptance results
Complete handoff inventory
Open-risk and ownership register
Buyer or prime retains: Platform authority
Security authorization
Hosting
Overall program management
Enterprise operations and maintenance

Start with the work

Match a package to a real requirement.

Share the buyer, acquisition context, expected role, safe source material, and timing.

Discuss the right work package