You finally submit the manuscript. It took months of analysis, revisions, and coordination, so putting it on your review report feels good. But a rushed summary can turn “four manuscripts at different stages” into “four publications” before you notice the difference.
That small wording change matters. Readers need to know what has actually happened, not just how much work went into it. The book's sample separates submitted, accepted, and published items in its detailed list. Keeping those distinctions clear throughout the narrative makes your record easier to understand and check.
Let the label describe the current stage.
A submitted manuscript has been sent for consideration. Acceptance reflects a different milestone, and publication another. Use your institution's permitted categories and the status supported by the relevant record as of the reporting date.
If a decision requests revisions, describe that stage accurately. Don't treat an invitation to revise as acceptance unless the formal decision actually establishes acceptance. Likewise, a manuscript you're preparing to submit isn't already under review.
These distinctions don't erase effort. They help you explain it honestly. You can describe substantial progress on a project without presenting the hoped-for outcome as completed.
Make the summary match the detailed list.
Suppose, in a fictional example, you have two published articles, one accepted manuscript, and one submitted manuscript. A clear overview reports those stages separately. Calling all four “published articles” would conflict with the details and leave a reviewer wondering which account is accurate.
Check headings, totals, narrative sentences, and the CV together. A detailed entry can be correct while a summary above it quietly overstates the record. This often happens when a sentence survives from an earlier draft while individual entries change.
Be equally clear when reporting several outputs from one project. A presentation, a manuscript, and a grant proposal may be distinct products, but identify each for what it is. Follow the institution's reporting categories rather than combining unlike outputs under an impressive total.
Keep dates and supporting records together.
Maintain the appropriate submission confirmation, decision notice, or publication information in your working archive. Use the records required or permitted for the review, respecting any confidentiality or sharing restrictions. You don't need to attach every email just because you saved it.
When a status changes near the submission deadline, check the rules for updates. There may be a designated reporting cutoff or procedure for adding later information. Don't quietly replace the date with a newer one if the review requires the record as of an earlier point.
The same care helps with grant reporting. A proposal submitted, an award notice received, and project work completed are different stages. Explain the one you can document.
Use precise language without underselling progress.
You can say what you contributed to a submitted study: developed the design, completed analysis, led drafting, or coordinated revisions. Those statements make the work visible while leaving the publication outcome open.
Before your next review, audit every item with a status label. Compare it with the underlying record, then compare the entries with your overview totals. This is a small job with a useful payoff: readers can focus on the substance of your research instead of untangling what the list actually means.
Adapted from The New Faculty Handbook by Zafer Unal, chapter 15, pp. 251–254.
