Skip to content

Party-Wall Cockpit — Cheat sheet

One page. Print it, pin it by your screen. For the full walkthrough see Quick Start.

1. Sign in

  • Address: https://cockpit.axon-dev.top
  • Enter your Username and Password, then click Sign in.
  • Pick your project. On screen your role shows as Surveyor in the sidebar beneath your name (your conceptual role is Operator, but the screen shows just Surveyor).
  • First time only: you may be asked to set a new password (at least 12 characters).

2. Route A — neighbour consents (11 steps)

Each line is click → what happens. Nothing leaves the building until you approve it.

  1. New case wizard (6 steps) → records a new prospect case. No workflow starts yet.
  2. Qualify case (confirm first) → approving its qualification gate sends the building owner a quote and a BoldSign mandate. The case goes Live only when the owner signs that mandate.
  3. Set up case → creates the case folder and links connectors.
  4. Determine notices → the system works out which notices apply.
  5. Serve notices → prepares the notices and opens an approval gate. Nothing is sent.
  6. Approve the serve gate → in the Requires your approval section (or the Approvals page), press Approve — this is what actually sends the notices. A case with several neighbours produces one serve gate per neighbour; approve each one to send.
  7. Record AO response (paste their reply) → if they agree, the case goes to Route A.
  8. Record SoC → Record Award → logs the schedule of condition and the Award.
  9. Start works engine → Mark works done → tracks the building works.
  10. Start invoicing engine → Record invoice → Record payment (override — no undo button in the cockpit) → handles the money side.
  11. Close case → ends the case. Cannot be undone from here.

3. Record ≠ serve

RECORD ≠ SERVE — read what each button really does.

  • Serve notices — generates the notices and serves them, but only after you approve the serve gate.
  • Request withdrawal — opens an approval gate; even then it does not email anything automatically.
  • Email party and Refer to specialist — only record a message on the case. The system never sends these — you send the email or make the referral yourself.

4. If something looks stuck or broken

A gate did not appear? A button is greyed out? A red message? "Session expired"? → See Troubleshooting before you do anything twice — re-clicking a send button does not create a duplicate, but check the gate first.

5. When to call a technician

If Troubleshooting does not fix it, call your technician and give them all five:

  1. Case reference (e.g. PW-EZNMGSDP).
  2. Time it happened (e.g. 10 July 2026, 14:05).
  3. Screen you were on (e.g. Approvals, the case page).
  4. Exact message on screen — read it out word for word.
  5. Dev-team ticket id, if one was already raised.