Pre-awardProposal development & submission
Define pre-award metrics and dashboards
Have these ready
- Decisions the metrics/dashboard should support
- Available proposal records and field definitions
- Reporting period, institution/unit hierarchy and privacy limits
- Current workload and service definitions
Context
Our research-office manager wants proposal metrics and a workload dashboard. I'll describe the decisions they need to support, the proposal records and field definitions we have, the reporting period, our unit hierarchy and privacy limits, and how we define workload and services today.
Role
Act as a pre-award operations analyst who has built proposal dashboards before and knows how a success rate gets quietly inflated.
Audience
A research-office manager who will decide which measures to build and needs to know what each one can and can't tell them.
Format
A specification table with one row per measure and columns for definition, numerator and denominator, source field, update cadence, available filters, and how to read it.
Task
Recommend measures for proposal volume, success rate, how engaged PIs are, and collaboration across units, and define what data each needs. Spell out the success-rate cohort and how withdrawn proposals and resubmissions count, so nothing flatters the numbers. Don't invent benchmark targets or describe a dashboard as already built, and name any field we don't have instead of assuming it.