This example is a working template
The example uses only fictional project data. It is not an issued document, invoice or confirmed client approval. Copy the structure into your project and adapt it to the agreed services.
Example project: Nordlicht Relaunch. Service period: 7–11 September 2026. Version: 01. Review status: prepared for professional review. Responsible role: project lead. Enter a real name or approval only after the corresponding action occurs.
Service items
| Date | Activity | Duration | Hours | Net |
|---|---|---|---|---|
| 7 September 2026 | Tested mobile navigation with keyboard controls | 60 minutes | 1.00 | €120.00 |
| 9 September 2026 | Corrected agreed views after review | 30 minutes | 0.50 | €60.00 |
| Total | Two selected activities | 90 minutes | 1.50 | €180.00 |
The calculation stays visible
60 minutes divided by 60 is one hour; 30 minutes divided by 60 is 0.5 hours. Total: 1.5 hours. At the example rate of €120, this gives €180 net. This template includes no tax calculation and is not a complete invoice.
Another 20 minutes of internal handover are not selected for billing in this scenario. Total recorded effort is 110 minutes, while this record's service basis is 90 minutes. Both figures are correct but answer different questions.
Complete before use
Agreement
Replace project, period, billing model and any agreed rate with the actual details.
Activities
Make descriptions specific enough for the recipient to identify the work. Do not copy confidential internal notes without review.
Review
Have the responsible person review duration, selection and description. Enter name and review date only after review has occurred.
Use
When the record feeds an invoice draft, document the version used and its link to the draft.
How to incorporate the template into your process
Copy the table and header details into your project document. This page's print view reduces navigation and controls but does not create a signed or legally reviewed record. Check all fictional details before sharing.
When correcting, identify the changed item. Create a traceable new version rather than silently replacing one already shared. Test separately whether your application logs versions and approvals.
From the guide to the sample project.
Try the steps in the OOKI demo: tasks, client view, time entries and invoice draft with fictional data. No login required.
Try the demo (DE)