Peptide Testing Deliverables: Agree Reports, Files and Access Before Ordering

Start with the work your team will do after delivery

Write one sentence before comparing quotations: “Our team needs to [action] using [output] in [working environment].” For example, the action might be importing results into a project table or asking a specialist to revisit a defined processing question. Identify the person who will perform it, rather than letting procurement guess the required format.

Separate a readable conclusion from reusable results and reviewable measurement records. A PDF may communicate the laboratory’s findings. A structured results file may make comparison easier. Instrument files may support additional work when the required content, software and permissions are available. Receiving one does not establish that the others are included.

There is a concrete reason to ask. Novatia’s published peptide/protein service page lists raw-MS-data posting as an additional service. That is one supplier’s arrangement, not an industry pricing rule or a reason to assume what another laboratory includes. Novatia service page.

Copy a delivery-scope matrix into the quotation discussion

Use the rows relevant to the project. Mark each as included, separately scoped, unavailable or not required, and add the agreed reference. The matrix is an editable procurement tool, not a laboratory qualification standard.

Avoid labels such as “full data package” unless the attached list explains them. If a laboratory cannot supply a requested item, record the limitation before placing the order. Decide whether another deliverable, an agreed review session or a different scope meets the project’s need; do not presume access to its systems or proprietary methods.

Compare the useful scope, using a clearly hypothetical example

Consider a hypothetical peptide research project that will place external results into an internal comparison table. Proposal A names a final PDF. Proposal B also names a structured results file, but its column definitions and sample mapping are unresolved. No prices, turnaround times or real customer results are assumed.

B is not yet the more usable delivery. The receiving team still needs to agree the fields and test a representative example. A could meet the project’s immediate need if the team only needs the report’s conclusion. If later reprocessing is planned, neither description establishes that the relevant instrument records and reader are available.

Compare the proposals against the selected matrix rows. Ask each laboratory to confirm the same requested function and to separate included work from an additional export, interpretation or review activity. Agree a written scope reference, so a later request does not depend on two different understandings of “report included.”

Check readability before the real results arrive

Ask for a blank template or an authorized, non-confidential example. Do not ask the laboratory to disclose another client’s records. Check file type, reader and version, any license or account requirement, and the intended access route. Name the people who will confirm that the format works in your environment.

For a structured export, agree the field definitions, units, missing-value convention and sample identifiers relevant to your workflow. For instrument records, ask the intended reviewer what supporting context is needed for the specific task. An export label alone cannot answer that question. A failed import may be a receiving-system issue, a format mismatch or a delivery gap; agree how the parties will distinguish them.

Keep a delivered package as received and identify any working copies used for conversion or internal comparison. Record who handles conversion and how the relationship to the supplied files will remain clear. Technical controls should fit the project; a file checklist alone does not establish that the experiment was valid or the material acceptable.

Keep access, custody and applicable record obligations separate

A laboratory’s agreement to retain records does not by itself give the buyer a downloadable copy or continuing portal access. Conversely, receiving files does not settle ownership, reuse permission or the laboratory’s remaining obligations. Write these points separately, including what happens when an account closes or a download link expires. Let the relevant contract and quality reviewers confirm the terms; this article assigns no universal retention period or legal entitlement.

FDA’s 2018 guidance addresses drug-CGMP records. Q1(b)/(d) distinguish contextual information and record functionality; Q9/Q10 explain why copies and available readers must preserve what the applicable record requires. These provisions are not a blanket instruction for every research order to deliver all raw files to the buyer. FDA final guidance, Q1(b)/(d), Q9/Q10.

For a regulated project, the responsible quality team should determine the required records and review arrangements before commercial scope is finalized. For other projects, define the useful delivery explicitly rather than borrowing a CGMP checklist without assessing its relevance.

Send a confirmation that the receiving team can approve

Copy and adapt this template. Remove rows that are not needed and replace the placeholders; it does not prescribe a testing service.

Subject: Confirming deliverables for [project / quotation reference]

Our receiving team needs to [specific action] using [working environment]. Please confirm the attached delivery-scope matrix before we place the order.

For each requested item, identify the files and versions supplied, the supporting information included, any exclusions, and whether it is included in this quotation or separately scoped. Please distinguish the final report, structured results and any agreed instrument records.

Please provide a blank or authorized non-confidential example so [recipient / reviewer] can check readability, field definitions and sample mapping. Identify the reader, license or account conditions, and any functions the supplied format does not support.

Confirm the transfer route, permitted recipients and use, access period, record-retention arrangements and local-archive responsibility. Please distinguish retention by your laboratory from the copies or access delivered to us.

If an agreed file is missing or unreadable, who will assess the issue and what correction is included? Please list requests that would be treated as additional interpretation, conversion or new work. We will confirm any applicable quality or regulatory record requirements through our responsible reviewers.

Please return the agreed scope reference and name the delivery contact. We will name our receiving and review contacts separately.

Have the receiving team approve the agreement for usability, and the analytical or quality team approve the relevant scientific and record requirements. A successful download is a handover check, not scientific acceptance.

For a peptide material project, the quality and documentation page provides context for discussing existing records. Share a non-confidential project outline through the technical inquiry route when you need to clarify material and documentation scope. This article does not offer third-party testing, certify a laboratory, or promise to receive and hold external instrument files.

Sources checked: 2026-10-13. FDA guidance and the named supplier page support the limited statements attributed above. The matrix, hypothetical comparison and confirmation message are editorial tools for defining a project-specific order.