Masterplan Optimiser
Users

Users

Set up planning and schedule access step by step

Follow the planner path when you build and publish on Desktop. Follow the participant path when you only receive an authenticated or public schedule. Host, governance and instance-key custody are not user responsibilities.

Desktop planner needs

  • A supported Windows, macOS or Linux workstation
  • Permission to plan the event and the necessary operational source data
  • For Server publishing: its HTTPS URL and one event publish secret
  • For Google Calendar: an authorised Google account
  • For PDF: a writable local output folder

Participant needs

  • A current browser and passkey-capable device or password manager
  • An activation link/QR code or deliberately public schedule URL
  • Contact with the event organiser if the assigned event or email is wrong
  • No Desktop installation, Server shell or evidence key

From a planning idea to everyone's calendar

Planning stays local until you deliberately publish a finished schedule.

Desktop app

Define, optimise, review, and finalise

Publish

MP-OPT Server

Private masterplan and public General Schedule

Google Calendar

Personal calendar distribution

PDF

Light A4 portrait schedule with printable task details

View

People and organisers

Browser, installed web app, or calendar

Planner setup and first publication

  1. 1

    Install Desktop

    Install the signed release and complete the first-launch integrity check.

    Done when: Desktop opens and reports the expected version.

    Open guide
  2. 2

    Create or open an event

    Use the project hub, set the dates and keep only necessary operational information.

    Done when: The event opens and its local project is available.

    Open guide
  3. 3

    Model the work

    Add people, capabilities, locations, templates and task instances.

    Done when: The flow check has enough structured input to assess feasibility.

    Open guide
  4. 4

    Optimise and review

    Run the flow check and optimiser, inspect diagnostics, then make deliberate final edits.

    Done when: Every published day is ready and the final schedule has been reviewed.

    Open guide
  5. 5

    Configure destinations

    Select any combination of Google Calendar, MP-OPT Server and PDF. Connect only the services you intend to use.

    Done when: Every selected destination shows ready; PDF has a title and workstation folder.

    Open guide
  6. 6

    Publish the intended scope

    Preview and publish one selected day or all ready days, then read every destination result.

    Done when: Server/Calendar data and the portrait PDF contain exactly the intended dates.

    Open guide
  7. 7

    Protect and close

    Keep processor identity in the OS credential store, export only intentional project copies and follow deletion work orders when assigned.

    Done when: No untracked operational export or unresolved Desktop work order remains.

    Open guide

Participant activation and everyday use

  1. 1. Receive access

    Use the activation link or QR code prepared by an authorised organiser.

  2. 2. Register a passkey

    Create the passkey on the intended device. The private credential stays in its authenticator.

  3. 3. Open the authenticated Masterplan

    Sign in and confirm that only assigned events and permitted schedule details appear.

  4. 4. Choose optional device features

    Enable PWA, offline schedule or notifications only when useful on that device.

  5. 5. Manage access

    Review sessions and passkeys from account security; report a wrong event or unexpected message to the controller.

Passkey sign-inEventsPWA and offlineNotifications

Two schedule audiences

The audience is fixed by the publication surface rather than selected field by field.

Public Schedule

Always public to anyone holding the intentionally published route or bearer link

Masterplan

Always restricted to authenticated people with an assigned event role

Schedule data lifecycle

Publishing copies a deliberate final state. It does not expose the working project database.

  1. 1

    Planning inputs

    People, capabilities, locations, templates

  2. 2

    Task instances

    Editable event-specific work

  3. 3

    Optimised result

    Suggested times and assignments

  4. 4

    Final schedule

    Reviewed tasks and assignments

  5. 5

    Published copy

    Full event or selected dates

Committed web edits are shared server-side overlays. A later publish clears the overlays covered by that publish; an unsaved browser draft remains local to that browser.

Passkey and session flow

The authenticator retains the private passkey; the Server stores a public credential and bounded session digest.

  1. 1

    Challenge

    Server issues a short-lived WebAuthn challenge

  2. 2

    User presence

    Authenticator signs for the exact origin

  3. 3

    Verification

    Server verifies public credential, origin and counter

  4. 4

    Session

    Protected cookie carries a bounded session token

  5. 5

    Reauthenticate

    Privileged actions request a fresh passkey assertion

For complete Desktop procedures, use the canonical App documentation. For processor-key and evidence formats, use Evidence-Public.