Joe's notes

Life Admin Tracker

Properties1
descriptionAdmin pipeline; kidney consultant appointment confirmed for Mon 19 Oct 2026, 14:45, York Hospital.

11 min read

Life Admin Tracker

Frozen original (4 November 2026). Case explanations now live in cases; operational state lives in the app and case-status.md. This file is kept as the evidence of what was recorded, and is not updated.

1. Flight Refund — EgyptAir

StatusTaskDetailsNext Action
🔴AESA — retrieve and respond to 26 Oct document requestPortal list remains “En trámite”; history added “PENDIENTE DE APORTAR DOCUMENTACIÓN” on 26 Oct. DEHú notice and exact deadline unknown.Sign in to DEHú with Cl@ve, read the notice, then prepare the required response by its deadline
  • Status: 🟠 Review request registered 01/10/2026; expediente still “En trámite” on 26/10, with a new pending-documents entry
  • Booking: MS768 (BCN→CAI) + MS851 (CAI→ADD) | Dec 20, 2025
  • Claim amount: €600 (£520) under EC 261/2004
  • Delay: >4 hours at final destination (Addis Ababa) due to missed connection
  • Case reference: 2026/ADR02/018280 — filed 20/07/2026
    • The earlier BORR/ADR02/00192929 is AESA’s draft marker (“borrador”), not the filed reference. Corrected 30 Sep 2026 by logging into the portal.

⚠️ The decision (read from the signed document, 2 Oct 2026)

AESA issued “FIN DEL PROCEDIMIENTO MEDIANTE DECISIÓN DE INADMISIÓN” — the complaint is not admitted for processing. The claim as filed is closed.

  • Stated ground: the flight “salió y llegó a un aeropuerto situado en un país que no es miembro de la Unión Europea”, so it falls outside art. 2.2.a of Orden TMA/201/2022.
  • Signed by: María Francisca Patilla Carmona, Jefa de División de Derechos de los Pasajeros
  • Registry entry: 2026287421, dated 01/10/2026
  • Document: 11994235_2_DECISION INADMISION GENERAL.pdf (3 folios, CSV AESASGEEPGEE000OVFR1AM96HVIUDA)

Worth challenging. AESA’s stated ground says the flight both departed and arrived outside the EU, but the itinerary starts at Barcelona, an EU airport, and EC 261 covers a journey beginning in the EU on a single booking. On the face of it that is the point to make. Verify the ticketing (single booking vs separate legs) before relying on it, because that is what the argument turns on.

The rebuttal — lodged, and accepted

Joe submitted the response rebutting the inadmission on 01/10/2026, through the portal. The filename 1_AESA_review_request_Spanish_DRAFT.pdf makes it look like a draft; it is not. The same registry batch (2026287421) carries 3_aesa_justificante_aceptacion_2026_10_01_b1932138.pdf — an acceptance receipt — and the expediente now reads “En trámite / In process” rather than closed.

Backing evidence uploaded with it: the trip confirmation, the original itinerary and the original receipt, so the rebuttal is on the ticketing basis, which is the right ground.

Where it stood — 2 Oct 2026 (history)

ItemDetail
Current stateEn trámite (in process) — the revisión is live
AESA’s decision due~01 Nov 2026. AESA has one month from the revisión; silence counts as a refusal (desestimada)
If it goes against youThe decision is explicitly not binding on the passenger, who “podrá ejercer las acciones civiles que tenga frente a la compañía aérea”. AESA can also be asked for a fresh complaint once the cause of inadmission is cured, within one year of complaining to the airline
  • Next action: Joe must retrieve the 26 Oct DEHú notice using Cl@ve and check its response deadline. Do not wait for ~01/11/2026 without reading it; the one-month review-decision date does not reveal the document-response deadline.
  • Monitoring: case-watch polls the AESA portal daily at 9:10am and reports portal changes, but it cannot read DEHú notifications. After Joe reads the notice, update this tracker with the actual requirement and deadline.

Status history (AESA portal)

DateState
20 Jul 2026Claim submitted (telematic)
28 Sep 2026EN ADMISIÓN
29 Sep 2026PENDIENTE DE APORTAR DOCUMENTACIÓN
01 Oct 2026PENDIENTE DE APORTAR DOCUMENTACIÓN · inadmission decision issued
02 Oct 2026En trámite · Trámite finalizado
26 Oct 2026En trámite; latest history entry: PENDIENTE DE APORTAR DOCUMENTACIÓN

Documents on file

26 entries across four registry batches — 2026207865 (18/07/2026, the original claim), 2026284490 (29/09/2026), 2026287421 (01/10/2026, includes the decision) and the notification receipt. Includes the claim form, Trip.com itinerary and receipts, Flightradar24 history, the EgyptAir “We care” reply, passport, and a seven-document response bundle with a Spanish review-request draft.

Note: the tracker previously read ”🟢 En trámite … Deadline pressure: None immediate”. Both were wrong by 2 Oct 2026. AESA had already inadmitted the claim on 01/10 and the decision carries a one-month review window.

2. Protective Claimant Award — Redundancy (Employment Tribunal)

  • Status: 🟢 Parked — waiting on judicial service to lift stay
  • Case number: 6003560/2026
  • Tribunal: Leeds Employment Tribunal
  • Judge: Employment Judge Jeram
  • Respondent: Moores Furniture Group (in administration)
  • Administrator: Interpath Ltd
  • Claim letter dated: 30 April 2026

Actions Taken:

TaskStatusDetails
Submit refusal letter to Tribunal✅Emailed LeedsET@justice.gov.uk with Section 8.2 refusal letter
Request written consent to proceed✅Emailed mooresemployees@interpath.com for Interpath agreement
Provide video hearing details✅Emailed Tribunal with contact info + confirmed Chrome installed
Respond to strike-out warning✅Response submitted by 14 May 2026 deadline
Tribunal — stay to be lifted🟡With judicial service — nothing else Joe can do

Updates

  • 14 Aug 2026 — Interpath published Progress Report 1 + Creditor’s request for a physical meeting on IPS creditor portal (case M112B5441 per the portal report, M Realisations 2026 Ltd, formerly Moores Furniture Group — reference disputed, decision 36C)
  • 29 Sep 2026 — the ET portal’s “Date last modified” for case 6003560/2026 moved to 29 September 2026; it had not moved since submission, and the portal exposes no narrative.
    • Explained 10 Oct 2026: that was Joe’s own login to the portal, not a case event. The record has not moved on the Tribunal’s side, so the case is genuinely still parked with nothing for Joe to do.

Optional:

  • ELIPS support — elips@elaweb.org.uk if you want free 40-min legal advice clinic

3. Kidney Donation — Living Donor for Laura

StatusTaskDetailsNext Action
⏳Paired-exchange matchingConsultant medical exam done 19 Oct; tests go into the next UKLKSS matching runWait for Joanne’s next step; chase if she goes quiet
⬜Surgery / donationDates unknown until a paired match is foundPre-plan recovery and the work calendar once dates land

Recipient: Laura Willerton · Donor: Joe · Coordinator: Joanne Barwick (“Jo”), York Hospital — joanne.barwick1@nhs.net. Route: paired-exchange scheme (tissue typing showed not a direct match with Laura).

Process Pipeline — history

StageStatusNotes
Referral / initial appointment✅Booked 30 Apr 2026; appt 18 May at York Hospital
Blood group compatibility✅Compatible with Laura
Blood / urine tests✅All clear
Tissue typing✅Results in — not a direct match → paired-exchange route
Enter paired-exchange scheme✅Entered 20 Aug 2026
Consultant appointment✅ BookedMon 19 Oct 2026, 14:45, York Hospital — confirmed by Joe 10 Oct 2026 (Jo’s “Tuesday 19th” was the slip, the date was right)
Scheme assessment / paired-match⏳Medical exam at the 19 Oct appointment, then tests scheduled for the UKLKSS matching run
Surgery / donation⬜
Recovery + work calendar⬜Pre-plan once dates known

Current Focus

✅ Consultant appointment booked for Mon 19 Oct 2026, 14:45, York Hospital, confirmed by Joe on 10 Oct 2026. That resolves the day/date mismatch in Jo’s 8 Sep email. Nothing to chase. The medical exam at this appointment feeds the UKLKSS matching run.

Chaser Log

DateAction
30 Apr 2026Initial appointment booked
18 May 2026Appointment at York Hospital
22 May 2026Blood group compatible confirmed, waiting on tissue typing
25 May 2026Acknowledged, said you’d wait
18 Jun 2026Chased: “Any updates on tissue typing?“
20 Jul 2026Chased — still waiting on tissue typing results
20 Aug 2026Tissue typing results in — not a direct match; entered paired-exchange scheme; now waiting on consultant appointment
04 Sep 2026Chased in writing — asked what was still outstanding and flagged the October UKLKSS run
08 Sep 2026← Joanne: not a tissue-type match with Laura, so direct donation is off; kidney sharing (paired exchange) confirmed as the route. Consultant medical exam offered: “Tuesday 19th October at 14.45” — day and date disagree (19 Oct 2026 is a Monday)
08 Sep 2026Accepted the slot the same day (the day/date mismatch was not spotted at the time); Jo to send the appointment letter
15 Sep 2026Queried the day/date mismatch with Jo in writing — is it Mon 19 Oct or Tue 20 Oct, and is 14:45 right? Awaiting her reply
10 Oct 2026Resolved. Joe confirms the appointment is Mon 19 Oct 2026, 14:45, York Hospital. The date in Jo’s email was correct and the weekday was the typo. No reply from Jo needed, nothing further to chase
26 Oct 2026Chased — auto-detected from Gmail (re: Scheme assessment / paired-match)
26 Oct 2026← Joanne: RE: Next Appointment
27 Oct 2026← Joanne: Re: repeat blood test

4. Complaints

Section 75 Claim — escalated to the Financial Ombudsman

  • Status: 🟠 With the Financial Ombudsman Service, awaiting an investigator
  • Claim: Section 75 claim against HomeServe Finance Limited, the lender on the £2,954 fixed-sum loan for the BOXT boiler installation. Submitted 21 Jul 2026. (The BOXT complaint and the S75 claim are the same dispute, so they are tracked as one entry now.)
  • HomeServe final response: 25 Sep 2026 (Caoimhe Whelan, Customer Relations). The external flue remedial work is confirmed complete. BOXT’s offer stands at £250 against the £450 asked for, and HomeServe will not raise it. They closed the complaint as their final position.
  • FOS case reference: PNX-6154478-P3L2 — complaint received 24 Sep 2026, named against Homeserve Finance Limited.
  • Ombudsman Connect: account registered and active. The portal is how FOS communicates, so watch it and the inbox.
  • FOS timescales (their own guidance): an investigator within 6 to 8 weeks of submission, then 6 to 8 weeks from there to an outcome. Expect first contact around early to mid November and an outcome around the new year.
  • Referral deadline: 6 months from the 25 Sep final response, so ~25 Mar 2027. Not a constraint now that it is submitted.
  • Open question: whether to take BOXT’s £250 directly. It is a live offer, and accepting it may settle the matter, so that is a decision to make deliberately rather than by default.
  • Portal monitoring — password reset 10 Oct 2026, vault not yet updated. case-watch had been locked out of Ombudsman Connect: the vault password was rejected and two failed attempts on 30 Sep counted against the account, which locks on the next one. Joe reset the password on the portal on 10 Oct 2026, but the vault item FOS Financial Ombudsman still holds the pre-reset value: a single sign-in attempt on 10 Oct reached the password screen and was rejected (“Please enter valid password to proceed”), so one failed attempt has now been used. Do not retry until the new password is in the vault.
    • Verified about the flow (read-only probes, 10 Oct): the portal redirects to an Azure AD B2C page, step 1 is email only (#signInName → #continue, accepted), step 2 is the password (#password), and step 3 is a one-time passcode, since the same screen offers “Reset how you receive your one-time passcode”.
    • Not yet automated. The fos portal in case-watch.py still carries fetcher: None, enabled: False, and no fetch_fos has been written. The passcode step needs one live run to pin down before a fetcher can be finished and tested.
  • Next action: get the new password into the vault item (Joe by hand, or an agent-run “Forgot your password?” reset that stores the new value). Then the fetcher is one build and one test away. FOS will make contact in the meantime — an investigator is due early to mid November.

Rail Ombudsman — LNER

  • Status: ✅ Closed — LNER compensated Joe (confirmed by Joe, 10 Oct 2026)
  • Reference: R175958, against LNER (London North Eastern Railway)
  • Filed: 04/09/2026 · Outcome: compensation received
  • Last state read from the portal (2 Oct 2026): the ladder had reached Response Received 23/09/2026, with Complete still pending. The closure itself was not read from the portal, so the ladder above is the last verified position rather than the ending.
  • Documents (3): Application Form.pdf · Gmail - Thank you for your enquiry Joe.pdf · Gmail - Seat Guarantee.pdf — all uploaded 04/09/2026 19:49
  • Next action: none. Case closed.
  • Monitoring: retired 10 Oct 2026 — the rail portal was removed from case-watch.py, so it is no longer polled daily. Nothing left to watch.
  • Was previously untracked: this live complaint had no entry in any tracker until 2 Oct 2026.

🅿️ Parked / No Action Needed

ItemStatusNext Update

Last updated: 2026-10-27 (AESA DEHú document request recorded 26 Oct; exact response deadline remains unknown. Kidney consultant appointment confirmed for Mon 19 Oct; Moores data breach section removed at Joe’s request, nothing actionable in it; Rail Ombudsman closed, LNER compensated; FOS vault password still stale, see §4)

Graph View

Backlinks