Database Lock and What It Commits You To

Part of Clinical Project Management (PM) Training: Inspection Readiness and Close-Out.

About 1 minutes. Free, in your language, no account needed.

Lock is a declaration

Locking the database says the data is complete and correct and the analysis can proceed on it. Unlocking afterwards is possible and is a documented, audited event that invites the question of what was wrong with the first declaration.

So the work happens before, not after.

What has to be true first

Every query resolved or formally closed with a reason. External data reconciled, including safety. Coding complete. Protocol deviations recorded and classified. Any participant with missing critical data chased to a documented end. Randomization records reconciled against what was dispensed.

A lock declared with open queries is a lock that will be broken.

The project manager's part

Lock is coordination. Data management, statistics, safety, medical, the sites and the vendors all have to finish in an order, and each one's finish depends on someone else's.

Build the lock sequence backwards from the date and find the long pole. It is usually external data or a small number of sites with outstanding queries.

Do not let a date force a declaration

Pressure to lock for a reporting deadline is real. A lock that requires an unlock two weeks later costs more than the delay would have, and it leaves an audit trail that says the trial declared completeness it did not have.

If the data is not ready, the honest position is to say so and move the date.