MEP Coordination Meeting Notes for Small Jobs

The mechanical foreman can move the exhaust duct six inches. The electrician can move the light. The plumber cannot move the sanitary branch without checking slope and ceiling clearance. The sprinkler fitter is waiting for direction. The ceiling crew starts tomorrow.

Everyone stands below the same crowded soffit and agrees to "make it work."

Two days later, nobody remembers which item was supposed to move first. The electrician says the light location was approved. The designer says no revised layout was issued. The plumber has already installed part of the branch. The owner did not know the solution would lower the ceiling. A verbal coordination win has become demolition, a change request, and another mobilization.

The meeting was not the failure. The missing record was.

For a small tenant improvement, restaurant renovation, office buildout, equipment replacement, or multifamily turnover, an MEP coordination meeting does not need a federated BIM model, a full-time VDC team, or an hour-long transcript. It needs the current drawing or a marked photo, the people who understand the affected work, and notes that turn every conflict into:

• an exact location;
• a clearly described issue;
• a decision or an open question;
• the person authorized to resolve it;
• an action owner;
• a due date and need-by date;
• the work that remains held;
• and the document that releases the work.

MEP is shorthand for mechanical, electrical, and plumbing. On a real small job, the same meeting may also need fire protection, controls, low-voltage, structural, architectural, ceiling, millwork, equipment-vendor, or facilities input. Invite the disciplines affected by the work, not everyone in the contact list.

If the project is still being priced, first level the trade interfaces in the multi-trade quote workflow and carry the agreed responsibilities into a statement of work. Coordination notes should resolve how the approved work will fit, sequence, and hand off in the field. They should not hide scope gaps that belonged in the estimate.

A coordination note is not a transcript

Meeting notes should not read like this:

Mike said the duct might work. Elena did not like it. Sam will check. Everyone discussed the ceiling. Meeting ended at 9:42.

That paragraph proves people talked. It does not let a foreman act.

A useful record says:

MEP-014 — Back restroom, above ceiling grid B-3, sheet M2.1 Rev. 4 and site photo P-27. Existing beam blocks the shown exhaust-duct route. Mechanical proposed route M-2 around the east end of the beam. Open: the appropriate design professionals must confirm the route, fire/smoke implications, and required detail through RFI-007 by August 3. Mechanical fabrication and ceiling close-in at grid B-3 remain on hold. Other restroom rough-in may continue. Action owner: Rivera Mechanical, Jordan Lee. Decision authority: project design team through the designated RFI process. Cost/schedule review required after response.

That entry can be checked, assigned, forwarded, corrected, and closed.

Write the notes around issues, decisions, constraints, and commitments. Leave out conversational filler, blame, jokes, bargaining positions, and guesses about why someone made a mistake.

Know which meeting you are holding

Small projects often mix five different conversations and call all of them "coordination."

One short meeting may touch all five. The notes must keep the outputs separate.

Do not let "coordinated" mean:

• the customer accepted added cost;
• the designer approved a design change;
• the authority having jurisdiction approved code compliance;
• a substitution was accepted;
• one contractor assumed another employer's safety duties;
• an unresolved issue was released for fabrication;
• or everyone silently accepted the minutes as a contract change.

The governing contract, agreed communication procedures, and applicable law determine who can approve what. The meeting record should identify that authority instead of manufacturing it.

The AIA–AGC joint framework, released May 27, 2026, recommends addressing scope gaps early, naming authorized liaisons, tracking changes in a centralized log, and documenting change procedures. Use that discipline, but let the governing contract define each person's authority.

Hold the meeting when the next handoff is at risk

Do not schedule a standing meeting merely because large jobs have one. Hold a coordination meeting when a shared condition needs a shared answer.

Useful triggers include:

• two or more trades need the same ceiling, wall, shaft, trench, equipment pad, riser, shutdown, lift, or access route;
• fabrication or material release depends on an unresolved dimension;
• a penetration, sleeve, hanger, curb, housekeeping pad, or access panel must be located before another trade closes the work;
• a current drawing, submittal, equipment selection, or field condition conflicts with another;
• a shutdown, inspection, startup, test, or owner-access window requires several participants;
• one crew's sequence creates a hazard or blocks another crew;
• an answer is needed before concrete, drywall, ceilings, roofing, insulation, millwork, or finishes conceal the area;
• or a prior coordination decision changed and downstream parties need a controlled update.

The meeting may be ten minutes in the room itself. The important part is that the issue is visible before the irreversible handoff.

Use a site assessment checklist before the meeting when dimensions, existing equipment, access, shutoffs, occupancy, or finish conditions are still unknown. A coordination meeting cannot resolve facts that nobody has measured.

Invite the people who can describe, decide, and commit

The Lean Construction Institute describes the "last planner" as the person closest to the work who has authority to make schedule decisions and reliable commitments. That is a useful test for a small coordination meeting.

For each issue, include:

1. Someone who understands the field condition.
2. Someone who understands each affected trade.
3. Someone authorized to make the decision, or a named route to that person.
4. Someone who can commit the labor, material, information, or access needed for the next step.

Depending on the issue, that may mean:

• project manager or general contractor;
• superintendent or working foreman;
• mechanical, electrical, plumbing, or fire-protection lead;
• controls or low-voltage representative;
• architect or responsible design professional;
• equipment supplier or manufacturer's technical representative;
• owner, tenant, facilities manager, or shutdown coordinator;
• ceiling, framing, structural, roofing, or finish-trade lead;
• inspector or authority representative when the jurisdiction offers or requires that coordination;
• safety representative for overlapping hazards or unusual work.

Do not invite a salesperson in place of the person who knows the route, clearance, control sequence, or installation constraint. Do not accept a promise from someone who cannot assign the work. If the decision maker cannot attend, the issue should leave the meeting with an assigned RFI, submittal, owner decision, or other written request—not a guess.

Record who attended, who was invited but absent when their input matters, and who is receiving the minutes for action or information. Attendance alone does not equal approval.

Set the controlling reference set before the meeting

The phrase "the latest plans" is not a usable reference.

Put the current reference set at the top of the agenda:

• project and meeting number;
• meeting date, time, place, and coordinator;
• drawing or sketch number, title, revision, and date;
• specification section or scope-attachment revision;
• approved submittal, equipment schedule, or shop-drawing number;
• current RFI, architect's supplemental instruction, bulletin, or change document;
• current model or coordination-file version, if one exists;
• current look-ahead or milestone date;
• site photo, scan, or field-measurement set;
• prior minutes revision and open-item log.

If participants are looking at different revisions, stop and reconcile the reference set before deciding a route.

For projects that use BIM, the National Institute of Building Sciences' NBIMS-US Version 4 planning guidance makes project reference information, roles, milestones, collaboration procedures, information exchanges, and model-federation standards explicit parts of the execution plan. A five-trade renovation does not need a full BIM execution plan, but it needs the same minimum discipline: identify which information is current, who authors it, who receives it, and when it is exchanged.

For selected equipment, connect the coordination reference to the approved submittal form and submittal register. A screenshot cropped from an old product sheet should not control a curb opening, service clearance, power requirement, drain location, or access panel.

Use one issue ID from discovery through closure

Give each coordination issue a stable ID such as MEP-001, MEP-002, and MEP-003.

Keep that ID when the issue becomes:

• a marked drawing;
• a model viewpoint;
• an RFI;
• a submittal clarification;
• a pricing request;
• a change order;
• a work-order instruction;
• a daily-report entry;
• an inspection item;
• an as-built note;
• or a closeout exception.

Do not create a new disconnected label at every handoff. The stable ID lets the office answer:

Which field issue caused RFI-007, change order CO-004, the one-day ceiling hold, and the revised as-built route?

If the project uses model-based coordination, buildingSMART's BIM Collaboration Format shows how an issue can travel between software tools with a captured model view and references to the affected model elements. If the project does not use BIM, reproduce the same clarity with a sheet/detail reference, room, grid, elevation, annotated photo, and dimension.

The software is optional. The stable location and ownership are not.

Give every issue a location that another person can find

"Duct conflict above ceiling" is not a location.

Use the smallest combination that makes the condition findable:

• building, floor, tenant, room, or unit;
• grid or column line;
• wall, ceiling, shaft, roof zone, or equipment area;
• sheet, detail, schedule, and revision;
• elevation or height reference;
• equipment, panel, valve, fixture, or asset ID;
• model viewpoint or clash ID;
• photo number with a wide view and close view;
• field dimensions and the points from which they were measured.

Example:

Suite 204, corridor outside electrical room, grid C/5, above ceiling, E3.2 Rev. 2 feeder route and M4.1 Rev. 3 supply-duct route, photos P-41 through P-43, measured 10 feet 2 inches above finished floor to underside of beam.

Do not treat a field measurement as a redesign. Record who measured, when, with what reference points, and whether the dimension still requires verification by a responsible trade or designer.

Record the conflict before the proposed fix

Write what exists and what conflicts before writing the preferred solution.

Weak:

Move pipe around duct.

Stronger:

The installed 4-inch sanitary branch at grid D/7 occupies the same route shown for the supply duct on M3.1 Rev. 5. The pipe elevation, required slope, beam depth, ceiling elevation, and duct dimensions have not yet been reconciled. Plumbing proposes route P-2 east of the beam; mechanical has not confirmed duct clearance; designer response required before either trade extends through this bay.

Separate:

1. Observed fact — what the drawing, model, measurement, product data, or field condition shows.
2. Conflict — which two requirements or planned activities cannot both occur as currently shown.
3. Options — bounded alternatives proposed by qualified participants.
4. Decision needed — the exact question and authorized responder.
5. Release condition — the document or verified fact required before work continues.

This structure keeps the minutes useful when the first proposed fix is rejected.

When the documents do not match the field, use the stop-and-document path in When the Plans Don't Match the Field. The coordination log gathers the multi-trade consequences; it does not replace the formal clarification or change route.

Use a controlled status vocabulary

"Open," "closed," and "discussed" are too coarse for coordination work.

Use statuses that tell the next person what may happen:

Never use "approved" alone. Write:

Approved by whom, acting in what role, on which document, for which issue, on what date, and with what price, schedule, testing, or inspection conditions?

Separate a coordination decision from an RFI, submittal, and change

The meeting should classify the outcome before anyone leaves.

Coordination within the approved documents

The trades may be able to select an installation sequence or route that stays within the approved design, each trade's contractual responsibility, applicable clearances, and the authority of the people present.

Record:

• the chosen option;
• the exact approved reference;
• the affected trades;
• who confirmed it was within their authority;
• the field release and verification step;
• whether shop drawings, layout, or as-built records need updating.

Do not label a route "within scope" merely because nobody has priced it yet.

Design or document clarification

When the plans, specifications, schedules, approved submittals, or field conditions create a question for the designer or other contract authority, open an RFI.

The meeting note should state the question, not only "RFI required." Include:

• exact references;
• observed condition;
• affected systems;
• proposed options, if appropriate;
• required-by date;
• affected fabrication or activity;
• known cost or schedule exposure;
• work that may continue;
• work that remains held.

For federal work that includes it, FAR 52.236-21 gives a clear example of the boundary: discrepancies are submitted for a written determination, contractor shop drawings are coordinated and reviewed, and material variations may require a contract modification. It is not a universal rule for private, state, or local work, so check the actual contract instead of importing the clause into a job where it does not apply.

Product or fabrication information

When the issue depends on selected equipment, dimensions, electrical data, controls, drain connections, curb, weight, access, or a proposed substitution, use a submittal.

Send the complete package with a transmittal that identifies the project, issue ID, submittal number, revision, purpose, attachments, and required response. A meeting photo of a catalog page is not a controlled equipment selection.

Price, scope, or time change

When the proposed resolution adds, deletes, or changes contracted work, price, schedule, warranty, or a customer selection, route it through the agreed change process.

Use a signed change order when the parties are agreeing to the changed scope and impact. A construction change directive may fit a contract that authorizes directed work before full agreement, but it is not a generic substitute for customer approval. The contract determines whether that mechanism exists and who may issue it.

If the decision changes a milestone or access window, use a schedule change notice as required. Do not bury a schedule impact inside meeting minutes and assume the notice requirement disappeared.

Safety action

If the conflict exposes workers to energized equipment, pressure, hazardous substances, falls, lifting paths, confined spaces, impaired fire protection, unstable materials, live utilities, or another hazard, make the condition safe and use the project's safety process.

The meeting log should identify:

• the condition and location;
• people or trades potentially exposed;
• immediate protection or stop;
• responsible employer contacts;
• required hazard assessment, permit, plan, or qualified-person review;
• communication to affected workers;
• release authority and verification.

It should not prescribe technical controls beyond the competence and authority of the participants.

OSHA's recommended practices for host employers and contractors advise exchanging hazard and control information before work starts and when conditions change, coordinating work planning and scheduling, resolving program differences, and keeping managers with decision-making authority available. A meeting note can document the communication path. It cannot transfer away duties that the law assigns based on each employer's role and actual control.

Build the agenda around the next two weeks, not the whole project

Small coordination meetings fail when they become tours through every open project question.

Use a focused agenda:

1. Confirm current documents and prior-minute revision.
2. Confirm the next milestone and near-term work areas.
3. Review overdue actions and holds.
4. Review new issues by location, in installation sequence.
5. Decide what can be resolved within present authority.
6. Route design, submittal, cost, time, owner, inspection, and safety questions.
7. Confirm deliveries, shutdowns, access, testing, and inspections.
8. Read back every owner, due date, need-by date, and field hold.
9. State when notes will be distributed and how corrections must be submitted.

The Lean Construction Institute's Last Planner System separates what should happen, what can happen after constraints are removed, what people will commit to, what did happen, and what the team learned. A small contractor does not need to implement the full system to use that discipline.

For each near-term activity, ask:

• Should: What does the approved project sequence require?
• Can: Are design information, access, labor, material, equipment, predecessor work, safety controls, and inspections ready?
• Will: Which person commits to what specific result and date?
• Did: Was the handoff completed and verified?
• Learn: If not, what constraint or planning failure should change the next plan?

"Plumber to coordinate" is not a commitment.

"Avery Plumbing to field-verify invert elevations at points P1 and P2, upload two labeled photos and a dimensioned sketch, and notify the coordinator by 2:00 p.m. August 1 so RFI-009 can be issued before the August 4 underground inspection" is.

Track due date and need-by date separately

An action can be completed on its promised date and still arrive too late for the project.

Record:

• Action due: when the owner will provide the measurement, sketch, price, response, or approval.
• Need-by: the last useful date before fabrication, delivery, inspection, shutdown, concealment, or crew commitment is affected.
• Affected activity: the exact task, location, and responsible crew.
• Float or consequence: what happens if the need-by date is missed.

Example:

If the miss changes the agreed completion date, notice path, or cost, record that separately. Do not turn the issue log into an unsupported extension-of-time approval.

Use a constraint log, not a vague action list

An action list says what someone will do. A constraint log says what prevents the next reliable commitment.

Common MEP constraints include:

• current design response;
• field dimension;
• owner equipment or finish selection;
• approved submittal;
• manufacturer data;
• structural review;
• permit or inspection;
• utility coordination;
• shutdown authorization;
• occupied-area access;
• material delivery;
• predecessor framing, pad, sleeve, curb, or penetration;
• required temporary protection;
• safe work plan or qualified-person review;
• test equipment or balancing/commissioning support.

For each constraint, record the remover, due date, evidence, and affected work.

Do not assign "GC" or "team." Assign a named organization and person. If one organization owns the action and another owns the answer, show both:

Rivera Mechanical drafts route M-2 and supporting dimensions. North Design is the authorized responder to RFI-007. Harbor Build submits the RFI and updates the field release after the written response.

Keep one issue log beside the minutes

The minutes record what happened in a meeting. The issue log carries open items across meetings.

Recommended issue-log fields:

The minutes can then say:

MEP-012 updated from "awaiting submittal" to "released for defined work" based on approved submittal 23-014 Rev. 2 dated July 30. Electrical and controls may rough in the listed points. Final control sequence remains subject to functional testing. Work orders WO-E-118 and WO-C-044 updated. Verification owner: Morgan Chen at startup.

That is more useful than copying the entire history into every meeting.

A worked small-job coordination record

Consider a 2,400-square-foot café renovation with a low ceiling, a new exhaust fan, a relocated panel, new restroom plumbing, modified sprinklers, and work around an operating neighboring tenant.

The next irreversible handoffs are:

• wall close on August 5;
• ceiling grid on August 6;
• rooftop opening on August 7;
• electrical shutdown on August 8.

The meeting uses architectural sheet A2.3 Rev. 6, mechanical M2.1 Rev. 4, plumbing P2.1 Rev. 3, electrical E3.2 Rev. 2, fire-protection shop drawing FP-07 Rev. 1, equipment submittal 23-014 Rev. 1, and site photos P-21 through P-48.

Notice what the record does not say:

• It does not say the meeting approved an engineering change.
• It does not promise that every proposed route complies with every adopted code.
• It does not direct an unsafe shutdown.
• It does not authorize added cost.
• It does not release work from a superseded equipment sheet.
• It does not stop the entire project when only one bay is affected.

It tells each person what is known, what is not known, who must act, and exactly what remains held.

Read back the action log before people leave

The meeting coordinator should end by reading each open item aloud:

MEP-014: Rivera Mechanical owns the sketch by August 1. Harbor Build submits RFI-007 the same day. North Design is the requested responder by August 3. Exhaust fabrication and ceiling close-in at grid B-3 remain held. Adjacent rough-in continues.

Ask:

• Is the owner the person who accepted the commitment?
• Can that person actually deliver it?
• Is the due date specific?
• Is the need-by date earlier than the affected handoff?
• Is the decision authority named?
• Is the field hold narrow and clear?
• Does anyone present understand the decision differently?

Correct the entry while the people and drawings are still together.

Distribute notes as a controlled record

Send the minutes while the decisions are still useful. Follow any contract deadline; otherwise, establish a practical project rule such as same-day distribution for short field meetings.

Use a file identity like:

Harbor Café — MEP Coordination Meeting 04 — 2026-07-31 — Rev. 0

The distribution should identify:

• project and meeting number;
• date/time and location;
• prepared by;
• current revision;
• attendees and recipients;
• reference documents;
• new decisions and actions;
• open issue log;
• attachments;
• correction method and deadline;
• next meeting or check-in, if needed.

Send it through the agreed channel. A construction transmittal is useful when the contract or project needs a formal delivery record.

Do not state, "Silence means acceptance," unless a valid contract procedure expressly says that and the project team has reviewed how it works. Instead say:

Submit factual corrections or differences in understanding in writing to the coordinator by 3:00 p.m. August 1. The coordinator will issue a revised record or log the disputed item. Contract changes, design approvals, submittal approvals, and safety releases require their separate authorized documents.

If someone disputes the notes, preserve Rev. 0. Issue Rev. 1 with the corrected wording, date, author, and change note. Do not silently overwrite history.

Push released decisions into field documents

The meeting record is not the last stop.

Once an issue is properly released:

1. Update the affected drawing, marked plan, model issue, or sketch reference.
2. Update the crew's construction work order with the exact released scope and revision.
3. Update procurement, fabrication, or submittal records.
4. Update the short-term schedule and access/shutdown plan.
5. Update the JHA or safety briefing when the work method or hazards changed.
6. Record what actually happened in the construction daily report.
7. Verify inspections, tests, startup, and remaining exceptions.
8. Carry the installed condition into redlines, as-builts, manuals, labels, and closeout.

The daily field handoff workflow keeps the next crew from working from yesterday's memory. The as-built and redline closeout workflow preserves the installed route after the ceiling hides it.

If a field decision creates an unresolved deficiency rather than an accepted final condition, open a punch list item. Do not close the coordination issue merely because the conflicting materials now fit.

Verify closure in the field

An email answer closes a question. It does not prove the work matches the answer.

Before marking the issue verified closed, capture:

• final installed location;
• governing response, submittal, change, or release document;
• photo or model update;
• field dimension when relevant;
• inspection or test result;
• access and service clearance review by the responsible party;
• labels, controls, startup, balancing, or commissioning status when applicable;
• updated redline or as-built reference;
• remaining exception, if any;
• verifier and date.

The current NIBS guidance for coordinating design and construction identifies coordinated models, coordinated shop drawings, updated design information, and a list of coordination concerns—including RFIs—as distinct outputs. That distinction matters even without BIM: resolving the conversation, updating the document, and verifying the field condition are three different completion steps.

Keep safety communication in its own lane

An MEP meeting often reveals safety issues because several employers share the same work area.

Examples:

• electrical work overlaps plumbing demolition;
• one trade removes a guard, cover, or ceiling tile another crew expects;
• hot work occurs near combustible materials or occupied operations;
• a lift, hoist, or delivery blocks an egress or work path;
• fire protection or alarm service will be impaired;
• a shutdown changes lighting, ventilation, refrigeration, or life-safety conditions;
• a roof opening, floor penetration, trench, or shaft will be left exposed;
• testing introduces pressure, motion, heat, chemicals, or energized equipment.

Record the coordination facts, then use the safety records and qualified people required for the actual work.

Do not write:

GC responsible for all safety.

Do write:

Electrical contractor reports energized-panel exposure in the planned plumbing access route. Plumbing work in the marked zone is held. Electrical and plumbing employers will exchange hazard/control information before work resumes. Harbor Build coordinates the shared-area schedule. Each employer remains responsible for its employees and applicable duties. Required JHA/permit/qualified-person release references to be added before field release.

OSHA's multi-employer citation policy evaluates creating, exposing, correcting, and controlling employer roles from the facts. A sentence in meeting minutes does not erase duties arising from an employer's role or actual control.

Rewrite these twelve dispute-prone notes

Remove or rewrite these:

1. "All trades coordinated." Which systems, areas, references, and unresolved exceptions?
2. "Move as needed." Who may choose the route, within what limits, and who verifies it?
3. "Approved in meeting." By which authorized person and source document?
4. "No cost impact." Who evaluated labor, material, equipment, remobilization, testing, and schedule?
5. "No schedule impact." Which activity, milestone, need-by date, and downstream handoff were checked?
6. "Per code." Which adopted rule, design professional, qualified trade, manufacturer instruction, inspector, or authority supports that statement?
7. "By others." Name the responsible organization or keep it as an unresolved scope gap.
8. "ASAP." Use an action due date and need-by date.
9. "Discussed." Record decision, question, owner, and next document.
10. "Closed." Identify release source, field verification, and close date.
11. "Everyone agrees." List the decision participants and distinguish attendance from authority.
12. "Minutes supersede plans." Follow the actual document hierarchy and change procedure.

Neutral factual wording is stronger than blame.

Instead of:

Electrician failed to leave room for duct.

Write:

Installed electrical conduit in corridor grid C/5 occupies the route shown for supply duct on M4.1 Rev. 3. Electrical installation reference and sequence are under review. Mechanical and electrical leads will provide marked options; coordinator will determine the required RFI/change route.

A one-page small-job meeting-note format

Use this order.

Header

• Project, address, customer/owner, and contract or work-order number.
• Meeting number, date, time, location, and coordinator.
• Purpose and near-term milestone.
• Attendees, organizations, roles, and absent required participants.
• Distribution list.

Current reference set

• Drawing, detail, specification, scope, submittal, RFI, change, and schedule revisions.
• Model or coordination-file version, if used.
• Site-photo and field-measurement references.
• Prior minutes and issue-log revision.

Prior actions

New and open issues

Near-term handoffs

Safety and operational coordination

• Shared hazards and affected employers.
• Shutdowns, impairments, occupied-area controls, access, and emergency contacts.
• Separate JHA, permit, plan, or release references.

Close

• Actions read back and confirmed by named owners.
• Factual-correction method and deadline.
• Next check-in.
• Prepared by, issued date/time, and revision.

That is enough for many small jobs. Add complexity only when the contract, system, risk, or number of issues requires it.

Sources

Sources checked July 30, 2026.

• American Institute of Architects and Associated General Contractors of America, Toward Collaboration's Future: Strengthening the Architect-Contractor Relationship, with the AIA release announcement dated May 27, 2026, for current industry guidance on early collaborative meetings, clear roles and gaps, designated liaisons, regular checkpoints, centralized change tracking, proactive constraint communication, documented change procedures, and consistent meeting cadence, accessed July 30, 2026.
• National Institute of Building Sciences, NBIMS-US Version 4 — BIM Execution Planning Standard, current online Version 4 module, for project references, roles, milestones, collaboration activities, information exchanges, responsible parties, meeting structure, and controlled plan updates, accessed July 30, 2026.
• National Institute of Building Sciences, NBIMS-US Version 4 BIM Use 09 — Coordinate Design and Construction, current definition and attributes for design/construction coordination, including constructability and access review, coordinated models/shop drawings, updated design information, and coordination-concern/RFI outputs, accessed July 30, 2026.
• Lean Construction Institute, Last Planner System, current official overview of pull planning, make-ready planning, handoffs, weekly commitments, constraint management, daily huddles, completion review, and learning from variance, accessed July 30, 2026.
• Occupational Safety and Health Administration, Communication and Coordination for Host Employers, Contractors, and Staffing Agencies, current recommended practices for exchanging hazard information, coordinating work planning and scheduling, resolving program differences, communicating changing conditions, and making decision-capable managers available, accessed July 30, 2026.
• Occupational Safety and Health Administration, Multi-Employer Citation Policy, CPL 02-00-124, current directive for fact-specific creating, exposing, correcting, and controlling employer analysis, accessed July 30, 2026.
• Acquisition.gov, FAR 52.236-21 — Specifications and Drawings for Construction, FAC 2026-01 effective March 13, 2026, used only as bounded federal-contract context for written discrepancy determinations, coordinated shop drawings, written variations, and appropriate contract modifications, accessed July 30, 2026.
• buildingSMART International, BIM Collaboration Format, current official openBIM overview of exchanging coordination issues between software tools with captured model views and references to affected model elements, accessed July 30, 2026.

This article is for general information and is not legal, engineering, architectural, code, safety, scheduling, or contract-administration advice. Project authority, document hierarchy, design responsibility, change requirements, notice rules, safety duties, licensing, adopted codes, inspections, and approval procedures vary by contract and jurisdiction. Verify the current requirements with the customer or owner, responsible design professionals, licensed trades, safety professionals, insurer, attorney, manufacturer, building department, utility, and authority having jurisdiction before releasing affected work.