At a glance
A practical version-control method for the records you send to a new fertility clinic: build a dated report index, mark the latest version of each document, send one consolidated package, and keep a log of what was sent and acknowledged.
Most record problems at a new clinic are not caused by missing paperwork. They come from the same test arriving twice in different formats, an early draft sitting next to a final report, or two labs reporting the same measurement with different numbers and no note explaining which one is current. The clinic then has to guess which document to trust.
You can prevent most of this before you send anything. The method below is about version control, not interpretation: you decide what exists, what is current, and what was sent. Your new clinicians decide what the results mean.
Start with a dated report index, not a folder of files
A report index is a single list that describes every document in your package. Build it before you assemble the files, because writing the list forces you to notice duplicates and outdated versions you might otherwise send without thinking.
For each document, record:
- Document name — what it is, in plain words (for example, “day-5 embryology summary” or “stimulation monitoring bloods, cycle 2”).
- Report date — the date on the report itself, not the date you received it.
- Source — the laboratory, clinic or hospital that issued it.
- Status — final, preliminary, amended, or superseded.
- File name — the exact name of the file you are sending, so the clinic can match list to attachment.
- Note — anything the reader needs to know, such as “replaces the earlier version dated 3 March” or “same test repeated at a second lab; both included.”
A simple table works well. Keep the index as its own document (a spreadsheet or a clean one-page table) and send it as the first page of the package.
Identify the latest version of each report and label the rest
For every test or cycle event, decide which document is the current one. Then mark older versions as superseded rather than deleting them. Deleting creates a gap the clinic cannot see; labelling keeps the history visible while removing ambiguity.
Three situations cause most of the confusion:
- Amended reports. If a lab reissues a report with a correction, send both and state clearly which is the amended, current version.
- Preliminary versus final. If you only have a preliminary result, say so in the index. Do not present it as final.
- Repeated tests at different labs. The same measurement may be reported by two laboratories with different reference ranges or units. Include both, flag them as a known duplicate, and note which result you understand to be the current one — then leave the interpretation to the clinicians.
If you are unsure which version is current, say that in the index rather than choosing silently. A short note such as “two versions received; current version not confirmed” is more useful than a guess.
Send one consolidated package from a single sender
Duplicate reports often arrive because several people send records separately — you, a relative, your previous clinic, and a translation service. Each sender may include a different subset, and the clinic ends up reconciling them.
Choose one sender and one method. Put the report index first, followed by the documents in the order listed. If a document is large, keep the file name identical to the entry in the index so nothing has to be matched by memory.
Then ask the clinic to confirm receipt against the index — not simply “did you get my email” but “can you confirm you received items 1 to 12, and note any that are missing or unreadable.” This turns a vague acknowledgement into a check you can act on.
Keep a sent-log
A sent-log is a short record of what left your hands. It protects you if a document is later reported as missing, and it stops you resending the same file twice.
| Field | What to record |
|---|---|
| Date sent | The date you sent the package |
| Recipient | The named person or department, if known |
| Method | Portal upload, email, or hand delivery |
| Contents | Index version number and item count |
| Acknowledgement | Date and wording of the clinic’s confirmation, or “not yet confirmed” |
Update the log whenever you send an amendment. If you send a corrected report later, note it as a separate entry rather than editing the original line.
Ask which document set becomes the working record
Before or during your first consultation, ask the clinic two practical questions:
- Which set of documents will you treat as my working record?
- If a report is amended or a new result arrives later, how should I send it so it is added to that record?
The answers tell you whether to keep sending through the same channel and whether your index needs a new version number each time. They also clarify who on the clinic side is responsible for filing what you send.
This is a coordination question, not a clinical one. Your treating clinicians interpret the results and decide what they mean for your care; the administrative task is making sure they are reading the right version.
A short pre-send checklist
- Every document in the package appears in the index, and every index entry has a matching file.
- Each entry shows a report date, a source, and a status.
- Older versions are labelled superseded, not deleted.
- Known duplicates are flagged, with a note on which result you understand to be current.
- Preliminary or unconfirmed results are marked as such.
- One sender, one method, index first.
- You have asked for receipt confirmation against the index.
- The sent-log is updated.
If you are preparing records for a first review of a previous cycle, a structured records checklist for reviewing a previous IVF cycle can help you decide what belongs in the package. If you are specifically handing records over after a clinic change, the points to confirm with the receiving team are set out in handing over IVF records to a new clinic. For stimulation and monitoring paperwork, which is often the most duplicated part of a file, see organising stimulation and monitoring records.
Where coordination help fits
Record organisation is one of the practical tasks a coordination service can support: assembling a dated checklist, drafting the index, communicating document requests to the hospital, and keeping a log of what was sent and acknowledged. The clinician’s role is separate — interpreting results, answering clinical questions about diagnosis, options, risks and individual chances, and deciding what treatment to recommend.
If you would like help preparing a consolidated package or a report index before approaching a clinic, you can request a case review and describe what records you currently hold. Scope and any fees are confirmed individually, and appointment availability is subject to hospital confirmation.
Your next practical step
Bring your coordination questions.
Ask about appointments, records, travel or the practical arrangements for your visit.



