Skip to content
Worklog· an app for Microsoft 365

Worklog: Every hour worked ends up on an invoice.
Without chasing timesheets.

People log their hours, the project manager approves them and accounting gets the billing input in one click — including work beyond the service allowance.

Who it's for Companies that sell their time consulting, development, service
What it costs from €89 per month by company size, no surcharges for features
How fast Deployed typically within half a day sample data with one button

Runs in your Microsoft 365 — no third-party cloud and no extra passwords.

Book a demo
How it works

From a logged hour to an invoice in three steps.

One flow instead of spreadsheets scattered across the team — and every step shows who signed off on what.

  1. People log their hours

    In a weekly grid or with quick logging — project, milestone, work type, hours. They send the whole week for approval with one button.

    Copy an empty week from the last one
  2. The manager approves them

    A project manager sees their own projects in the queue and approves in bulk or one by one. A rejection carries a reason the author sees on the record.

    An email goes out on every step
  3. You invoice

    Export approved hours as a client report to Word or to a spreadsheet, and mark billed hours with the invoice number.

    For service contracts only work beyond the allowance
Inside the app

See it in practice

A project overview on the dashboard, logging hours in half a minute, a project page with a progress strip, acceptance criteria to tick off and client tasks, and approving submitted timesheets with one click.

What changes

Today vs. with Worklog

This is what companies that sell their time — consulting, development, service — tell us before they deploy Worklog.

Today “At the end of the month I chase hours across the whole team.”Everyone keeps their own timesheet — in Excel, in notes, or not at all. Rates are dug out of emails.
With the app Hours add up as you goA week in the grid, sent with one button. The rate comes from a price list per client, project and person — not guesswork.
Today “How much of that allowance did we actually use?”It comes out too late. Overages don't get billed and unused hours lapse with no rules.
With the app You see allowance usage as you goUnused hours carry over by your rules and work beyond the allowance is calculated separately.
Today “I assemble the billing input by hand from spreadsheets.”From spreadsheets nobody approved, with no record of who signed off on what, and the client report formatted by hand.
With the app A billing input from approved hoursA client report in Word using your branded template — and a verifiable record at every step.
Customer experience
No more chasing hours at month-end. And work beyond the allowance finally gets billed — before, it quietly lapsed.
IT services · 25 consultants · 18 projects + 7 service contracts

Getting started took half a day. Consultants learned to log hours in a few minutes, and accounting exports the billing input in a morning instead of three days.

3 days → a morningpreparing billing inputs
2service contracts with overage work recovered
100 %of hours approved with an audit trail
The fastest route

30 minutes on screen, no company presentation

  • 5 minYour current practice — how you collect and bill hours today
  • 10 minLogging hours and approvals through the eyes of a colleague and a manager
  • 10 minService allowances, the billing input and the revenue outlook
  • 5 minWhat a rollout would look like for you + an indicative price
Pick a demo slot → Free and without obligation · online in Teams
8 areas — click one for details

Log hours without delay

Quick logging (project, milestone, work type, hours, note) and a weekly grid across Monday to Sunday. Copy an empty week from the last one as drafts. A timesheet can also be started straight from a milestone or task.

Clients, projects and milestones

A clear tree of client → project → milestone → task. The project page shows in a single progress strip the hours used from the budget, acceptance criteria met, tasks done and what is waiting on the client. Milestones as months of a service contract or functional blocks with an hour budget; clients can be pulled in from EP365 CRM.

Approvals with an audit trail

Submitted timesheets wait in a queue — the administrator sees everything, a project manager their own projects, and a project manager’s own hours are approved by the administrator. Approve or reject in bulk or one by one; a rejection carries a reason the author sees on the record. An email goes out on every step.

Service contracts and allowances

A service-contract project has monthly prepaid hours and a carry-over mode for unused ones (none, full, or partial with a cap). The month-end close calculates the carry-over and passes it on. You see usage and overage work in one overview.

A matrix rate price list

Hourly rates at three levels: client, project and a personal rate on the project. When logging, the most specific one is picked and saved with each timesheet — a later price change doesn't rewrite history. Non-billable hours are recorded without an amount.

Billing and a client report

Export approved hours grouped by client to Word using your template (logo, header, footer) or to a spreadsheet, and mark selected hours as billed with an invoice number. Summaries respect currencies (CZK and EUR per project).

Month-end close and revenue outlook

If you have EP365 CRM, one button calculates the billable revenue from approved hours — for service contracts only the amount beyond the allowance, for fixed milestones the price after acceptance — and writes it into the revenue outlook. Running it again doesn't double anything.

Import hours and roles

Import hours from a spreadsheet with a preview, people matching and protection against a double import. Four roles: administrator, project manager, contributor and biller. A project manager edits the projects they lead and approves hours on them — also for a colleague they stand in for. Projects and clients the administrator assigns to them are visible to them and open for logging time; contributors can be limited to just their own clients and projects.
Area
EP365 Worklog
Excel & spreadsheets
Cloud time-tracking
In-house SharePoint build
Data in your Microsoft 365
yes, entirely
local files
third-party cloud
usually yes
No third-party server
yes
yes
runs at the vendor
depends on the build
Approvals with an audit trail
yes, with a rejection reason
no
partially
needs coding
Service allowances and carry-over
yes, with rules
by hand in a spreadsheet
rarely
no
Matrix price list and rate snapshot
client · project · person
no
basic rates only
no
Client report (Word from a template)
yes, with your logo
manual formatting
generic template
no
Revenue outlook from hours
links to the CRM forecast
no
no
no
Deployment
in half a day
immediately
sign-up and setup
weeks of development

Data stays with you

Hours, rates, clients and timesheets are stored exclusively in your Microsoft 365 environment, under your identities and permissions. No export to a third-party cloud, no data leaving the company.

No new passwords

People sign in with their company Microsoft account. When an employee leaves, IT handles it in one step — blocking the account removes access to the timesheets too.

Rates seen only by those who should

In the app a contributor sees only their own clients and projects, and rates and amounts only the administrator and the biller. SharePoint permissions hold part of the line themselves: a contributor cannot overwrite or delete someone else’s timesheet, cost rates open for the administrator only, and people with read-only access to the SharePoint site cannot see timesheets at all — not even with a direct link.

A single external dependency

The licence is just an encrypted file the app downloads from our CDN — nothing is sent. No hours, rates or client data reach us.

No extra automations

Email notifications go straight from the browser via Microsoft 365, and rate, usage and close calculations run at your end. No further licences or services to sign off.

Verifiable history

Who approved or changed what and when is traceable in the Microsoft 365 audit — no separate logging system, no side records.

Licence

Monthly licence by company size

Up to 25 M365 users
€89 / month
26–70 M365 users
€145 / month
71–150 M365 users
€205 / month
More than 150 M365 users
Individual

The subscription depends on the total number of internal users in your Microsoft 365. Within a given size you get the full scope of the app, with no surcharges for individual features.

Deployment

On-site implementation

€509 one-off

We help you get started: installation, an initial team workshop, theme setup to match your brand, configuration of work types, the price list and the report template, optionally an import of clients and hours and a link with EP365 CRM.

What is not included

The fixed price covers a standard rollout. Data import and configuration beyond a standard rollout. We will send a precise quote after a short call.

Extended support

Support pricing

€110 / hour

Consultations, environment adjustments, custom reports or user support beyond the implementation.

How support is billed

Support is billed per started 15 minutes of work. We always tell you the expected scope in advance.

Prices exclude VAT
Where are our hours and rates stored?
Exclusively in your Microsoft 365 environment, within your SharePoint. The app has no database or server of its own — no data leaves your company. The licence is checked by downloading an encrypted file from our CDN, which sends nothing. Only what you choose to send leaves — for example a bug report e-mailed from the app.
Do we need any extra automations or a separate cloud?
No. Email notifications go straight from the browser via Microsoft 365 (the sender is always the signed-in user) and rate, allowance-usage and close calculations run at your end. No further licences or external services.
How does timesheet approval work?
A contributor submits hours for approval — the project managers of the affected projects get an email. In the queue the administrator sees everything and a manager only their own projects; approvals happen in bulk or one by one. A rejection carries an optional reason the author sees on the record and in the notification — they fix the timesheet and resubmit. An approved timesheet can no longer be changed by the author. A project manager’s own hours are approved by the administrator.
Can we also track tasks the client has to complete?
Yes. On a task you choose that the client completes it — supplying documents, access or a sign-off, for example — and optionally name the person at the client. A filter shows what is waiting on the client, and the project page shows the number of open client tasks in the progress strip and on every milestone. Tasks and milestones have acceptance criteria to tick off; each ticked item keeps who ticked it and when.
How do service contracts and carry-over work?
A service-contract project has monthly prepaid hours (an allowance) and a carry-over mode for unused ones: none, full, or partial with a cap. The month-end close calculates the unused hours and carries them into the next month — the bundle is then the allowance plus the carry-over. Hours beyond the bundle are billed at the price-list rate, or a rate inherited from the contract in EP365 CRM.
Do we have to have EP365 CRM?
No, Worklog works fully on its own — you keep clients directly in the app. With EP365 CRM you additionally get a pick list of companies from the CRM when creating a client, inheritance of the allowance and rate from a service contract, and the approved hours written into the revenue outlook at the month-end close.
How quickly do we deploy it?
Typically within a few hours to half a day. You add the app to your Microsoft 365 environment and the first load creates everything needed by itself. Sample data is available with one button and live data can be imported from a spreadsheet.
Can we adjust the work types and the report template?
Yes. Work types are a configurable list and the client report has a template with your logo, header, introductory text and footer. You set rates as a matrix for client, project and specific person, and you match the app's colour to your brand.
How do app updates work?
You upload the package to your App Catalog just once. New versions then load on their own and your admin manages them right inside the app — on the Version management card in Settings they can pin a version or roll back to an earlier one. No repeated package deployments: we ship improvements continuously — without a pinned version your site gets them automatically, with a pinned version you switch when you choose.