Skip to content
Hypamoon

For teams that run on SmartDok

SmartDok holiday requests: approved, then logged

SmartDok records absence once it is known, and a leave and absence planner is the most requested card on its own idea board. Until then, requests for holiday, time off in lieu or a day off arrive by text message, a note or a call, and the office types them in later.

How it goes today

  1. An employee texts or calls the foreman to ask for days off.
  2. The foreman checks the planning and answers by text.
  3. Someone at the office writes the approved days down.
  4. The office registers the absence in SmartDok on the right absence code, day by day.

How it can go

Leave requests get an answer, and approved days land in SmartDok.

Employees fill in a short request form for holiday, time off in lieu or other leave, with the dates. Their manager gets the request with who else is away those days, and approves or declines it. Approved leave goes into SmartDok as absence on the absence code you chose, so it shows in hour approval and in the payroll export. You also get a simple overview of who is away in the coming weeks. Remaining holiday balances stay where you keep them today.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. SmartDok first switches on access for your company when you ask them, which can take a few business days. After that you create the key yourself and paste it in the portal, never in the chat.

Your request

With Hypamoon, build a leave request form for our team: holiday, time off in lieu and other leave, with dates. Send each request to the employee's manager with who else is off those days. When the manager approves, register the leave in SmartDok as absence on the matching absence code. Give me an overview of who is away in the next four weeks.

SmartDok sales first switches on API access for your company, and asks who builds the connection and for which system. After that an administrator creates the key under Company settings, API administration, chooses which modules it may use, and it stays yours. The key is valid for a year and can be renewed.