Meetings, issues and RFIs
How do we run the weekly loop so issues actually close?
A fixed agenda, decisions with an owner and a date, open items rolled forward every week, and questions to the design team tracked until they are answered.
Understand
What it is, in plain language
- Pedia · WorkflowsModel federationCombining separate discipline models into one coordinated view without merging them, so each team keeps ownership of its own model.
- Pedia · GlossaryCoordination issueA recorded problem between models or disciplines, with an owner, status and due date, tracked until it is resolved.
Learn
Short lessons with a quick check
Do
Tools that export Excel, PDF and Word
- Tool · Excel · PDF · WordCoordination Meeting PackUse it every week: agenda, attendance, issue log, actions and minutes.
- Tool · Excel · PDF · WordRFI RegisterUse it to track questions sent to the design team until they are answered.
- Tool · Excel · PDF · WordDelivery TrackerUse it every week to report delivery progress to the project team and the client.
How it works
The process, at a glance
Weekly coordinationRepeat every cycle until the stage is coordinated
1Share modelsChecked, in the CDE
6Fix in own modelsEach task team
7Verify and closeIn the next shared model
- 1OpenRaised with an owner and a due date
- 2In progressThe owner is working on it
- 3ResolvedOwner says it is fixed
- 4ClosedVerified in the next shared model
Common mistakes
What goes wrong most often on real projects.
- Screen-sharing thousands of clashes instead of a short issue list.
- Decisions without an owner or a due date.
- Closing issues on a promise instead of a verified model.
Is it in place on your project?
Tick what is done — it counts towards the checkpoint on your learning path.
0 / 4 in place
Keep going