Research plans can change when access fails, instruments need revision, or preliminary work exposes a problem. The important task is to make those changes traceable, not to present the final design as though every decision was fixed from the beginning.
A protocol change log records what changed and why. Use it alongside any formal amendment, registration, or approval process your project requires.
Preserve the Earlier Version
Keep the original plan and identify the version currently in use. A date and descriptive version label can prevent confusion between drafts. Do not overwrite the only record of an approved procedure.
Record changes when they occur. Reconstructing decisions at the writing stage can blur whether a choice preceded data collection, followed a pilot, or emerged after analysis.
Record More Than the New Wording
Explain the reason, affected activities, and consequences for interpretation. A wording adjustment may be minor, while a new recruitment criterion can change the population represented.
| Change-log field | What to include | Why it matters |
|---|---|---|
| Previous plan | The relevant earlier procedure | Establishes the starting point |
| Change and date | The revised decision and when it occurred | Preserves sequence |
| Rationale | Evidence or constraint behind the decision | Explains the choice |
| Approval and impact | Required authorization and affected claims | Connects process to reporting |
Do not use the log as a substitute for approval. It documents decisions; it does not authorize them.
Distinguish Planned and Exploratory Decisions
In an invented thesis, the student adds a new comparison after noticing an unexpected pattern. The comparison may be informative, but it should not be described as a prediction specified before the evidence was examined.
Keep the timing clear. Report exploratory work honestly and use the relevant methodological guidance for its interpretation. Avoid rewriting earlier hypotheses to match later findings without disclosure.
If a change affects consent, data handling, or participants, follow the required amendment process before implementing it. Ask the appropriate institutional contact when uncertain.
Carry Changes Into the Thesis
Review the methods, findings, limitations, and conclusion for consequences of the change. A revised sample boundary should remain visible where claims about the population appear.
Include the level of detail required by the field and assignment. The submitted thesis may not need the entire working log, but its account must accurately represent consequential decisions.
- Retain earlier versions.
- Date decisions promptly.
- Explain reasons and interpretive effects.
- Complete required approvals separately.
- Keep planned and exploratory work distinguishable.
Frequently Asked Questions
Should every typo correction be logged?
Not necessarily. Prioritize changes that affect procedures, evidence, interpretation, or required approvals.
Can I change the research plan after starting?
Sometimes, but follow the relevant supervisory, methodological, and approval process rather than assuming permission.
Does a change mean the project failed?
No. A justified adjustment can be appropriate. Its consequences and reporting still need careful treatment.
Where should the log be stored?
Use the project’s approved recordkeeping system and protect any confidential information it contains.
Conclusion
Keep the research history honest. A clear change log supports accurate reporting and prevents the final thesis from disguising when and why important decisions were made.
