Department Drawing Coordination Work Brief

This drawing coordination work brief sets out a proposed departmental assignment for reviewing conflicts between architectural, structural and building-services information. Its purpose is to identify details that do not agree, record the construction decisions they affect and direct clarification to the appropriate project reviewers before the affected work proceeds.

The brief is a draft for project-team review, not a record of a completed assignment or an instruction to change a design. Confirm the review scope, named responsibilities and decision-making authority against the project appointments before using it.

Purpose and boundaries of the drawing coordination work brief

The proposed task is to compare the information needed for a defined area or construction activity. This might involve a room, a floor junction, an opening or a services route. Keep the review boundary specific enough that the team can identify the relevant drawings and understand which site activities depend on the outcome.

Coordination should establish whether the different disciplines describe a compatible arrangement. It should not become an informal redesign exercise or assume that one drawing automatically overrides another. Where a conflict requires a design decision, refer it to the person authorised to make that decision under the project arrangements.

Define the assignment before reviewing details

Record the project reference, area under review, intended construction activity and reason for opening the task. State whether the concern comes from a drawing comparison, a site observation, a proposed product or a change issued by a designer. Distinguish confirmed information from assumptions that still need checking.

• Identify the physical limits of the review.
• List the disciplines whose information may be affected.
• State the decision or coordinated detail needed from the assignment.
• Identify related work that could conceal, obstruct or depend on the unresolved detail.
• Record who will confirm that the review has covered its agreed scope.

Drawings and construction details required for review

Begin with the relevant drawing register, where one is available, and establish the issue status of each document. Record drawing numbers, titles, revisions and issue dates rather than relying on filenames alone. A recently received file should not be assumed to replace an earlier instruction without checking its purpose and status.

Assemble a consistent review set

Collect the architectural plans, sections and details that define the area, together with the corresponding structural and building-services information. Include specifications, schedules and relevant written instructions where they influence the same detail. If an essential document is unavailable, record the gap instead of treating the incomplete set as coordinated.

Where installation depends on a particular product, request the relevant proposed product information through the project’s agreed review process. Do not substitute an assumed equipment size, fixing arrangement or maintenance clearance for information that has not been confirmed.

Check what exists on site

If construction has already started, identify which dimensions or conditions need site verification. Record the location, date and source of any measurements used in the review. Drawings and photographs can support the discussion, but a photograph alone may not establish dimensions or hidden construction.

Flag any difference between the documented arrangement and the observed work. Keep that discrepancy visible as a separate action so that a proposed coordination response does not accidentally rely on an unverified site condition.

Interfaces to check between architecture, structure and services

Review the places where one discipline’s requirements occupy the same space as another’s. Follow the proposed arrangement through plans, sections and details rather than checking each drawing in isolation. A route that appears clear on a plan may still require clarification when its level, support or access requirements are considered.

Openings, supports and service routes

Compare proposed doors, windows, ducts, pipes and other openings with the structural information for the same location. Identify penetrations or recesses that are shown by one discipline but absent from another. Refer any proposed alteration to structural elements for appropriate design review; the coordination brief does not authorise cutting, drilling or relocation.

Check whether the services route has been considered alongside ceilings, walls and the supporting arrangement. Where a route depends on an opening or support detail that has not been issued, record that dependency explicitly.

Levels, finishes and thresholds

Compare the stated level references and distinguish structural levels from finished levels. Review adjoining rooms, thresholds and service outlets where the final arrangement depends on the build-up of finishes. Do not assume that similarly labelled dimensions use the same reference point.

The guidance on planning finished floor levels can support the wider discussion. For this assignment, the required output is a confirmed relationship between the relevant drawings, not a newly assumed floor build-up.

Access, operation and maintenance

Consider whether the coordinated arrangement allows the intended components to be installed, operated and accessed. Check doors, access panels, valves and equipment against nearby finishes and fittings, using confirmed product requirements where available. Record any access requirement that remains unknown.

For example, a valve location may need to be reviewed alongside a cupboard or wall finish rather than only on a plumbing layout. The article on planning plumbing isolation valves provides related planning context, while the actual position still needs project-specific confirmation.

Record conflicting details and their construction implications

Give each issue a unique reference and describe the conflict in neutral, factual language. Identify the drawings involved, the precise location and the information that does not agree. Avoid entries such as “check services” that leave the reviewer to discover the question again.

Separate the observed conflict from its possible consequences. An opening shown in different positions is an observation; its effect on fabrication, installation or sequencing requires assessment. Where cost or programme effects are not yet known, record them as requiring review rather than assigning an unsupported amount or delay.

Compact coordination record checklist

Use the following fields to structure the issue register. They are proposed recording requirements, not evidence that any review or approval has taken place.

Record field	What to capture	Review check
Location and reference	Issue number, area and drawing references	Can another reviewer find the detail?
Conflict	The specific information that disagrees	Are observations separate from assumptions?
Construction dependency	Work or procurement affected	Is the affected scope clearly bounded?
Clarification owner	Named reviewer and required contributors	Has responsibility been accepted?
Required response	Decision, revised detail or confirmation needed	Will the response resolve the question?
Closure evidence	Response reference and checked outcome	Have related documents been reconciled?

Assign clarification actions and responsible reviewers

Assign a named action owner for each issue rather than sending an undirected request to the whole team. The action owner should obtain the necessary response, while the design decision remains with the appropriately authorised reviewer. Confirm these roles rather than assuming that attendance at a coordination meeting creates approval authority.

Ask a question that can be answered

A useful clarification request states the conflict, identifies the relevant documents and explains which decision is needed. Ask the reviewer to confirm the intended arrangement and identify any drawings or specifications requiring amendment. Mark any suggested solution as a proposal for review, not an instruction for construction.

Agree a response date with reference to the affected activity and record it in the action register. If the response requires input from several disciplines, identify who will bring those comments together so that the site team does not receive incompatible partial answers.

Identify unresolved decisions before affected work proceeds

For every open issue, identify the construction step that depends on its resolution. This may concern ordering, fabrication, setting out, forming an opening or covering completed work. Record the dependency precisely without implying that all work across the project must stop.

Bring unresolved dependencies to the person authorised to direct the affected work. Any decision to hold, resequence or release an activity should follow the project’s agreed authority and communication arrangements. Silence, an unanswered message or a marked-up discussion sketch should not be recorded as approval.

Prepare a clear decision list

• State which arrangement still needs confirmation.
• Identify the activity or order that relies on the answer.
• Record any further site checks or specialist input required.
• Identify who can confirm the decision and who must receive it.
• Keep temporary proposals separate from accepted construction information.

Where a response changes scope, materials or sequence, refer those consequences through the relevant project review process. A technically coordinated detail may still need separate consideration of cost, procurement or contractual instructions.

Review responses and close coordination actions

Check each response against the original question and the other affected documents. A reply may resolve one drawing conflict while leaving an associated level, opening or access detail unanswered. Keep the issue open, or create a clearly linked follow-up action, until the remaining question has an assigned route to resolution.

Record the response reference, revision and reviewer before changing the issue status. Confirm that the agreed information has reached the people responsible for the affected work and that superseded information is identified through the project’s document-control arrangements.

Expected departmental handover

The proposed handover should include the review-set register, marked-up issue references, action register and supporting responses. Add a short summary distinguishing closed issues from unresolved decisions. For each outstanding item, state the owner, required next action and construction dependency.

Closure means that the recorded question has an adequately documented answer; it does not by itself certify installed work or approve unrelated details. Any subsequent site verification or inspection should remain identifiable as a separate task.

Bring one unresolved interface to the project team

Start with a specific drawing interface that is unclear: an opening, a service route, a level junction or an access requirement. Gather the relevant drawing references and ask the project team what clarification is needed, who should provide it and which activity depends on the answer.

For wider guidance on managing site information and follow-up, see how to supervise a building project in Uganda. Use this draft brief to support that discussion, then adapt the responsibilities and review steps to the actual project arrangements.