The travel request that adapts to your rules.
The premote travel request is designed for complex approval processes and enterprise requirements. It is easy to configure and user-friendly for travellers.
- Enterprise travel request for complex requirements
- No-code configuration, no IT project
- Automate downstream processes with agentic workflows
Trusted by HR & global mobility teams
How the request adapts to each case.
Every answer can change the form, for example its required fields, approvers or registrations. Four cases 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 every trip is not enough.
The premote travel request is built as a dynamic decision tree. Your specialist teams configure their own required fields, custom fields and dynamic rules without an 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.
Edge cases don't fit the standard form, so they end up in spreadsheets, emails and individual people's heads. That is where expensive gaps appear, such as a forgotten export control check, a missing security clearance or an approval that was never obtained.
The request as a decision tree.
Every answer drives the next question, required field and approver. Rules can be combined by department, purpose, destination or risk level and are set up by click, with no development project.
- No-code configuration: Set rules by click, without an IT project or waiting time.
- 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 replaces ten manual steps.
- Each department sets its rules once and the request applies them automatically.
- Right approval, matching form and registrations obtained automatically.
- Workflows, AI agents, reporting & premote compliance attached directly.
More compliance features from premote.
See premote in action.
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 internal rules of any complexity that would otherwise end up in 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, without email ping-pong or 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.