One detail from the second half of the 2016 conversation with Carol Hagen carried a larger project lesson. When someone added a markup, she said, “you know who did it at what time.”
That visible authorship was only the beginning. The record could also preserve replies, status changes, responsibility, and the route to the next reviewer.
A trustworthy record keeps authorship intact
Carol Hagen said one participant could not change another person's markup in the workflow she demonstrated. The system logged who added an item and when, while replies stayed connected to that item.
That structure did not guarantee a good decision. It made the history of the decision easier to inspect. When disagreement surfaced later, the team could return to the actual sequence instead of rebuilding it from memory.
Different reviewers need different states
Carol Hagen used a complex approval path to explain why one generic status was not enough. A subcontractor, general contractor, architect, public agency, or joint-venture partner could enter the review at a different point and require a different response.
The record needed to show more than accepted or rejected. It needed to reflect who could act and which review came next.
For one active review path, write down the status each participant actually uses. Compare that list with what the project record displays. If the record hides a handoff, decide who will update the workflow before the next item follows the same route.
Participation should not depend on authoring expertise
Carol Hagen also described a 2016 three-dimensional PDF workflow that allowed people without specialist model-authoring tools to see the issue and add a specific comment. Her example did not make every participant a BIM expert. It made the subject of the discussion more accessible.
That distinction matters. The person who can identify a field or design concern may not be the person who created the model. The review process should give that knowledge a clear way into the record.
The record has to outlast the meeting
Carol Hagen described people contributing at the same time or at different times across locations. Participants could return to the markups and replies after a meeting they missed or could not attend in full.
Persistent access helps only when people know how to use it. Carol said training needs varied by role and task. Some users needed a class, while others could use a short video or a focused answer for the problem in front of them.
Let the record carry context, not judgment
A collaboration record can show authorship, responsibility, status, and sequence. It cannot decide whether the markup is correct or whether the next reviewer has enough information to approve it.
That boundary makes the record more useful. Let it carry the history and handoff clearly, then leave the technical judgment with the people responsible for the decision.
