Batch Detail View
The Batch Detail View shows the live execution state of a workflow run.
Batches represent grouped execution of protocols across multiple samples, with shared scheduling, progress tracking, and compliance context.
Batch Header
At the top of the page, you'll find key batch metadata:
- Batch name
- Domain
- Associated species
- Workflow
- Creation timestamp
- Current batch state (e.g. Sterilized, In Progress, Completed)
Quick actions provide access to:
- Printable batch identifiers and QR codes
- Workflow navigation
Batch Progress Summary
The progress summary provides a real-time overview of execution status:
- Completed batches
- Unperformed steps
- Active progress
- Percent completion
This section is useful for supervisors and technicians monitoring execution at a glance.
Batch Samples
Each batch automatically generates batch samples, which represent individual biological units created during batch setup.
From this section, users can:
- View all samples associated with the batch
- Navigate to individual sample detail views
- Track per-sample execution status
This structure enables bulk planning with individual traceability.
Protocol Schedule
The Protocol Schedule is the core execution timeline for the batch.
It shows:
- All protocols in workflow order
- All steps within each protocol
- Scheduled execution times
- Completion status per step
Each protocol section includes:
- Links to the protocol definition
- Links to the protocol schedule view
Executing Steps
Each protocol step may be:
- Scheduled
- Pending
- Completed
- Skipped
- Failed or contaminated (where applicable)
Technicians can:
- Mark steps as complete
- Record execution timestamps
- Trigger state transitions automatically
All step completions are recorded as immutable execution events.
Execution Timeline
As steps are completed, the batch timeline is populated with:
- Workflow start events
- Step completion events
- Manual actions
- System-generated state changes
The timeline provides a chronological execution log suitable for review and audit.
Compliance Section
If compliance frameworks are enabled, this section displays:
- Applicable compliance requirements
- Checklist completion status
- Required evidence
- Approval gates (where configured)
Compliance state is evaluated continuously as execution progresses.
Batch Files
Files attached to a batch may include:
- Images
- PDFs
- Exported reports
- Supporting documentation
Batch files are distinct from sample-level files but may be referenced together in reports.
Batch Lifecycle
A batch progresses through the following lifecycle states:
- Created
- Pending
- In Progress
- Completed
or - Failed / Contaminated / Aborted
State transitions are recorded automatically and cannot be edited retroactively.
Relationship to Samples
- Batches define shared execution context
- Samples carry individual biological history
- Protocol execution affects both batch and sample records
This design allows Flask Track to scale execution without losing traceability.
Who Uses This Page?
- Technicians execute and complete protocol steps
- Scientists monitor experimental progress
- Administrators oversee operations and compliance
- Auditors review execution integrity and timelines
If you want to know what is happening right now, this is the page to use.