API project definition
Describe the API purification project using the material and project identifiers approved by your team. Request clarification of the intended separation task before equipment selection.
Use api project brief to describe the decision your project team needs to make and the material or output it wants reviewed. Separate the requested outcome from the observations your own reviewers will assess. Ask the bidder to identify unanswered questions in that target description and to relate its response to the same project objective before commercial scope is discussed. Identify the review question associated with the requested output so that the proposed scope can be assessed against the purpose of the enquiry.
API starting material records
List the starting material documents available for supplier review and identify the owner of each. Ask which additional information is needed to assess the request.
For api starting material records, identify the submitted material, its project reference and the person authorized to release its description. Distinguish information already attached from information that needs approval before sharing. Ask which additional sample records are needed to assess the requested work, and agree how later questions will refer back to the same material without confusing separate preparations. Ask the sample owner to distinguish material available for an initial discussion from any material that would need separate approval for submission.
API analytical review
Define the analytical questions for your laboratory reviewer. Request the documents needed to discuss those questions in relation to the proposed purification scope.
Use api analytical questionnaire to separate the questions assigned to each project reviewer and the documents needed to answer them. Connect each open question with the proposed item or stage it affects. Ask for a response addressing those questions individually, and have the responsible reviewer record the agreed description that the purchasing team should use when it prepares the request for commercial terms. Ask the assigned reviewer to distinguish a request for more information from approval of the proposed item, so that open questions remain clear.
API method information
Attach the existing method information your team may release and identify unresolved development questions. Ask for a proposed review sequence before agreeing further work.
Organize api method brief around the current method description, the observations available for disclosure and the questions still unresolved. Identify the author or owner of the method record so that requests for additional information reach the appropriate project role. Ask which parts of the proposed work depend on further method information, and keep those questions attached to the current method discussion. Ask the method owner to mark documents that describe completed work separately from proposed changes awaiting a laboratory decision.
API sample and collection records
Describe the required links between submitted samples and collected material. Ask how the proposed project documentation would identify and report them.
In api sample record plan, specify the labels needed to connect collected material with the starting sample and the intended review. Describe the record fields your laboratory needs, including the project reference and the description of the material presented for assessment. Ask for a proposed record layout and have the laboratory compare it with the way it plans to receive and interpret the results. Include a request to distinguish the starting material identifier from the identifiers proposed for subsequently collected samples and their accompanying records.
API purchasing boundaries
Separate equipment purchase requirements from requested method or purification discussions. Ask each bidder to identify the exact scope addressed in its response.
For api purchasing schedule, identify the requested items individually and describe the boundary of each item in plain language. Ask the bidder to mark the equipment or work addressed by its response and identify any requested element needing separate discussion. Keep the proposed scope connected to the project brief so that a price comparison relates to the same requested equipment or work. Request separate identification of requested items that remain open for discussion so that they can be reviewed without obscuring the proposed inclusions.
API purification requirements: documents to request
| Ask about | Request with your inquiry |
|---|---|
| Which details should the api project brief identify for api project definition? | API project brief |
| Which details should the api material dossier identify for api starting material records? | API material dossier |
| Which details should the api analytical questionnaire identify for api analytical review? | API analytical questionnaire |
| Which details should the api method brief identify for api method information? | API method brief |
| Which details should the api sample record plan identify for api sample and collection records? | API sample record plan |
| Which details should the api purchasing schedule identify for api purchasing boundaries? | API purchasing schedule |