The travel request that adapts to your rules.
The premote travel request is not a static form but a dynamic decision tree: easy to configure, with unlimited dependencies. Every answer drives the next question, the next required field, the next approver – from export control to security clearance, with no IT involved.
- Dynamic decision tree – unlimited dependencies
- No-code configuration, no IT project
- Automate downstream processes with agentic workflows
Trusted by leading HR & global mobility teams
How the request adapts to each case.
Every answer can rebuild the form: different required fields, different approvers, different registrations. Four cases that show how far configuration reaches.
Defense & export control
Export check triggered automatically – before approval.
Internal travel purpose
Addresses & contacts pre-filled.
Risk-based approval
Extra steps added automatically.
Secured site visit
Done before the person arrives.
One form for everyone? That's the problem.
The premote travel request is built AI-native as a dynamic decision tree: your specialist teams configure their own required fields, custom fields and dynamic rules by click – with no IT project. Wherever manual work would arise, connected AI agents take over – from export control to approval.
Classic travel requests only know one form for everyone.
But edge cases never fit the standard form – so they end up in spreadsheets, emails and people's heads. Exactly where the expensive gaps appear: forgotten export control, missing security clearance, an approval never obtained.
A decision tree, not a form.
Every answer drives the next question, required field and approver – combinable by department, purpose, destination or risk level. Set up by click, with no development project.
- No-code configuration: Set rules by click – no IT project, no waiting.
- Unlimited dependencies: Every answer can redefine fields, steps and approvers.
- Dynamic queries: Fields appear based on earlier answers or attributes from the HR file.
Five departments, one coordinated request.
Legal, export control, security, global mobility and tax set their rules once, upfront. When one triggers, the request automatically pulls the right approval, fills the form and runs registrations – one request instead of ten manual steps.
- Each department sets its rules once – the request applies them automatically.
- Right approval, matching form and registrations obtained automatically.
- Workflows, AI agents, reporting & premote compliance attached directly.
More travel compliance from premote.
Get to know premote with no commitment.
Johannes Hillebrandt · Co-Founder & CEO @premoteFrequently asked questions about the travel request
A classic form shows everyone the same fields. The premote request is a decision tree: every answer drives the next question, required field and approver. So a single request models arbitrarily complex internal rules – instead of offloading them to spreadsheets and emails.
No. Rules, dependencies and approval paths are configured by click – with no development project. Your team can make changes itself at any time.
Fields and questions appear based on earlier answers or on attributes from the HR file. So every traveller sees only what is relevant to their case – and nothing important is forgotten.
Legal, export control, security, tax and global mobility set their rules once, upfront. When a rule is triggered, the request automatically pulls the right approval, fills forms and runs registrations – no email ping-pong, no forgotten stakeholders.
No. premote triggers the check automatically and structures the process, but it does not replace the legal assessment by the exporter or the responsible authority (e.g. BAFA). The decision stays with you – premote makes sure it isn't forgotten.
Yes. Workflows, AI agents, reporting and full premote compliance – A1, EU Posted Workers Directive, risk assessment, permanent establishment – attach directly to every request. One request triggers what would otherwise be ten manual steps.