SynC · SynC Standards
Project Management and Coordination
Contents
- 1Scope
- 2Project Management Terms
- 3Referenced Standards
- 4Submittals
- 4.1Project Management Submittals
- 5Project Representatives and Key Personnel
- 5.1Owner's and Engineer's Representatives
- 5.2Contractor's Project Manager and Superintendent
- 5.3Replacement of Key Personnel
- 6Project Meetings
- 6.1Preconstruction Conference
- 6.2Progress Meetings
- 6.3Meeting Minutes
- 7Requests for Information
- 7.1What a Request for Information Is
- 7.2Content and Submission of a Request
- 7.3Engineer's Response
- 7.4Request for Information Log
- 8Coordination Drawings
- 8.1Where Coordination Drawings Are Required
- 8.2Lead Trade and Sequence of Overlays
- 8.3Coordination Method
- 8.4Clash Resolution
- 8.5Engineer's Review of Coordination Drawings
- 9Project Communication and Records
- 9.1Project Platform
- 9.2Electronic File Formats
- 9.3Transmittals and Written Communication
- 10Coordination with Other Standards
Download
Build a datasheet from this standard
Start a project with this standard already attached — one click, no setup.
Use in a project
1 Scope
NOTE The authority of the Owner's and the Engineer's representatives, and the obligation to keep a competent superintendent on the site, originate in the Agreement and the General Conditions, which are contract instruments, not specifications. This standard carries those obligations into the project manual, where the subcontractor who reads only the technical section for its trade finds them, and it states the administrative detail those instruments leave open: how often the parties meet, who records what was decided, how a question about the documents is asked and answered, and how a conflict between two trades is settled before it is built. (1.2)
NOTE A project on which these procedures are not written down runs on them anyway, by habit and by whoever speaks loudest at the first meeting. Writing them once, here, means that the response time on a request for information, the party who records the minutes, and the trade that leads the coordination drawings are decided by the Owner and the Engineer before bid, priced by every bidder on the same basis, and not renegotiated in the field. (1.3)
1.4 The Contractor shall comply with this standard in addition to any coordination, meeting, or communication requirement stated in a technical standard.
1.5 Where a requirement of this standard conflicts with the Agreement, the General Conditions, or the Supplementary Conditions, those documents shall govern.
NOTE The following are outside the scope of this standard: (1.6)
- The construction schedule, its updates and recovery schedules, the look-ahead schedule, the daily construction reports, and the progress photographs, which Construction Progress DocumentationConstruction Progress DocumentationResolves to the current adopted revision.sync/construction-progress-documentation governs
- The submittal register, the transmittal and review workflow, and the action and informational classification of submittals, which Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures governs
- The pre-installation meetings held before a particular feature of work begins, which Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures and Quality RequirementsQuality RequirementsResolves to the current adopted revision.sync/quality-requirements govern
- The content, the drawing scale, and the space priority rule of the coordination drawings for the mechanical and electrical work, which Common Work Results MechanicalCommon Work Results for MechanicalResolves to the current adopted revision.sync/common-work-results-mechanical and Common Work Results ElectricalCommon Work Results for ElectricalResolves to the current adopted revision.sync/common-work-results-electrical state for their disciplines
- Requests to substitute a product, which Product RequirementsProduct RequirementsResolves to the current adopted revision.sync/product-requirements governs
- Change proposals, field orders, construction change directives, change orders, time extension requests, the notice of a differing site condition, and the notice of a claim, which Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures governs
- The contracting arrangement, the Owner's separate contractors, work by the Owner, the Contractor's use of the premises, and the working hours, which Summary Of Work And Work RestrictionsSummary of Work and Work RestrictionsResolves to the current adopted revision.sync/summary-of-work-and-work-restrictions governs
- The Owner's operating constraints, the shutdown and outage requests, the tie-in meetings, and the role of the Owner's operators on a facility that stays in service while it is built on, which Maintenance Of Plant OperationsMaintenance of Plant OperationsResolves to the current adopted revision.sync/maintenance-of-plant-operations governs
- The confidentiality classes of project information and the terms a hosted service meets before project documents are processed on it, which Document Confidentiality And Ai UseDocument Confidentiality and AI UseResolves to the current adopted revision.sync/document-confidentiality-and-ai-use governs
- The commissioning kickoff and commissioning meetings and the commissioning issues log, which CommissioningTotal Building CommissioningResolves to the current adopted revision.sync/commissioning governs
- The Contractor's safety program, which is the Contractor's means and methods and is not specified
2 Project Management Terms
NOTE The following terms are used in this standard with the meanings given here: (2.1)
- The Owner's representative is the individual the Owner designates in writing to act for the Owner on the project, with the authority the Owner's designation and the Agreement give that individual
- The Engineer is the design professional named in the Agreement as the Owner's representative during construction, and the Engineer's authority is the authority the Agreement and the General Conditions give it, no more and no less
- A resident project representative is the Engineer's representative stationed at the site, whose authority is limited to observing and reporting the Work and to the further duties the Agreement assigns
- The Contractor's project manager is the individual responsible for the administration of the Contract on the Contractor's behalf, including the schedule, the submittals, the payment applications, and the changes
- The superintendent is the Contractor's individual in charge of the Work at the site, with authority to direct the Work and to receive instructions on the Contractor's behalf
- Key personnel are the Contractor's project manager, the superintendent, and any other individual the Contract Documents or the Contractor's accepted staffing list names as key
- A request for information is a written question from the Contractor to the Engineer about the meaning, the intent, or an apparent conflict or omission in the Contract Documents, or about a field condition that affects how the Work shown is to be built
- A coordination drawing is a drawing or a model the Contractor prepares to lay out the work of two or more trades in a shared space before that work is fabricated or installed, as distinct from a shop drawing, which shows one trade's work for review
- A clash is a conflict found on a coordination drawing or in a coordination model in which two elements occupy the same space, or one element occupies the clearance another requires
- Model-based coordination is a coordination method in which each trade contributes a three-dimensional model of its work to a federated coordination model on which clashes are detected
- The project platform is the single hosted system on which the project's submittals, requests for information, transmittals, meeting minutes, logs, and issued documents are exchanged and recorded
- A transmittal is the record that a document was sent, by whom, to whom, on what date, and for what action
- A working day is a day other than a Saturday, a Sunday, or a holiday the Agreement recognizes
3 Referenced Standards
3.1 The project procedures, the meetings, and the records shall comply with the latest adopted edition of each of the following unless a specific edition is cited or the Contract Documents direct otherwise.
3.2 Where referenced documents conflict, the more stringent requirement shall govern unless the Engineer of Record directs otherwise in writing.
| Standard | Title |
|---|---|
| AIA A201 | General Conditions of the Contract for Construction |
| AIA E203 | Building Information Modeling and Digital Data Exhibit |
| AIA G202 | Project Building Information Modeling Protocol Form |
| EJCDC C-700 | Standard General Conditions of the Construction Contract |
| ConsensusDocs 200 | Standard Agreement and General Conditions Between Owner and Constructor |
| ConsensusDocs 301 | Building Information Modeling Addendum |
| NBIMS-US | National BIM Standard-United States |
| ISO 19005 | Document Management, Electronic Document File Format for Long-Term Preservation (PDF/A) |
NOTE The general conditions in common use each provide for a superintendent, for the Engineer's or the Architect's authority during construction, for written communication between the parties, and for the Contractor's review of the documents before building from them, and they differ in what they call the question the Contractor asks and in how much of the procedure they state. The model protocols for building information modeling are exhibits a project attaches to the Agreement when the model is a contract deliverable; where the model is only a coordination tool, this standard states what the project needs from it. (3.3)
4 Submittals
4.1 Project Management Submittals
4.1.1 The Contractor shall submit the following, each at the time this standard states for it:
- The key personnel list, naming the project manager, the superintendent, and each other individual proposed as key personnel, with the qualifications of each, before the preconstruction conference
- The project directory, listing the Contractor's and each subcontractor's project contacts with telephone numbers and electronic addresses and the contact reachable at any hour for an emergency at the site, before the preconstruction conference and within five working days after any change
- The coordination drawings for each area where this standard requires them, before any work in that area is fabricated or installed
- The request for information log, current at each progress meeting and closed at closeout
- The record of transmittals, exported from the project platform at closeout
Project Management Submittals Requiredcheckbox
☑ Key personnel list with qualifications
☑ Project directory with emergency contact
☑ Coordination drawings for each required area
☑ Request for information log
☑ Record of transmittals
4.1.2 Project management submittals shall be transmitted and tracked through the submittal procedure of Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures.
4.1.3 The closed request for information log and the record of transmittals shall be delivered with the record documents under Closeout ProceduresCloseout ProceduresResolves to the current adopted revision.sync/closeout-procedures.
NOTE The key personnel list and the directory are asked for before the preconstruction conference because the conference is where the Owner meets the people it will be dealing with for the life of the project, and a name that is unacceptable is easier to replace before that person has started than after. (4.1.4)
5 Project Representatives and Key Personnel
5.1 Owner's and Engineer's Representatives
5.1.1 The Owner shall designate its representative in writing before the preconstruction conference and shall notify the Contractor in writing of any change.
5.1.2 The Engineer's authority to act for the Owner during construction shall be the authority the Agreement and the General Conditions give it, and nothing in this standard enlarges or reduces that authority.
5.1.3 The Engineer's representation at the site shall be as indicated in the datasheet.
Engineer's Representation at the Siteradio
○ A resident project representative at the site whenever Work is in progress
○ A resident project representative at the site during the phases the Contract Documents designate
○ Periodic site visits by the Engineer, with no resident project representative
NOTE A resident project representative whenever Work is in progress gives the Owner a continuous record of what was built and when, an observer present for every test and every cover-up, and a person on the site who can answer a question the same day, and it is the arrangement a treatment plant, a pump station, or any project with buried or concealed work usually carries, at a cost to the Owner of a full-time salary for the duration. Residency during designated phases, such as the yard piping and the structural concrete, puts the observer where the concealed work is and withdraws it for the finishes, at the cost of a gap in the record for the phases it does not cover. Periodic visits leave the record to the Contractor's daily reports and the Engineer's visit reports, and they suit a small project or one whose work is visible at completion, at the cost of tests and cover-ups that happen between visits. (5.1.4)
5.1.5 A resident project representative shall not have authority to approve a change in the Work, a substitution, a deviation from the Contract Documents, or an adjustment of the Contract Sum or the Contract Times, and shall not direct the Contractor's means, methods, or safety.
5.1.6 The Contractor's communications to the Owner on matters within the Engineer's authority shall be routed as indicated in the datasheet.
Routing of Contractor Communications to the Ownerradio
● Through the Engineer
○ Directly to the Owner's representative, with a copy to the Engineer at the same time
NOTE Routing every communication through the Engineer is what the general conditions in common use provide, and it keeps one party in possession of the whole record and keeps the Owner from giving an instruction the Engineer learns of after the fact. Direct communication with a copy to the Engineer is used by an Owner with its own construction management staff who wants to hear from the Contractor first, at the cost of two parties who have to agree on what was said before either answers. (5.1.7)
5.1.8 An instruction given to the Contractor by anyone other than the Owner's representative or the Engineer, including an operator, an inspector, or a representative of a utility, shall not be acted on as a change until the Contractor has confirmed it through the procedure of Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures.
5.2 Contractor's Project Manager and Superintendent
5.2.1 The Contractor shall designate in writing, before the preconstruction conference, a project manager and a superintendent, and the two roles shall be held by different individuals unless the Owner accepts one individual for both in writing.
5.2.2 The superintendent shall be present at the site as indicated in the datasheet.
Superintendent Presence at the Siteradio
● Full time whenever Work is in progress at the site
○ Full time during the phases the Contract Documents designate, and whenever a subcontractor is working, with part-time presence otherwise
○ Part time, at the frequency the Contractor's accepted staffing list states
NOTE A superintendent present whenever work is in progress is what the general conditions in common use require and what nearly every project carries, because the superintendent is the one person with authority to stop or redirect a crew on the spot. Presence during designated phases and whenever a subcontractor is working is accepted on a project with long periods of single-trade work, such as a pipeline, where a foreman runs the crew and the superintendent covers several sites, at the cost of an instruction given to a foreman who cannot act on it. Part-time presence suits a small project of short duration, such as a single equipment replacement, and it is priced lower, at the cost of days on which no one at the site can speak for the Contractor. (5.2.3)
5.2.4 The superintendent shall have authority to act for the Contractor at the site, and a communication given to the superintendent shall be as binding on the Contractor as a communication given to the Contractor.
5.2.5 The superintendent shall have the experience on work comparable in type and size to the Work indicated in the datasheet.
Superintendent Experience on Comparable Workrange
Not less than
years
351015
NOTE A stated number of years on comparable work is the one qualification an Owner can check from a resume, and it is set against the kind of work rather than the dollar value: five years on treatment plant or pump station work is a common requirement on that kind of project, and it excludes a superintendent whose experience is in buildings, who will meet the hydraulic profile, the tie-ins, and the operating staff for the first time on this job. A higher figure narrows the field to the larger contractors and raises the price; a figure of zero leaves the qualification to the Owner's review of the staffing list alone, which is what a small project of ordinary difficulty usually does. (5.2.6)
5.2.7 The superintendent responsible for the temporary facilities under Temporary Facilities And ControlsTemporary Facilities and ControlsResolves to the current adopted revision.sync/temporary-facilities-and-controls shall be the superintendent designated under this standard unless the Contractor's accepted staffing list names another individual for that duty.
5.3 Replacement of Key Personnel
5.3.1 The Contractor shall not replace a member of the key personnel without the Owner's written consent, except where the individual dies, becomes incapacitated, or leaves the Contractor's employment.
5.3.2 The Contractor shall give the Owner written notice of a proposed replacement, with the qualifications of the proposed individual, not less than the number of days indicated in the datasheet before the replacement takes effect, and within two working days after a replacement the Contractor could not foresee.
Notice Before Replacing Key Personnelrange
Not less than
days
7142130
NOTE Fourteen days is what most projects allow, because it is enough time for the Owner to read the qualifications and object and short enough that the Contractor is not left without a superintendent while it waits. A longer notice suits an Owner whose review goes through a board or a committee that meets monthly, at the cost of a Contractor who has to carry the outgoing individual for that long. (5.3.3)
5.3.4 A replacement shall have qualifications not less than those of the individual replaced and not less than this standard requires.
5.3.5 The Owner may require the Contractor to remove from the Work an individual who, in the Owner's reasonable judgment, is incompetent, careless, or uncooperative, or who disregards the Owner's operating rules at the facility, and the Contractor shall furnish a replacement within the notice period indicated in the datasheet.
5.3.6 Where the Owner and the Contractor disagree whether the ground for a removal is reasonable, the Engineer shall make the initial determination, subject to the dispute resolution provisions of the Contract Documents.
5.3.7 The Contractor shall not be entitled to an adjustment of the Contract Sum or the Contract Times on account of the replacement of key personnel under this article.
NOTE The superintendent is the person the Owner is actually buying when it accepts a bid, and a superintendent swapped out after award for one with half the experience is the oldest substitution there is. The consent requirement, the notice, and the equal-qualification rule are what let the Owner hold the Contractor to the people it proposed, and the Owner's right of removal is the remedy when the person proposed does not work out. (5.3.8)
6 Project Meetings
6.1 Preconstruction Conference
6.1.1 The Engineer shall schedule and chair a preconstruction conference, held at a location the Owner designates, not more than the number of days indicated in the datasheet after the notice to proceed and before any Work begins at the site.
Preconstruction Conference Held After Notice to Proceedrange
Not more than
days
710142130
NOTE The conference is held before the first work at the site because the procedures it settles, the platform, the submittal schedule, the shutdown requests, and the lines of authority, are the ones the first week of work needs. A short interval after the notice to proceed suits a project with a short mobilization, such as one where the Contractor is already on an adjacent site, and a longer interval gives the Contractor time to engage its major subcontractors so that they attend, at the cost of a start at the site that waits for the conference. (6.1.2)
6.1.3 The Owner's representative, the Owner's operating and maintenance staff where the facility is in service, the Engineer and its resident project representative, the Contractor's project manager and superintendent, the subcontractors the Contractor expects to be at the site in the first sixty days, the testing agency engaged under Quality RequirementsQuality RequirementsResolves to the current adopted revision.sync/quality-requirements, and a representative of each utility whose service is affected shall attend the preconstruction conference.
6.1.4 The agenda of the preconstruction conference shall include the following:
- The key personnel of each party, the lines of authority, and the routing of communications under this standard
- The project platform, the file formats, and the procedures for submittals, requests for information, and transmittals under this standard and Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures
- The submittal schedule and the long-lead items under Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures
- The construction schedule, the progress reporting, and the progress photographs under Construction Progress DocumentationConstruction Progress DocumentationResolves to the current adopted revision.sync/construction-progress-documentation
- The schedule of values and the application for payment procedure under Payment ProceduresPayment ProceduresResolves to the current adopted revision.sync/payment-procedures
- The change procedures, the pricing of changes, and the notice requirements under Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures
- The contracting arrangement, the Owner's separate contractors, the use of the premises, the working hours, and the personnel access requirements under Summary Of Work And Work RestrictionsSummary of Work and Work RestrictionsResolves to the current adopted revision.sync/summary-of-work-and-work-restrictions
- The Owner's operating constraints, the shutdown request procedure, and the Contractor's plan for maintaining plant operations under Maintenance Of Plant OperationsMaintenance of Plant OperationsResolves to the current adopted revision.sync/maintenance-of-plant-operations, where the facility is in service
- The temporary facilities, the site utilization, and the construction utilities under Temporary Facilities And ControlsTemporary Facilities and ControlsResolves to the current adopted revision.sync/temporary-facilities-and-controls
- The quality control program, the testing agency, and the pre-installation meetings under Quality RequirementsQuality RequirementsResolves to the current adopted revision.sync/quality-requirements and Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures
- The coordination drawing program, its lead, and its method under this standard
- The confidentiality classes of the project information and the handling of security-sensitive documents under Document Confidentiality And Ai UseDocument Confidentiality and AI UseResolves to the current adopted revision.sync/document-confidentiality-and-ai-use
- The bonds and the insurance certificates in force under Warranties And BondsWarranties and BondsResolves to the current adopted revision.sync/warranties-and-bonds and Insurance RequirementsInsurance RequirementsResolves to the current adopted revision.sync/insurance-requirements
- The permits obtained and the permits outstanding, and the party responsible for each
- The Contractor's safety program, presented by the Contractor as its own responsibility, and the emergency contacts at the site
- The progress meeting schedule and the location of the meetings
6.1.5 The Engineer shall record the preconstruction conference and distribute the minutes under the Meeting Minutes article of this standard.
NOTE The agenda is long because the conference is the one time every party is in the room before the habits of the project form. A topic left off it is settled later, by whoever is on the site that day, and the setting usually does not match what the Contract Documents say. (6.1.6)
6.2 Progress Meetings
6.2.1 Progress meetings shall be held at the site, or at another location the Owner designates, at intervals not longer than the interval indicated in the datasheet while Work is in progress, and at the times fixed at the preconstruction conference.
Progress Meeting Intervalrange
Not more than
weeks
124
NOTE A weekly meeting suits a project with many trades on the site at once, or one in an operating facility where the shutdown requests for the coming week have to be settled, and it costs each party an hour or two of its senior people every week. A meeting every two weeks is the common interval on a project of ordinary pace. A monthly meeting suits a project with a single trade and a long duration, such as a pipeline or a tank, and it is also the interval at which the payment application is reviewed, at the cost of a month between the Owner's opportunities to raise a problem in a room with everyone present. (6.2.2)
6.2.3 The progress meetings shall be chaired and recorded by the party indicated in the datasheet.
Party Chairing and Recording Progress Meetingsradio
○ The Engineer
○ The Contractor
○ The Owner's representative
NOTE The party that records the minutes writes the project's running history, and the choice is between independence and cost. The Engineer chairing and recording gives the Owner a record kept by its own representative, and the Engineer's time to do it is in the Engineer's fee, which the Owner pays. The Contractor chairing and recording puts the meeting in the hands of the party that controls the schedule and the subcontractors, which is where the information is, and it is priced in the bid, at the cost of a record written by the party most of the disputes will be with and a review of every set of minutes by the Engineer to catch what it leaves out. The Owner's representative chairing and recording suits an Owner with its own construction management staff who runs its projects that way, at the cost of the Engineer learning what was decided from the minutes. (6.2.4)
6.2.5 The Contractor's project manager and superintendent, each subcontractor whose work is in progress or begins before the next meeting, the Engineer or its resident project representative, and the Owner's representative shall attend each progress meeting, and the Contractor shall require the attendance of any subcontractor or supplier whose work is on the agenda.
6.2.6 The agenda of each progress meeting shall include the following:
- The minutes of the previous meeting and any objection to them
- The schedule status, the look-ahead schedule, and any recovery schedule under Construction Progress DocumentationConstruction Progress DocumentationResolves to the current adopted revision.sync/construction-progress-documentation
- The submittal register status under Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures and the request for information log under this standard, including the items whose response is overdue
- The pending change proposals, time extension requests, and notices under Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures
- The shutdown and outage requests for the period to the next meeting under Maintenance Of Plant OperationsMaintenance of Plant OperationsResolves to the current adopted revision.sync/maintenance-of-plant-operations, where the facility is in service
- The coordination drawing status and the clashes referred to the Engineer under this standard
- The tests and inspections performed and scheduled, and the open non-conformances, under Quality RequirementsQuality RequirementsResolves to the current adopted revision.sync/quality-requirements
- The permits, the utility work, and the work of the Owner's separate contractors affecting the Work
- The Owner's items, including complaints from the public and from the facility's staff
- The incidents at the site since the last meeting, reported by the Contractor
6.2.7 A statement made at a progress meeting, and its record in the minutes, shall not constitute the written notice the Contract Documents require for a claim, a change, a time extension, or a differing site condition, and the Contractor shall give that notice under Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures.
NOTE The progress meeting is where a delay or a changed condition is usually first mentioned, and a Contractor who mentioned it there and nowhere else will say the Owner had notice. The general conditions in common use require the notice in writing within a stated time, and a line in the minutes recorded by someone else is not that notice. Saying so here keeps the minutes a record of the meeting rather than a reservoir of unnoticed claims. (6.2.8)
NOTE Pre-installation meetings before a particular feature of work are convened and recorded under Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures and Quality RequirementsQuality RequirementsResolves to the current adopted revision.sync/quality-requirements, and the commissioning meetings under CommissioningTotal Building CommissioningResolves to the current adopted revision.sync/commissioning, and they are not progress meetings under this standard. (6.2.9)
6.3 Meeting Minutes
6.3.1 The party recording a meeting shall distribute the minutes, through the project platform, to every attendee and to every party on the project directory whose work the minutes affect, within the number of working days indicated in the datasheet after the meeting.
Minutes Distributed After a Meetingrange
Not more than
working days
235710
6.3.2 A party receiving minutes shall state any objection to them in writing within the number of working days indicated in the datasheet after their distribution, failing which the minutes shall be the record of the meeting.
Objection to Minutes Stated After Distributionrange
Not more than
working days
235710
NOTE The two periods together decide how long a decision made at a meeting stays open. Minutes distributed within two or three working days reach the parties while the meeting is fresh and before the next week's work relies on what was decided, and they cost the recording party a prompt turnaround on every meeting. A longer distribution period is accepted where the recording party has a small staff, at the cost of minutes that arrive after the decisions in them have already been acted on. The objection period is set so that it ends before the next meeting at the interval the project uses, and a period longer than that interval leaves two sets of minutes open at once. (6.3.3)
6.3.4 The minutes shall record the date, the attendees, each item discussed, each decision made and the party who made it, each action item with the party responsible and the date due, and each item carried forward.
6.3.5 The minutes shall not modify the Contract Documents, and a decision recorded in the minutes that changes the Work, the Contract Sum, or the Contract Times shall take effect only through the procedure of Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures.
6.3.6 Where the parties disagree about what was decided at a meeting, the minutes as distributed and not objected to shall be the record, and where an objection was made and not resolved, the Engineer shall make the initial determination, subject to the dispute resolution provisions of the Contract Documents.
7 Requests for Information
7.1 What a Request for Information Is
7.1.1 The Contractor shall submit a request for information to the Engineer where the Contractor finds the Contract Documents unclear, in conflict, or silent on a matter the Work requires, or finds a field condition that differs from the condition the Contract Documents show in a way that affects how the Work is to be built.
7.1.2 A request for information shall not be used to request a substitution, which Product RequirementsProduct RequirementsResolves to the current adopted revision.sync/product-requirements governs, to propose a change or request a time extension, which Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures governs, to transmit a submittal, which Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures governs, or to give a notice the Contract Documents require to be given in another form.
NOTE The request for information is a question, and the three things it is routinely used for instead are each a different procedure with a different review, a different approval, and a different effect on the Contract. A substitution asks the Engineer to accept a product the documents do not name, and the product standards set what that request has to show. A change proposal asks for money or time, and the modification procedure sets the notice and the pricing. A submittal asks for review of the Contractor's own work. A question dressed as any of these, or any of these dressed as a question, is answered under the wrong rules, and the answer is then cited as something it was never meant to be. (7.1.3)
7.1.4 The Contractor shall review the Contract Documents, including the drawings and the specification sections of every trade whose work bears on the question, and the field conditions, before submitting a request for information, and shall state in the request its own interpretation or proposed resolution.
7.1.5 The Engineer may return without a response a request for information whose answer is stated in the Contract Documents, identifying where, and the returned request shall be closed on the log as answered by the documents.
7.1.6 The cost of the Engineer's time to review and return a request for information whose answer is stated in the Contract Documents shall be borne as indicated in the datasheet.
Cost of Answering a Request the Contract Documents Already Answerradio
○ Borne by the Owner
○ Charged to the Contractor at the rates the Agreement between the Owner and the Engineer states, and deducted from sums due the Contractor
NOTE A request whose answer is on the next sheet costs the Engineer the same hour as a real one, and on a project with several hundred requests the hours add up to a fee the Owner did not budget. Charging the Contractor for them is what some Owners do to make the Contractor's review of the documents real before it asks, at the cost of an argument over every charge about whether the answer really was in the documents, and it suits a project on which the Engineer's construction phase services are billed hourly. Leaving the cost with the Owner avoids the argument and is the arrangement under a lump-sum construction phase fee, where the Engineer carries the hours. (7.1.7)
7.2 Content and Submission of a Request
7.2.1 Each request for information shall address one subject.
7.2.2 Each request for information shall state the project name, a sequential number, the date, the subject, the specification section and the drawing sheet and detail the question arises from, the question, the Contractor's interpretation or proposed resolution, whether the Contractor expects the response to affect the Contract Sum or the Contract Times, the date by which the response is needed and the schedule activity that date is drawn from, and the originator where the question arose with a subcontractor or a supplier.
NOTE A request that asks three questions gets one response, and two of the questions are answered in a sentence meant for the third. One subject per request is what lets each question be logged, answered, closed, and cited on its own, and it is what lets the Engineer answer the easy question today without holding it for the hard one. (7.2.3)
7.2.4 A request for information shall be submitted by the Contractor through the project platform, on the form the platform provides or, where the platform provides none, on the form the Engineer issues at the preconstruction conference.
7.2.5 A request for information originating with a subcontractor or a supplier shall be reviewed by the Contractor, shall carry the Contractor's own interpretation or proposed resolution, and shall be submitted by the Contractor as its own request.
7.2.6 A resubmitted request for information on a subject already answered shall carry the original number with a sequential suffix and shall state what in the response is unclear or incomplete.
7.2.7 Sketches, photographs, and marked drawings needed to understand the question shall be attached to the request and shall be identified by the request number.
7.3 Engineer's Response
7.3.1 The Engineer shall respond to a complete request for information within the number of working days indicated in the datasheet after receiving it.
Response to a Request for Informationrange
Not more than
working days
357101421
NOTE The response time is the Owner's trade between the quality of the answer and the pace of the Work. A short period, such as three or five working days, suits a project on which the Work waits for the answer, such as a tie-in or a congested renovation, and it gets a quick answer from whoever is available at the Engineer's office, with the structural or the electrical consultant consulted afterward, if at all. A period of ten working days or more gives the Engineer time to route the question to the consultant whose discipline it belongs to and to check the answer against the rest of the documents, at the cost of a Contractor who schedules around it or who builds what it thinks the answer will be. The period the project picks is the one the Engineer's construction phase fee was priced on. (7.3.2)
7.3.3 The response time shall run from the Engineer's receipt of a request that contains everything the Content and Submission article requires, and the Engineer shall return an incomplete request within two working days, stating what is missing, without a response.
7.3.4 Where the Contractor identifies a request as affecting a schedule activity and states the date by which the response is needed, the Engineer shall respond by that date where the date allows a considered answer and otherwise shall state, within two working days after receipt, the date by which the response will be issued.
7.3.5 The Engineer's response shall answer the question asked, by a clarification, a reference to where the Contract Documents answer it, a sketch, or a direction, and the Engineer may request further information where the question cannot be answered as asked.
7.3.6 A response to a request for information is a clarification of the Contract Documents and shall not of itself change the Work, the Contract Sum, or the Contract Times.
7.3.7 Where the Contractor considers that a response changes the Work, the Contract Sum, or the Contract Times, the Contractor shall give notice under Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures within the time that standard states and before acting on the response, and a Contractor that acts on the response without that notice shall not be entitled to an adjustment on account of it.
7.3.8 Where the Engineer considers that a response involves a change in the Work, the Engineer shall say so in the response and shall initiate the procedure of Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures, and the Contractor shall not proceed with the changed Work until that procedure authorizes it, except where the Owner directs otherwise in writing.
NOTE The request for information is the most common route by which a change enters a project without anyone having agreed to pay for it. A response that says to add a valve has changed the Work, and whether the Contractor is paid for the valve depends on whether anyone said so before it was installed. Requiring the notice before the Contractor acts, and requiring the Engineer to flag the change when it sees one, puts the question of cost on the table while the valve is still in the supplier's warehouse. (7.3.9)
7.3.10 A response to a request for information shall not relieve the Contractor of its responsibility for the coordination of the Work, for its means and methods, or for the accuracy of the dimensions and quantities it takes from the Contract Documents.
7.4 Request for Information Log
7.4.1 The Contractor shall maintain a log of every request for information on the project platform, listing for each request its number, the date submitted, the subject, the specification section and drawing sheet, the date the response is needed, the date the response was issued, its status, whether the Contractor has given notice of a cost or time effect, and the date closed.
7.4.2 The Contractor shall present the current log at each progress meeting and shall identify the requests whose response is overdue under the Engineer's Response article.
7.4.3 Where the project platform generates the log from the requests entered on it, the platform's log shall satisfy this article, and the Contractor shall keep the status and the notice entries current.
7.4.4 The Contractor shall incorporate each response that affects what is built into the record documents under Closeout ProceduresCloseout ProceduresResolves to the current adopted revision.sync/closeout-procedures, identified by the request number.
NOTE The log is the only place the project can see how many questions are open, how long they have been open, and which of them the Contractor says will cost money. Presenting it at every meeting keeps the overdue ones from aging quietly, and the notice column is what makes the clarification-is-not-a-change rule visible: a request that has been open for a month with no notice beside it is one the Contractor has accepted as a clarification. (7.4.5)
8 Coordination Drawings
8.1 Where Coordination Drawings Are Required
8.1.1 The Contractor shall prepare coordination drawings as indicated in the datasheet.
Coordination Drawing Programradio
○ Required for the spaces the Contract Documents designate
○ Required for every space where the work of two or more trades shares a room, a gallery, a shaft, a chase, or a ceiling
○ Not required beyond the areas the discipline standards require them for
8.1.3 Where coordination drawings are required for designated spaces, the spaces shall be as designated on the contract drawings.
8.1.4 The content, the drawing scale, and the space priority rule of the coordination drawings for the mechanical work and the electrical work shall be as Common Work Results MechanicalCommon Work Results for MechanicalResolves to the current adopted revision.sync/common-work-results-mechanical and Common Work Results ElectricalCommon Work Results for ElectricalResolves to the current adopted revision.sync/common-work-results-electrical state, and this standard governs the program, the lead, the method, the sequence, the clash resolution, and the Engineer's review.
8.1.5 Where a discipline standard on the project indicates a coordination drawing lead, a coordination method, or a response period different from the one indicated in this standard, this standard shall govern.
8.2 Lead Trade and Sequence of Overlays
8.2.1 The coordination drawings shall be led by the party indicated in the datasheet, who shall assemble the composite drawing or the federated model, issue it to the trades, convene the coordination meetings, and record the resolution of each clash.
Coordination Drawing Leadradio
○ The Contractor's own staff
○ The mechanical trade
○ A coordination consultant retained by the Contractor
NOTE The Contractor's own staff leading carries neutral authority over every subcontractor and is where a model-based process is usually run from, at the cost of a Contractor who has to hold the staff and the tools to do it. The mechanical trade leading puts the drawings in the hands of the trade with the largest and least flexible elements, which is the order the space priority rule produces anyway, at the cost of a lead who is also a party to most of the clashes. A retained consultant brings the tooling and the neutrality where the Contractor has neither, at a fee the Contractor carries in its price. (8.2.2)
8.2.3 The lead shall issue, for each area, a background showing the structure, the architectural elements, the equipment, and the clearances the equipment standards require, before any trade adds its work.
8.2.4 Each trade shall add its work to the coordination drawings for an area, at true size and including its insulation and its service and code clearances, within ten working days after receiving the background or the previous trade's overlay.
8.2.5 The trades shall add their work in the order of the space priority rule the discipline standards state, so that the elements that cannot move are placed before the elements that can.
8.2.6 A trade that has not added its work within the ten working days shall be deemed to accept the space the other trades have taken in that area, and shall route its work around them at its own cost.
8.2.7 The lead shall convene a coordination meeting for each area, attended by every trade with work in it, before the coordination drawings for that area are submitted to the Engineer, and shall record the clashes found and how each was resolved.
NOTE The deemed-acceptance rule is what gives the sequence teeth. Without it the trade that answers last holds up the area, and the trades that answered on time wait for it or build and are told later to move. With it, silence costs the silent trade and no one else. (8.2.8)
8.3 Coordination Method
8.3.1 The coordination method shall be as indicated in the datasheet.
Coordination Methodradio
○ Two-dimensional composite overlay drawings
○ Model-based coordination with clash detection
○ The Contractor's choice, stated in its coordination plan
NOTE Overlay drawings are produced with ordinary drafting tools, are within the reach of every subcontractor, and are adequate where the overhead space is generous and the trades are few, at the cost of conflicts in the vertical dimension that an overlay does not show. Model-based coordination finds those conflicts before they are built and is what keeps rework out of a congested gallery or ceiling, at the cost of every trade modeling its work to a common standard, which the smaller subcontractors meet by hiring it done. Leaving the method to the Contractor lets the Contractor match the method to its subcontractors, at the cost of the Owner finding out at the preconstruction conference which it will get. (8.3.2)
8.3.3 Requirements in this article apply where model-based coordination is indicated in the datasheet or stated in the Contractor's coordination plan.
8.3.5 The lead shall run clash detection on the federated model for each area, shall report hard clashes, in which two elements occupy the same space, and clearance clashes, in which an element occupies a clearance another element requires, and shall record the resolution of each.
8.3.6 Models shall be exchanged among the trades, and furnished to the Engineer, in an open, vendor-neutral exchange format in addition to any native format the lead uses.
8.3.7 Where the Engineer furnishes its design model to the Contractor for use as a coordination background, the model shall be furnished under the license and the confidentiality obligations of Document Confidentiality And Ai UseDocument Confidentiality and AI UseResolves to the current adopted revision.sync/document-confidentiality-and-ai-use, the Contract Documents and not the model shall govern the Work, and the Contractor shall verify the dimensions it relies on against the Contract Documents and the field.
NOTE A design model is drawn to communicate the design, not to fabricate from, and a duct modeled at its nominal size without insulation or a pump modeled as a box of the right footprint is correct for its purpose and wrong for coordination. Saying that the documents govern the model keeps a dimension taken from the model from becoming a claim when it differs from the sheet. (8.3.8)
8.4 Clash Resolution
8.4.1 The trades shall resolve the clashes among themselves at the coordination meeting, moving the element that costs the least to move, and the lead shall record each resolution on the coordination drawings.
8.4.2 A clash the trades cannot resolve among themselves shall be referred by the lead to the Engineer in writing, with the proposed resolutions and the consequence of each, before any work in the affected area proceeds.
8.4.3 Where a clash results from a conflict in the Contract Documents, the referral shall be made as a request for information under this standard, and the Engineer's response shall be subject to the Engineer's Response article.
8.4.4 Where a clash results from the Contractor's routing, sequencing, or choice of equipment, or from a product that differs in size or configuration from the basis of design, the Contractor shall resolve it at no cost to the Owner and without an adjustment of the Contract Times.
8.4.5 Work installed in an area before the coordination drawings for that area are accepted shall be relocated at the Contractor's cost where it conflicts with the accepted drawings or with the work of another trade shown on them.
NOTE The dividing line in a clash is whose fault it is. Two ducts that cannot both fit in the space the drawings allot them are the Engineer's problem and are answered as a question about the documents. A duct that does not fit because the Contractor bought a taller unit than the one scheduled is the Contractor's problem and is moved at the Contractor's cost. Most clashes are the second kind, which is why the referral to the Engineer carries the proposed resolutions: the Engineer is asked to pick one, not to find one. (8.4.6)
8.5 Engineer's Review of Coordination Drawings
8.5.1 The Contractor shall submit the coordination drawings for each area to the Engineer, through the submittal procedure of Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures and within its review period, before any work in that area is fabricated or installed.
8.5.2 The Engineer's review of coordination drawings shall be limited to conformance with the design intent and with the space the Contract Documents allot to each system, and shall not extend to the dimensional accuracy of the drawings, the fit of the work, or the coordination among the trades, which remain the Contractor's responsibility.
8.5.3 Coordination drawings are not shop drawings, and the Engineer's review of a coordination drawing shall not constitute review or acceptance of any product, size, or configuration shown on it.
8.5.4 A product, a size, a route, or a configuration shown on a coordination drawing that departs from the Contract Documents shall be submitted for review as a shop drawing or a product data submittal under Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures, and where it affects the Contract Sum or the Contract Times, noticed under Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures, and the coordination drawing shall not substitute for either.
NOTE A coordination drawing shows where things go; a shop drawing shows what they are. A Contractor that routes a larger duct on the coordination drawing, gets the drawing back marked reviewed, and then cites the review as acceptance of the duct has used the one to do the other's work, and the Engineer never looked at the duct. Keeping the two reviews separate is what lets the Engineer review a coordination drawing quickly, for the thing it is for. (8.5.5)
9 Project Communication and Records
9.1 Project Platform
9.1.1 The project platform shall be provided by the party indicated in the datasheet, and every submittal, request for information, transmittal, set of meeting minutes, log, and document issued during construction shall be exchanged and recorded on it.
Project Platform Provided Byradio
○ The Owner
○ The Engineer
○ The Contractor, on a platform the Owner accepts
NOTE The Owner providing the platform suits an Owner with a capital program that runs on one system, and it keeps the record in the Owner's hands from the first day to the last, at the cost of a license and an administrator the Owner carries. The Engineer providing it is the usual arrangement where the Engineer administers the construction contract, because the Engineer is the party reviewing what passes through it, at the cost of a record that lives on the Engineer's system until it is exported. The Contractor providing it, on a system the Owner accepts, puts the platform where the most entries originate, and it is priced in the bid, at the cost of a record kept by the party most of the disputes will be with and a dependence on the Contractor's subscription for access to it. (9.1.2)
9.1.3 The platform shall give the Owner, the Engineer, the Engineer's consultants, the Contractor, and each subcontractor the Contractor designates access to the documents each needs, with each party's access limited to what the confidentiality classes of Document Confidentiality And Ai UseDocument Confidentiality and AI UseResolves to the current adopted revision.sync/document-confidentiality-and-ai-use permit it to see.
9.1.4 The platform shall be a conforming service under Document Confidentiality And Ai UseDocument Confidentiality and AI UseResolves to the current adopted revision.sync/document-confidentiality-and-ai-use, and the terms on which it processes the project information shall be as that standard requires.
9.1.5 Where the Contractor provides the platform, the cost of the platform, its licenses, and its administration shall be included in the Contract Sum, and the Owner, the Engineer, and their consultants shall have access at no cost to them.
9.1.6 A document shall be received, for the purpose of every response period in this standard and in Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures, on the day it is posted on the platform and the recipient is notified by the platform or by electronic mail, and where it is posted after the end of the recipient's working day, on the next working day.
NOTE The platform is required to be one system because a project run on two, a submittal system here and an electronic mail thread there, has a record no one can reassemble when the question is what was sent and when. The definition of receipt is what every response period in the project is measured from, and without it the period starts when the recipient says it read the notification. (9.1.8)
9.1.9 The party providing the platform shall export the complete record on it, including every document, every log, and the transmittal history of each, in the formats indicated in the Electronic File Formats article, and shall deliver the export to the Owner before final payment under Closeout ProceduresCloseout ProceduresResolves to the current adopted revision.sync/closeout-procedures.
9.2 Electronic File Formats
9.2.1 Documents exchanged on the project platform shall be in the formats indicated in the datasheet for their kind.
Electronic Formats for Project Recordscheckbox
☑ Searchable portable document format for correspondence, minutes, requests, and submittals
☐ Archival portable document format under ISO 19005 for the closeout export
☐ Native drawing files for coordination drawings, in addition to the portable document format
☐ Open, vendor-neutral model exchange format for coordination models
☑ Delimited text or spreadsheet format for the logs
NOTE A searchable document and a log that opens in a spreadsheet are what every project needs and what every party can produce. The archival format is asked for by an Owner whose records retention policy requires a file that will still open in thirty years, and it costs a conversion step at closeout. Native drawing files and the open model format are asked for where the Owner will carry the coordination drawings or the model into its facility records or into the next project, and they cost the trades the delivery of a file they would otherwise keep to themselves. (9.2.2)
9.2.3 A portable document format file of a drawing shall be produced from the drawing file and not from a scan where the drawing exists as a file, shall be at the sheet's size and scale, and shall retain its text layer.
9.2.4 Files shall be named under the convention the Engineer issues at the preconstruction conference, which shall identify the project, the kind of document, its number, and its revision.
9.2.5 The Contractor shall not alter a drawing file or a model the Engineer has issued except to add its own work to a copy identified as the Contractor's, and shall not remove a title block, a seal, an issue date, or a confidentiality marking from any file or its derivative.
9.3 Transmittals and Written Communication
9.3.1 Every document sent between the Owner, the Engineer, and the Contractor during construction shall be accompanied by a transmittal that identifies the sender, the recipient, the date, each document sent with its number and revision, and the action requested, and the transmittal record the project platform generates shall satisfy this requirement.
NOTE The transmittal is the project's evidence of what was sent and when, and the response periods in this standard, in Submittal And Quality ProceduresSubmittal and Quality ProceduresResolves to the current adopted revision.sync/submittal-and-quality-procedures, and in Contract Modification ProceduresContract Modification ProceduresResolves to the current adopted revision.sync/contract-modification-procedures are all measured from it. A platform that stamps every upload with its sender and date produces the record without anyone writing a transmittal, which is one of the two reasons the platform is required. (9.3.2)
9.3.3 A posting on the project platform, an electronic mail to a representative named in the project directory, and a letter shall each be written communication for the purpose of this standard, and a telephone call, a text message, or a conversation at the site shall not be, unless confirmed by one of the three within one working day.
9.3.4 The manner and the time of giving a notice the General Conditions require, including the notice of a claim, shall be as the General Conditions provide, and the written communication rule of this standard shall not substitute for them.
9.3.5 The Engineer shall post on the project platform each site visit report, each field observation, and each written site instruction within two working days after the visit or the instruction.
9.3.6 The Contractor shall keep the project directory current on the project platform and shall notify the Engineer of a change in a representative, a telephone number, or an electronic address within five working days after the change.
NOTE The text message is where site instructions actually travel, and it is the communication least likely to be found a year later. The rule does not forbid it; it requires that an instruction given by one be confirmed by a means the record keeps, which puts the burden of confirming on whoever wants to rely on it. (9.3.7)
10 Coordination with Other Standards
10.1 The Contractor shall include in each subcontract and purchase order the meeting attendance, the request for information, the coordination drawing, and the project platform obligations of this standard that apply to the subcontractor's or supplier's scope, and shall bind each of them to submit its questions through the Contractor and not to the Engineer directly.
10.2 Where a technical standard requires a conference, a coordination drawing, or a communication for its own work, that requirement shall be read as a requirement under the procedures of this standard, and where the two differ, the more stringent requirement shall govern unless the Contract Documents direct otherwise.
10.3 The Contractor shall reconcile the meeting, request for information, coordination, and communication requirements of the Agreement, the General Conditions, and each technical standard with this standard, and shall report in writing, before the preconstruction conference, any conflict between them.
NOTE A subcontractor that sends its questions straight to the Engineer, and an Engineer that answers them, between them produce an answer the Contractor never saw and a change the Contractor did not price. Flowing the procedure into the subcontract is what keeps the Contractor in the path, which is where the Contract puts it. (10.4)
This standard is written and maintained by SynC and licensed under Creative Commons Attribution 4.0. You may share and adapt it, including commercially, provided you credit SynC Standards, link to the license, and indicate any changes. Each standard is drafted from cited sources under published authoring rules, reviewed before adoption, and corrected in the open. Keep the attribution and notice below with any copy; it carries the warranty notice the license asks you to retain.
"Project Management and Coordination," SynC Standards, revision 1. Licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Source: https://synergyinconstruction.com/standards/general/project-management-and-coordination. Reference material only; not professional engineering advice and provided without warranty. Verify against governing codes and have a licensed professional review before use.