Give staff one place for project records, purchase and travel requests, approvals and progress reports. Keep each request with its research and funding context, so the next decision does not get lost in email.
PROJECT / WORK IN PROGRESSAwarded project Delivery overview
Project foundationConfirmed
Purchase requestIn review
Quarterly updateNext report
Activities, decisions, and reports connected
SCINDU / UNIVERSITY PLATFORMProjects & reportingILLUSTRATIVE PRODUCT VIEW / 05
FREE FOR UNIVERSITIES / SOFTWARE + IMPLEMENTATIONWhy it’s free
WHY YOUR TEAM WOULD USE IT
Know who needs to do what before the next report is due.
A funded project brings purchases, travel, publications, approvals, and reporting. Connect these processes to the project so its history doesn’t disappear across forms and inboxes.
THE PLATFORM AT WORK
Start with a real task.
Follow the people, decisions and records from the first input to a useful result.
CHOOSE A USE CASE
Illustrative workflows. Content, access and rollout are agreed with your institution.
AN EXAMPLE FROM THE UNIVERSITY OFFER
Prepare a quarterly research update
A reporting deadline arrives while work is still underway. Keep the progress account, source context and reviewer decision with the project lifecycle.
Project lead · institutional reviewer
START WITH
Project progress, completed work, issues and relevant output references
WHO ACTS / 01
Project lead
Open the project and linked grant workflow. Review the reporting period, research activities and outputs so the update reflects the work that actually happened.
THIS STEP PRODUCES
The evidence and context needed to write the update.
PROJECT / REPORTING CONTEXT
Reporting period open
Project
Recyclable composites research
Context
Linked award and prior decisions
Material
Progress, issues and output references
EXAMPLE RECORD01 / 03
Next owner: Project lead
WHAT YOU LEAVE WITH
A reviewed periodic update retained in the project lifecycle
Researchers author and review the report. Automatically assembled evidence-backed report packs are a planned addition, not the current reporting workflow.
Carry a reviewed award into the existing institutional project record. Keep its funder, project relationships, and related grant accessible to authorised people.
Project description, stage, and people
Permission-aware grant connection
Internal project before public publication
02
Planned work and responsibilities
Bring planned research activity and supporting tasks into the institution’s workspace. Make the next action and the person responsible visible.
Planned research activities
Owners, status, and next steps
Task-focused action and waiting lanes
03
Purchases connected to the work
Prepare a purchase request with its specification, justification, funding source, and attachments. Retain the review decision and the next administrative step.
Structured purchase requests
Funding-source references
Review and request history
04
Travel with a useful plan
Connect research travel to its purpose, itinerary, costs, funding sources, and approvals. Keep a readable summary available to the people reviewing it.
Trip and conference planning
Cost lines and funding sources
Institutional travel approval
05
Publications and outputs
Link publication planning and the actual approved output to the research. Public publication remains an explicit editorial decision.
Draft and planned publication context
Authors, groups, and project links
Approved public research outputs
06
Reporting with continuity
Keep quarterly reports and final review in the grant lifecycle, with the project connection and decision trail available as the work develops.
Quarterly reporting stages
Progress and final review
Persistent workflow and decision history
↗
THE RESULT WE’RE WORKING TOWARDS
Less context to reconstruct when the next decision or report is due.
WHAT COMES NEXT
The next capabilities.
Proposed additions to the roadmap. These are planned, rather than current features.
PLANNED / 01
Evidence-backed reporting packs
Assemble editable report drafts from approved progress updates, publications, and activity records, with links back to the evidence.
PLANNED / 02
Budget and effort planning
Connect project allocations, partner contributions, commitments, and effort estimates beyond the existing funding-source register.
PLANNED / 03
Research-office portfolio
A permissioned view across project milestones, reporting deadlines, and stalled approvals for the teams overseeing delivery.
START WITH A USEFUL SCOPE
Start with your institution.
Software and implementation are free for universities. We agree the rollout, institutional responsibilities, and research-data scope before onboarding.
01 / MAP
Start with the actual work.
Review your current content, people, processes, and institutional structure.
02 / IMPLEMENT
Connect the right foundation.
Configure the identity, records, access, and workflows agreed for your unit.
03 / EXPAND
Let the useful connections grow.
Introduce the next processes and units once the initial scope is working.