How to Increase University Publication Capacity Responsibly

Begin with a sentence that connects the intended outcome to the institutional mission. For example: “Enable more research teams to complete credible studies and submit their findings to suitable journals, while improving transparency and participation.” This is an illustrative planning statement. It can accommodate stronger Web of Science or Scopus visibility without making database coverage the only reason to undertake research.

Clarify which outputs matter alongside journal articles. Some departments may also contribute books, datasets, software, policy reports, exhibitions or practice-based work. Identify where these contributions belong in the institution's assessment and support arrangements. CoARA's assessment commitments support qualitative judgement informed by responsible quantitative indicators and recognition of diverse contributions. They are voluntary commitments, not a certification of an institution's research quality.

Translate the mission into decisions. Does the institution need more studies reaching analysis, more faculty participating in collaborative projects, or fewer manuscripts returning repeatedly for unresolved methodological problems? These are different situations. Each requires a different budget and different evidence of progress. A target to increase indexed publications should sit alongside the means of achieving it and explicit expectations about research integrity.

Create a simple project register with a stable project identifier, department, research question, responsible investigator, current stage, next decision and principal obstacle. Keep personal or sensitive research details out of the management view unless they are necessary and appropriately authorised. Link to controlled project records instead of copying raw data into a central tracking sheet.

Use stage definitions that a department can apply consistently. “Analysis under way” should mean more than someone intending to analyse the data. “Ready for internal review” should mean that the draft, supporting results and relevant declarations are available. “Submitted” should refer to a completed journal submission. The exact definitions can vary, but they must be written down before anyone compares progress.

Ask teams to explain stalled projects. A manuscript may be waiting for co-author input, a design decision, data access, a laboratory result or an affordable publication route. Record a reason and a proposed next action. Avoid treating all delays as a writing problem. Where the institution lacks reliable starting information, a research-performance audit can establish a baseline before a wider programme is designed.

A publication pipeline needs useful decision points rather than continuous pressure to move every project forward. At the design stage, check that the question, study approach, feasibility and necessary approvals align. Before analysis, confirm that the data and documentation can support the intended questions. Before drafting, establish the main findings and their limitations. Before submission, assess journal fit and the completeness of the manuscript package.

These checks should help teams decide whether to proceed, revise the plan, seek specialist input or pause a project. A well-founded decision to stop an unsuitable analysis is not automatically a failure of the programme. It may prevent further investment in a claim that the available evidence cannot support.

Choose the smallest practical evidence requirement for each stage. A design decision may need a two-page study brief and focused review. A complex analysis may require a protocol, code, data dictionary and specialist discussion. Applying the same checklist to every discipline can create unnecessary work while overlooking the issues that matter. Departmental representatives should help define the checks and test them on real projects before wider adoption.

Build a service menu around problems, with clear entry requirements and outputs. A methods clinic can resolve a specific design choice. A writing group can help researchers develop arguments and maintain progress. A statistical consultation can assess the suitability of an analysis. An editorial review can improve the communication of work whose evidence is already available. These activities are complementary, but they are not interchangeable.

Consider three levels of support. Open workshops can address common needs across a faculty. Small-group sessions can work through related projects with sufficient time for discussion. Individual project support can address specialised or consequential decisions. This is a proposed planning structure; the appropriate mix depends on demand, expertise and resources.

Allocate faculty time as deliberately as external expenditure. A writing workshop followed by no opportunity to write may generate attendance records without useful drafts. A mentor who is already overloaded may become another queue. Define what the researcher prepares, what the mentor reviews and which decisions need another specialist. Publication-capacity development can connect these support choices to a coordinated institutional workplan.

Consider an illustrative faculty register containing 40 projects. Twelve are still refining their questions, eight have data but unresolved analysis decisions, ten have partial drafts, six are preparing a first submission and four are revising after review. These are synthetic demonstration figures, not a benchmark or a client result.

An institution might initially request a workshop for all 40 teams. The register suggests a more specific response. The eight analysis-stage projects need an initial methods discussion before editing can be scoped. The ten partial drafts need a check on whether results and author inputs are complete. The six submission-stage projects need journal-fit and readiness checks. The four revision projects need comment-by-comment planning against the editor's actual decision.

The allocation should remain provisional until the projects are reviewed. A draft labelled “almost complete” may contain an unresolved design issue, while a project apparently at an early stage may already have strong material. The purpose of the register is to locate the right conversation, not to judge a study from a status label.

Review what the institution rewards in practice. If every reward depends on a publication appearing before a fixed date, teams may favour work with shorter production cycles even when longer projects matter more to the institution. An alternative is to recognise defined contributions at several stages, while retaining scrutiny of the resulting work.

Examples include completing a well-reviewed protocol, contributing reusable documentation, leading a constructive internal review or developing a genuine cross-department collaboration. The institution must decide which contributions warrant recognition and how evidence will be checked. Avoid creating a new points system before understanding how staff may respond to it.

Budget decisions also need transparency. State how projects become eligible for methods support, editing assistance or publication-charge funding. Separate eligibility from automatic entitlement. A fair process should explain priorities, disclose relevant conflicts and provide a route for questions. For journal charges, check the actual publication model and the funder's requirements; consultancy and publisher charges should not be blended into an unexplained “publication fee”.

Use a compact set of indicators with definitions, owners and review dates. Process measures can show whether support is being used and whether projects reach agreed decision points. Outcome measures can describe submissions, decisions and eventual publications. Context measures help explain changes in staff, departmental composition, resources or database coverage.

For a readiness measure, define the denominator. “Projects passing internal review” is difficult to interpret without knowing which projects were eligible, how many were reviewed and what “passing” means. Record whether a review found substantial unresolved issues. Do not improve the indicator by quietly weakening the review or excluding difficult projects.

For publication measures, retain the source, extraction date, document types and coverage rules. Compare disciplines carefully and avoid treating a short-term change as proof of programme impact. Bibliometrics and research-impact analysis can support interpretation, but the management discussion must also consider what the research contributes and what alternative explanations remain.

Include participation measures that reveal concentration. A rise in output from a small established group may coexist with limited support for the wider faculty. Track who can access the programme, whether different career stages are represented and which departments still have unmet needs. Use aggregated reporting where possible, and explain to participants how the information will inform decisions.

An illustrative first cycle can start with agreement on scope and a manageable set of departments. Establish the register, examine a sample of project records and speak with researchers and support staff. Produce a short list of obstacles with evidence, likely causes, ownership and possible remedies. Do not begin with a university-wide software procurement if the basic problem is an unclear handover between two existing teams.

Choose a limited pilot that can produce observable outputs. For example, test an analysis-support referral process on a defined set of projects, or introduce an internal manuscript review form in one faculty. Agree how participants will report difficulties. The pilot should reveal the work required to maintain the process, including coordination and specialist review time.

At the review point, distinguish implementation from results. Did the referral route operate? Were the planned reviews completed? Which decisions became clearer? Are the expected longer-term outcomes still plausible? Decide whether to continue, alter or stop the intervention. This creates an accountable improvement process without pretending that a short pilot can establish its eventual effect on publication output.

Before commissioning a programme, assemble the information needed for a useful discussion: the institutional objective, participating departments, available project records, known support gaps, decision-making responsibilities and any fixed constraints. An initial brief can describe these points without uploading manuscripts, datasets or personal performance files.

Ask a prospective provider to explain the proposed outputs, the expertise needed, the client's contribution, review stages and how additional work would be agreed. Clarify ownership of project materials, confidentiality arrangements and handover expectations before sharing restricted information. The scope should make clear which elements are advisory and which involve work on individual projects.

The research-performance self-assessment offers a practical starting record. Where coordinated delivery across the year is appropriate, the University Research Performance Programme describes a combined structure. The useful next step is to choose the problem the institution is ready to address, identify the evidence available, and define what a successful first stage would deliver.