When an outside job in an aviation operation goes wrong, the first reflex is to blame the contractor. A late inspection, a safety training session that missed the point, a parts order that arrived in the wrong spec: each one gets filed under “they did not deliver.” In many cases, though, the fault sits earlier, in a request that was too thin to deliver against. This article treats the vague request as a problem to be diagnosed, lists the symptoms that give it away and then shows a practical fix: a short written brief, sent before any work starts.
The problem: a request that leaves gaps
Take a typical sentence from a small operator’s inbox: “We need help with our safety documentation before the audit.” It sounds clear. It is not. Which documents? Which audit, and when? Who inside the organisation owns them? What would “help” look like: a review, a rewrite, a training session or a template? A contractor who receives that sentence has two choices. They can ask a long series of questions, which many busy people will not do, or they can assume. Assumptions fill the gaps, and the gaps are where disappointment lives.
Symptoms that point to the cause
Before blaming the people involved, check whether the job shows any of these signs.
- Scope that keeps growing. Each conversation adds “and while you are here” tasks that nobody wrote down.
- Dates that slip without anyone being surprised. If the deadline was never stated, it cannot be missed on purpose.
- Replies that feel generic. A standard brochure answer usually means the request gave nothing specific to answer.
- Arguments about what was agreed. When memory is the only record, memories differ.
- Cost surprises at the end. Extras appear because inclusions were never defined.
- Work that is technically complete but not useful. Nobody described what done should look like.
When a couple of these sound familiar, the likely root cause is not the provider. It is the starting message.
Diagnosis step: reread your own request
Pull up the original message you sent. Highlight every sentence that states a fact someone could check: a date, a deliverable, a limit. Then highlight every sentence that expresses a hope: “ASAP,” “as needed,” “something simple.” The ratio tells you a lot. A request made mostly of hopes forces the reader to invent the facts, and invented facts rarely match yours.
The fix: a brief in six lines
Replace the thin message with a short note that answers six questions. None of it needs technical language, and none of it is a legal document.
- Outcome. What should exist or be true when the work ends?
- Deadline. The date, the reason for it and any flexibility.
- Boundaries. What the work may and may not touch, including aircraft, records, areas of the operation and people.
- Inputs. What you will supply and when: documents, access, staff time.
- Budget range. A band, with what it should cover.
- Acceptance. How you will judge that the job is finished.
Rewrite the earlier example with those headings and it changes character: “Outcome: our hazard reporting procedure reviewed against current requirements, with a written list of gaps. Deadline: ahead of the audit date I will name in the first line. Boundaries: documents only, no changes to live forms. Inputs: our current manual and last year’s findings, delivered this week. Budget range: stated, covering review and one follow-up call. Acceptance: a list I can hand to the accountable manager.”
Why this works in safety-minded settings
Aviation organisations already value written procedures because spoken instructions drift. Applying that same instinct to outside work is natural. A brief is, in effect, a small procedure for the job itself: it names the objective, the conditions and the checks. It also makes responsibilities visible. When the inputs line says “we supply the manual by Friday,” the burden of that delay is clearly yours, not the provider’s, which keeps conversations fair.
Three cases, three rewrites
Case one: a maintenance visit. The original message said, “Please check the aircraft before our trip.” The rewrite names the aircraft, lists the work the owner believes is due, states the date of the first flight, says which records will be handed over and asks for a written list of findings as the end product. The shop can now plan hours and parts instead of guessing at them.
Case two: a training session. The original said, “We want a safety talk for the team.” The rewrite names the audience, the length, the language, the topics the manager wants covered, the date and what the team should be able to do afterward. The trainer can build material around that target instead of delivering a general talk.
Case three: a document review. The original asked for “someone to look over our manual.” The rewrite says which sections, against which requirement, with what deliverable and by when. It also says what will not be touched, so nobody edits a live controlled document by accident.
A note on tone
A brief should read as a clear request between adults. Avoid blame, avoid long backstories and avoid hedging. If a previous job went badly, leave that out; the brief is about the next job, not the last one. Short, calm sentences carry authority without sounding aggressive, and they are easy for the reader to act on.
Finding someone to send it to
The brief is ready, so who gets it? Start with contacts you already trust. If you need a local professional from another field, such as a photographer for aircraft handover images or an interpreter for a training session, ProfessNow offers a way to look people up: you choose a trade and a city, read the profiles that are listed and send a booking request. Add the brief to that request so the first answer already responds to your needs.
Common reasons the fix fails
- Writing it but not sending it to everyone. Different recipients with different versions reintroduce the original problem.
- Treating it as final. If circumstances change, update the note and tell everyone.
- Leaving out the acceptance line. It is the most skipped item and the most useful one.
- Hiding the budget range. A range invites a realistic plan; silence invites guessing.
Who should write it?
Whoever owns the outcome. In a small operation that is often the manager or the person who will use the result, not whoever happens to be sending emails that day. If several people have a stake, circulate the draft to them for a quick read before it goes out, so that competing wishes are settled in-house rather than discovered by the provider. One agreed page is far easier to work with than a thread of conflicting messages, and it protects the working relationship from the start.
What to check afterward
When the work is complete, put the brief next to the deliverable and tick each line. Did the outcome happen? Was the deadline met? Were the boundaries respected? Were inputs delivered on both sides? Was the budget range honoured? Did the acceptance test pass? Record any line where the answer was no, and use it to improve the next brief. Over a few jobs, you will build a short template tuned to your operation, and the symptoms listed earlier will fade.
In short
Vague requests produce vague results, and the cure is cheap: a handful of written lines before the first conversation. Diagnose your last disappointing job by rereading the message that started it. If it was mostly hope, rewrite it as outcome, deadline, boundaries, inputs, budget range and acceptance. Then send it, keep the thread and compare the results next time. The change is small, practical and surprisingly effective.
