In 2016, I spoke with David De Yarza and Vishal from GamePlan about the experience of using a project record after the original conversation had passed. David described the search problem in familiar terms from that moment: “It's still a nightmare to find something from three months ago.”
The issue was not whether an email or file existed. It was whether a team member could recover the decision, its context, and its approval path when the question returned.
Search should lead back to the decision
David De Yarza demonstrated a project history where a team could search a plain-language term, find a related submittal, and see its status, participants, dates, and attached material. He also showed how a discussion connected to the item could preserve why the answer was reached.
In one example, David said his team had spent money addressing an adhesive problem after nobody could find the communication that led to the material choice. Search is not a guarantee against every repeat problem. Its value here is the ability to recover the route to a past decision.
The workflow has to respect the agreement
David De Yarza and Vishal from GamePlan both explained that projects route RFIs, submittals, and other communication differently. Contract terms and leadership roles could require information to pass through the general contractor rather than move directly between every participant.
Vishal said the software needed to adapt to valid project workflows instead of forcing every team into one process. A searchable record is more useful when it reflects who was allowed to communicate, review, and approve.
Test one closed item
Choose a completed RFI, submittal, or field issue and ask someone who was not part of the original exchange to find the decision. See whether that person can recover the question, response, approval, and surrounding context from the project record.
If a step is missing, note whether the gap came from the search terms, the workflow, or information that was never captured.
Adoption needs more than an intuitive screen
David De Yarza described users with different levels of comfort and different training needs. He said project leadership had to commit to the communication system if the team was expected to keep project information out of scattered email.
Those product and adoption observations came from 2016 and should not be used to describe teams or products today. The practical limit is simpler: search can only return the context that people recorded through a workflow they actually used.
Search supports a decision trail, not a perfect memory
Search cannot prove that a past decision was correct, prevent a dispute, or replace the contract. It can help a team recover what was asked, who responded, what was approved, and why the answer moved forward.
That is enough to make the history useful. A reliable project history gives the next decision a traceable starting point without asking an inbox to carry the whole story.
