Startup Appendix D: Frequently Asked Questions
This FAQ is intended to clarify how the policy is applied in practice, including the role of department and college judgment, discipline-specific variation, and the process for supplements, appeals, and exceptions.
Eligibility
All newly hired tenure-track assistant professors, associate professors, and full professors are eligible, provided the position is listed on the approved Biannual Hiring Plan and carries documented expectations for research or scholarship activity. Currently tenured Kansas State University faculty, non-research-engaged teaching positions, and positions without documented scholarly activity expectations are ineligible.
Faculty relocating an existing research program to Kansas State University may receive a reduced startup package, typically reflecting equipment, infrastructure, or other resources already available. In such cases, startup discussions should focus on transition costs, facility modifications, and time-limited staffing or research support needed to reestablish the program.
The primary department leads the startup discussion, while the secondary appointment is considered in determining the overall package. Shared equipment, infrastructure, and other startup needs should be coordinated across participating units to avoid duplication and to reflect the faculty member’s actual research responsibilities.
Funding Calculation
The startup package is calculated using the Faculty Research Startup Package Allocation Rubric through a two-step process: first, a base allocation is identified by academic rank and research field; second, the base is adjusted using the policy’s identified factors, including prior experience, grantsmanship, field infrastructure needs, strategic fit, and research effort. The rubric is intended to provide a consistent starting framework while allowing documented justification for circumstances addressed through supplements, appeals, or approved exceptions.
Startup Package = Base Allocation × Experience Multiplier × Grantsmanship Multiplier × Infrastructure Scaling × Strategic Modifier × Research Effort Adjustment
|
Rank |
S/T/E/V Fields |
Applied Ag Sciences |
Non-STEV/Social Sciences |
Humanities/Arts/Design |
|
Assistant Professor (Base) |
$250,000–$350,000 |
$200,000–$300,000 |
$75,000–$100,000 |
$10,000 (fixed) |
|
Assistant Professor (Max) |
$600,000 |
$400,000 |
$150,000 |
$10,000 |
|
Associate/Full Professor (Base) |
$200,000–$300,000 |
$180,000–$280,000 |
$75,000–$125,000 |
$10,000 (fixed) |
|
Associate/Full Professor (Max) |
$800,000 |
$500,000 |
$200,000 |
$10,000 |
No standard startup allocation may exceed the maximum threshold for the candidate’s rank and field under the rubric. If documented needs exceed the standard cap, departments and colleges may request supplemental support, an approved exception, or other non-startup institutional research support through the applicable review process.
The rubric identifies a fixed standard amount for Humanities, Arts, and Design, but departments and colleges may document field-specific needs that warrant supplemental support or an exception request. Examples may include course release, summer salary, travel to archives, fieldwork, performance or studio materials, or other discipline-specific research infrastructure needs.
Yes. Colleges may supplement startup packages with college-level funds, independent of the OVPR, provided the supplement is documented in the offer letter and managed in accordance with applicable university policy. College or department supplements may be used to address documented market competition, disciplinary norms, shared infrastructure, or other recruitment needs not fully captured in the standard allocation.
Process and Approvals
The anticipated startup range is identified during the Job Requisition stage in PageUp before the position is posted, and the itemized budget is finalized during the offer stage. The final documentation should reflect the candidate’s research plan, justified budget categories, and any approved supplements or special conditions.
The requisition is routed back to the Department Head for discussion and revision before the position can be posted. This step is intended to clarify the proposed range, the research justification, and any concerns about policy alignment or available funds.
The Department Head and Dean develop and justify the proposed package based on the candidate’s research plan, disciplinary expectations, and recruitment circumstances. OVPR provides final approval to confirm consistency with policy, funding parameters, and institutional stewardship requirements; for designated or state-supported funding models, additional approvals may also be required.
The rubric is the standard framework for startup planning and negotiation, but documented adjustments may be considered through approved supplements, appeals, or exceptions. These may be appropriate when justified by disciplinary practice, documented market competition, unusual infrastructure needs, strategic recruitment circumstances, or other factors not adequately captured in the initial rubric calculation.
Department Heads and Deans play a central role in identifying disciplinary norms, candidate-specific research needs, unit priorities, and competitive market conditions. The OVPR review is intended to promote consistency and fiscal stewardship, but department and college leadership provide the primary discipline-specific context for justifying the proposed package.
Strategic fit should be informed by both institutional priorities and documented department- and college-level research strategy. Departments and colleges may provide written justification describing how a hire advances disciplinary strength, existing areas of excellence, interdisciplinary opportunities, or other unit priorities, and that justification should be considered in the review process.
Account Management and Spending
The startup account is established after the faculty member is hired and the offer is accepted. Spending may begin only after the appointment’s effective date unless a separate institutional process explicitly authorizes an exception in advance.
As a general rule, startup funds may not be spent before the effective appointment date. However, departments may request advance coordination or an approved exception when early action is necessary for time-sensitive needs, such as ordering equipment, preparing for compliance, setting up labs, or recruiting research personnel.
The initial deposit occurs on the hire date. Subsequent annual deposits occur on either July 1 or January 1, depending on the faculty member’s start date and the funding schedule described in the policy.
Unspent funds may carry forward within the account during the standard three-year funding period. Any balance remaining at the end of that period is normally returned to the OVPR-managed startup pool unless a no-cost extension is approved, 6 months in advance of the end date.
Yes, startup funds may carry forward during the standard three-year period, and a one-year no-cost extension may be approved in exceptional circumstances. Extension requests must be submitted 6 months before the end of the startup funding period (Year 3) and must clearly explain why the research timeline must be extended. Examples of circumstances that may warrant a no-cost extension include (1) a delay in graduate student recruitment or disrupted graduate program support, (2) field seasons, (3) delays in critical equipment purchase or installation taking more than 6 months, or other discipline-specific research constraints.
In general, transfers out of the startup account to other college, department, faculty, or research unit accounts are not permitted. Transfers to construction accounts for approved renovation or buildout projects are allowed, provided they are consistent with the policy.
Yes, but equipment purchases exceeding $10,000 require prior approval under the current policy and will be tagged as VPR assets. Requests should be supported by clear research justification, a long-term equipment maintenance plan, and be connected to the approved startup plan or an authorized revision to that plan.
Moving expenses are not part of the standard list of allowable startup expenditures under this policy. When moving support is important for recruitment, it should be addressed through other institutional recruitment mechanisms or, if permitted by university policy, through a separately approved exception.
Spousal accommodations are not part of the standard startup package under this policy. Because spousal accommodation can materially affect recruitment, any such arrangement should be handled through separate institutional hiring or recruitment processes rather than through the standard startup account.
No. Summer salary for periods before the faculty member’s effective start date is not an allowable startup expense under the policy.
OVPR should be notified promptly upon notice of resignation or departure. The startup account is then frozen, and any remaining balance is returned to the OVPR-managed startup pool in accordance with the policy.
Performance and Accountability
Yes. Faculty are expected to submit annual progress reports that address spending, research development, scholarly output, grant activity, and student training or mentorship. These reports are intended to provide accountability while recognizing that research progress unfolds differently across disciplines and methods.
No. The policy states that benchmarks are guidelines and that discipline-specific patterns are considered in evaluation. Timelines should account for differences across fields, including laboratory setup, assay validation, field seasons, archival access, cohort development, regulatory approvals, and normal variations in publication and grant cycles.
The review should consider the nature of the research program and whether the faculty member is making reasonable progress toward establishing a sustainable and competitive research trajectory. Delayed outputs do not, by themselves, indicate inadequate performance when the timeline is consistent with the discipline, methodology, or approved research plan.
If research milestones, publications, funding goals, or responsible spending expectations are not being met, the Dean, Department Head, and OVPR may require an accountability plan or other corrective action. Reviews should consider both documented progress and the disciplinary context before determining whether additional restrictions are warranted.
Spending targets are intended as planning guidelines rather than automatic compliance triggers. If spending is behind schedule, the department, faculty member, college, and OVPR should review whether the slower pace is justified by the approved research plan, procurement delays, field timelines, or other legitimate startup considerations.
Appeals and Exceptions
Yes. Written appeals may be submitted through the Dean when documented discipline-specific practices suggest underfunding, when significant strategic or recruitment circumstances arise, or when unforeseen research infrastructure needs are identified. The appeal should explain the basis for the request and provide supporting evidence relevant to the candidate, field, and market context.
Examples may include unusual infrastructure requirements, documented peer-market competition, shared facility costs, strategic cluster hires, highly distinguished recruits, or other research needs not fully reflected in the initial rubric calculation. As provided in the policy, exceptions require documented institutional justification and appropriate approvals.
Yes, but any deviation from standard procedures, such as deposit timing or account-use restrictions, requires prior written approval through the applicable review process. Requests must be submitted before the exception is needed, because retroactive exceptions are not permitted under the policy.
Non-startup research support refers to other approved institutional, college, or unit resources that may be provided outside the formal startup allocation structure. When such support is discussed during recruitment, its source, amount, intended use, approval path, and timing should be clearly identified in writing so all parties understand what is and is not part of the startup package.