02 / Capabilities · 05

Project coordination.

Keep site interfaces, constructability questions, technical information, responsibilities, and decisions connected to the work.

Back to capabilities

Project coordination

Project Coordination

Bring the right signal to the right participant.

Coordination is more than forwarding messages. Each issue needs context, ownership, timing, current information, and a visible route to closure.

Overview

Service Overview

Keep field conditions and technical decisions in the same conversation.

Tomy Engineering supports the coordination of participants, technical information, work fronts, constructability questions, inspections, and short-term actions around the needs of the site.

The service supports the appointed project team. It does not replace design responsibility, contractor supervision, statutory inspections, health-and-safety duties, or approvals held by other responsible parties.

Participant interfaces

Participant Interfaces

Different responsibilities. One coordinated route.

Access and authority follow the approved project role and work scope. Coordination makes interfaces visible without treating every participant as interchangeable.

01

Owner / Client

Priorities, decisions, approvals, and authorized project visibility

02

Consultants

Design information, technical responses, reviews, and discipline interfaces

03

Main contractor

Programme, work fronts, logistics, coordination priorities, and site status

04

Subcontractors

Assigned work packages, installation information, RFIs, evidence, and close-out

05

Suppliers

Technical submissions, lead times, delivery information, and approved product data

Issue to record

Issue To Record

Close the loop, not just the conversation.

A question is useful only when the responsible person, response, affected work, verification, and final record stay connected.

01

Observe

Identify an interface, constraint, discrepancy, or unanswered site condition.

02

Raise

Record the question with its location, context, current information, and required date.

03

Assign

Direct the action to the responsible participant without widening access unnecessarily.

04

Resolve

Coordinate the response, affected work, documents, and agreed next action.

05

Verify

Check that the response has been implemented and the required evidence is available.

06

Record

Close the item with its decision, revision, evidence, and remaining follow-up visible.

Coordination rhythm

Coordination Rhythm

Match the review cycle to the urgency of the work.

Immediate

Site constraints & urgent interfaces

Escalate issues that block safe or coordinated work through the approved project route.

Short-term

Lookahead & work-front readiness

Review upcoming activities, information needs, inspections, access, and participant dependencies.

Periodic

Coordination & progress review

Bring current actions, RFIs, documents, evidence, and decisions into one accountable review.

Coordination information

Project Information

Work from current information and leave a usable record.

Information required

  • Current coordinated drawings, models, specifications, and revision status
  • Programme, lookahead activities, work packages, and access constraints
  • Participant responsibilities and approved communication routes
  • Open RFIs, technical submissions, inspections, and approval requirements
  • Site observations, progress evidence, and known interface risks
  • Required response dates, hold points, and handover expectations

Typical records

  • Site coordination and action records
  • RFI, response, and decision history
  • Drawing, document, and submission status information
  • Inspection and approval follow-up records
  • Interface, constraint, and lookahead summaries
  • Verified evidence and close-out information

Connected record

Typical Records

Digital tools support traceability without replacing coordination.

Where included, the management portal can connect an RFI or question to its project and WBS context, retain progress history and evidence, and limit visibility to authorized participants.

Start a conversation

Start a Conversation

Need a clearer route from site issue to decision?