How AmpDesk works, what it's built for, and what production teams actually do with it.
Platform Overview
AmpDesk is the operational platform for production teams managing temporary event infrastructure. It covers the full cycle: structured supplier intake, power and utility simulation, rental request management, and technical reporting — all in one place, for every event you run.
The platform is built around the idea that every decision made on paper or in a thread somewhere — what a supplier needs, what your generators will handle, what equipment was ordered — belongs in a structured, accessible system. AmpDesk is that system.
AmpDesk is built for production companies, technical production managers, power and infrastructure coordinators, and event organisers running temporary sites with multiple suppliers, zones, and utility streams. It fits festivals, city events, corporate productions, multi-day trade shows — any event where utility coordination is complex enough to require a real system rather than improvised tooling.
The core problems:
Unstructured supplier data — requirements collected by email, arriving in different formats, manually consolidated into a single document
Infrastructure decisions based on assumptions — power sizing done without a clear model of actual load, timing and source capacity
Rental requests with no tracking — equipment requests confirmed over email or phone, with no central status or audit trail
Reporting generated manually — power summaries, outlet manifests and status overviews assembled by hand after the fact
AmpDesk replaces each of these with a structured, automated flow — so your team arrives on site with a plan that reflects what was actually collected and modelled.
No. AmpDesk is entirely web-based. You access it from any browser on any device. Suppliers don't need an account either — they receive a personal link and fill in their requirements directly. No app, no download, no registration for them.
Yes. Every new account starts on a free trial — no credit card required. You can create an event, set up zones and locations, add suppliers, and explore the full workflow before choosing a plan.
Most teams have their first event set up within 15 minutes: create the event, define zones and locations, add suppliers, configure their access, and send invite links when you're ready. The platform is structured but not bureaucratic — it moves at the pace of your setup.
Supplier Workflows
The flow is Add → Configure → Invite.
You first add a supplier to the event (company, contact details). Then configure their profile: which locations they cover, which modules they can access (power & water, rental desk), their invite language, and any date restrictions. Once everything is set, you send their personal link with one click.
This separation is deliberate — you define the structure before the supplier ever sees the form. No premature invites, no access to modules they don't need.
No. Each supplier receives a unique personal link by email. They open it, fill in their requirements across whatever locations and modules you've configured, and submit. No registration, no password, no friction. The link works on any device, including mobile.
The standard intake collects: average and peak power load per location, electrical connection types and quantities (Schuko, CEE 16A/32A/63A/125A, Powerlock, etc.), separate requirements for buildup and breakdown phases, water consumption in L/h, pressure type, wastewater, and special requirements.
You can extend any supplier's form with custom fields — yes/no questions, number inputs, short text, or free text — to collect anything specific to your event or production setup. Custom fields are assignable per supplier per location.
Yes. The supplier's link remains active until the event is locked. They can return, update their data, and resubmit any number of times before the deadline. If the event is locked and you need to grant an exception, you can open a 48-hour re-edit window directly from their supplier profile.
They'll appear as Invited in your supplier list. You can send a reminder directly from their profile — AmpDesk sends them an email with their original link and your event name. No need to dig up the original email.
AmpDesk automatically locks events 7 days before the configured buildup start date — preventing further supplier submissions once the planning window closes. You can also lock or unlock events manually at any time if you need a different deadline. Locked events can still be fully viewed; only submission is blocked.
Infrastructure Planning
Power Planning is AmpDesk's simulation engine. After suppliers submit their requirements, you configure your infrastructure model — generators, grid connections, batteries — per zone. The platform then simulates the full event timeline (buildup, show days, breakdown, including overnight idle hours), zone by zone, hour by hour, against the submitted load.
The output answers concrete operational questions: does our setup hold?, when does it run tight?, what's the actual fuel/runtime profile?, can we reduce capacity?
For each zone, AmpDesk builds an hour-by-hour demand curve from your supplier data — show kW during show hours, build-up kW during build-up hours, idle/overnight kW outside of those, peak windows added on top. It then runs the configured power sources (generator capacity, grid ceiling, battery throughput + SOC) against that curve and reports the result per hour: how much each source delivered, battery state of charge, whether capacity was exceeded.
Special handling: overnight bleed across midnight, BOH and campsite zones with their own operating schedules, peak windows for time-bound load spikes, and a per-day status (OK / tight / exceeded).
Generator-first — the generator runs continuously and supplies the base load. The battery acts as a buffer: absorbing surplus when demand is low, releasing it when demand spikes above generator capacity. This is the conservative default.
Battery-first — the battery carries the load by default. The generator stays off until battery state of charge drops to a configurable threshold (e.g. 10%), then runs until it recharges to a recovery threshold (e.g. 95%), then stops again. This significantly reduces generator runtime, fuel burn, and on-site noise — especially during low-demand periods like overnight idle. It's the operational core of how AmpDesk supports hybrid/sustainable infrastructure setups.
The mechanism is structural, not gimmicky:
Real load data replaces worst-case assumptions — generator sizing becomes a calculation, not a safety-margin guess
Hour-by-hour simulation exposes idle waste — most overnight diesel burn comes from generators running at 20% load. Battery-first mode lets you switch them off
Battery integration is modelled — you can see exactly how a given battery spec changes runtime hours and fuel demand before signing a rental contract
Peak windows are isolated — instead of sizing for the full peak across the event, you size for actual peak windows and use batteries to cover the spikes
The result, depending on event profile, is typically a smaller generator package, shorter generator runtime, and a measurable diesel reduction — backed by simulated and exportable data, not just claims.
Yes. The reporting layer is designed to support audit and compliance work:
Total event kWh broken down by phase and zone
Generator runtime hours and capacity utilisation per zone
Outlet manifest and cable schedule for technical sign-off
Reports are print-optimised. Auditors, municipal permit officers, or sustainability consultants get the structured, dated data they actually ask for — not a screenshot of a spreadsheet.
Peak windows let you define specific hours when demand spikes — a stage climax, a food court at lunch service, simultaneous teardown loads. During those hours the simulation uses peak kW instead of avg kW, giving you a more accurate picture of worst-case load and SOC depletion. Without peak windows, a simulation based on average load will understate actual stress on the source.
AmpDesk calculates kWh across the full event — every buildup day, show day, and breakdown day — not just show hours. Each day is split into time segments (show, BOH, overnight idle, buildup/breakdown) and energy is summed across all zones. The output directly informs fuel planning, generator rental sizing, and battery capacity decisions.
The simulation replaces worst-case guesses with data-driven modelling. You can see exactly when load peaks, how long a battery sustains overnight, how many runtime hours a generator actually needs, and what headroom you have before a source is undersized. Concrete numbers replace conservative padding — which typically translates to smaller equipment specs, lower rental costs, and less fuel burn.
AMP Map
AMP Map is AmpDesk's site network design tool — a canvas where you draw your power distribution directly on top of your site plan. Place generators, grid taps and battery sources. Route cables along defined pathways or free-route them with intermediate waypoints. Drop PDUs and configure local distribution per location. Every cable, every gauge, every source ends up in a single visual model of how power actually moves across your site.
The point is not to replace AutoCAD or a proper electrical schematic — it's to give your production team a working operational model: site plan, demand, sources, and cabling in one place, editable in minutes rather than days.
AMP Map reads live data from the rest of AmpDesk:
Location pins inherit their power demand from submitted supplier data — average and peak kW per location, automatically
Zones drawn on the map align with the zones you defined for the event
The bill of materials uses your drum inventory (set per event) to plan cuts
This means the map is never out of sync with reality. If a supplier updates their submission, the demand on their location updates with it.
The full toolkit:
Zone polygons — outline each zone on top of your site plan image
Location pins — placed for every event location, automatically labelled and demand-aware
Power nodes — generators (with kVA rating and quantity), grid connections (with grid tap), battery storage
Pathways — pre-defined cable corridors that cables can snap to and follow
Cables — gauge-aware (Schuko, CEE 16A/32A/63A/125A, Powerlock 250A and 400A), copper or aluminium, free-routed with waypoints or pathway-following
PDUs — placed on the map, drawn from your organisation's PDU model library, with cascade hierarchy
Local distribution — per location pin, a sub-tree of local PDUs and patch cables for the last metres of distribution
Battery backup clusters — group locations that share a battery backup for resilience planning
Yes — automatically, from what you've drawn. The bill of materials lists every cable section by gauge, total length per gauge, and runs a drum-cut optimisation against your event's drum inventory. The algorithm minimises piece count first, then waste — so you can prep drums in advance with a defensible plan rather than an estimate.
It also lists every PDU placed, every power source, and the network depth from each source. Useful directly for ordering, prepping, and explaining the setup to the team doing the actual install.
Yes. From the same map, AmpDesk generates a printable network topology diagram — a tree view from each power source through pathways, cables, PDUs and locations, including the local distribution sub-tree under each location. Suitable for site briefings, contractor handover, or hanging on the wall in the production office during build-up.
No. The canvas is designed for production teams, not electrical engineers. You upload your site plan as an image, set the scale once (drag a line, type the real-world length), and start placing elements. Pathways and snapping handle most of the routing work. Drawing the full network for a medium festival typically takes one or two sessions, not days.
Water Map
The Water Map is AMP Map's counterpart for water and wastewater infrastructure. Same canvas, same site plan, separate network. You place water sources, route pipes to collectors and buffer tanks, link locations to their water supply, and handle wastewater through sewage points or portable septic tanks.
It exists because water on temporary sites is just as operationally complex as power — and equally absent from most planning workflows. AmpDesk treats it as a first-class system, not a checkbox.
Six node types, plus the pipes between them:
Water sources — mains taps, water tanker fill points, or any clean-water entry into the site
Location pins — shared with the AMP Map, so each location appears in both networks consistently
Collectors — junctions where multiple pipes converge or branch
Buffer tanks — temporary storage, optionally linked to a model from your organisation's tank catalogue (with capacity)
Sewage points — outflow connections to municipal sewer
Septic tanks — portable wastewater storage units, with quantity per node
Clean-water pipes (blue) and wastewater pipes (dashed) are visually distinct. Each pipe can be assigned a tubing type from your catalogue, with responsibility tagged per segment.
Each location pin aggregates the water requirements submitted by its suppliers — show L/h, peak L/h, off-show L/h, pressure, wastewater rate. The Water Map uses that data to size buffer tanks, identify peak windows on the supply side, and produce a per-location demand summary in its bill of materials.
Yes. The water map BoM lists piping totals by tubing type, splits responsibility (your team vs supplier vs rental), inventories every node placed (tanks, collectors, sewage/septic), and shows location-level demand. The same role as the AMP Map BoM, applied to water.
Rental Desk
Rental Desk is AmpDesk's equipment request module. Suppliers browse your catalogue — generators, fencing, furniture, water connections, power distribution, or any item you list — and submit requests directly through their supplier link. Every request lands in a central dashboard with a clear status. You confirm or reject with one click.
The result is a full picture of every equipment request across every supplier, with no requests floating in email or confirmed verbally and then forgotten.
Email requests arrive in different threads, get missed in reply chains, and require manual reconciliation. With Rental Desk: every request is logged automatically at submission, carries a status (pending / confirmed / rejected) visible to both sides, and sits alongside every other request in one dashboard. The moment you confirm an item, the supplier sees it — no follow-up email required.
You define your catalogue once at the organisation level — organised by category (Power, Infrastructure, Furniture, Water, etc.) with items under each category. Items can carry descriptions, units, and a booking type. Once defined, your catalogue is reusable across every event — and you can activate only the relevant items per event so suppliers see a curated, event-specific catalogue rather than your full inventory.
Day-booking items are requested for a date range — the supplier picks the days they need the equipment. Used for things like fencing, cabins, generators on standby.
Slot-booking items are requested for pre-defined, named time windows that you control — for example, a single forklift bookable in 2-hour slots, or a service crane available in specific delivery windows. AmpDesk enforces remaining-capacity per slot, so two suppliers can't double-book the same window.
Both types live in the same catalogue. You choose per item what makes sense.
Yes. Rental Desk is enabled per supplier in their configuration panel. Within that, you can restrict access at the item level — useful when certain equipment is reserved for specific suppliers, allocated to specific zones, or only relevant to a subset of your supplier base. Suppliers see only what they're permitted to request.
Suppliers can submit a rental suggestion — a free-form request for an item that isn't in the catalogue yet. The suggestion lands in your review queue alongside normal requests. You can approve it (mapping it to a new or existing catalogue item) or decline with a note. Useful for capturing edge-case needs without forcing the supplier to email you out of band.
The dashboard shows all rental requests across your event, grouped by supplier and item. Each row carries a status — pending, confirmed, or rejected. You can filter by status or supplier, and confirm or reject individual requests inline. The overview gives you the full equipment picture without opening a single email thread.
On confirmation, AmpDesk creates one rental instance per unit — each numbered per event, with its own status and history. From the dispatch view you can print labels for prepping in the warehouse, and your on-site team uses the mobile app to pair each unit to the supplier who collected it. From that point forward every instance has an auditable trail: who has it, what interventions were logged, what damage was reported.
At the end of the event you can export a full rental PDF — every supplier, every confirmed item, every instance — for invoicing, insurance and post-event reconciliation.
Yes. Confirmed and rejected requests are visible to the supplier on their form page, with rejection notes when you've provided them. There is no ambiguity about status from either side.
On-site & Mobile
Yes. AmpDesk includes a mobile web app (PWA) designed for the technical team on-site during build-up, show and breakdown. It works in any phone browser — no app store install required — and is available on every plan, including the free trial.
The mobile view is deliberately narrower than the desktop platform: it focuses on the actions that happen on the ground, not on data entry that belongs in pre-production.
The mobile flow covers:
Browse zones, locations and suppliers for the active event
Pair rental equipment on the spot — link a physical unit (numbered per event) to the supplier who received it
Log interventions — record on-the-spot repairs, swaps, or fixes against a specific rental instance
File damage reports with photos, immediately, from the location where the damage happened
Site map view — read-only AMP Map access for verifying cable runs and PDU locations on the ground
Crew members with viewer-level access can pair equipment and file damage reports — they don't need an admin account to be useful.
When you confirm a rental request, AmpDesk creates individual rental instances — one per physical unit. Each instance gets a per-event number and carries its own status, supplier link, intervention log and full history.
On-site, your team scans or selects an instance, pairs it to the supplier who collected it, and from that moment the unit has an auditable trail: who has it, when it was paired, what interventions were logged, and what damage was reported. At the end of the event, you have a complete operational record per unit — useful for invoicing, insurance, and supplier accountability.
Damage reports are first-class records on the platform. From the mobile app, the field user captures the damage, attaches photos, and submits — the report lands in the event's damage report list immediately, attributed to the user who filed it.
Reports can be enriched later from the desktop with additional context, cost estimates, and resolution notes. Every photo, every status change is logged. Useful for post-event cost reconciliation, insurance claims, and demonstrating duty of care to clients.
Yes. From the rental dispatch view you can generate printable labels for every confirmed rental instance — each label carries the supplier, item, instance number and event reference. Useful for prepping equipment in the warehouse before load-out, or for tagging on-site distribution.
Reporting & Visibility
The main outputs:
Power summary — avg and peak kW per location and zone total, across all event phases
Energy & Hours — total kWh across the full event (including overnight idle), directly useful for fuel planning and generator sizing
Outlet manifest — socket counts and types per location, the key deliverable for distribution board and cable planning
Water overview — L/h consumption, pressure requirements, and wastewater per location
Supplier status overview — who submitted, who hasn't, what's pending or missing
Custom field responses — all answers consolidated in a single table for review
Reports update in real time as suppliers submit — you don't wait for a data export.
Reports are print-optimised — use your browser's print function (Ctrl+P / Cmd+P) to save as PDF. A one-click export is on the roadmap.
Yes. Invite team members to your organisation with the role that fits: Admin for full access, Moderator for content management, or Viewer for read-only access to all events, data and reports. Viewer access is useful for clients, site managers, or any stakeholder who needs visibility without editing rights.
Yes. Archived events are read-only but fully accessible — all submitted data, reports and configurations remain available for as long as your account is active.
Events & Structure
An event is your top-level container — one festival, one production. Inside it you define zones (Stage Area, Food Village, Campsite, Production), and inside each zone you define locations (Main Stage, Bar 02, Sanizone East). Suppliers are assigned to specific locations. All power, water and rental data is tied to those locations — giving you location-level precision in every report and simulation.
Yes, depending on your plan. Starter supports 3 events per year, Basic 5, Premium 10, and Platinum is unlimited. Events can overlap in dates — relevant when running multiple festivals in the same season, or managing concurrent productions.
Yes. Each event has a full timeline: buildup days, one or more show periods (which can span multiple days), and breakdown days. Suppliers submit requirements per phase. Power Planning simulates across the full duration. Reporting covers every day in the event lifecycle, not just show days.
Not yet via a direct duplicate function — this is on the roadmap. For now, zones and locations are configured per event.
Plans & Billing
Event Token — from €600 one-off, activate a single event without a subscription
Starter — €1,500/year (or €400/quarter), up to 3 events
Basic — €3,000/year (or €800/quarter), up to 5 events
Premium — €5,500/year (or €1,500/quarter), up to 10 events
Plans with quarterly pricing also support quarterly billing.
All plans include the full AmpDesk feature set — supplier intake, custom fields, Power Planning, AMP Map, Water Map, Rental Desk with instance tracking, the on-site mobile app, damage reports, and all reporting. There are no feature-gated modules — the difference between plans is scale: how many events per year, how many zones per event, how many suppliers per event, and how many team members.
This is deliberate. A small team running one event a year should have access to the same operational toolkit as a large production company running ten — what changes is the size, not the depth of what you can do.
A subscription gives you access to the platform continuously for the plan period — useful if you run multiple events per year and want ongoing access to all features, your full event history, and team collaboration.
An Event Token is a one-off purchase tied to a single event activation — no subscription, no recurring cost. Tokens are sized by visitor count (Small / Medium / Large / XL) and carry their own zone and supplier limits. Ideal for organisations that run one event per year.
Yes. Each plan includes a base user count. Extra seats are purchasable per user per month — pricing varies by plan. Platinum supports a flat add-on for unlimited extra users.
Payments are processed via Mollie. Annual plans are billed once per year. Quarterly plans are billed every three months. A VAT invoice is generated for every transaction and available to download from your Billing page.
Yes. Upgrades are prorated — you pay only the difference for the remaining portion of your billing period.
All invoices are on your Billing page inside AmpDesk — each with full VAT details, downloadable at any time.
Paid plans are non-refundable. The free trial is available specifically to evaluate the platform before committing. Questions about billing? hello@ampdesk.be
Security & Data
Supplier links are unique, token-based, and tied to a single supplier. A supplier cannot access another supplier's data or form. All connections use HTTPS. Organisation data is fully isolated between tenants on the platform.
Only members of your organisation can view your event data. Platform administrators can access data for support purposes but do not share it with third parties, and all access is logged.
AmpDesk is hosted in Belgium. All data is stored and processed within the EU.
Yes. Contact us at hello@ampdesk.be to request full data deletion.