Keep the permission with the specimen.

A researcher can find the right matrix, timepoint and volume and still be unable to use the specimen. The proposed research must be assessed against its recorded permission, current restrictions, scientific suitability and distribution requirements. Keep that assessment connected to the material and its history.

The fictional request above asks for 0.30 mL per specimen for external genomic analysis. All three candidates have 0.50 mL. BB-017 is outside its recorded consent scope, BB-018 still needs review, and BB-019 has a withdrawal hold. The query has found candidates—not authorised a shipment.

Record the participant or source code, collection protocol, consent document and version, date, recorded scope and any relevant institutional determination. Keep the original source available to authorised reviewers. A summary field makes the assessment searchable; it does not replace the document or decide how it applies.

Capture the distinctions the collection needs: study-specific or future research, analysis type, recipient restrictions, commercial involvement, data sharing, recontact and return-of-results provisions. Represent missing, ambiguous and conflicting evidence explicitly. Do not translate an unanswered question into permission.

Fictional records in the actual Seal interface. Published identifies a saved version, not permission for research use. View full size

Changes need their own history. Link a new consent or determination to the record it updates, retain effective dates and identify which specimens, derivatives, requests and distributions need reassessment. Recontact work needs an authorised scope, assigned owner and recorded outcome; not every unanswered request can be resolved by obtaining a new form.

A withdrawal request starts an assessment of scope and action. Preserve what was received and when, identify the affected specimens and associated data, and record the restrictions needed while the request is assessed.

Stored aliquots, distributed material and derived data need different follow-up. A local inventory hold does not establish what a collaborator still holds, whether a dataset remains in use, or which prior work can be affected.

WR-019 keeps those branches in one assessment. New dispatch is held in the fictional workflow. Recipient follow-up and data review remain open. Record acknowledgements, authorised disposition, execution evidence and any limits on what can be retrieved or changed.

Fictional records in the actual Seal interface. Published identifies a saved version, not permission for research use. View full size

Collection provenance includes the source, method, time, processing delay, matrix, additives and initial condition. Processing links the procedure, equipment, operators, reagents and actual quantities to every resulting aliquot or derivative. A daughter tube keeps its lineage; it does not automatically gain permission for another use.

Model the real storage hierarchy: site, freezer or tank, rack, box and position. Retain moves, temporary locations, retrievals, thaws and returns. Reconstruct occupancy during a temperature event using the event interval and custody evidence; the current freezer map alone cannot establish the exposed population.

Quality is purpose-specific. Keep viability, integrity, concentration, freeze-thaw history and the source measurements beside the requested method's requirements. An acceptable concentration cannot substitute for an unresolved condition history. Preserve the quantity consumed by testing even if its result is later invalidated.

Explore sample management and equipment controls.

A request defines the research question, study, recipient, specimen criteria, amount and associated data needed. Search within the requester's permitted records. Keep the candidate evidence, exclusions, reservations, scientific review and applicable agreements with the request rather than spreading the decision across correspondence.

After the required approval, connect the allocation to the pick, scanned container, packing conditions, logger, custody, shipping details and recipient receipt. A substituted tube needs its own eligibility check. Receipt discrepancies, returned residuals and subsequent use belong in the same history.

Track the outputs as well as the dispatch: analyses, derived datasets, publications and acknowledgements can link back to the distributed specimens. Report the underlying records and counting rules so one publication using many specimens is not accidentally counted many times.

Ask neil to compare the proposed research with permitted source documents and specimen records, reconstruct a withdrawal's downstream scope, or build the request workflow from your protocol. It can prepare linked assessments and configuration for review—not just a written recommendation.

For a new cohort request, ask for candidate specimens and explicit inclusion and exclusion reasons. For a withdrawal, ask for stored descendants, prior distributions, associated datasets and unresolved recipient actions. Missing custody or source evidence should become a linked question, not an invented conclusion.

For a new collection, ask neil to author templates, required fields, references and review states, then prepare verification cases: missing consent evidence, a changed purpose, a withdrawal arriving before dispatch, an insufficient aliquot and an unauthorised attempt to complete the request. It can assemble the proposed change with requirement links and the affected operating procedures.

neil operates within the user's permissions. Authorised people interpret the source and institutional requirements, assess suitability, verify configuration and approve or publish changes. A draft does not grant access to participant identity or authorise specimen use.

Design access around the role and purpose. A researcher may need a coded specimen record and a limited set of characteristics; a custodian or authorised identity-linkage role may need different information. Keep that distinction in the configured permissions and verify it through search, references, exports and API access.

A code is not proof of anonymity. Decide where identity mappings are held, who may access them, what can be exported and how linkage or re-identification is authorised and recorded. Do not place direct identifiers in the research-facing specimen title, free-text notes or a broadly accessible attachment.

Use the collection's institutional governance and applicable requirements to define those controls. The NCI Governance Best Practices provide a reference for governance planning; they do not replace local review or demonstrate software compliance.

Retention follows the collection's governing protocol, agreements and institutional decisions. Preserve the rule, triggering event, review date and any active holds. An elapsed date should identify work to review, not silently dispose of a specimen.

Authorised disposition records the exact material or data in scope, method, executor, time and evidence, with a witness where required. Preserve the history according to the applicable retention and access requirements. A completed local action does not close outstanding recipient follow-up.

Plan for the repository itself: equipment failure, emergency transfers, staffing changes, system recovery and collection transfer or closure. Link procedures, training, equipment evidence and continuity tests to the work. Accreditation and compliance depend on the institution's applicable scope, implemented controls and evidence—not on a software label.

Explore laboratory operations and quality management.