Two Subjects, Two Files, Planning MOTS-c and NAD+ Evidence Reviews
One shared folder of papers makes two different subjects look comparable. A two-file log keeps each question, its sources and its limits clearly separate.

A shared folder of papers on MOTS-c and NAD+ makes the two look more comparable than the evidence allows. If you are planning a MOTS-c and NAD+ evidence review, the cleaner approach is two separate files, each built around the question it is meant to answer, plus a short cover note saying how, or whether, they connect.
This article is about mechanics: how to set up the log, what to record against each source, and where to keep product paperwork so it does not leak into the literature notes. The method works whether you end up buying one material, both or neither.
Why one pile of papers misleads
Both subjects turn up in discussions that use similar vocabulary, and that overlap invites grouping. But a molecular definition, a laboratory observation and a proposed outcome are different kinds of evidence, and they answer different questions. Put them under one heading and they begin to read as a single body of support.
Start by writing the question for each material separately, as a sentence. "What is MOTS-c, according to the primary literature?" and "What is NAD+, and where does it appear in our project?" are both questions about definition. A question about outcome belongs in a different file entirely, if it belongs anywhere in this review at all.
Set up the log
Give each subject its own table or spreadsheet with the same fields:
- Source, and the date you read it
- Subject (MOTS-c or NAD+)
- Material studied
- Model or setting
- What was measured
- Whether it is preclinical, involves people, or is a reference entry
- One sentence on why it belongs in the file
- One sentence on what it cannot tell you
Identical columns in both files make a later comparison fair, because you can see exactly where the evidence is thin on each side. They also stop context being stripped away, which is how a narrow laboratory observation ends up sounding like a broad conclusion.
Write the relevance sentence
A short explanation of why a paper is in the file is worth more than another citation. Two examples of the kind of line that works:
- "Describes MOTS-c as a peptide. Gives no information about any supplier's batch."
- "Reference entry describing NAD+ as a coenzyme. Background only, with no comparison to MOTS-c."
Someone picking up the file in six months can read those and know what each source is for without re-running your search.
Keep supply documents in their own section
Papers explain why a question matters. They cannot confirm what a particular product contains. A batch report does the opposite: it describes a tested sample and says nothing about biology. Mixing the two is how an unverified assumption ends up looking like a finding.
Give product records their own part of the file, pointing at the relevant listing, such as MOTS-c 10mg or NAD+ 1000mg. Where a report is published on the Certificates of Analysis page, note the batch number on your label next to it. Not every product or batch has a report, so "none found" is a legitimate entry and worth recording.
Decide what is out of scope, and say so
A team might limit its reading to material identity and park outcome questions for later. That is a reasonable boundary as long as it is written down. One line in the cover note, such as "outcome literature not reviewed", stops a colleague assuming the folder is more complete than it is.
The final hand-over note should state the questions, the sources used for each, the limitations that remain and what would change your conclusion. Sometimes the right recommendation is a narrower review rather than more purchasing. Because everything CLOVA supplies is for laboratory research use only, any purchase should follow from a research question your team has already written down.
Frequently asked questions
Can both subjects share one bibliography?
They can share a reference manager, but keep the summaries separate. The cover note is the place to describe any overlap, and it should say why the overlap does or does not matter to your project.
How many sources are enough?
There is no magic number. A review is enough when each question has its sources and its limits written down, and a colleague can see at a glance what is missing.
When should purchasing get involved?
Once the questions are settled. At that point you know which listing, if any, to ask about and which document you need to see, which makes the enquiry much shorter.


