Authorship, review and evidence boundary
- Technical review
- East Baoyu Engineering Editorial Team
- Reviewed
- 2026-09-05
- Scope
- General engineering and procurement guidance. This article is not a project-specific design, capacity statement, certificate, warranty, code interpretation or contract requirement.
Evidence basis: Official and public references identified in the article. Project values and release decisions require qualified review under the applicable project responsibilities.
Read the Editorial PolicyA custom steel structure design change is not local simply because the markup touches one member or dimension. Treat it as a system change until the project can show where the effect stops. Compare the request with the controlled baseline, trace both the load path and the information path, identify physical work already completed, and obtain evidence from every affected owner. Then classify the request as a clarification, a bounded local change or a wider system change. This diagnostic method helps a project engineer decide the review route before anyone edits shop drawings or modifies steel. It does not approve a design, assign contractual liability or authorize fabrication, repair or site work.
Start with the Contradiction, Not the Requested Edit
A change usually arrives as an instruction: move an opening, revise a support, change a member, rotate a plate, substitute a section or accommodate another trade. The first useful question is not “Can the detailer make the edit?” It is “What controlled information does the request contradict?”
Build a short comparison between two states:
- the current baseline: the drawing, model, specification, calculation, interface schedule and commercial scope presently authorized for a named use;
- the requested state: the proposed geometry, function, material, interface or sequence after the change; and
- the physical state: what has already been ordered, cut, drilled, welded, coated, packed, shipped or erected.
Do not let an email attachment silently replace a controlled baseline. Record the requester, reason, affected location, source document, proposed use and urgency. If the request responds to an RFI or clash, preserve the original question and the condition found. If it introduces a new requirement, say so directly.
ANSI/AISC 303-22 provides one U.S. structural-steel contracting framework. Its published text distinguishes documents issued for different purposes and addresses subsequent revisions after structural design documents are issued for construction. That framework is useful for asking who owns the revised information and what it may be used for, but it is not a universal contract rule. The actual project agreement, adopted code and named authorities control. AISC also lists an erratum issued in January 2025, so the project should verify the adopted copy rather than relying on an undated extract (AISC 303-22; AISC revisions and errata).
The initial output is a contradiction statement, not a solution:
The requested state changes [identified information or physical condition] from [current controlled state] to [proposed state] for [stated reason]. The affected design, supply and construction boundaries are not yet confirmed.
That sentence prevents the team from treating the first visible edit as the full scope of the change.
Is It a Clarification, Local Change, or System Change?
Use the following diagnostic tree before choosing the review path. The three outcomes are editorial triage labels; replace them with the project’s contractual terminology and status codes.
A clarification candidate adds an agreed interpretation without changing the technical or commercial baseline. Even then, the interpretation may need distribution to detailers, inspectors and site teams if they could otherwise act differently.
A local-change candidate changes something real, but evidence shows that the consequences stop at a defined boundary. “Local” is therefore a conclusion from an impact search, not a label supplied by the requester. A plate rotation, for example, may look local but could alter bolt access, weld orientation, drainage, coating repair, packing or erection access.
A system change affects, or may affect, more than one design function, interface, deliverable, work package or responsible party. Uncertainty belongs in this route until it is resolved. The purpose is not to make every request large; it is to prevent an untested assumption from making the decision small.
Where Can the Impact Travel?
Trace two paths in parallel. The physical path follows forces, fit, access and construction. The information path follows models, drawings, lists, machine data, inspection records and commercial instructions. A change is bounded only when both paths stop at known points.
| Impact surface | Diagnostic question | Evidence that can close the branch |
|---|---|---|
| Structural behavior | Does the request alter actions, support conditions, stiffness, stability, connection behavior, robustness, fatigue exposure or temporary states? | Responsible-design review, revised calculation or documented no-impact determination tied to the exact configuration |
| Geometry and interfaces | Does it change datums, grids, levels, clearances, tolerances, holes, embeds, equipment, envelope or another trade’s connection? | Coordinated interface check using the current architectural, structural, civil and MEP information as applicable |
| Derived information | Which drawings, model objects, bills, nesting files, CNC data, weld maps, erection diagrams, labels or schedules inherit the changed value? | Dependency list plus verified regenerated outputs with matching revision and use status |
| Fabrication and quality | Which pieces have material committed or work performed, and can the proposed route affect procedure, inspection, traceability, coating or nonconformance status? | Piece-level status, approved technical disposition, revised work instruction and required reinspection evidence |
| Logistics and erection | Does the change alter shipping units, lifting points, temporary stability, erection sequence, site access, survey control or work already installed? | Updated logistics/erection review and site-state confirmation by the assigned parties |
| Commercial and authority | Does it change quantity, scope, schedule, price basis, design responsibility, permit information or approval authority? | Contract-route decision, variation record and named technical/ commercial authorization |
Do not force every row to become applicable. Mark a branch not affected only with a reason and an accountable reviewer. Mark it open when information is missing. A blank cell is not evidence that the consequence does not exist.
This impact table differs from a building system boundary schedule. The boundary schedule defines the original scope before award. The change table starts after a baseline exists and tests whether a new request crosses that scope.
Which Evidence Can Close Each Branch?
A redline shows intent, not completion. Close each applicable branch with evidence that answers four questions:
- What changed? Identify the old and new state at object, member, assembly, zone or document level.
- Who checked the consequence? Name the role with authority for the structural, interface, fabrication, site or commercial decision.
- Which outputs changed with it? Link the calculation, drawing, model, bill, machine file, inspection step, packing list or erection information that carries the decision forward.
- What state is now permitted? State whether the change is accepted for coordination, pricing, procurement, fabrication, construction or another project-defined use.
ISO 19650-2:2018 describes an information-management process for the delivery phase of assets and the exchanges of information within it. ISO’s current page says the edition was confirmed in 2024 but is expected to be replaced by a draft revision. Use that status as a reminder to record the adopted edition and project information requirements; do not convert the standard’s public abstract into a proprietary change workflow (ISO 19650-2:2018).
When teams coordinate through models, an issue record can preserve object identity, viewpoint, owner, comments, status and linked evidence without circulating another uncontrolled model copy. buildingSMART describes BIM Collaboration Format (BCF) as an open standard for model-based issue management and explicitly includes design proposals and change requests among its uses. BCF can support the evidence trail, but software status alone does not grant technical or contractual approval (buildingSMART BCF).
Whatever system the project uses, keep one authoritative change identifier across the question, technical review, revised outputs, commercial decision and closure. If separate platforms assign separate IDs, map them rather than expecting reviewers to infer the relationship.
What If Physical Work Is Already Ahead?
The same requested geometry can require a different response depending on the physical state. Establish that state before promising a date or describing the change as simple.
- No commitment yet: design and commercial effects can be reviewed before material or production is authorized.
- Material committed: check section, grade, length, quantity, reservation and cancellation or reuse constraints.
- Fabrication underway: isolate affected pieces and derived data; identify completed operations and conditions that a later change could invalidate.
- Coated, packed or shipped: protect identity, assess repair and handling implications, and confirm which delivery or site packages must be intercepted.
- Erected or connected: record the as-built condition, temporary and permanent load state, access and site safety boundary before any technical disposition or physical work.
AISC’s July 2026 architecture newsletter gives a practical timing example: a change during shop-drawing review may remain a redline, while the same change after fabrication starts can require refabrication and affect the change-order and schedule route. This is not a universal cost formula. It supports a narrower principle: physical state is part of the change definition (AISC architecture newsletter).
Protect affected work without stopping unrelated work by default. Identify the member, assembly, drawing, work package and site zone that may be affected. Then state what may continue, what must wait, and who can change that boundary. A broad verbal stop creates confusion; an unrecorded partial stop lets the old condition continue downstream.
Worked Example: One Roof Opening, Several Consequences
Consider a hypothetical industrial building. An equipment team asks to move a roof opening after the structural model and initial fabrication documents have been coordinated. The markup changes only the opening outline. The impact search must test more than that outline.
First, compare the new opening with the load-bearing arrangement. Does it interrupt a purlin, beam, deck support, diaphragm path, brace, collector, truss panel or local reinforcement? If the answer depends on another discipline’s load or equipment support, that input becomes an open branch rather than an assumed zero effect.
Next, follow geometry and access. The opening curb, cladding, drainage, fire or maintenance route, duct or cable clearance and installation access may depend on the old location. The structural solution may remain adequate while another interface no longer fits.
Then inspect derived information. A model object may move while a shop drawing, bill of material, nesting file, hole list or erection diagram retains the earlier coordinates. If pieces have already been cut or drilled, the proposed response may require a technical disposition and a new inspection condition—not merely a revised drawing cloud.
Finally, check supply and construction state. Which shipping unit contains the affected member? Is it packed, in transit or erected? Does the modification alter coating repair, field work, temporary support, lift planning or the sequence of adjacent trades? Which contract party owns the redesign, cost and schedule decision?
The example does not prescribe the answer. It demonstrates why the marked object is only the starting node. The change becomes bounded when accountable evidence closes every applicable branch and synchronized documents describe the same final state.
Complete the Custom Steel Change Card
Use one card for each proposed change or clearly linked group of changes. The card is an East Baoyu editorial tool, not an AISC, ISO or buildingSMART form.
| Card field | What to record |
|---|---|
| Change identity | Project identifier, change ID, requester, date, reason and required decision date |
| Baseline contradiction | Controlled document/model and revision, current state, proposed state and affected use |
| Affected population | Members, assemblies, zones, interfaces, deliverables and physical pieces potentially involved |
| Impact branches | Structural, geometry/interface, derived data, fabrication/quality, logistics/erection and commercial/authority status |
| Physical progress | Ordered, cut, drilled, welded, coated, packed, shipped, erected or otherwise committed state |
| Owners and evidence | Reviewer for each applicable branch, required calculation/check/coordination record and current evidence reference |
| Decision | Clarification, local-change candidate, system change, rejected request or another project-defined status |
| Permitted use | Coordination, pricing, procurement, fabrication, construction or other named purpose—and what remains prohibited |
| Synchronized outputs | Revised models, drawings, lists, files, procedures, inspection records, packing/erection information and transmittals |
| Residual actions | Open item, affected boundary, interim protection, owner, due date and evidence required for closure |
The card should be short enough to review but specific enough to reconstruct the decision. Attach or link the detailed calculations, models, drawings and commercial records; do not paste uncontrolled duplicates into the card. Reopen it when the proposal, affected population, physical state or evidence changes.
Related Resources
- Structural Steel Buildings — establish the original system and interface boundaries before a change occurs.
- Custom Steel Fabrication RFQ — remove uncertainty before pricing a custom fabricated assembly.
- Steel Fabrication Drawing Approval Workflow — control drawing review, comments and production use.
- BIM and Model LOD for Structural Steel Fabrication — define what model information may be relied on for fabrication.
References
- American Institute of Steel Construction — ANSI/AISC 303-22
- American Institute of Steel Construction — Revisions and Errata
- American Institute of Steel Construction — Architecture Center Newsletter
- ISO — ISO 19650-2:2018
- buildingSMART International — BIM Collaboration Format
Next Step: Trace One Proposed Change
Choose one live request and complete the contradiction statement, diagnostic tree and Custom Steel Change Card before editing production information. A defensible decision identifies where the effect starts, where it stops, which physical work already exists and which evidence supports the boundary. If any branch is still open, protect only the affected scope and route the question to the named project authority.
When the proposed change affects East Baoyu’s potential supply, submit the controlled baseline, requested state, affected member or assembly IDs, current fabrication/site status, design and interface questions, required decision date and requested commercial scope through Steel Structures. East Baoyu can clarify available manufacturing-document inputs and the quotation effects that require review. The project’s appointed designers, contractors, inspectors and commercial authorities retain responsibility for design adequacy, change approval, site safety, contractual entitlement and permission to proceed.
References, disclosure and change record
References and further verification
- https://www.aisc.org/globalassets/aisc/publications/standards/a303-22w.pdf
- https://www.aisc.org/aisc/publications/revisions-and-errata/
- https://www.iso.org/standard/68080.html
- https://info.buildingsmart.org/standards/bsi-standards/bim-collaboration-format/
- https://www.aisc.org/architecture-center/newsletter/
- https://eastbaoyu.com/structural-steel-buildings/
- https://eastbaoyu.com/custom-steel-fabrication-rfq/
- https://eastbaoyu.com/steel-fabrication-drawing-approval-workflow/
- https://eastbaoyu.com/bim-model-lod-structural-steel-fabrication/
- https://eastbaoyu.com/steel-structures/
Disclosure: East Baoyu manufactures and supplies products discussed on this website. Structured drafting tools may assist research and editing, but technical claims, project inputs and release decisions require qualified review under the applicable project responsibilities.
Version 1.0: Scheduled as EB50-021 on 2026-09-05.
View the public Content Change Log · Corrections: info@baolaipipes.com
