A quick guide to the reporting workflow.

Quick Update

Record a dated project fact close to when it happens. Connect it to the relevant activity and organisation so EURtracker can preserve useful reporting context over time.

Progress

Review the material that will become Project Memory. This is the human checkpoint between raw project notes and reporting-ready evidence.

Readiness

Check expected partner and activity coverage. Missing reporting material should stay visible rather than being filled automatically with assumptions.

Reports

Generate a Partner Report or Project Report pack from reviewed and submitted material. Edit the narrative where needed and keep within configured character limits.

Professional DOCX

Download a structured Word handoff with report context, narrative answers and source traceability. A ready/preliminary status helps distinguish complete coverage from a report that still has gaps.

Send feedback from the workspace

Authenticated users can send a bug report, improvement idea or question. EURtracker automatically attaches the current page, user role and app version while keeping feedback separate from formal reporting data.

Restart the in-app tour

Project Leaders and Project Partners receive different guided walkthroughs. The tour can be dismissed at any time and restarted here whenever the user wants a refresher.

If something does not look right

• Confirm you are using app.eurtracker.com for normal sign-in.
• Check the active project, organisation and reporting period.
• Review Progress before expecting new Quick Updates to appear in reporting.
• If a report shows missing coverage, return to Readiness and identify the outstanding partner/activity.
• For a reproducible problem, use Feedback and describe what happened and what you expected. Never include passwords or secrets.