1. How it usually happens
In real life, "aliens" often take less cinematic forms: blackout, flood, closed road, network failure, building fire, lift broken, urgent works, evacuations, electrical system damage, impossibility accessing house, suspended public services, broken meters, documents stuck in inaccessible room. The result is very earthly: you cannot pay, deliver, send, participate, meet a deadline, or complete an obligation.
The sci-fi version is funnier: green light on balcony, vibrating objects, washing machine communicating in Morse code, third-floor neighbour convinced they were appointed galactic ambassador. But, if you must explain why you didn't fulfil a duty, whoever listens will need verifiable elements: blocked access, absent connection, unavailable documents, visible damage, sent communications, extension requests, technical interventions.
The unusual point is people often document the spectacular event and forget practical effect. They make ten videos of strange sky, but no screenshot of portal error, no photo of blocked gate, no email to deadline recipient, no proof of attempt to fulfil. If your "alien invasion" prevents doing something, you must link event to specific duty.
Another detail: no need convincing the world a flying saucer landed. You need to show that, at that moment, a concrete impediment existed. Also because, historically, when someone says "aliens arrived" to justify delay, recipient tends to put the email in "creative" folder. Better a dry proof than a thousand little green men drawn in pen.
2. What you need to prove
You must prove existence of concrete impediment, its duration, and link to duty you couldn't meet. Practically: what you had to do, by when, what prevented you, what attempts you made, and when you notified involved people.
Object of proof is not "aliens exist". Useful object is: "on this date, for these documented reasons, I couldn't access, send, pay, deliver, work, or complete planned activity".
It can be useful to prove:
- existence of event or impediment on a certain date;
- location conditions, like blocked accesses, damage, evacuation, or lack of services;
- impossibility using necessary tools, like internet, energy, computer, keys, documents, or vehicles;
- content of communications sent to suppliers, clients, employer, landlord, administration, or other subjects;
- deadline or duty to respect;
- attempts made to fulfil anyway;
- technical errors, portal blocks, failed connections, or unavailable services;
- duration of impediment;
- any public notices, building communications, operator notifications, technical reports;
- visible damage to house, systems, devices, or documents;
- any requests for extension, suspension, postponement, or reorganisation.
The practical question is: "If someone asks why I didn't do that thing, which files show it wasn't simple negligence?" Alien excuse makes people laugh. A timeline with proofs, less spectacular, works much better.
3. What to collect
Gather proofs showing event, but especially effect on fulfilment. If problem is physical, photos and video of location are needed. If digital, screenshots, emails, logs, error messages, and attempt proofs are needed. If involving third parties, keep communications.
You can collect:
- photos and video of affected area or house;
- photos of blocked doors, closed streets, inaccessible rooms, damage, floods, fires, cables, meters, or broken systems;
- screenshot of absent connection, portal error, failed send, unavailable service, or blocked app;
- emails or messages advising of problem;
- answers received from suppliers, administration, landlord, employer, client, or technical service;
- public notices, building communications, operator notifications, fault reports;
- receipts of support tickets or calls to technicians;
- quotes, intervention reports, or invoices;
- documents showing deadline or obligation to respect;
- proofs of attempts to fulfil, like screenshots, failed receipts, drafted drafts, error messages;
- summary PDF with timeline, impediment, involved duty, and attachments;
- original files of photos, video, screenshots, emails, and documents.
If you want to keep "alien invasion" tone even in personal notes, do so in separate note: "10:10 PM, presumed extraterrestrial activity above router". In summary to share, however, write: "connection interruption, impossible complete send, attached screenshot". Router will appreciate discretion.
4. How to proceed
First secure people, house, and devices. If there's real risk, like fire, flood, exposed wires, gas, break-in, evacuation, or access block, contact competent services immediately. Documentation comes after safety. Even in case of alien invasion, first commandment remains: avoid being crushed by levitating IKEA furniture.
Then document fact methodically. Take general photo, then details. If problem changes over time, repeat documentation. If you can't access house, photograph blocked access or keep communication confirming it. If you can't send document, screenshot error, time, and attempt.
Right after, notify who needs to know. Message must be clear, short, and verifiable: "Due to this documented impediment I cannot complete activity by deadline. Attach proof and request instructions/extension/new date." Avoid overly colourful tales if writing to supplier, office, or client. "Portal down and attach screenshot" beats "Zargon fleet neutralised modem".
Finally prepare summary PDF. Insert date, time, place, involved duty, what happened, what you tried doing, who you notified, what answers you received, and what files you attach. Timestamp main files ASAP.
Practical procedure:
- secure people, house, and systems;
- photograph or film concrete impediment;
- save screenshots of errors, blocks, or unavailable services;
- keep documents showing deadline or duty;
- note date, time, duration, and practical consequences;
- notify interested subjects in writing;
- ask for extension, instructions, or receipt confirmation;
- keep answers, tickets, interventions, and receipts;
- create chronological PDF with attachments;
- timestamp photos, video, screenshots, summary, and communications;
- keep originals in dedicated folder.
A sober message example: "Today, July 14, since 9:20 AM I cannot access property due to entrance block caused by emergency intervention, as per attached photo and communication. Therefore I cannot retrieve documents needed for dispatch due today. I request new deadline or alternative instructions." No green lasers, but maximum practical yield.
5. Mistakes to avoid
Most common mistake is documenting spectacle and not impediment. Video of sky, noise, or chaos might be curious, but serves little if you don't show you couldn't enter, send, pay, work, or deliver. Always link event to concrete duty.
Another frequent error is notifying too late. Even if amidst disaster, send short message ASAP. People are more accommodating when receiving prompt notice than a fanciful explanation three days later. Classic "I couldn't because it was impossible" works better if accompanied by documented attempt.
Beware of tones. If writing official communications, stay practical. You can joke with friends about aliens kidnapping meter, but with whoever must evaluate your delay better talk about blackout, blocked access, damage, fault, emergency, service interruption, or unavailable documents.
Also avoid manipulating files or creating overly elaborate reconstructions. Retouched photos, badly cropped screenshots, edited videos, and hyper-dramatic tales reduce credibility. Keep originals, create copies only for sharing, and maintain linear timeline.
Besides cryptographic attestation, consider prompt communications, written extension request, technical tickets, professional interventions, third-party certifications or confirmations, and contact with competent services if real risk for safety, house, or health exists.
Free timestamping helps you secure files showing concrete impediment in time, without adding costs on a day when it already seems universe opened a ticket against you.
6. After documenting
After collecting and timestamping materials, send summary to interested subjects: client, supplier, employer, landlord, administration, insurance, school, body, professional, or whoever awaited your fulfilment. Attaching a few key files is better than sending whole alien saga season.
Ask for practical solution: extension, new date, alternative method, suspension, appointment, recalculation, portal reopening, receipt confirmation, or instructions. Keep a copy of everything: sent message, attachments, answer, and new deadline.
If impediment concerns house or utilities, also notify whoever can intervene: landlord, administration, service operator, technician, insurance, or emergency service. If problem involves safety, health, blocked accesses, threats, fires, gas, water, or electricity, quickly contact competent local services.
If someone disputes delay or non-fulfilment, prepare simple timeline: duty, deadline, impediment, proofs, attempts, notices, answers, proposed solution. For economic, contractual, or delicate situations, you can turn to a legal consultant, mediation service, consumer protection association, or professional competent in involved sector.
The operational moral is this: alien invasion can stay in title, but dossier must speak earthly. Dates, photos, messages, screenshots, tickets, summary. And if a flying saucer really lands in the garden, go ahead and shoot a horizontal video: at least this time nobody will be able to say you documented it poorly.