01 Answer first
How should technical submittals be reviewed in a turnkey water bottling project?
Schedule each submittal against a project gate, define completeness, assign decision-specific reviewers, classify comments, state what each approval status authorizes, resolve conflicts, and preserve comment closure through controlled revisions.
02 Where it fits
Position in the project journey
Project execution — from initial vendor data through approved-for-use and final records.
03 Buyer inputs
What the buyer should prepare
- Reviewer roles and decision authority
- Local confirmation and buyer inputs
- Response and release priorities
04 Allot Tech and manufacturing-resource inputs
What should be clarified or provided
- Complete controlled submittals
- Comment responses and revised evidence
- Disclosure of downstream dependencies
Allot Tech coordinates requirement, quotation and project communication. Detailed engineering, manufacture, testing, documentation and confirmed service are performed by selected manufacturing resources according to the signed scope.
05 Technical scope
Questions and work to control
Create the Submittal Schedule From Project Gates
List each required drawing, calculation, specification, data sheet, sample, procedure, and record with planned issue, review, and release dates.
Define a Complete Submission Package
State mandatory references, revision notes, supplier checks, interfaces, open items, native or published format, language, and linked documents needed for review.
Assign Reviewers by Discipline and Decision
Name technical, quality, operations, maintenance, site, safety, commercial, and qualified local reviewers only where their decision is required.
Use Controlled Comment Categories
Differentiate correction, clarification, deviation, preference, local confirmation, information, and hold points so each response has the right consequence.
Define What Each Status Authorizes
Approved, approved with comments, revise and resubmit, rejected, or information-only status should state which dependent work may proceed and under what conditions.
Resolve Conflicting Comments
Route discipline conflicts to the named decision owner and update the governing requirement or interface instead of asking the supplier to choose silently.
Control Resubmission and Comment Closure
Require a response to each comment, visible changes, retained history, updated references, and closure confirmation at the next revision.
Measure Review Risk Against the Schedule
Track overdue inputs, incomplete reviews, repeated comments, conditional approvals, and downstream activities at risk before they become manufacturing delays.
Buyer questions answered
Practical answers before you request a quotation
Does approval transfer design responsibility?
Approval meaning and responsibility should be defined in the signed agreement and project procedure; review does not silently rewrite them.
Can comments be closed by email?
Relevant decisions should be incorporated into the controlled document, response record, and revision history.
Who resolves conflicting reviewer comments?
The project should name the authorized decision owner for the affected requirement or interface.
06 Responsibility
Assign the owner before the work is due
Land, building and civil work, permits, import and customs, local taxes, site utilities, unloading, lifting, local labor, travel support and commissioning materials are not automatically included. Confirm every responsibility before order.
07 Common risks
What commonly creates avoidable uncertainty
- Incomplete packages start the review clock
- Approval status has no defined meaning
- Email decisions do not reach controlled documents
08 Acceptance or completion
How to know the stage is complete
A submittal closes when required reviewers decide, every comment has a response and status, and the authorized revision is recorded.
09 Required documents
Records that support the decision
- Submittal schedule
- Comment-response sheet
- Approval-status register
10 Next project step
Turn this decision into a reviewable project brief
Share the product, container, target output, destination and available site information. Unknown inputs can remain open for the first review.
Turnkey scope is project-specific and is defined by the signed technical and commercial agreement.