Understand definitions, records, and execution
Keep the system model, operating content, and actual work distinct.
Three layers, three responsibilities
| Layer | What it describes | Example |
|---|---|---|
| Definition | The fields, relationships, lifecycle, forms, and permitted actions for a type of record. | The Master Batch Record record type. |
| Record | Specific content authored under a published definition. | MBR-104, including its ingredients and instructions. |
| Execution | Actual work performed against an applicable approved revision. | Batch B-0934, its observations and sign-offs. |
Configure a type before creating its records
A definition determines what information belongs in the record, how it relates to other records, and which actions are available. A form is a view of that model. Editing a form field on one record does not redefine the whole record type.
Use organization-specific fields and terminology where they add meaning. Preserve stable identifiers, units, and relationships so other workflows can interpret the information consistently.
Publication and use are separate decisions
Drafting a change does not make it effective. Review and activation determine when the changed model or operating content can be used. An execution should retain the revision that governed it, including after a later revision becomes effective.
- Check whether you are editing a type, a record, or an execution.
- Review the impact of a definition change before activating it.
- Use the applicable source revision when interpreting historical evidence.