Make the handoff from incoming sample to assigned work clearer.

1. Can you match every sample to the right client and project?

   Agree the client, contact and project details required before intake.

2. Does each sample have one clear, unique identity?

   Trace a field label to its lab identifier and decide how duplicates are resolved.

3. Do you record who collected and received the sample, and when?

   Walk through a sample record and agree who fills in missing collection or receipt details.

4. Is there a clear decision path when a sample arrives with a problem?

   Name who can accept, hold or reject a sample using your approved procedure.

5. Does each accepted sample have agreed tests and an owner?

   Check one request from test selection through assignment, due work and escalation.

6. Are the report contents and recipients agreed before work starts?

   Confirm the required report scope, recipients and publication authority for one request.

Find what needs to be settled before moving laboratory data.

1. Do you know which records must move and which must stay accessible?

   Inventory active and historical records, then name the archive and retention owner.

2. Can you open usable exports, including attachments and past reports?

   Open a representative export and retrieve its attachments and issued report.

3. Have you agreed how old fields and record links fit the new system?

   Review sample field mappings, units, history and duplicate or missing-value decisions.

4. Have you compared migrated records with their originals?

   Compare record counts and inspect a complete sample, its results and report against the source.

5. Have the right people tested access and everyday work?

   Have named users try intake, review and publication, including actions their role must not allow.

6. Is there an agreed, tested plan for switching over or going back?

   Rehearse restoration and agree freeze handling, rollback triggers and final sign-off owners.

Check the path from completed results to an authorized report.

1. Can a reviewer verify who and what the report covers?

   Check report grouping, client, project and sample identifiers against the request.

2. Are the results, units and important comments complete and checked?

   Review included and excluded tests, methods, units, qualifiers and incomplete work.

3. Are review questions resolved by an authorized person?

   Confirm the required quality evidence and name who resolves returned or incomplete work.

4. Has someone inspected the actual finished report layout?

   Open the approved template output and check long comments, page breaks, attachments and missing values.

5. Can only approved people release the report to approved recipients?

   Test allowed and denied publication actions and confirm the recipient and delivery approvals.

6. Can you retrieve the final report and clearly identify corrections?

   Retrieve an issued report and check how a correction identifies the superseded version.

Clarify receipt decisions without guessing at acceptance limits.

1. Does the receiving team know which approved procedure applies?

   Identify the approved method, procedure revision and project requirements for a representative sample.

2. Can you match field labels, lab labels and custody records?

   Trace a sample through its field identifier, lab identifier and custody paperwork.

3. Are collection and receipt times clear, including time zones?

   Check date, time, time zone and receiving staff details; agree how missing information is handled.

4. Are sample condition, containers and preservation checked and recorded?

   Record actual observations and compare container and preservation details with the applicable approved procedure.

5. Does a qualified person decide what to do with delays or missing details?

   Name who reviews applicable holding-time requirements and records acceptance, hold, qualification or rejection with reasons.

6. Do receipt exceptions follow the sample into work and reporting?

   Trace one accepted deviation into preparation, assignment and the reviewed deliverable.

Turn vendor conversations into evidence you can actually compare.

1. Have you seen your real sample workflow demonstrated, including mistakes?

   Ask for a sanitized intake-to-retest scenario that includes missing information and a correction.

2. Have you checked calculations and reports against your own examples?

   Compare approved reference inputs, units and expected outputs, plus a report and relevant field or lot details.

3. Have you seen who can review, correct and publish work?

   Observe both allowed and denied actions for your roles, including returned-for-correction work.

4. Have you tested how data comes in, moves across and comes back out?

   Open a sanitized import and export, trace identifier matching, and inspect a migrated record and archived report.

5. Are rollout, recovery and ongoing support responsibilities clear?

   Request restoration evidence and agree rollout sign-off, rollback authority and support escalation owners.

6. Are must-have features proven today, with unresolved needs called out?

   Separate current, scoped and planned capabilities, then record any unresolved launch requirement without averaging it away.