Evidence before ornament
Impact Liaison is being built around the real operational pain of evidencing impact, not around generic dashboard features.
About Impact Liaison
A small internal platform for teams that have to prove real-world research impact.
The site is being shaped around the operational work of impacts teams: gathering evidence, tracing influence, and exporting clean records for downstream reporting.
Minimal runtime, serious workflow
The code stays small and understandable while the workflow still handles the messy realities of institutional impact evidence.
Internal-first release
The first module is designed for authenticated staff use, not broad public traffic.
Modular growth
The publications tool is the first module, with room for future internal tools once the pilot hardens.
Why start with publications
Publication retrieval is a clean first internal module because it touches author identity, time windows, deduplication, evidence exports, and the practical handoff into impact reporting processes.
Why the app is authenticated
This first release is for internal team use. The workflow is more useful when it can hold selected authors, retrieved rows, and export-ready previews in a secure workspace instead of exposing the tool as a public utility.
Why the code stays minimal
The runtime is intentionally small so the product can move quickly while still keeping logic explicit: routes, auth, OpenAlex retrieval, and CSV export all remain inspectable without framework-heavy indirection.