Turn requests into assigned work
A request sent to the whole team can sit unanswered or get picked up twice. Create the work under its project and assign the person responsible for moving it forward.
Modeling a project, producing a drawing and helping with a design question require different work. Set up routes for the work your team does, with assignments at the stages that need them.
Let the scope develop into packages
Early on, you may know the area and assembly types before you know every rack or drawing. Start with that scope, then break it into packages as the design develops.
Keep names and package boundaries consistent through coordination, detailing and fabrication. The shop should be able to recognize the work without rebuilding the project structure at each handoff.
Review drawings with prefab
A familiar rack and a one-off build do not need identical review steps. Agree where prefab needs to weigh in on materials, assembly and buildability before the drawings are treated as finished.
Keep drawings in Documents and the review discussion in Comments alongside the work. When an issue needs another design pass, the responsible team can see the question and the step that needs attention.
Keep a revision from holding the whole scope
Consider this scenario. One package needs a design change while the others have completed their reviews.
Keep the revision with that package and confirm which others can proceed with the project and prefab teams. Review the affected field date separately. The result is a defined handoff for the ready work and an owner for the unresolved issue.
Walk through your VDC process
Bring a request, the design work it creates and the way it reaches fabrication. We can map that process in Building Swell, including the reviews and handoffs your team needs.
Book Demo