For years you've lip-read from 80 feet and guessed. That ends today.
How it reaches you.
The creator routes each cue to specific roles. The wrong people never see it. The right people never miss it.
PIANO · STAGE LEFT
9:41● ● ●
TapFlag
Sunday Morning Service
GUITAR · STAGE RIGHT
9:41● ● ●
TapFlag
Sunday Morning Service
9:41TAPFLAG · FOH●●●
ACTIVE
INCOMING CUE
Can't hear myself
Piano · just now
INCOMING CUE
Battery dying
Guitar · just now
Listening…
LOG
3MCan't hear myself · Piano
7MMore me · Vocals
12MKill click · WL
SOUND TECH · FOH BOARD
Every musician gets a direct line to you — no hand signals, no lip-reading, no guessing across 80 feet of stage.
The old way vs. TapFlag.
Situation
Old way
TapFlag
Lip-reading distance
✕ 80 ft, bad angle, guessing
✓ Exact cue text on your screen
Missed cues mid-set
✕ Common — you didn't see the wave
✓ Persistent on-screen until acknowledged
Post-service "who missed what"
✕ He-said / she-said, no record
✓ Full timestamped log per event
Debrief time
✕ 40 minutes reconstructing the set
✓ Five minutes — the log is already there
Signal clarity
✕ Every role sees the same IEM chatter
✓ Role-filtered — only what's yours
Built for the engineer who's done guessing.
Only your cues. Nothing else.
Role routing means "more me" routes to FOH only — not lighting, not ProPresenter. Your screen stays clear. Your attention stays on the mix.
Per-role filtering set by the creator, not by you
No cross-role noise from band or stage cues
Optional audio ping if you want it — off by default
Heard. On the record.
Every cue that reached you is logged with a timestamp and an acknowledgment trail. Post-service debriefs take five minutes instead of forty.
Timestamped log of every cue sent & received
Acknowledgment trail per recipient, per cue
Filter the log by role — replay just your feed
On in 60 seconds.
Your worship leader shares a six-letter code. You type it on the tablet you already have at FOH. That's it — no install, no account, no new hardware.
Runs in a browser tab on your existing device
Sub-second cue delivery over live Supabase Realtime
Separate channel — doesn't touch Clear-Com or IEMs
Questions sound techs ask.
How it fits beside your existing comms stack.
How does TapFlag actually get a cue to me at FOH?
Your worship leader taps a card on their phone. A Supabase Realtime push delivers it to every matched role in under a second. On your tablet you see the cue text and can tap to acknowledge — no arm-waving needed.
Does TapFlag replace Clear-Com?
No. Clear-Com handles your audio-booth traffic. TapFlag covers the silent signals from stage that currently get lost: "more me," "five more minutes," "kill click." Different channel, different job.
Will I get cues meant for the drummer or lighting tech?
No. The creator assigns each cue card to specific roles. If a card isn't routed to FOH, you don't see it. Your screen only shows what's yours.
Can I review cue history after the service?
Yes. Every cue is logged with sender, recipients, timestamp, and whether it was acknowledged. The post-service "I sent that" vs "I never saw it" argument is over.
Do I need a new device or install anything?
No. TapFlag runs in a browser tab on the tablet you already have at FOH. Enter the six-letter event code from the worship leader and you're live.
Every cue that's yours, every time.
Join with a code on the tablet at FOH. No install. No account. On in under a minute.