What Projects does
The result is a connected project record: the board shows the decision, while linked tool records retain the inputs and working information behind it.
How it fits into the workflow
- Create the project and organize a board around rooms, zones, building elements or review packages.
- Develop information in tools such as the Texture Editor, Schedule Builder, Color Palette Tool or U-Value Builder, then save the useful output to the project.
- Add material choices, images, notes and specification clauses alongside those tool records.
- Issue a focused client, technical or contractor review link and preserve the decision against the board revision that was actually reviewed.
Where it can save time
Projects reduces the repeated work of copying values between disconnected documents, rebuilding approval boards and searching for the calculation or palette behind a decision. Reopening a linked tool record is usually faster and clearer than interpreting a screenshot or an old exported file.
Compliance and professional limits
Projects supports traceability, review and decision records, but it does not replace the project common data environment, appointment, contract administration process or statutory submission. A recorded approval is evidence of that review event, not proof that the selected design complies with every applicable requirement.
Professional boundary: Define who is authorized to approve each kind of information and continue to issue controlled contractual or statutory information through the project systems required by the appointment.
In summary
Projects is most useful when its saved output remains connected to the project decision and is reviewed within the limits described above.