CYBUILD ENGINEERING SOLUTIONS
PROJECT DESK — DISCUSSION PREPARATION

Make the interfaces clear before work expands.
Public guide edition 2026-10-22
https://www.cybuild.net/project-desk/scope-and-interfaces/

NEXT DECISION
Who needs to provide or review what so the next project decision can be made?

BEFORE THE FIRST REVIEW
Begin with the problem and the intended next step.
• What change or project problem needs attention, and what decision is currently holding progress?
• Which disciplines are already engaged, and which interfaces need additional capability?
• What information is available now, and which assumptions would otherwise shape the scope?

Bring to the conversation: Describe the immediate deliverable and the information needed to prepare it. Identify the appropriate roles without assuming their acceptance of a responsibility.

Keep the limit clear: A general list of disciplines does not establish the agreed scope, professional responsibility, or authority to proceed.

AS INFORMATION DEVELOPS
Revisit the boundaries when new constraints appear.
• Has a field condition, equipment change, or review input affected the original scope?
• Which role can supply the missing input, and which responsible designer needs to review its effect?
• Does the next action require a clarification, a revised deliverable, or an explicit scope decision?

Bring to the conversation: Bring the changed condition and its affected interfaces into the project conversation. Confirm the responsible parties and next action through the agreed project process.

Keep the limit clear: Recognizing an interface does not transfer responsibility or authorize additional services.

BEFORE THE NEXT ISSUE
Make the state of the work understandable to the next person.
• Are the issue purpose, included scope, and known limitations clear to the recipients?
• Which inputs and decisions still need an identified responsible role?
• What should happen next, and which conditions need to be met first?

Bring to the conversation: Use a short discussion brief to communicate the next decision, supporting information, and open questions. Keep private assignment records in the agreed project workspace.

Keep the limit clear: General preparation guidance supports a conversation. It does not replace the project agreement or discipline-specific review.

General preparation guidance. Confirm project-specific requirements and responsibilities with the appropriate project team. This brief contains public prompts only; it does not create a portal record or establish approval.