Buyer Guidance
Steel Structure Project Responsibility Matrix: A Buyer’s Working Guide
A simple working record can keep project inputs, confirmations, and controlling documents visible before an instruction is treated as final.
The direct answer
Before an RFQ or cross-party project decision is treated as final, put the decision in one shared responsibility matrix. Name the person or party expected to provide the input, the person or party expected to confirm it, the document that records it, and the point at which the project team will treat it as settled.
The value is not a universal allocation of liability. It is a practical way to expose unanswered questions early: who is providing the current brief, who is checking the design or local requirements, who is issuing any formal QC or inspection record, and which signed document controls an obligation. Until the project team can answer those questions, the matrix should show the item as open.
Working record
What this working matrix is—and is not
A responsibility matrix is a coordination record for a cross-party project review. It can help buyers, project managers, coordinators, suppliers, and appointed professionals see whether an item has an identified owner and a traceable record.
It does not:
- transfer contractual responsibility;
- replace design review, code-compliance work, authority approval, or local professional judgment;
- certify a product, inspection result, programme, price, capacity, or project outcome; or
- make a person an engineer of record, inspector, contracting party, or approver simply because their name appears in a spreadsheet.
Signed project documents remain the source of contractual responsibility. Local design, code-compliance, and authority matters remain with the buyer-appointed professionals. Formal inspection is issued by factory QC or an appointed third party, within the scope actually agreed for that project.
Role clarity
Start with five roles—not five assumptions
Use the labels below as a starting point, then replace them with the people and entities actually involved. The wording deliberately separates coordination from formal authority.
| Role | Useful working contribution | Boundary to record in the matrix |
|---|---|---|
| Buyer or buyer’s project manager | States the project brief, commercial priorities, and the people authorised to give project instructions. | Confirm which instructions need written confirmation and who is authorised to give it. |
| Buyer-appointed local professional | Addresses the project’s design, local code-compliance, and authority-approval questions within their appointment. | Record the appointed person’s scope; do not assume another party has this authority. |
| China-side coordinator | May support sourcing, factory matching, quotation and scope coordination, production follow-up, evidence coordination, and export-handover coordination. | Coordination does not equal formal design approval, inspection, acceptance, or contractual authority. |
| Factory QC or appointed third-party inspector | Issues any formal QC or inspection record only where that party is appointed and the record’s scope is clear. | Identify the issuer, appointment, scope, and record—not a presumed result. |
| Contracting parties | Allocate obligations through the documents they execute. | The matrix should point to the controlling signed document rather than restate or alter it. |
YYN’s approved role is China-side coordination and sourcing support. This guide does not describe YYN as a manufacturer, fixed-factory owner, inspector, engineer of record, or necessarily a contracting party.
Decision record
A simple decision-and-record matrix
Create one row for each decision that could otherwise be misunderstood. Keep the entries factual and project-specific. If a field is unknown, write “to be confirmed”; do not fill the gap with an assumption.
| Decision or question | Proposed input owner | Confirmation needed from | Record to identify | Status |
|---|---|---|---|---|
| Current project brief and quotation basis | Buyer / project manager | Person authorised by the buyer | Current dated brief or written instruction | To be confirmed |
| Design, local code, or authority requirement | Buyer-appointed local professional | Relevant appointed professional or authority process | Referenced drawing, calculation, or approval route, if applicable | To be confirmed |
| Factory-facing scope clarification | Buyer / project manager and coordinator | Party authorised to settle the scope | Written clarification linked to the quotation basis | To be confirmed |
| Formal QC or inspection record | Factory QC or appointed third party | The party that defined the required record | Record issuer, scope, and date | To be confirmed |
| Change after a quoted basis | Relevant project parties | Person or party named in the controlling process | Revision or change record linked to the affected basis | To be confirmed |
| Contractual obligation or acceptance point | Contracting parties | The parties to the signed document | Signed document reference | To be confirmed |
This is intentionally a working framework, not a list of mandatory project stages. A small project may need fewer rows; a complex project may need additional rows for interfaces, delivery handover, or document revisions.
Review questions
Questions that prevent a false “final” signal
At a cross-party review, ask these questions before marking a row complete:
- What exactly is being decided or confirmed?
- Which version of the brief, drawing, quotation basis, or record is being discussed?
- Who is providing the information, and who has authority to confirm it for this project?
- Does the item require input from a buyer-appointed professional, factory QC, an appointed third party, or the contracting parties?
- Where will the confirmed position be recorded, and who receives that record?
- If the item changes, what reference in the matrix must be updated?
The goal is clarity, not bureaucracy. A clear “not yet confirmed” entry is safer than an ambiguous checkmark.
Limitations to keep visible
Coordination can clarify a record; it does not create formal authority.
This guide cannot determine local legal duties, engineering adequacy, inspection requirements, acceptance conditions, or contract allocation. Those matters depend on the project, the appointed professionals, the inspection appointment, and the documents the relevant parties sign. It also does not prove that a factory, coordinator, inspector, or buyer has performed an action or achieved an outcome.
Apply this guide to your project
Send the documents you have and the responsibility question you need to clarify.
YYN can help identify missing inputs and open assumptions without replacing project engineering, inspection, or contractual authority.
