Project management
EU project management: a first-100-days checklist for coordinators
6 min read · Updated 28 August 2026
The grant is signed and the celebration is over. What happens in the first hundred days determines whether the project runs on rails or on adrenaline. This checklist covers the operational basics for coordinators, especially first-time ones.
Set up governance before the kick-off
- Confirm the bodies defined in the consortium agreement — general assembly, executive board, WP leaders — and name real people with deputies.
- Agree a meeting rhythm: monthly WP calls, quarterly board, annual plenary. Put dates in calendars for the full year now.
- Define one written decision log. Decisions in chat threads are decisions nobody can find at review time.
Financial discipline from month one
- Brief every partner's finance contact on eligible cost rules and the personnel cost calculation before they book time.
- Require timesheets or an equivalent reliable record from the start; retrofitting them for an audit is not possible.
- Track budget consumption against effort consumption. Spending 40% of budget for 15% of person-months is an early warning, not a rounding issue.
- Keep procurement and subcontracting documentation as you go — best value for money must be demonstrable.
Reporting rhythm
- Map all deliverables and milestones into a shared calendar with internal deadlines two to four weeks before the official ones.
- Assign a reviewer for every deliverable who is not its author.
- Prepare periodic reports continuously — collect partner input quarterly rather than in a panic before the period closes.
- Log deviations as they happen with justification. Explained deviations are normal; unexplained ones are findings.
Risk and quality
- Maintain the risk register from the proposal as a live document with owners and review dates.
- Watch for the standard failure modes: a silent partner, a dependency slipping in an early WP, and unresolved data access for pilots.
- Escalate early. A three-month slip raised at month six is manageable; the same slip raised at the review is not.
Amendments and changes
- Know which changes require a formal amendment — budget transfers beyond thresholds, partner changes, duration extensions — and which only need reporting.
- Start amendment discussions well before the change takes effect; approval takes time.
Habits that pay off at the review
- One structured document repository with a naming convention agreed on day one.
- A single up-to-date public-facing project summary that partners can reuse.
- Evidence collected alongside indicators, not reconstructed afterwards.
- A rehearsal before each project review, with the project officer's likely questions written out.
Frequently asked questions
- How much effort should coordination take?
- For a mid-size collaborative project, budgeting the equivalent of a part-time dedicated project manager across the duration is realistic. Under-resourcing coordination is a common and expensive mistake.
- What triggers an audit?
- Audits can be random or risk-based. The practical defence is consistent record-keeping: time records, cost documentation, and traceable procurement.
- Can a partner leave mid-project?
- Yes, through an amendment. The consortium agreement should define the process, the handover of results, and how remaining tasks are redistributed.