FOVEKI USER GUIDE · PUBLIC EDITION

From first brief
to doors open.

Use FOVEKI to give each person a clear next action while the producer keeps the final call. This guide follows the complete operating path across every invited role.

Public guide · Updated August 20, 2026 · Organization license required

Producer Command showing the next required checkpoint before the production can advance
NEXT ACTIONVisible before movement

THE OPERATING RULE

Check. Report. Route.
Review. Decide.

  1. 01
    Check the condition

    Begin with what is visible now, not an assumed plan.

  2. 02
    Report what changed

    Keep the observer, time, source, and affected work attached.

  3. 03
    Route the response

    Send the action to the person responsible for it.

  4. 04
    Review and decide

    A proposal never silently becomes the producer's decision.

01 · FIRST ARRIVAL

Enter through the invitation
entrusted to you.

FOVEKI opens the correct workspace from a current invitation. The invitation establishes the production, role, and permitted scope.

01

Open the current link

Use the newest invitation sent for the production. Old or already-used links cannot restore a different role.

02

Continue securely

Complete the requested sign-in or access restoration. Never share an invitation or access code.

03

Confirm your workspace

Check the production name, assigned role, reporting line, and next decision before acting.

04

Recover calmly

If access cannot be restored, ask the producer to correct the individual record and issue a fresh invitation.

02 · PRODUCER COMMAND

Thirteen checkpoints.
One accountable path.

Advance because the required record is visible. Availability of another button never replaces a required confirmation.

01

Purpose and scope

Record the outcome, boundary, date, venue, and production promise.

02

Ownership

Assign each primary lead and confirm no required area is uncovered.

03

Reporting lines

Place supporting team members beneath the correct lead.

04

Brief acceptance

Keep acknowledgement open until both sides visibly confirm it.

05

Program

Define sessions, rooms, speakers, capacity, access, and price.

06

Audience

Import or add guests, review duplicates, and confirm the invitation offer.

07

Published context

Approve biographies, broadcast details, and sponsor placements.

08

Communications

Send bounded updates to the right audience and keep action visible until acknowledged.

09

Task response

Review lead proposals, corrections, and closure requests separately.

10

Arrivals

Confirm who is inside, expected, delayed, or blocked.

11

Continuity

Validate the protected package and local coordination path.

12

Open actions

Resolve or explicitly hold every consequential signal.

13

Final call

Review the shared condition and record GO or NO GO as producer.

03 · LEAD + TEAM WORKSPACES

Delegation becomes
working responsibility.

Every assignment has an owner, boundary, expected result, and visible return path.

LEAD WORKSPACE

Own the bounded outcome.

  1. Read and acknowledge the brief.
  2. Confirm reporting line and authority.
  3. Delegate specific supporting work.
  4. Review team updates.
  5. Return unclear work with a correction.
  6. Submit a resolution proposal to the producer.
TEAM WORKSPACE

Check, report, and escalate.

  1. Confirm the production, role, lead, and boundary.
  2. Open assigned work and perform the requested check.
  3. Report what changed and what remains open.
  4. Submit the update to the lead.
  5. Escalate anything beyond assigned authority.
  6. Continue until accepted closure is visible.

Communications and escalations

  1. Choose the narrowest correct audience: individual, lead group, staff, or published audience.
  2. State what changed, what is needed, who owns it, and when it matters.
  3. Use escalation for a decision, blocker, safety concern, or production change outside your authority.
  4. Persistent updates remain visible until the required recipient acknowledges them.
  5. Acknowledgement confirms receipt; it does not mark the work complete.
  6. The assigned owner proposes resolution and the accountable reviewer closes it.

04 · MEDIA + PRESS ROOM

Prepare the outward story.
Keep operations isolated.

The Media Lead prepares producer-approved published context without gaining operational authority.

MEDIA LEAD

Prepare the package.

  1. Add or edit consented speaker biographies and headshots.
  2. Prepare program context, broadcast details, and sponsor assets.
  3. Review crop, wording, rights, and destination links.
  4. Submit the complete package for producer approval.
PRESS ROOM

Publish only what was approved.

  1. Invitation-only and read-only.
  2. Active speaker appears first when on stage.
  3. No attendance, readiness, team work, or producer controls.
  4. No active stream displays a calm unavailable state.

05 · REGISTRATION + ADMISSION

From invitation
to the right door.

Guests choose sessions; the production records selections, confirms payment when configured, and issues access tied to that registration.

INVITE

Review the offer

See available sessions, speakers, rooms, times, and prices.

SELECT

Choose sessions

Confirm free sessions or continue to secure payment where enabled.

PASS

Keep access ready

Present the issued QR pass at the named session entrance.

ENTER

Follow direction

A successful scan shows exactly where the guest goes next.

Admission team

  1. Open the delegated admission task.
  2. Confirm published session doors are visible.
  3. Scan continuously; successful scans advance automatically.
  4. Stop only for invalid, wrong-session, or already-admitted access.
  5. Use manual code entry only when camera or QR is unavailable.
  6. Direct the guest to the destination shown after success.

Scale safely: multiple authorized staff members may scan concurrently. Admission never depends on one person or one device.

06 · SHOW-DAY CONTINUITY

Keep the production moving
when the cloud cannot.

The verified package preserves the working picture. Local updates remain attributed and reconcile deliberately when service returns.

01

Verify the package

Confirm the continuity banner names the correct production and snapshot.

02

Start the local hub

The producer starts the hub; team devices join on the same local network.

03

Record locally

Continue bounded work with author and time attached to every update.

04

Restore deliberately

When service returns, review reconciliation before accepting the synchronized state.

RECOVERY + SUPPORT

When the flow is interrupted,
show the next safe action.

Wrong email
Correct the individual record and resend a fresh invitation.
Expired or used token
Issue a new token. Never alter accepted history.
Missing push
Open FOVEKI and inspect the persistent in-app action.
Payment incomplete
Do not issue admission access until payment is confirmed.
Wrong reporting line
Stop work and ask the producer to correct ownership.
Need help
Email support@foveki.com with production, role, device, message, and time.

Authorized administration: maintenance controls, access reviews, release gates, and configuration changes are available only in the signed-in FOVEKI Control Room. Operational users continue from their own workspace.

KEEP THE PUBLIC GUIDE

Take the operating path
into the room.

Download the sanitized public edition for role orientation, checkpoint reviews, and show-day reference.

Download PDF · 225 KB