Field guides / Before launch
What does this crew actually need to share?
Use roles rather than a roster of personal details. A good brief tells each person what to do next if the pilot disconnects, a door is inaccessible or the group is split.
What to check
Name the three decisions
Agree who controls departure, who verifies the job or cargo hand-in, and who can call an abort. On a small crew one person may hold two jobs. Read back a named rendezvous and a backup destination in the same channel.
Share only what changes the next action
For a pickup, send the container count, privately agreed meeting place and the role that confirms receipt. Keep account credentials, real-world details, unrelated inventory and a private org roster out of the brief. Get consent before recording anyone's voice or sharing their position outside the group.
Rehearse the first handoff
Ask the person at the receiving end to repeat what will count as success: the correct crate and count, a completed objective, or the crew back aboard. Use agreed voice or text and an alternate if it fails. If you want a mentor rather than crew for this run, go to RSI’s Guide System yourself.
Worked example
Two pilots, one missing crate
The loader sees two boxes move. The contract holder sees credit for one. Report both observations with their locations instead of assigning blame or calling the job done. Have the holder identify the remaining objective before the pilot leaves the verified pickup or hand-in point.
Proceed or hold
- Proceed when
- Everyone knows who can launch or abort, where to regroup and which person will check the last objective.
- Hold when
- No one owns the hand-in, the agreed fallback requires one missing pilot, or someone did not consent to public sharing.
My field card
Write down what you saw. VerseToolkit does not send or save these entries. Download a copy before leaving if you want to keep them.