A year-end research project inventory is a structured review that turns a scattered collection of half-finished analyses, saved PDFs, and conference notes into a clear picture of what is ready to submit, what needs revision, and what should be closed or archived. The starting point is not to clean your desk; it is to define, for every project, the single next action that moves it toward a decision.
Most clinicians and medical researchers face the same starting state in December: active grants, a few manuscripts at different stages, abstracts accepted for conferences that are now in the past, and a library of references accumulated through the year. The inventory works when it separates submission readiness from mere activity. A project that received 40 hours of work but has no analyzable dataset is less "ready" than a short manuscript with a complete analysis and a drafted discussion.
The steps below use a focused clinical example—a randomized feasibility trial of a pharmacist-led medication review in older adults with polypharmacy—to show decisions, artifacts, and completion criteria. You can adapt the same sequence to systematic reviews, observational analyses, qualitative studies, or methodology projects.
What Is the Real Goal of a Year-End Inventory?
The goal is a written decision for every open project, not a longer to-do list. By the end of the exercise, each project should carry one of four labels:
- Submit-ready: the manuscript, supplementary files, and disclosure materials meet the target journal's requirements and have passed your internal checks.
- Revision-active: the project has a concrete revision task with an owner and a deadline.
- Data-pending: the next step is a defined analysis, data extraction, or query that does not require a new writing sprint.
- Archive or close: the work is paused with a dated note explaining why, so you can reopen it later without re-learning the context.
The inventory is not about guilt. It is about converting uncertainty—"where is that manuscript?"—into a status that lets you plan the first quarter. A useful artifact is a single project register, a table with one row per project and columns for status, next action, owner, deadline, and evidence backbone.
Start by Listing Every Project, Not Just the Papers
Begin with a raw dump. List every grant deliverable, manuscript draft, protocol, abstract, and analysis plan that consumed time in the past year. Include projects that stalled, projects that are waiting on co-authors, and projects that exist only as a promising dataset.
For each item, record three fields:
- Furthest output: the most complete artifact you can find, such as a drafted methods section, a pruned dataset, or an approved protocol.
- Last activity date: when the project last changed state.
- Blocking question: the single question that, if answered, would let you move the project forward. For example, "Does the primary outcome differ between arms after adjusting for baseline frailty?" is a blocking question. "Make more progress on the paper" is not.
This listing step matters because research teams routinely undercount dormant projects. A project without a clear owner and blocking question will survive the inventory and re-emerge as an emergency in February.
Which Projects Are Actually Close to Submission?
Submission readiness is a checklist, not a feeling. For a clinical trial manuscript, the core evidence items are:
- A pre-specified primary outcome with a complete analysis.
- A CONSORT or equivalent flow of participants through eligibility, randomization, allocation, follow-up, and analysis.
- Tables that match the results text and the study protocol.
- A discussion that states the main finding, compares it with prior evidence, and names the principal limitations.
- Complete author, funding, conflict-of-interest, and data-sharing statements.
Systematic reviews follow the same logic with PRISMA items. The screening and selection process should be documented well enough that another reviewer could repeat it. Cochrane guidance emphasizes planning searches from eligibility criteria, using multiple sources, documenting the process, deduplicating records, screening in stages, linking reports of the same study, and updating searches before publication. If your review cannot show a dated search log, a deduplication count, and a record of how reports were linked to studies, it is not submission-ready even if the writing is polished.
The worked example below shows how this checklist separates a manuscript that looks done from one that can actually leave your desk.
Worked Example: Pharmacist-Led Medication Review Feasibility Trial
Suppose your team completed a two-arm pilot randomizing 120 older adults with polypharmacy to a pharmacist-led medication review or usual care. The primary outcomes are recruitment rate, intervention fidelity, and completion of medication changes within 60 days.
Year-end starting state. You have an abstract accepted at a national pharmacy meeting in October, a clean analysis dataset, draft Table 1, and a results section that is 70% written. The discussion is an outline. The protocol was registered, but the registration record does not list the 60-day completion outcome as primary.
Inventory decision. The project is not submit-ready. The registration mismatch is a blocking question because reviewers will compare the registered outcomes with the manuscript. The next action is to submit a protocol amendment to the registry before finalizing the results narrative. The owner is the first author; the deadline is week two of January.
Evidence strength note. This is a feasibility trial, so the results provide direct evidence about recruitment and fidelity but indirect evidence about clinical outcomes. The discussion must avoid claiming effectiveness. State the limitation explicitly: the sample was sized for feasibility, not for a between-arm effect on falls, hospitalizations, or medication appropriateness.
Completion criteria. The manuscript is ready when (1) the registry mirrors the primary outcomes, (2) the CONSORT extension for pilot trials is complete, (3) Tables 1–3 match every number in the text, and (4) the discussion confines conclusions to feasibility. If any criterion fails, the project remains revision-active.
How Do You Audit the Evidence Backbone of Each Project?
The evidence backbone is the set of references, datasets, and source records that support the project's claims. A year-end audit asks three questions:
- Can every cited reference be resolved to a durable identifier? A DOI is a persistent identifier that resolves through the DOI system and can remain stable when the location or descriptive metadata of an object changes. Practical translation: if a reference has a DOI, prefer that over a bare URL.
- Does the reference metadata match the actual paper? Title, authors, journal, volume, and year should be checked against a scholarly record, not against the memory of the person who typed the bibliography.
- Are the search and selection processes documented? For reviews, the screening workflow should be reconstructable: databases searched, dates, query strings, deduplication method, and stage-by-stage inclusion counts.
In the pharmacist trial example, the evidence backbone includes the trial registration, the baseline and follow-up data dictionaries, and the references supporting the medication review intervention. A missing data dictionary means the analysis is not reproducible by a colleague, which is an evidence-strength and applicability problem that should be fixed before submission.
Where Do Search and Reference Tools Fit in the Inventory?
Tools are useful when they shorten a concrete step in the audit, not when they are added as a productivity garnish. The WisPaper workflow can support three inventory tasks directly.
First, locate and verify the references. When the reference section of a manuscript has accumulated entries through copy-paste from colleagues and older drafts, the bibliographic list needs a systematic check. You can use WisPaper search to find academic papers through the scholarly search interface and compare the retrieved record with each entry in the manuscript. Where the entry is already in a BibTeX file, TrueCite checks BibTeX against real academic databases to flag hallucinated references. This matters most for references copied from secondary sources or citation generators.
Second, consolidate the working library. An inventory is the moment to convert a folder of unsorted PDFs into a library that mirrors the project register. My Library lets you save or upload papers and organize them in the WisPaper library. One discipline that pays off: create one collection per inventory status, such as Submit-ready, Revision-active, and Archive, so the library reflects the decisions made this week.
Third, resolve evidence questions during revision. When a reviewer or a co-author asks what a set of accepted papers actually reports, Library QA lets you ask questions based on papers uploaded to My Library or added from search results. This is most defensible when the question is narrow: "In the pilot trials included in this library, what follow-up completion rates were reported?" rather than "What should our discussion say?"
Each of these steps supports a named inventory artifact: a verified reference list, an organized library, and answered blocking questions. Use them in that order.
How Should You Organize Projects for the Next Quarter?
The inventory's output determines the first quarter's structure. Assign each project to a lane and make the lane visible.
Lane A: Final push. Projects that passed the submission-readiness checklist need only formatting, a final author read-through, and submission. Give each a target journal or meeting and a submission date.
Lane B: Defined revision. Projects with a named blocking question and an owner. The revision brief should be one paragraph: the problem, the decision needed, and the evidence the decision will call on.
Lane C: Analysis or data work. Projects moving from data-pending to an analyzable result. These belong in a shared analysis plan, not in a manuscript drafts folder.
Lane D: Parked. Projects placed in archive with a dated note. Archive is a legitimate status. It means the project will not consume planning attention until a named trigger (a grant decision, a new dataset, a co-author completing their piece) fires.
A practical governance rule is a two-week review cadence: Lane A and Lane C items get weekly attention, Lane B gets biweekly, and Lane D is reviewed only when the trigger fires.
What Does a Reusable Inventory Checklist Look Like?
Use the checklist below as a shared worksheet. Score each item Yes, No, or Not applicable, and write the evidence or file location in the third column.
| Item | Status | Evidence location |
|---|---|---|
| Project has a one-sentence decision question | ||
| Furthest output artifact is identified and dated | ||
| Last activity date is recorded | ||
| Owner and deadline are assigned | ||
| Primary outcome and analysis are defined | ||
| Study flow or screening flow is documented | ||
| Protocol and registry match the analysis plan | ||
| Reference list is resolved to durable identifiers | ||
| Data dictionary or codebook exists | ||
| Limitations section names applicability and indirectness | ||
| Target journal or meeting is selected | ||
| Submission or revision date is set | ||
| Archive note is written for paused projects |
How Do You Know the Inventory Is Ready?
Completion criteria keep the exercise from becoming a ceremonial year-end reflection. The inventory is ready when all of the following are true:
- Every project that consumed time in the past year appears in the register, including dormant ones.
- Each row has a blocking question or a named decision, not an adverb like "continue."
- Each project's evidence backbone has been audited for reference resolution, dataset documentation, and protocol-registry alignment.
- Submission-readiness claims are supported by a completed checklist, not by team optimism.
- Every manuscript's limitations section distinguishes strength of evidence, applicability to the target population, indirectness of any surrogate or feasibility outcomes, and identifiable limitations.
- The first quarter now has named lanes, owners, and dates.
If a project's next step is still "discuss at the next meeting," the inventory is not done. The point of the exercise is that the next meeting opens with decisions, not with rediscovery.




