Research development programme
Faculty Publication Development Programme
Give a faculty cohort a structured route from research work to well-prepared manuscripts. The Faculty Publication Development Programme can combine project assessment, methods support, writing development and internal review, with each research team working towards defined and realistic preparation milestones.
The programme is intended for faculties and departments that want to strengthen publication capability across a group of researchers. It can support a healthier flow of research into manuscripts while retaining responsibility for genuine scholarship, accurate reporting and appropriate journal selection.
On this page 9 sections
01
Address the reasons manuscripts are not moving forward
A faculty may have useful studies that remain unfinished because researchers need different kinds of support. One team may need to clarify the analysis; another may have results but no coherent manuscript structure; a third may be repeatedly submitting to journals that do not fit its work. Treating every project as a language-editing task would miss those differences.
The programme can begin with a structured assessment of the participating projects and the faculty's existing support. It should identify the barriers that can be addressed within the engagement and those that require institutional decisions, further data collection or specialist work outside the initial scope.
This programme is distinct from a university-wide strategy exercise. It concentrates on a defined cohort and its projects. Broader institutional priorities can be addressed through publication-capacity development or the University Research Performance Programme.
02
Select a cohort and establish project readiness
Participation should be based on a transparent purpose and realistic readiness criteria. The institution may choose a group with completed data collection, a disciplinary cluster or a cohort of researchers developing their first papers. The selection should consider access to source material, available author time, supervisor or team support and the type of assistance required.
An initial project profile can record the research question, design, data status, analysis status, manuscript stage, author roles and intended audience. It should distinguish a completed study from an idea that still requires research. The programme can then propose an appropriate route for each project rather than assign every participant the same deadline.
The institution should also decide how projects are prioritised if demand exceeds the agreed capacity. Transparent criteria reduce confusion about who receives individual support and how training activities relate to the wider cohort. Participation should not be treated as a promise of publication or an entitlement to unspecified services.
03
Build a development plan for each project
A project plan can identify the next meaningful decisions, the support required, author responsibilities and review points. A methods issue may need resolution before substantial writing begins. A manuscript with a clear analysis may move directly to structure, reporting and journal fit. A project with incomplete records may need a preparation stage before either route is feasible.
The programme can combine research design, statistical consulting or qualitative support with manuscript development where the scope and specialist capacity permit. These are defined work packages, not an assumption that every participant receives the full service catalogue.
Each plan should make dependencies visible. Authors may need to clarify collection procedures, retrieve source files, resolve contribution questions or obtain institutional permissions. A milestone should reflect the completion of that work, not merely the passage of time since a session was delivered.
04
Combine cohort learning with focused project support
Shared learning can address common needs in structure, reporting, journal selection and responding to peer review. Academic writing workshops can give participants practical methods they use across several papers. Focused support can then address the specific difficulties identified in individual project plans.
The balance should be explicit. A cohort workshop may include selected passages and group exercises, while a manuscript-development task may involve detailed work on one paper. The proposal should identify the amount of individual feedback and the boundaries of any editorial or analytical support.
Researchers need time to apply the learning. The programme can include author work between review points, with supervisors or departmental leads helping maintain progress. The aim is to leave participants better able to prepare and review future manuscripts, alongside the specific outputs commissioned for the current cohort.
05
Review manuscripts and make informed submission decisions
An internal review stage can examine whether the manuscript explains the research clearly, reports methods and results consistently, addresses important limitations and provides the information the intended journal requires. Review criteria should reflect the study type and the level of assessment actually included.
A preparation decision may identify a paper as ready for journal selection, ready after defined revisions or in need of further research work. These categories should be meaningful and documented. An internal readiness decision is not a prediction of acceptance and should not be presented as a journal-quality certification.
Illustrative deliverable: a cohort progress record
For a hypothetical faculty cohort, a progress record could include the project identifier, current stage, main unresolved issue, next author action, support task, responsible person and review date. One project might be awaiting a verified analysis table; another might be revising its introduction; a third might be comparing suitable journals.
The record would show the reason for each status and distinguish a manuscript prepared from one actually submitted or accepted. It would contain only the information needed for programme management, with appropriate access arrangements. This is an illustrative template, not a record of Outlier Science clients or publication results.
06
Outputs and a balanced account of progress
Depending on scope, programme outputs can include cohort and project assessments, individual development plans, workshop materials, analysis or editorial deliverables, internal review records and submission-preparation packages. A summary can identify recurring barriers and recommendations for the faculty's future support model.
Progress measures should capture both completed work and capability development. They might examine readiness reviews completed, author actions resolved, documented methods, use of internal review or participant work that demonstrates learning. Manuscript submissions and later editorial decisions can also be recorded where relevant, with their dates and meanings kept distinct.
No universal publication target should be imposed without considering discipline, study maturity and the time needed for research. A programme cannot guarantee a number of accepted or indexed papers. It can provide a transparent account of the support delivered, the preparation achieved and the issues that remain.
07
Faculty and author responsibilities
The institution should provide a sponsor, a cohort coordinator and a process for selecting participants. Departmental or project leads need to support author participation and resolve institutional dependencies. Researchers provide accurate study materials, engage with feedback and approve the final account of their work.
Authorship and acknowledgement should follow genuine contributions and applicable rules. The programme does not supply papers for people to claim as their own or create research findings to meet a publication target. Research integrity is part of the programme's design and the way progress is described.
Confidentiality arrangements should cover manuscript circulation, access to project records and the use of examples in group sessions. Participant material should not automatically become teaching content. The institution and research teams need to identify what can be shared and who is authorised to see it.
08
Scope, timetable and engagement model
The quotation depends on cohort size, project readiness, disciplinary range, methodological needs, workshop design and the depth of individual support. A faculty with complete studies and mature drafts needs a different programme from one whose projects still require extensive design or analysis work.
A proposed schedule can be organised around assessment, project planning, development, internal review and submission preparation. Durations should be agreed after the projects are understood. The timetable should include author work and institutional review rather than allocate all time to external support.
The agreement should specify manuscript numbers or another clear capacity basis, revision rounds, included decision stages and treatment of additional projects. Journal fees, new data collection and specialist work outside the agreed scope should be identified separately. Later peer-review response support can be included or commissioned as a further stage.
09
Faculty programme questions
Can the programme help increase Scopus or Web of Science publications?
It can strengthen the research preparation and support processes that contribute to suitable submissions, including current journal-coverage checks where required. Acceptance and indexing remain external decisions. Progress should be measured through the actual preparation, submissions and later outcomes, without promising a fixed increase.
Can researchers with unfinished studies join?
They can be considered if the programme includes a suitable planning or development route. Their milestones should reflect the research still needed. A project that lacks data or essential approvals should not be treated as a manuscript ready for rapid submission.
Is language editing included for every participant?
Only where the programme scope provides for it. Some projects may need methods support first, while others need structural work or a focused edit. The assessment and proposal should explain how support is allocated across the cohort.
How are supervisors and co-authors involved?
The project plan can identify review responsibilities and decisions requiring the author team. Supervisors or project leads remain responsible for their institutional roles. External support should help coordinate a clear process without replacing scientific ownership or author approval.
Can the programme begin with a pilot cohort?
A pilot can test participant selection, support needs and review processes before wider adoption. Its purpose and evaluation should be agreed in advance. Findings should inform the next phase without assuming that one cohort represents the needs of the entire university.
What happens after submission?
The programme agreement should state whether the engagement ends at preparation, includes submission assistance or covers a defined review round. Editorial timelines vary and should not create an implied unlimited commitment. Further support can be scoped when the journal's decision and requirements are known.
Describe the faculty, likely cohort and current manuscript stages to discuss a faculty publication programme.