Concrete mix submittals: coordinating designer and supplier reviews
Admin · 22 October 2026
Illustrative image. Photo by Saad Salim on Unsplash. Unsplash License.
A concrete mix submission needs a clear relationship to the application for which it is proposed. A supplier can provide a technically detailed document while the project remains uncertain about which specification, location or delivery arrangement it addresses. Coordinating the review means giving the responsible specialists a defined proposal and ensuring their conclusions reach procurement and site planning before the work relies on it.
For package managers, the role is to organise information and decisions. Mix design, specification and acceptance require competent technical assessment. The management process should not invent technical values or substitute a general checklist for the actual requirements. It should make the review scope, current references and remaining actions clear.
Identify the application and specification
State the proposed location or element and the design information that governs it. Where the project has several applications, avoid assuming one submission covers all of them. Ask the designer and supplier to confirm the relevant scope. Stable references help the team connect comments and decisions to the intended work.
Provide the current specification and clarify unresolved information through the appropriate technical route. A supplier should not have to infer a requirement from conflicting drawings or an old enquiry. Record the questions and their owners, with dates linked to the planned supply. This helps prevent a review from progressing on a basis that another team has already changed.
Define the required submission
The responsible designers and specialists should identify the evidence required for the actual application. The package team can then communicate that request clearly to the supplier. A complete submission is one that addresses the defined questions, not simply one containing many pages. Ask for an index or clear references where it helps reviewers locate the relevant information.
The Concrete Centre’s specification guidance provides industry context for considering concrete requirements and lower-carbon options. The project’s appropriate specialists should determine applicable current standards and technical evidence. This article does not prescribe a mix or claim that one generic submission format suits every concrete application.
Assign reviewers and decision authority
Identify who reviews each relevant aspect and who coordinates the overall response. The designer, supplier and delivery team may hold different responsibilities. Make the purpose of each review explicit. Attendance at a coordination meeting should not be interpreted as acceptance of matters outside a participant’s actual scope or authority.
Record the status resulting from review under the project’s procedures. A request for additional information is different from a conclusion that the proposal is ready for a defined use. The buyer and site team should understand what may proceed and what remains conditional. Ambiguous language can create conflicting assumptions at the point of ordering.
Bring delivery requirements into the discussion
Give the relevant specialists a clear account of the intended work sequence and site constraints. They should assess the technical implications and required controls. The package manager should identify dependencies and make sure the right information reaches the people planning and undertaking the work. The package manager should not improvise placement or other technical instructions.
Consider a hypothetical package where the design submission is reviewed before the contractor has confirmed the intended delivery sequence. The team needs to establish whether the proposal and planning assumptions remain aligned. A technical review of one basis should not be treated as approval of an arrangement that has changed materially without further consideration.
Manage comments as specific questions
Review comments should identify the relevant requirement, information gap and response needed. A broad instruction to comply can leave the supplier uncertain about what prevented completion. Where a question requires another designer or specialist, name the route. The coordinator should track the response rather than assume that forwarding the comment resolves the matter.
When information returns, identify what changed and link it to the earlier comments. Reviewers need a clear account of the revision so they can assess it efficiently. Retain the earlier issued record as required by the project. Quietly replacing a file without a revision trail makes it difficult to establish what the team actually reviewed.
Connect review with the supply programme
Work backwards from the planned use to establish when the submission and decisions are needed. Include time for questions, further evidence and the supplier’s confirmation. If an input is not available as assumed, assess the consequence with the planner and relevant technical team. A deadline does not establish that an unresolved proposal is suitable.
Keep requested dates distinguishable from confirmed commitments. The supplier may attach conditions to availability. Record those conditions and identify the project actions needed to support them. A programme line that says mix approval complete should correspond to a defined decision and evidence, not merely the date a document was uploaded.
Control changes after review
Establish what changes require reassessment under the project’s arrangements. The relevant specialists should determine the technical significance. Communicate the process to the supplier, buyer and site team so a revised proposal is not treated as an informal purchasing adjustment. Keep the exact product or mix reference connected to the accepted record.
The APM change control overview provides general context for controlled decisions. The actual contract and technical procedures govern what must happen on the project. Record the reason, authority and revised information where a change is accepted, including any consequence for associated evidence or planning.
Agree records for supply and verification
Ask the appropriate technical and quality teams to define the records and checks required during delivery. Identify who collects the information, who reviews it and how it connects to the relevant work. The package manager should make the process practical without substituting personal judgement for the specified technical criteria.
Keep consequential discrepancies visible and route them promptly. A record that does not match the expected reference needs the appropriate review. The team should not assume equivalence because descriptions look similar. Retain the decision and evidence so later users can understand how the matter was addressed.
Reconcile the final package record
At closeout, confirm that the required technical information and relevant delivery evidence describe the work actually provided. Assign owners for outstanding records and identify the appropriate acceptance route. The receiving organisation should understand the scope and status of the information rather than receive an unexplained folder of mixed revisions.
Review which submission questions appeared late and why. The cause may concern an unclear application, missing design information or an uncommunicated delivery change. Apply a specific improvement to the next package. A useful mix-submittal process gives competent reviewers a clear proposal, connects their decision to supply and preserves a traceable account of the basis the project relied on.
Use a clear response schedule
For each significant comment, show the original question, supplier response, revised reference and review outcome. This makes it easier to see whether the response addresses the issue or merely supplies another general statement. The technical reviewer should determine adequacy; the coordinator ensures the question does not disappear between versions. Where a response affects another discipline or planned activity, identify the linked action rather than treating closure as a local document task.
Keep the schedule proportionate to the submission. Its purpose is to help competent people follow the evidence, not create a second uncontrolled technical specification. Use stable references and the project’s status conventions. When the review is complete, retain the accepted information set and explain any remaining conditions to those managing supply. A new package manager should be able to locate the final position without interpreting several contradictory email threads or assuming that the most recent attachment is automatically the authorised one.
Identify the final review reference in the package handover so incoming personnel can locate the accepted information without reconstructing the comment history.
