Everything you can change, and what happens if you don't.

This is a plain-English tour of every control in the promoter console. It is written for somebody running their first track-to-track event, not for somebody who already knows the software — so each setting says what it does for your event, what it is set to before you touch it, and what a racer sees when you move it.

Most of it you can leave alone. A route, a name and a Publish is a working event. Everything below that is there for when you want it, and the defaults are chosen so that doing nothing is a reasonable answer.

Two changes cannot be undone. They are listed on their own, near the top, so nobody finds out the hard way.

Who can change what

Everyone you add belongs to your organisation, not to a single event, and their role applies to every event the organisation owns. There are three, and they only ever widen — a role never takes away ordinary racer access to the app.

Owner

Everything an editor can do, plus the three things that change the organisation itself: adding and removing employees, renaming the organisation, and deleting it. An organisation always keeps at least one owner — the last one cannot be removed, demoted or allowed to leave, so transfer ownership first if you are handing the event on.

Editor

Runs the event day to day: event details, branding, vendor pins, driver alerts, publishing, the SOS and reports monitors, restrictions for your own organisation. This is the role for the people actually working your event.

Viewer

Reads everything and changes nothing. Useful for a sponsor, a timing partner or a safety crew who needs to watch the SOS monitor without being able to post an alert. The buttons are not merely hidden — the change is refused on our side too.

A handful of controls are marked DragDuro below. Those are ours to set, and you will see them filled in and greyed out. They are listed anyway, because knowing what they do explains a lot about how the racer's app behaves.

The two that can't be undone

Everything else in the console can be changed back. These two cannot, and both are behind a confirmation for that reason. Read them once now rather than at 2am the night before your event.

Changing the route id

The route id is your event's permanent name in the system — the thing every link, every QR code on a printed sheet, your big-screen display URL and every vendor pin, SOS and branding setting hangs off. Change it and all of that moves to the new id and every existing link and QR code to the old one stops working. There is no undo and no redirect from the old id. If you print your route id on anything, change it before you print, and never during a live event. Between events it is safe; the day racers are driving, it is not.

Deleting the organisation

Archives the whole organisation: every employee is removed, every route it owns is unpublished, and it stops appearing anywhere. Nothing is thrown away — the records are kept so we can bring it back for you — but you cannot undo it yourself from the console. Owners only. If what you actually want is to take one event off the air, unpublish that event instead; that is reversible.

Your event's details

Route & Legs

An event bundles one route with its branding, vendors, alerts and settings. You create it with a name and a route id; the route line, the checkpoints and the start/finish strips themselves are drawn in the route maker, not here. Everything on this screen except the artwork is saved together by the Save details button — nothing is applied as you type.

Creating the event

You

+ Create event asks four things in turn: a name, a route id, the dates, and a start date. Only the first two are required, and every one of them can be edited afterwards on this screen — except the route id, which needs the Change id button below and cannot be undone. So it is worth a moment's thought now: pick something short, lowercase and durable, like your event and its year.

Choose the route id carefully: It is the only answer here that is expensive to change later. Everything else is a text field you can fix in a second.
Already taken: Two events can never share a route id, including one somebody else already used. You'll be told to pick another.

Event name

You

What your event is called, everywhere: the racer's app, the big screen, the printed sheets, your own event list. Up to 120 characters.

Default: Whatever you typed when you created the event.
What a racer sees: The event title on the route screen, unless you have set a separate display name under Branding — that one wins where it is set.

Dates

You

Free text, and purely cosmetic — write it however you would write it on a flyer. Feb 9–14, 2026 is fine, so is Sick Week 2026. Up to 80 characters.

Default: Empty. Shows as “dates not set” in your own event list and simply doesn't appear to racers.
What a racer sees: This exact text beside the event name.

Start date

You

A real calendar date, and a different thing entirely from the Dates field above. Racers never see it. Its only job is to tell us when your event starts, so the offline map along your corridor can rebuild itself automatically about a week beforehand and your racers download a current one.

Default: Empty. Leave it blank and that automatic pre-event refresh never runs — the map still works, it is just whatever was built the last time the route changed.
What a racer sees: Nothing directly. Indirectly: a fresher downloadable map for the drive.

If your event is published and this is blank, the console says so in red on this screen. That warning is the only nag in the whole product, and it exists because a blank here is invisible until the week of the event.

Route id

Can't be undone

Your event's permanent identity. You cannot type over it — there is a Change id button beside it that runs the move properly. Ids are 2–64 characters: letters, numbers, hyphens and underscores, no spaces or slashes.

Default: The id you chose when you created the event. Two events can never share one.
What a racer sees: It is in the link they open and the QR code on their printed sheet.

One way, no undo

Changing it re-keys the route, the vendor pins, any live SOS and your branding to the new id, and breaks every link and QR code pointing at the old one. Do it between events, never during one, and never after you have printed anything.

Info link

You

An https:// link to a page of your own — the day schedule, tech and gate times, house rules, registration. Anything a racer might want mid-event that isn't the route.

Default: Empty, and the button is simply not shown.
What a racer sees: An Event info button in the route app that opens your page.

Publishing, and the offline map

Route & Legs → Publish

A draft event is private. Nobody can open it, it is not on the big screen, and it is not in anybody's route list. Publishing is the switch that makes it real, and it is also what starts the two builds that make the route usable in a dead zone.

Event status — Publish / Unpublish

You

One button. Published events appear to racers and on the big screen; unpublishing takes them straight back off the air.

Default: Draft. A new event is private until you say otherwise.
What a racer sees: Nothing at all while it is a draft. Once published, the route, the checkpoints and everything else you have configured.
Reversible?: Yes, both ways, as often as you like.

Offline map

Automatic

The strip of map along your route that a racer can download before they leave, so the line stays on screen when the phone signal doesn't. You don't configure this — it builds itself when you publish, and again whenever the route line moves. The row on this screen is a status readout: not built, queued, building, ready, or failed with the reason.

Default: Builds automatically. There is nothing to switch on.
What a racer sees: A Save offline map option in the app's settings for this route.

Speed limits & road names

Automatic

Read from OpenStreetMap immediately after the offline map is built. They feed the speed-limit badge in the racer's app and the street names on the turn card and the printed turn-by-turn sheets. Also just a status readout — but worth glancing at, because if this one fails it does not retry on its own, and the only symptom is that speed badges and street names never show up.

Default: Runs automatically after each map build.
If it says Failed: Press Rebuild offline map, which retries both. If it keeps failing, tell us.

Rebuild offline map

You

The manual escape hatch for “the map looks stale”. It re-runs the map and the road data together. Only available on a published event, and there is a cool-down between presses — if it declines, the message tells you why.

Default: Not needed. Publishing and editing the route already trigger it.
Viewers: Read-only — the button is greyed out.

What racers can do on the road

Route & Legs

Four checkboxes that decide how much your racers can put on each other's screens. Each is per-event, and all four save with Save details.

Vendor applications

You

Whether a signed-in racer or shop can ask for a map pin on your route themselves. With it off — which is how it arrives — you add the vendor pins you want, from the Vendors screen, and they go live immediately with no review step. With it on, applications turn up as pending and you approve or deny each one.

Default: Off. Nobody can apply until you turn it on.
What a racer sees: Your event listed as open for pin applications on their account page — only while this is on.
Turning it back off: Stops new applications and stops existing applicants editing their own pin. Your pins, and your ability to approve, deny or deactivate anything already there, are unaffected.

Racer reports — Hazard

You

Lets racers warn each other about debris, a crash, a stopped car or an animal on the road between tracks. Reports are anonymous to other drivers, expire after 30 minutes, and any signed-in racer can confirm one or mark it gone.

Default: On.
What a racer sees: A pin on the map and the option to post one themselves.
Turning it off: Hides existing pins of that type immediately.

Racer reports — Road

You

The same thing for road surface: construction, gravel, potholes, standing water. The type that most often saves an oil pan.

Default: On.
What a racer sees: A pin on the map and the option to post one themselves.

Racer reports — Police

You

Police sitting, running radar, or on a traffic stop. This one is deliberately off unless you turn it on: hosting police-spotting on your event should be a decision you make, not something you discover.

Default: Off.
What a racer sees: Nothing until you enable it.
The big screen: Police reports never appear on the venue display, even with this on. A screen in a public building is a broadcast, not a racer's phone. That is not a setting.

Turning all three off

You

Perfectly legitimate — clear all three boxes and racer reports are simply not a feature of your event. Nothing else changes; SOS is separate and is always available on a published event to a racer with a live location.

The arrival card, and your artwork

Route & Legs

When a racer reaches a checkpoint they can take a photo and get back a branded card to post. The photo and the finished card never leave their phone — the only thing uploaded in the whole flow is the artwork you provide here.

Arrival card on / off

You

Whether the card exists for this event at all. Left on, it uses your branding colours and wordmark automatically — you do not have to supply anything.

Default: On. This is the one racer-facing feature that is on by default and worth knowing about.
What a racer sees: A camera step at each checkpoint, then a card they can save or share.

Card artwork — four slots

You

Optional, and there are two different ways to use it. Upload a full-frame design per shape and the racer still chooses which shape to post; or upload a logo only, which replaces the wordmark on the card and changes nothing else. You can do either, both, or neither.

The four slots: Square 1080×1080 · Portrait 1080×1350 · Story 1080×1920 · Logo only, a transparent PNG.
Format: PNG, under 3 MB. Each slot uploads and removes independently.
Default: All four empty. A shape with no frame just uses the standard card at that shape — it never borrows another shape's art.
Saved when?: Immediately, unlike everything else on this screen. There is no Save step for artwork.

A frame covers the whole card, so on a shape that has one your logo doesn't show — it appears on the shapes you left standard. Upload something at the wrong shape and the console warns you it will be stretched, but still accepts it: your art, your call.

If your event is an older one you may instead see a note about a single overlay — one frame at its own shape, with the racer's shape picker hidden. That still works and nothing is forcing you off it. To move to the four slots, upload the shapes you want and then remove the single overlay. A new event never has one.

Branding the racer's screen

Branding

Seven settings that restyle the driver app and the big screen for your event. There is a live phone preview beside them, so you can see the result before saving. These save together with Save & publish and take effect straight away.

Event display name

You

The name shown on the racer's screen, if you want it to differ from the event name in your own console.

Default: Your event name.

Tagline

You

A short line under the name. Yours to write.

Default: Compete. Drive. Compete.

Logo URL

You

An https:// link to your logo image. We link to it where you host it rather than asking you to upload one, so updating it on your side updates it here.

Default: Empty — a plain DD chip stands in.

Primary colour

You

The dominant colour of the racer's screen: the route line, the logo chip, the main buttons.

Default: DragDuro amber, #FF8A1E.

Accent colour

You

Used sparingly, and mostly for one thing: the I need help button. Pick something that reads as urgent, and don't make it the same as your primary.

Default: DragDuro redline, #FF3B30.

Show logo

You

Whether the logo chip appears at all on the driver app and the big screen.

Default: On.

Replace the wordmark & wordmark colouring

You

Swaps the DragDuro wordmark on the racer's screen for your organisation's name. Turning it on reveals a second control for how the name is coloured: half white, half your primary colour (the way ours is set), all white, or all primary.

Default: Off — the DragDuro wordmark. Colouring defaults to the split style when you switch it on.
What a racer sees: Your organisation's name where ours was, plus a small “Powered by DragDuro” line. That line is required and appears automatically when you replace the wordmark.
Note: The name used is your organisation name, not the event name — so renaming the organisation restyles every event where this is on.

Vendor pins

Vendors

Shops, sponsors, food, fuel and parts, pinned on the racer's map along your route. You create these yourself — that is the normal path, and it needs no review step. Applications from other people are the opt-in described above, and are off unless you turn them on.

Add a vendor pin

You

Name and a location are required; the location can be a street address or a place name and we look up the coordinates for you. Phone, website and opening hours are optional and shown on the pin.

Type: Vendor · Sponsor · Food · Fuel · Parts. Defaults to Vendor. It sets the pin's label.
Goes live: Approved immediately, on the map within about a minute.
Viewers: Don't see this form at all.

Approve / Deny / Deactivate

You

How you moderate pins other people applied for. Deny asks for a reason, and that reason is shown to the applicant. Deactivate takes a live pin off the map; it can be approved again later, so it is not a deletion.

Default: An application arrives as Pending and shows nothing on the map until you approve it.
Also here: A Restrict button on each row, for an account that keeps submitting junk. See below before using it.

Driver alerts

Driver Alerts

One banner, pushed to every racer currently on your route. This is the control you reach for when there is a crash on the route, a strip has gone on a rain delay, or a road has closed.

Level

You

Sets the banner's colour and icon, and nothing else — it does not change who sees it or how fast. Use it honestly; a racer who learns that Danger means “merch tent moved” stops reading the banner.

Options: Info · Warning · Danger.
Default: Warning.

Message

You

Up to 280 characters, shown in full across the top of the racer's map. There is a live preview under the box.

Default: No banner. A new event has none.
To take it down: Clear banner, or post an empty message. Both do the same thing.
How fast: Racers pick it up on their next refresh — a minute or so, not instant. It is a notice board, not a radio.

The big screen

Big Screen

A read-only display page for a TV at the venue: the route, the checkpoints, current road conditions and anyone who has raised an SOS. There is nothing to configure — it inherits your branding and your event settings. Two buttons: Copy URL and Open display.

What it shows, and what it won't

Automatic

A multi-day event splits into per-day legs — the drives between one strip and the next — and the display has a switcher to step through them. Police reports are never shown here, whatever you have enabled for the app, and a report the field has disputed drops off it entirely.

Your organisation and its people

Org settings · Employees

An organisation owns your events, your employees and your branding. Most promoters have exactly one and rarely touch this screen.

Organisation name

Owners only

Your organisation's friendly name. It labels things across the console — and, where you have switched on Replace the wordmark for an event, it is the name racers see on their screen.

Default: The name it was created with.
Watch out: Renaming updates the wordmark on every event where wordmark replacement is on, not just the one you are looking at.

Add an employee

Owners only

An email address and a role. They sign in with Google using that address, and the role applies to every event the organisation owns — roles are not per-event.

Roles: Editor (the default) · Owner · Viewer. See Who can change what.
Before they sign in: Adding them works whether or not they have ever used DragDuro; access is waiting when they first sign in.

Remove an employee

Owners only

Immediate. They keep their ordinary racer account and lose only the console.

The one refusal: You cannot remove, demote or leave as the last owner. Promote somebody else first — an organisation with no owner would be unmanageable.

Delete organisation

Can't be undone

Owners only, and behind a confirmation. See the two that can't be undone — and consider unpublishing an event instead, which is reversible.

Restricting an account

Restrictions

The last resort for somebody abusing the social features. It is a capability restriction, not an account ban: they keep full driver access — the route, the map, the checkpoints, seeing other people's SOS pins and reports — and lose four specific abilities.

What it blocks

You

Exactly four things, and nothing else: submitting or editing vendor pins, raising their own SOS, viewing another racer's SOS contact details, and posting or acting on racer reports.

It takes away their SOS

Restricting somebody for spamming reports also removes their ability to call for help on the road. That is one capability set, not four switches. Be sure. Applying a restriction also clears the account's live pins and any active SOS.

Who you are restricting

You

Either type their account email, or — much better — press Restrict on the actual pin, SOS or report row. That way the account is read from the record and you never need to know their email at all.

Why it matters: Restricting by email blocks them going forward but cannot take down what they have already posted. Restricting from the row does both.

Reason

You

Up to 200 characters. Internal only — it goes in the audit log for you and for us, and is never shown to the person restricted. Write it for whoever has to review this in a month.

Default: Empty.

Duration

You

How long it lasts. It lifts by itself when the clock runs out, and you can lift it early at any time from the list below the form.

Options: 24 hours · 7 days · 30 days · Permanent.
Default: 7 days.

Scope — this org vs platform-wide

Mixed

Your restrictions apply to your organisation's events. A platform-wide tab also exists so you can see whether an account is already restricted everywhere — those are set and lifted by DragDuro only, and are read-only to you.

Default scope: This org.

Set by DragDuro, not by you

Org settings · Admin

A few things appear in the console filled in and greyed out. They are listed here because they explain a lot about how the racer's app behaves, and because it is better to know they exist than to wonder why a field won't take a value.

Driver refresh rates

DragDuro

Six numbers, in seconds, that decide how often each racer's app checks for something new. They are set per organisation — so they apply across all your events — and only we can change them. You can see exactly what your racers are running at.

SOS pins: How often a racer's map refreshes who needs help. 15s by default.
Driver alert banner: How quickly your banner reaches them. 60s by default.
Road reports — fastest: The quickest reports refresh, used while things are changing. 30s by default.
Road reports — when quiet: It slows down to this on a quiet road and snaps straight back the moment anything changes. 120s by default.
Route updates: How soon a racer is told you have republished the route. 120s by default.
Vendor pins: How often the vendor pins refresh. 30 min by default.

Why they are ours: the racer's app runs all of this polling off a single timer that ticks at the SOS rate, which is what lets the phone's radio sleep in between. Every other rate therefore has to be a whole multiple of the SOS rate, and none of them can be faster than it. If an event genuinely needs something faster, ask us — it is a conversation, not a locked door.

All-routes vendor pins

DragDuro

A pin that shows on every route on DragDuro, not just yours. Only we can create one — a pin on somebody else's event isn't a promoter's decision to make. If you have a partner who genuinely belongs everywhere, ask.

Unpublishing somebody else's route, and forced renames

DragDuro

We can unpublish a route and rename an abusive event name. We deliberately cannot publish one on your behalf — going live is always the promoter's action.

If you change nothing at all

The defaults, in one place

Draw the route in the maker, create the event, press Publish, and here is exactly what your racers get. This is a complete, working event.

Your route, its checkpoints and its start and finish strips, on a map they can follow and re-join from anywhere. A downloadable offline map of the corridor, built for you, with speed limits and street names read in behind it. Hazard and road reports so racers can warn each other; no police reports. The arrival card at every checkpoint, in DragDuro amber, with the standard frame. SOS available to any signed-in racer with a live location. The big-screen display, ready for a TV. Printable checkpoint and turn-by-turn sheets. And no vendor pins, no event info link, no banner and no applications from anybody — because you haven't added them yet.

The things most worth a first-timer's five minutes: set a start date so the offline map refreshes itself before the event; set your primary colour and logo; and add an info link to your schedule page. Those three change what a racer sees more than everything else on this page put together.