An issue must connect drawings and discipline owners while separating the solution decision from publication of revised documents.
Index
A clash between drawings involves more than one discipline; distributing only a task list loses the technical intersection.
The rule that changes the scope
An issue must connect drawings and discipline owners while separating the solution decision from publication of revised documents.
A project manager handles tasks; a custom portal links elements, solution proposals and technical deliverables.
A coordination decision can affect documents absent from the original question. Staff should add those relationships without giving the issue a new identity. Request a discipline view to check each owner's outstanding work and an issue view to verify the combined solution. Include receipt of an incomplete revision in scope: publishing a new file does not prove the conflict is resolved or that every participating discipline updated its design.
Specify operational deliverables
- Locate the incompatibility in the documents and identify the participating disciplines.
- Record the proposed solution and the people responsible for updating each sheet.
- Link closure to checking published revisions rather than simply answering a comment.
Test the exception before acceptance
In a hypothetical scenario, one discipline fixes its drawing while another has not published its revision; the issue must remain partly open.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring an anonymized coordination issue and the documents used to verify its resolution.