This is institutional knowledge. It is not documented in any SOP. It is not available on the IRB's website. It was learned through years of interaction, accumulated observation, and occasional painful experience. And it is extraordinarily valuable -- because it is the difference between a submission that sails through review and one that gets returned with a request for revisions that a more experienced coordinator would have anticipated.

The problem, of course, is that this knowledge lives in one person's head. When that person leaves -- transfers to another department, takes a new position, retires -- the knowledge leaves with them. The next coordinator starts from zero, making the same mistakes, discovering the same patterns, rebuilding the same mental map. At a site managing 15 or more studies across multiple IRBs, the institutional knowledge about each IRB represents months of accumulated operational intelligence. Losing it is not merely inconvenient. It is operationally costly.

This lesson teaches you to make that knowledge explicit. To build a structured repository that captures what the formal procedures do not -- the operational patterns, the reviewer preferences, the timing insights, the unwritten rules -- and to maintain it as a living resource that survives personnel changes and strengthens the playbook system you built in Lesson 3.

This is institutional knowledge. It is not documented in any SOP. It is not available on the IRB's website. It was learned through years of interaction, accumulated observation, and occasional painful experience. And it is extraordinarily valuable -- because it is the difference between a submission that sails through review and one that gets returned with a request for revisions that a more experienced coordinator would have anticipated.

The problem, of course, is that this knowledge lives in one person's head. When that person leaves -- transfers to another department, takes a new position, retires -- the knowledge leaves with them. The next coordinator starts from zero, making the same mistakes, discovering the same patterns, rebuilding the same mental map. At a site managing 15 or more studies across multiple IRBs, the institutional knowledge about each IRB represents months of accumulated operational intelligence. Losing it is not merely inconvenient. It is operationally costly.

This lesson teaches you to make that knowledge explicit. To build a structured repository that captures what the formal procedures do not -- the operational patterns, the reviewer preferences, the timing insights, the unwritten rules -- and to maintain it as a living resource that survives personnel changes and strengthens the playbook system you built in Lesson 3.