Time Tracking & Attendance
Softworks
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Softworks Workforce Management Solutions Ltd · www.softworks.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Softworks Workforce Management Solutions Ltd earns its best marks on the planning side: absence and planning scores cluster at 7 to 8, built on automatic accruals by service and hours worked, skills-checked shift swaps, demand forecasting with over- and understaffing alerts, and gap-filling by email and SMS. Time capture scores range 4 to 7, and there the judges genuinely split — five of six scored 6 to 7 on the breadth of capture paths (biometrics, proximity devices, clock terminals, geofenced mobile clocking, honour-based timesheets), while the lower score came from a judge weighing offline capture at signal-less field sites, on which the captured pages give no public information. Working time law sits flat at 4: compliance is framed around the European Working Time Directive and the US Fair Labor Standards Act, with no public information on German recording-duty mapping, retention periods or inspection-ready export. Sovereignty, weakest of the product criteria, scores 1 to 2 — hosting region, contracting entity, ownership and subprocessors are unconfirmed — and payroll export scores 3 to 4 with no payroll system named. No prices are public.
Speaks for it
- Absence and planning scores cluster at 7 to 8 on evidenced automatic accruals, skills-checked shift swaps, demand forecasting with over- and understaffing alerts, and gap-filling by email and SMS
- Time capture paths are broad — biometrics, proximity devices, clock terminals, geofenced mobile clocking and honour-based timesheets — with edited timesheets routed to a manager for approval
- Project tracking works standalone or bundled with the time and attendance modules, offering work breakdown structure, critical path and actual-versus-budgeted-hours reports
- ISO 27001 and ISO 9001 certifications, GDPR statements and an on-premise deployment option are published
Held against it
- Sovereignty scores 1 to 2, with hosting region, contracting entity, ownership and subprocessors unconfirmed on the captured pages
- No public information on offline capture or the stated limits of geofenced mobile clocking
- Working time law sits at 4 with no spread, as the named regulations are the European Working Time Directive and the US Fair Labor Standards Act and no public information covers German daily maximums, retention or an inspection-ready export
- Payroll integration names no system and documents no export format; the only tax forms mentioned are P45/P60
- Project and billing stops at cost reporting, with no public information on a billable flag, rate cards or an invoice-ready export
Best for
- You need automated rostering and absence management in one system — automatic accruals, skills-checked swaps, demand forecasting and automatic gap-filling are the highest-scoring evidence here
- You run mixed clocking and non-clocking staff and want several capture paths with manager sign-off on edited timesheets
- You track projects for internal cost visibility — actual versus budgeted hours — rather than client billing
Avoid if
- Your compliance case rests on the German recording duty — the published rules name the European Working Time Directive and the Fair Labor Standards Act, and no public information covers daily maximum or eleven-hour rest warnings, retention or an inspection-ready export
- You bill clients by the hour and need rate cards, a billable flag and invoice-ready output; the project pages document cost tracking, not billing
- Your procurement requires a confirmed hosting region, contracting entity or subprocessor list before signature, all of which are recorded as unconfirmed
The scores
Capture in the real workplace
panel disagrees
Show reasoningHide reasoning
How this is scored
How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
0 — One browser timer and nothing else; anyone away from a desk records nothing.
3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.
5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.
8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.
10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.
The Operations Lead
Biometrics, proximity devices, digital clock terminals and geofenced mobile clocking cover my desk, workshop and field crews in one platform, and edited timesheets route to a manager for approval with alerts on who has not signed off — that is the capture breadth I need. We found no public information on offline capture when a site has no signal, on stated limits of the geofencing, or on bulk corrections showing who changed what, which keeps it short of the top band. 1 3 4 6
The Payroll Officer
Biometrics, proximity devices, digital clock terminals, geofenced mobile access and honour-based timesheets for salaried and off-site staff give me several real capture paths, and an edited timesheet lands on a manager for approval before it counts. But we found no public information on offline capture when the network drops, on the stated limits of the geofencing, or on bulk correction with attribution of who changed what. 1 3 4
The Works Council Advocate
Terminals, biometrics, proximity devices and mobile clocking with geofencing are all on offer, plus honour-based timesheets for non-clocking staff, and edited timesheets go to a manager for approval — that breadth earns its place. But we found no public information on offline capture or on the limits of the geofencing — what GPS stores, who may read an individual's day, and what can be switched off — and with biometric capture also offered, the vendor leaves the monitoring perimeter undescribed. 1 3 4 6
The Agency Owner
Biometric readers, proximity devices, digital terminals, geofenced mobile clocking and honour-based timesheets for the salaried side give me more capture paths than most vendors publish, and edited timesheets flow to a manager for approval instead of an admin queue. I found no public information on offline behaviour or the stated limits of the geofencing, which is what I would want pinned down for field crews. 1 3 4
The Field Supervisor
The pages show real capture paths — biometric, proximity and digital clock terminals, a mobile app with geofencing, and honour-based timesheets for staff who don't clock — plus a supervisor screen where timesheets are edited and authorised, with manager sign-off on employee edits. But we found no public information on offline capture or how the app behaves when the signal is gone, and on my sites that is the difference between a record and a Friday reconstruction from memory. 1 3 4
The Skeptic
Biometrics, proximity devices, digital clock terminals and mobile clocking with geofencing are all shown as capture paths, and edited timesheets go to a manager for approval on a single authorisation screen — a genuinely broad set of ways in. But we found no public information on offline capture or on the stated limits of geofenced check-in, and no bulk correction is evidenced, which is exactly what I want answered before believing a terminal photograph. 1 3 4 6
Working-time law & audit record
Show reasoningHide reasoning
How this is scored
Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.
0 — Hours are summed and nothing else; no break handling, no limits, no retention statement.
3 — Break deduction exists but is a flat rule; no daily maximum or rest-period checks, and no stated retention period.
5 — Configurable break rules, warnings on the 8/10-hour daily maximum and the 11-hour rest period, and per-employee reports covering the recording duty.
8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, and an export built for an inspection.
10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.
The Operations Lead
The compliance story is built around the European Working Time Directive and the US Fair Labor Standards Act, with configurable rules for minimum rest, mandatory breaks, maximum weekly hours and overtime, plus audit trails. We found no public information on the German recording duty after the BAG ruling, on warnings for the daily maximum or the eleven-hour rest period, or on a retention period and an inspection-ready export, so I would still have to argue the German case myself. 1 6
The Payroll Officer
The pages claim minimum rest periods, mandatory break times, maximum weekly working hours, overtime rules and audit trails under the European Working Time Directive, which is more than a flat break deduction. But everything is generic EU-level language: we found no public information on the German recording duty, daily maximum-hour warnings, a stated retention period, or an export built for an inspection. 1 3 6 7
The Works Council Advocate
Start, end and breaks are registered at the terminal, rest periods, breaks and maximum weekly hours are modelled as rules, and the European Working Time Directive is named. But we found no public information mapping anything to the German recording duty and its daily maximum and rest rules, no retention period, and the audit-trail statements stay general rather than showing who changed what, when. 1 3 4 6 7
The Agency Owner
Configurable break and rest rules, maximum weekly hours and predefined overtime alerts are more than a flat deduction. The compliance story is framed around the European Working Time Directive and the US Fair Labor Standards Act, and I found no public information on German recording-duty mapping, a retention period, or an export built for an inspection. 1 6 7
The Field Supervisor
Minimum rest periods, mandatory breaks, maximum weekly hours and overtime rules are stated, with audit trails and overtime-threshold alerts behind them, and the vendor names the European Working Time Directive. We found no public information on the German recording duty specifically — daily maximum warnings, the eleven-hour rest check, a retention period, or an export built to hand an inspector. 1 6 7
The Skeptic
The compliance story rests on the European Working Time Directive and the US Fair Labor Standards Act, with rules for minimum rest periods, mandatory breaks and maximum weekly hours plus overtime alerts — weekly, not the daily maximum a German inspector asks about. We found no public information on retention periods, tamper-evident change history, or any export built for an inspection, and no mention anywhere of the BAG 2022 ruling or the ArbZG sections this criterion turns on. 1 6 7
Absence & shift planning
Show reasoningHide reasoning
How this is scored
Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.
0 — No absence handling; vacation lives in a separate calendar or spreadsheet.
3 — Vacation requests with approval, but entitlement is manual, carry-over is not handled and there is no rostering.
5 — Automatic entitlement and carry-over, sickness recording, an absence calendar, and basic shift planning with availability.
8 — Public-holiday calendars per location, pro-rata entitlement, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.
10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.
The Operations Lead
Automatic leave accruals by service and hours worked, Bradford Factor and return-to-work handling, shift templates with skills and constraint checks, swaps validated against roles before manager approval, over- and understaffing alerts and automatic gap-filling by email and SMS describe a roster that reflects reality. We found no public information on public-holiday calendars per location or on carry-over of untaken leave. 1 5 6
The Payroll Officer
Accruals computed from length of service, hours worked and company policies, Bradford Factor reporting, return-to-work handling, shift swaps pre-checked against skills before manager approval, demand forecasting with over- and understaffing alerts, and gaps filled automatically by SMS to qualified colleagues — planning and recording clearly live in one system. What holds it back: we found no public information on public-holiday calendars per location or rest-period checks at the moment a roster is published. 1 5 6
The Works Council Advocate
Accruals and balances compute themselves from service and hours worked, rosters come from templates with skills and compliance checks, swaps are checked before approval, and gaps are filled by automatic contact with qualified colleagues. I note the Absence Predictor that identifies employees likely to be absent — that is individual-level monitoring which goes to co-determination before it ever touches a works agreement. 1 5 6
The Agency Owner
Automatic accrual by service and hours worked, Bradford Factor and return-to-work for sickness, shift templates with skills-checked swaps, and overstaffing and understaffing warnings cover most of what I need before a roster goes out. I found no public information on per-location public-holiday calendars or how carry-over is handled. 1 5 6
The Field Supervisor
This is the strong side: accruals computed automatically from length of service and hours worked, sickness with return-to-work handling, roster templates with skills and compliance checks, shift swaps auto-checked against roles before manager approval, and understaffing alerts with gaps filled automatically by email and text. We found no public information on public-holiday calendars per location or carry-over of untaken leave. 1 5 6
The Skeptic
Automatic accruals by service and hours worked, Bradford Factor reporting, return-to-work workflows, shift swaps checked against skills before manager approval, schedule templates, demand forecasting with over- and understaffing alerts and acuity-based rostering — the planning half is richly evidenced. What I could not find: public-holiday calendars per location, pro-rata entitlement and carry-over handling, all of which the pages are silent on. 1 5 6
Project, cost-centre & billing
Show reasoningHide reasoning
How this is scored
Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.
0 — Attendance only; no project, task or cost-centre dimension at all.
3 — A free-text note or a single project field, with no rates, no billable flag and no per-project reporting.
5 — Projects and tasks with a billable flag and per-project reports, plus a rate per person or per project.
8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.
10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.
The Operations Lead
Time tracks against a work breakdown structure with six real-time project reports including actual versus budgeted hours and project costs, and timesheets pass an approval workflow before sign-off. We found no public information on a billable flag, client rate cards, budget warnings or an invoice-ready handoff into named accounting systems — the rates the pages show are premium pay rates, not billing rates. 6 7 8
The Payroll Officer
Time, activity, budget and cost per project with work breakdown structure, dependencies, critical path and actual-versus-budgeted-hours reports is real allocation work. But we found no public information on a billable flag, rate cards by person or role, or an invoice-ready output — the reporting stops at reports that can be "exported for further analysis", which is where re-entry begins. 7 8 1
The Works Council Advocate
Time, activity, budget and cost per project are evidenced with work-breakdown structure and actual-versus-planned reporting, and timesheets pass an approval before they are reported. We found no public information on a billable flag, billing rate cards, cost centres or an invoice-ready export — and the productivity reports follow individual employees, which a works council will want to bound before anyone acts on them. 6 7 8
The Agency Owner
Time, activity, budget and cost per project with a work breakdown structure, actual-versus-budgeted-hours reports and manager sign-off is a workable skeleton for a services firm. But I bill forty people, and I found no public information on rates or rate cards, a billable flag, a client or cost-centre dimension, or an invoice-ready export — the story ends at project cost reporting. 1 7 8
The Field Supervisor
Recorded time carries project, task through a work breakdown structure, and cost against budget, with actual-versus-budgeted-hours reports a lead can act on and management approval before sign-off. We found no public information on a billable flag, rate cards by person or role, or an invoice-ready export — the time stops at the report. 7 8
The Skeptic
Project tracking is real — work breakdown structure, dependencies, critical path, budget-versus-actual reports and cost per project, standalone or bundled with the time-capture modules. But we found no public information on a billable flag, on person or project rates, or on any invoice-ready export; the chain from recorded time to revenue stops at a printable report. 7 8
Payroll handoff
Show reasoningHide reasoning
How this is scored
How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.
0 — No payroll path stated; the month leaves as a spreadsheet someone retypes.
3 — Generic CSV said to be usable for payroll, with no named system, no defined format and no handling of surcharges.
5 — A named payroll integration or a documented export format for at least one major system, covering hours, absences and overtime.
8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.
10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.
The Operations Lead
Clockings are verified through time clock integration and digital sign-off, and validated data covering hours, absence, premium rates and overtime rules goes to a direct payroll integration — more than a spreadsheet someone retypes. We found no public information on a named payroll system or a documented export format; the only tax forms named are UK ones such as P45 and P60, and we found no public information on German payroll systems such as DATEV. 1 5 6
The Payroll Officer
"Direct integration with Payroll" with no system named is a promise, not a handoff; the pieces I need before a run exist — digital sign-off verifying clockings, premium rates and overtime rules costed into rosters, absences tied to time and attendance. But we found no public information on a named provider or documented format, a lock step before transmission, or handling of corrections that arrive after the close. 1 5 6 3
The Works Council Advocate
Clockings are verified and signed off digitally before validated data passes to payroll, shift premiums sit in the pay rules, and the integration is called direct. But no payroll system is named and no export format is documented on the captured pages — we found no public information on DATEV or any German payroll path — and the tax forms named are British ones. 1 5 6
The Agency Owner
Direct payroll integration with digital sign-off before the data passes across is stated in more than one place, which is the right shape. But I found no public information naming a payroll provider, documenting an export format, or covering night, Sunday and holiday surcharges, so nothing here is verifiable before a sales call. 1 5 6
The Field Supervisor
The vendor states direct, automated payroll integration, with clockings verified by digital sign-off and premium rates costed on rosters, but we found no public information naming a payroll system or documenting an export format — the only tax forms mentioned are P45/P60. Nothing captured speaks to DATEV or any German payroll. 1 5 6
The Skeptic
Payroll integration is asserted repeatedly — direct integration with payroll, clockings validated and passed on — but no payroll system is ever named and no export format is documented, which is less than a generic CSV with a shape you can inspect. P45/P60 tax-form processing suggests a UK payroll focus, still without a named target, and we found no public information on surcharge handling, a lock step before transmission, or tax-adviser access. 1 6
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.
0 — Non-EU vendor and contracting entity, hosting region unstated or non-EU, subprocessors not named.
3 — EU hosting offered as an option, but the contracting entity is non-EU or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but the subprocessor chain includes non-EU providers without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.
The Operations Lead
The pages state GDPR compliance, ISO 27001 certification and an on-premise deployment option, and list offices in Ireland and the UK alongside Canada and the USA. The contracting entity's jurisdiction, the hosting region and the subprocessor list are all unconfirmed on the captured pages, so I cannot show my works council where the data sits or who processes it. 1 6 7
The Payroll Officer
GDPR compliance and ISO 27001 are claimed and an on-premise deployment option is offered, which is more than nothing. But we found no public information on where cloud data is held, the jurisdiction of the contracting entity, or a single named subprocessor — and the office list spanning Canada and the USA raises exactly the question the captured pages leave unanswered. 1 6 7
The Works Council Advocate
GDPR compliance and ISO 27001 are stated, and an on-premise deployment exists, which I welcome. But we found no public information on where the data is hosted, under which jurisdiction the contract is signed, or who the subprocessors are; the offices span Ireland, the UK, Canada and the USA, so the data's home is a question a works council cannot leave open. 1 6 7
The Agency Owner
The vendor presents as Irish-rooted with GDPR statements, ISO 27001 certification and an on-premise deployment option, which is a fair start. I found no public information on hosting region, the contracting entity's jurisdiction, or any named subprocessors, and that is not something I can accept on assumption for client data. 1 6 7
The Field Supervisor
Data residency, the contracting entity's jurisdiction and the subprocessor chain are all without public information on the captured pages; what is documented are GDPR and ISO 27001 statements and the choice of an on-premise deployment. An on-premise option counts for something in my book, but nobody can tell a buyer where the cloud data sits or who touches it. 1 6 7
The Skeptic
Offices in Ireland, the UK, Italy, Canada and the USA plus ISO 27001 and GDPR statements are everything the captured pages offer; hosting region, contracting entity, ownership and subprocessors are all recorded as unconfirmed. We found no public information on where the data lives, under which entity it is contracted, or who processes it — for a buyer weighing this, the certifications are not a substitute for a data-centre location. 1 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A per-user headline exists, but hardware, modules or a minimum seat count are unpriced or unmentioned.
5 — Per-user prices public for the main tiers with the billing period stated, but at least one commonly needed piece (terminal hardware, planning module, payroll export) sits in an unpriced bundle.
8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.
The Operations Lead
The commercial model is described — a predictable pay-as-you-use cloud subscription, modular purchase of items like Task Management, Time Clock Integration and Predictive Scheduling, and a choice of on-premise or cloud — but we found no public prices for any tier, module, terminal hardware or minimum seat count. For my headcount the annual invoice is a sales conversation, not a computation. 1 6
The Payroll Officer
Not one figure appears anywhere on the captured pages: a pay-as-you-use cloud subscription and named modules such as Task Management, Time Clock Integration and Predictive Scheduling, all unpriced, with no billing period or minimum stated. The annual invoice for a given headcount is a sales conversation, and I cannot budget what I cannot compute. 6 1
The Works Council Advocate
The captured pages describe a pay-as-you-use cloud subscription and name purchasable modules, but they give no figures for any tier, module or terminal. Every price is a sales conversation, so no annual invoice can be computed from public pages. 1 6
The Agency Owner
The pages name a pay-as-you-use cloud subscription and a modular menu — task management, time clock integration, predictive scheduling, analytics — plus a choice of on-premise or cloud, without a single figure among them. I cannot compute any part of my annual invoice for a given headcount from what is public. 1 6
The Field Supervisor
The pages describe a pay-as-you-use cloud subscription and modular purchasing across Task Management, Time Clock Integration, Predictive Scheduling and analytics, but we found no public price figure of any kind — no per-user rate, module price, hardware cost, term or VAT treatment. A buyer cannot compute any part of the annual invoice; every number is a sales conversation. 1 6
The Skeptic
The shape of the offer is described — a pay-as-you-use cloud subscription, modular purchase of Task Management, Time Clock Integration, Predictive Scheduling and Analytics, with on-premise as an alternative — but we found no public prices for any tier, module or terminal, no billing period and no VAT treatment. A buyer cannot compute even a rough annual invoice from these pages; every figure is a sales conversation. 6 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 23 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.softworks.com Checked 22 Sep 2026 Details →
- 2 Legal notice — found from the homepage www.softworks.com Checked 30 Sep 2026 Details →
- 3 Capture in the real workplace — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →
- 4 Capture in the real workplace — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →
- 5 Absence & shift planning — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →
- 6 Absence & shift planning — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →
- 7 Project, cost-centre & billing — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →
- 8 Project, cost-centre & billing — found from sitemap www.softworks.com Checked 1 Oct 2026 Details →