Root cause analysis: getting past the first plausible answer
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
A travel policy is mostly about deciding things in advance so nobody has to negotiate at an airport. Numbers, a booking route, and a clear line on what is not covered.
A travel policy states how business trips are approved, booked and paid for, and what limits apply. Its purpose is not to make travel cheap — it is to remove the negotiation that otherwise happens per trip, usually under time pressure and usually in favour of whoever is most senior in the conversation.
For a small company most of it fits on a page. The parts worth writing carefully are the approval threshold, the accommodation limit, and the paragraph about what happens when something goes wrong — because that is the situation people actually consult a policy in.
Add the sentence people actually need: what to do when a flight is cancelled, a hotel is unusable, or someone falls ill. A traveller stuck at midnight should not be inferring the policy from a limits table — give them permission to spend what is needed for safety, a named person to notify, and the reassurance that it will be sorted out afterwards.
Travel is one of the areas where a policy touches real duties. Employers generally owe a duty of care to travelling staff — more visibly for international or higher-risk destinations — which is why knowing who is where matters, and why insurance and an emergency contact belong in the document. Per-diem allowances, mileage rates and the treatment of trips that mix business with leisure all have tax consequences that differ by country. Write those parts with your accountant, and check your insurance actually covers the trips people take.
In Ettex, the policy sits in Ettex Docs with version history and comments while it is agreed, and a share link so it can be attached to the trip request rather than filed. Trip requests and post-trip expense claims work as forms in Ettex Forms — destination, dates, purpose, estimated cost, with file uploads for quotes and receipts, landing timestamped in one searchable inbox that doubles as the record of who is travelling where. Approved costs are categorised in Ettex Books with the receipt attached to the entry, and trip dates can sit in Ettex Calendar so the team knows who is away.
The boundary: Ettex is not a travel management system. There is no booking, no fare search or negotiated rates, no traveller tracking or risk alerts, no automatic policy checks at the point of booking, and no corporate card integration. It holds the policy, collects requests and claims through forms, and records the spend. Frequent international travel is a case for a dedicated travel platform.
Approval thresholds, the booking route, rules for flights, rail and car, accommodation limits, meal allowances, ground transport, what is not covered, insurance, and what to do when a trip is disrupted.
Either, but pick one. Per diems are simpler to administer; actuals are easier to justify. Check the tax treatment locally, since allowances above set rates can become taxable pay.
By city band rather than a single global figure. One number applied everywhere is generous in some places and unusable in others, which is how policies get broken.
Decide in advance and write it down — commonly allowed provided the company pays no more than it otherwise would, and with insurance implications made clear.
Generally yes — a duty of care that grows with the risk of the destination, which is why knowing who is travelling where, plus insurance and an emergency contact, belong in the policy. Check what applies in your jurisdiction.
Annually against what trips actually cost. Travel prices move faster than policies, and out-of-date limits are the main reason people stop following them.
A travel policy works when the numbers are current, the booking route is faster than the alternative, and the disruption paragraph exists. Decide it once so nobody has to negotiate it at an airport.
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
A code of conduct says how people here are expected to behave and what happens when they do not. Its value is not aspiration — it is having decided the hard cases before one arrives.
A project charter names the objective, the boundaries, the sponsor and the person authorised to run the work. Its main use comes months later, when people disagree about what was agreed.