Travel request for a small firm: five lines, a cost tier and a bill check

A small firm's travel request is five lines posted in Slack before anyone books: purpose, dates and destination, an estimate by category, the approver and who books. The estimated total decides who approves it, and after the trip the final bill is checked against that estimate. Perk says five or six fields is enough for a smaller team, and that is the whole form.
Without one, FirstHR describes the usual pattern as the owner approving a trip in a chat message, the employee booking on a consumer site, and the receipts arriving as photos weeks later. Nothing records what was approved, so an overrun surfaces after the money is spent and an exception has no named approver. A five-line request, an approval table and a final-bill check give every trip a named approver and a written estimate to compare against.
What goes in a five-line travel request?
Five lines: why the trip is needed, where and when, what it should cost by category, who approves, and who books. Each line closes a gap that the bill cannot close later.
- Purpose. One sentence naming the client, event or deliverable, such as "Kickoff workshop with the Acme ops team".
- Dates and destination. Departure and return dates, and the city. International trips say so here, because that changes who approves.
- Estimate by category. Airfare, lodging, ground transport and meals, each as a number. Navan's workflow guide lists the same four breakdowns for a request, and Perk's form asks for an estimated budget broken out by category. A single total hides which category overran later.
- Approver. A name, taken from the tier table below, not a guess by the traveler.
- Booking owner. Who will buy the tickets: the traveler, or the office manager or assistant. Booking stays with a person; the request only records who.
This is deliberately shorter than a corporate travel form. Ramp's travel policy guide says a startup under 50 employees should keep it simple, and says every trip should start with a formal approval that includes dates, destination, estimated cost and business justification. The five lines cover exactly those items plus the booking owner.
Post the lines in one Slack channel, for example #travel, and make the thread the record. A request sent by DM is the failure you are trying to remove.
Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.
Who approves a trip: tiers by estimated cost
The approver follows the estimated total. A routine trip goes to one manager, a larger one adds a second person, and an international one goes to an executive whatever it costs.
The dollar limits are yours to choose. Two vendor pages give examples, and neither is a standard. Otto's planning guide uses manager sign-off under $1,500, manager plus finance from $1,500 to $5,000, and executive review for international travel. FirstHR's template uses $750 and $2,500 and tells you to adjust its tiers to your actual spending. Both are vendor pages, so treat the numbers as sample inputs.
If your firm already has a table of who may approve what, reuse its dollar limits instead of inventing new ones. Delegation of authority for a small team shows how to build that table, and the trip tiers can borrow its rows.
Here is an example tier table for a 25 person firm. The numbers are made up for illustration.
| Estimated total | Approver | Review window |
|---|---|---|
| Up to $1,500, domestic | Operations lead | 2 business days |
| $1,500 to $5,000, domestic | Operations lead and the owner | 2 business days |
| Any international trip | Owner | 2 business days |
| Inside the minimum booking window | Owner, with a written reason | Same day |
| Any exception to the policy | Owner, in writing, before the spend | Same day |
The two-day review window comes from Otto's guide, which gives managers two business days. Name a backup approver for each row; Navan's guide recommends naming delegate approvers for when the primary reviewer is away or traveling.
Tier the approval on the estimated total, but let three triggers skip the dollar table: international travel, a booking inside the minimum window, and any exception to the policy. The dollar figure alone misses these. An international trip can cost less than a domestic one and still raise entry rule and insurance questions, which is why Otto and FirstHR send it up whatever it costs and Navan says it may need senior review. Otto requires a written reason for a short-notice booking, and its guide puts the usual domestic booking at 14 to 21 days out, with 7 days as the minimum. And FirstHR's template requires written approval from the owner or finance lead before an exception is spent, not after. Write all three into the table so no one has to remember them.
How do you check the final bill against the estimate?
Post the final totals in the same thread as the request, by the same four categories. The difference per category and in total is the check, and a trip returns to the approver only if it crosses a limit that was written before the trip.
Most guides stop short of this step. Navan says the approved trip is booked against the estimate and expenses are matched back to it later. Perk lists "expenses reconciled manually post-trip" as a drawback of the manual process. Neither gives a small firm a number for how far a final bill may drift from the estimate. Without one, either every difference gets argued, or none does.
The limit below is a recommendation with no source behind it. Adjust it to your own spend.
Check the final bill against the approved estimate by category and in total, and send a trip back to the approver only when it crosses a limit you wrote before the trip. A workable starting limit: the final total is more than 10 percent or more than $200 over the estimate, whichever comes first, or the final total lands in a higher tier than the estimate did. Differences under the limit are logged and closed. Differences over it go to the approver in the same thread with the per-category numbers beside them.
Write the limit in advance, because a rule decided after you see the overrun is a negotiation with a colleague, and a rule decided before is a rule. It also protects the traveler: a $70 overrun never reaches the owner.
Here is a made-up example. A designer travels to a client workshop. The approved estimate was airfare $480, lodging $620, ground $90 and meals $150, a total of $1,340, which is in the first tier. The final bill is airfare $540, lodging $610, ground $140 and meals $120, a total of $1,410. That is $70 over, about 5 percent, so it is logged and closed. A second trip with the same estimate ends at $1,700. That is $360 over, about 27 percent, and it crosses the $1,500 line into the second tier, so it goes back to the approver with the categories listed.
What does the Slack thread look like?
One thread carries the whole life of a trip: request, approval, a row in a sheet, the final bill and the comparison. The agent reads and writes; people decide.
The setup is a travel policy document in Google Drive that states the tiers and the booking window, and a Trips Google Sheet with one row per trip. The Kipwise agent is mentioned once in the thread and plain replies continue the work. It searches Google Drive and reads Docs and Sheets with the asker's own access. Reading Drive and editing a Sheet are separate connections, so people who only look things up are not asked for the second.
Here is the thread, with made-up names and numbers.
> Dana (traveler): @agent travel request. Purpose: kickoff workshop with Acme ops. Chicago, Mar 10 to 12. Estimate: air $480, lodging $620, ground $90, meals $150. Approver: ? Booking: me. > > Agent: Fields received: purpose, dates and destination, estimate, booking owner. Missing: approver. The estimate totals $1,340, which the travel policy places in the first tier, approved by the operations lead. International: no. Booking window: 6 days out, inside the 7 day minimum, so the policy requires a written reason from the owner. > > Dana: Client moved the date. Owner, please confirm. > > Owner: Reason accepted. Ops lead, go ahead. > > Ops lead: Approved.
The agent matched the estimate to the tier in the document and flagged the window, which is the part that needs reading. It did not pick an approver outside the policy and it did not approve anything. If it has not read the policy, it is instructed not to guess and says so instead of inventing a limit.
After the approval, Dana asks the agent to add the trip to the Trips sheet. The agent shows an Approve or Deny card for the new row, and only Dana, as the person who asked, can use it. The card expires after 30 minutes, and a denied or expired card writes nothing.
Write one Trips row at the moment of approval, because that single row is both the baseline the final bill is checked against and the written record of time, place and business purpose. Keep these columns: traveler, dates, destination, purpose, approved estimate by category, approver and date approved. The IRS says that even under the standard meal allowance you must keep records proving the time, place and business purpose of travel, and that a log, diary, notebook or other written record is acceptable. A row like this is that record, produced at the moment it is easiest to get right. The same row is the number the final bill is compared with, so you maintain one record instead of two.
After the trip, Dana posts the actual totals in the same thread. The agent reads the Trips row, compares each category and the total, and posts the difference. A trip under the limit is closed. A trip over it goes to the approver in that thread, and the exception is decided by a person.
Which trips get forgotten?
A weekly scheduled request catches them. Ask the agent in plain language to list, every Monday in #travel, the trips whose return date has passed and have no final total. The agent runs a scheduled request in the channel with the same tools and permissions as a live one. Creating the schedule needs one approval, and later runs do not ask again. Because this run only reads and lists, it needs no other write.
Each unclosed trip becomes a name in a list that the whole channel can see. That is a better nudge than an owner chasing receipts by DM, and it makes a late final bill visible before the next trip is approved.
Handle failure and edge cases
Most failures are a person skipping a step, so write down what each one costs.
- Booked before approval. Decide the rule once: no approval before booking means no reimbursement without the owner's written exception. Ramp's guide says exceptions that are written down are defensible and unwritten ones breed resentment.
- The estimate changes before booking. Post the new estimate in the thread and re-check the tier. A trip that was $1,300 and is now $1,700 has a new approver.
- The approver is away. Use the named backup. Do not let the request sit; Otto's guide sets the two business day review for a reason.
- The agent cannot read the policy. It reads with the asker's own access, so a traveler who cannot open the policy document gets no tier from it. Share the document with everyone who travels, and the agent will say plainly when it could not open it.
- A wrong row is approved. Only the person who asked can use the card, so the approver should read the row in the sheet once. Watch for a wrong approver name or a missing category.
- Receipts and booking. The agent does not book flights or hotels and does not read a receipt it was not given. Booking and receipts stay with a person.
For the report filed after the trip, the expense report guide covers receipts and the reimbursement clock. For approvals that are not trips, the approval request guide covers the generic request and the silence clock.
Verify it works
Run the process for a month, then check three numbers.
- Trips with a final total. Every trip whose return date has passed should have one. Anything else is on the Monday list.
- Trips back to the approver. A few is healthy; it means the limit is catching overruns. Many from the same category means the estimates are wrong. Fix the estimate habit, for example by pricing lodging at the real nightly rate for that city.
- Requests that arrived with fewer than five lines. If one line keeps being skipped, pin the five-line template at the top of #travel and ask for the missing line in the first reply.
Also check that the written limit still fits. If every trip clears the 10 percent rule, the limit may be too loose; if the owner sees most trips, it is too tight.
What to do next
Today, write the five lines and the tier table for your firm, with your own dollar limits and a named backup for each row, and pin the lines in your travel channel. Use them for the next real trip, yours included. If you want the agent to apply the tiers and compare the final bill, the Kipwise agent costs $10 per user per month with a minimum of 3 users, with $5 of personal credit per user per month. Run the next trip through it end to end and see which step still needs a person.



