Book a demo 14 days free

Architecture USP · Scopes

One entry.
Multiple books.
One truth.

Scopes are not tags and not categories. They are the operational business rules of your company — billability, hourly rate, budget bucket, HR workflow and UI default — bundled into one configured unit. They cascade through every level of the project graph, can be overridden per project, and every cell shows where its value came from.

18+ behavior properties per scope
49 inherited properties per project
9 levels of inheritance depth
Try free for 14 days Book a demo

Anatomy of a scope

18 behavior properties.
One configured business rule.

A scope in Temporalis EMS is a bundle of boolean flags, defaults and references that simultaneously turn it into a billing rule, HR category, budget bucket, rate carrier and UI preset. A tag does not know a single one of these fields.

01

Billing

Who appears on the invoice — and how?

  • Abrechenbar Stunden gehen direkt auf die Kundenrechnung.
  • Indirekt abrechenbar Fließt in die interne Kostenrechnung — taucht aber auf keiner Kundenrechnung auf.
  • Auf Rechnung ausblenden Eintrag wird beim Faktura-Lauf nicht als Position aufgeführt.
  • Stundensatz verbergen Rate und Umsatz erscheinen im Bericht als „—" statt als Betrag.
  • Auslage / Spesen Buchung wird als Beleg geführt, nicht als geleistete Zeit.
02

Planning & HR

Plan/actuals, absence, fixed price.

  • Plan-fähig Soll-Stunden für Forecast und Kapazitätsplanung erlaubt.
  • HR-Scope Aktiviert Antrag, Genehmigungs-Workflow und Saldo-Tracking (z. B. Resturlaub).
  • Festpreis-Scope Budget gilt als Pauschale — nicht als geplante Stundenmenge.
03

Defaulting

What does the editor pre-select automatically?

  • Auf jedes Projekt setzen Neue Projekte bekommen den Scope automatisch zugeordnet.
  • In jeder Zeitbuchung vorausgewählt Im Buchungs-Editor ist der Scope von Anfang an aktiv.
  • Default je Projekt-Typ Voreinstellung greift nur bei bestimmten Projekt-Arten (z. B. Festpreis vs. T&M).
  • Auf jeden Tarif/Item setzen Neu angelegte Tarif-Positionen erben den Scope automatisch.
04

Time-type whitelist

Which time types are allowed at all.

  • Erlaubte Zeitarten Liste der Buchungs-Typen, die für diesen Scope zulässig sind — Falsch-Buchungen werden bereits im Editor verhindert.

Beispiele:

  • Arbeit
  • Urlaub
  • Krankheit
  • Pause
  • Dienstreise
  • Kind krank
05

Rate & UI

Default rate, rebate, calendar color.

  • Default-Stundensatz Voreingestellte Rate — wird genutzt, falls Projekt oder Mitarbeiter keinen abweichenden Satz tragen.
  • Standard-Rabatt Voreingestellter Nachlass auf den Stundensatz dieses Scopes.
  • Kalenderfarbe & -stil Wie der Scope im Kalender und in Listen-Ansichten erscheint.
  • Editor-Icon Symbol in Auswahl-Menüs und im Buchungs-Editor.
  • iCal-Synchronisierung Buchungen erscheinen im persönlichen Kalender (CalDAV/iCal-Feed).

Each of these properties is defined tenant-wide together with the scope and follows the project graph via 0..9 INBOUND inheritance — not copy/paste per project.

01

Scenario · Consulting

Internal and external,
in parallel — with separate documentation.

A senior consultant sits with a junior colleague in a client workshop for two hours. From the client's perspective, this is a billable consulting service. From an internal perspective, it is simultaneously mentoring for personnel development. Until now: two tools, double entry, conflicting truths. With Temporalis EMS:

  • Multiple scopes in one click. In add mode she selects "External Consulting" and "Internal Mentoring" at the same time — the editor produces two linked entries.
  • SharedKey connects both. Both entries carry the same correlation ID — reports can group them and corrections propagate automatically.
  • Separate description per book. What appears on the client invoice has nothing to do with the internal mentoring note. Both texts are persisted separately.
  • Separate hourly rate per scope. Rate resolution runs per scope through the matrix Project × User × Scope × Role — external €180, internal €90, automatically.

"One update, two books. Billing and controlling are both correct in the same moment."

02

Scenario · R&D / Innovation

Research & Development
as its own clean bucket.

Research subsidies, innovation boxes, R&D reports — all of them require cleanly separated hour totals. With Temporalis EMS you configure a single "R&D" scope, and from the first time entry on, the data flows into the correct bucket.

  • Configured scope definition.isBillable=false, isIndirectlyBillable=true — flows into internal cost accounting but never appears on a client invoice.
  • Own rate, own report. The "Scope = R&D" filter delivers per-employee and per-project hours at the press of a button — the basis for the R&D subsidy certificate.
  • Inherited through the project graph. Set once on the holding company, "R&D" is automatically available in every subsidiary project — no maintenance per sub-tenant.
03

Scenario · HR & Employees

Individual employee scopes —
with approval flow included.

Vacation, sickness, training, continuing education, parental leave — these are not tags, they are business processes with application, approval, balance and plan/actuals impact. In Temporalis EMS they are first-class citizens as HR scopes.

  • isHRScope couples to an approval workflow. Requests go through manager, HR and, where applicable, deputy — with status, audit log and sick-note attachment.
  • Time-type whitelist prevents incorrect entries. supportedTimeEntryTypes = [vacation, sick, childSick] — work time cannot be booked here by definition.
  • Balance computed automatically. Remaining vacation, sick quota, training balance — all from approved entries, not from parallel-maintained Excel sheets.
04

Scenario · Group & Pro-Rata

One holding, three subsidiaries, a hundred projects —
one truth.

The holding defines once: "Consulting rate = €120, total budget €100,000." Subsidiaries inherit automatically. Sub-projects too. Whoever deviates locally sets an override — the rest of the hierarchy stays untouched.

  • Pro-rata split computed mathematically on the server. €100k divided across 4 parallel sibling projects = €25k per project — no Excel in between, no drift between views.
  • Override pattern instead of pure inherit. If you have a premium client at €150/h, you only override that one cell. The inheritance chain stays intact; on a later reset the field falls back to the parent value.
  • *Source fields make inheritance auditable. Every cell knows which ancestor delivered it. Auditing without back-calculation — and without guessing.
  • Pro-rata AND absolute view in parallel. The client sponsor sees the total budget, the team lead sees their share, the controller sees both — from the same data, in the same view.

Differentiation

Why scopes
are more than tags or categories.

At first glance, tags, categories and scopes seem interchangeable — they all classify somehow. In the Temporalis EMS code, however, these are three different constructs with three different jobs.

Feature Scope Tag Category
Controls billability (5 flags) ✓——
Carries hourly rate + matrix resolution ✓——
Inherits through the project graph (0..9 INBOUND) ✓——
Pro-rata budget per scope ✓——
Whitelist of allowed time types ✓——
HR workflow + approval ✓——
Defaulting in editors (3 flags) ✓——
Full-text search filter ✓✓✓

Tags and categories remain available in Temporalis EMS — for full-text classification and search refinement. But the heavy lifting of operational business logic sits in the scope.

Your model. Your rules.
Inherited on every level.

Configure your scopes in a 30-minute live demo — we map a concrete scenario from your business onto the project graph and show where inheritance actually saves you time in practice.

Book a demo Back to all features