Getting started
FlaskTrack separates reusable definitions from execution records. Define the procedure once, review it, and then execute the approved version through batches or samples.
Setup sequence
flowchart LR
A[Catalog records] --> B[Protocol]
B --> C[Protocol steps and forms]
C --> D[Workflow]
D --> E[Review and approval]
E --> F[Batch or sample execution]
F --> G[Evidence, inventory, audit, reports]Catalog records
Create reusable species, ingredients, tools, and plasmids. Add suppliers and supplier items when procurement or inventory tracking is needed.
Protocols
A protocol defines one laboratory procedure. Each protocol version has ordered steps, requirements, timing, structured data capture, and optional compliance controls.
Workflows
A workflow combines protocols into an operational sequence. Scheduled offsets determine when each protocol is expected to begin relative to workflow start.
Review and approval
Drafts and AI-assisted records remain reviewable. Approval should be based on the exact version, scientific content, required materials, form validation, and applicable compliance controls.
Execution
Create a batch for grouped work or a sample workflow for individually tracked work. FlaskTrack creates execution records from the selected workflow version and maintains their relationship to source definitions.
Minimum production configuration
Before production use, verify:
- user roles and account security;
- approved protocol and workflow versions;
- timezone and scheduling behavior;
- required forms and validation rules;
- inventory defaults and step overrides;
- alert destinations;
- audit and electronic-signature expectations;
- backup, retention, validation, and incident procedures owned by your organization.
Next steps
Begin with roles and permissions, then create a protocol and workflow.
After the core operating model is familiar, review the Digital Lab Assistant for natural-language questions and controlled action planning.