LEX ASTRA ACADEMY CS 115 / Reception and passenger accountability Lex Astra · School of Civil Practice Teaching edition 2956.3 / Live practical ———————————————————————————————————————————————— LEARNER WORKSHEET For cradleFleet boarding and reception coordinators. This is a private working copy. Downloading submits nothing and records no completion. Use exercise identifiers, not private player information. ———————————————————————————————————————————————— SESSION DETAILS Learner identifier: ____________________________________________________________ Instructor / assessor: ____________________________________________________________ Session date / agreed role or variant: ____________________________________________________________ Vessel, configuration and equipment: ____________________________________________________________ LIVE build / capability test date / tested by (if practical): ____________________________________________________________ Stop signal / recovery contact / communication arrangement: ____________________________________________________________ ———————————————————————————————————————————————— PURPOSE Prepare a CradleFleet passenger movement and confirm who boarded, arrived or still needs contact. COURSE CONTEXT The civil school applies the distinction between departure and receipt to passenger care. A passenger must not disappear from the record because the vessel completed its trip. ———————————————————————————————————————————————— ENTRY Complete: FD 100, FD 110, FD 120, FD 130, FD 140, FD 199 Equipment: Volunteer passengers, suitable berths and a tested route. ———————————————————————————————————————————————— CASE: A passenger missing from reception 1. P-01 through P-04 are volunteer identifiers on the boarding list. 2. All four are confirmed boarded. Reception confirms P-01 through P-03. 3. P-04 has disconnected; their latest in-game location is not currently confirmed. ———————————————————————————————————————————————— TECHNICAL KNOWLEDGE AND GAME SKILLS Passenger handling at ramps, lifts and landing sites Practical instruction revision 1 / 9 October 2026 Make boarding physically workable Choose an assembly point outside landing and loading movement. Explain the route to the ramp, lift and seat, then board in a sequence that avoids crowding narrow access. Test a lift before committing the full group. Verify that passengers have environmental protection for every exposed part of the journey, not merely for the destination interior. Secure the cabin before flight Check each person is aboard and in a usable seat where available; do not infer this from a party marker hovering near the hull. Confirm ramps and external doors are closed. Warn the pilot about anyone still moving or unable to use the intended seating. Boarding completion and readiness for manoeuvre are separate calls. Deliver beyond the ramp After landing, confirm the exit is usable and the ground is suitable before releasing passengers. Use one guide at the receiving point and one final cabin check. Record remaining aboard, disembarked and received separately. If the lift or ramp fails, keep passengers in a safe location while the crew tests an alternative instead of encouraging repeated jumps into an uncertain opening. PRACTICAL DRILL Board a small group, perform a short trip and guide them to a named reception point. Simulate a failed exit or missing passenger report and reconcile the cabin and reception counts. OBSERVED-SKILL CHECKS All passengers can reach their assigned places with the equipment worn. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ The pilot receives a verified cabin-ready call. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ A receiving count is based on actual arrivals, with unresolved people assigned a follow-up. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Apply the technical checks in the agreed role. Discussion and simulation do not certify live handling; Crew Support evidence does not confer Pilot qualification. GAME REFERENCES The linked pages were read for this revision. Community references mix release eras; each source note identifies what is used and what is excluded. Technical explanations below are an Academy synthesis, and drills and performance checks are Academy-designed. Before practice, compare the named actions with the installed LIVE build and actual equipment. Bind actions by name rather than copying old default keys. Research is not an in-game validation. Star Citizen Wiki — Controls https://starcitizen.tools/Guide:Controls Control categories, movement axes and targeting concepts. The page contains legacy bindings and flight-system descriptions; use the installed game’s bindings, not its key table. Star Citizen Wiki — Medical https://starcitizen.tools/Medical Body-part injuries, Hemozal, symptom medication, BDL, bed tiers and regeneration. Ship tables, resource costs and ranges change; inspect the actual bed and tool. Official LIVE release check: https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— METHOD 1: Collect only what the movement needs Use passenger handles or exercise identifiers, boarding point and the agreed movement need. Do not collect private health or identity details. Make sure the departure and reception teams use the same identifiers so they can compare lists. Reception begins before boarding. Tell passengers where to assemble, how their exercise identifier will be checked and what to do if they lose contact. Confirm the destination and any agreed assistance need in operational terms. A short, understandable instruction is more useful than a detailed manifest the passenger never sees. Practise: Prepare the passenger list and boarding brief. Ready when: The list supports matching passengers across the movement without unnecessary personal data. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 2: Count boarding and arrival separately Name who confirms boarding and who confirms receipt. Read back changes to either list. A seat assignment, boarding report and arrival report describe different events; do not advance a passenger to the next state without confirmation. Use one receiving confirmation for each passenger, tied to an identifier and time. At destination, distinguish remaining aboard from reaching the agreed reception point. A transport report can establish that the vessel landed without establishing that every passenger left it or reached the receiving coordinator. Practise: Run boarding and receiving checks with volunteers. Ready when: The record contains separate, confirmed departure and arrival counts. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 3: Keep the missing check-in visible Record the last confirmed state, current uncertainty and person making contact. If the passenger reconnects, update the list with the new observation. Do not diagnose a missing check-in or remove it to make the totals match. For P-04, keep four boarded, three received and one unconfirmed as separate facts. Assign a reconnect contact and a next update, then check the last supported location before proposing recovery. If the session closes, transfer the contact task explicitly; an unresolved arrival must not disappear when the original coordinator leaves. Practise: Handle one missing arrival acknowledgement. Ready when: The record preserves the missing passenger and a clear contact or recovery action. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— WORKED DECISION P-04 disconnects after boarding. Reception confirms three arrivals and keeps P-04 unconfirmed with a reconnect contact. 1. Enter four boarded and three received as separate observations. Leave P-04 unconfirmed with the earlier boarding report preserved. 2. Assign a reconnect contact and tell the transport and reception roles who owns it. 3. Update P-04 only when new evidence arrives, and hand over the contact task if the session ends first. ———————————————————————————————————————————————— YOUR EXERCISE Brief boarding, compare the arrival list and handle the missing check-in. Finish with an accepted follow-up, not a falsely balanced total. WHAT CHANGES One passenger does not check in at the destination. My decision and reason: ____________________________________________________________ ———————————————————————————————————————————————— YOUR WORKING RECORD Passenger identifier / boarding confirmation / time ____________________________________________________________ ____________________________________________________________ Arrival confirmation / receiver / current state ____________________________________________________________ ____________________________________________________________ Unconfirmed passenger / last observation / contact owner ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— CHECK YOUR REASONING Four boarded and the ship arrived. What arrival total can Reception enter? My answer before consulting the explanation: ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— EVIDENCE TO KEEP Matched departure and arrival lists and the missing-check-in handover. Criterion 1: The list supports matching passengers across the movement without unnecessary personal data. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 2: The record contains separate, confirmed departure and arrival counts. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 3: The record preserves the missing passenger and a clear contact or recovery action. Individual evidence / finding / assessor's reason: ____________________________________________________________ ———————————————————————————————————————————————— FINDINGS AND NEXT ATTEMPT Demonstrated: observed work meets the criterion. Further practice required: an observed gap needs a specific practice task. Interrupted: conditions prevented valid assessment; not a failure. Not assessed: enough evidence has not yet been collected. All three criteria need individual evidence. A team result or quiz cannot replace an unobserved practical. Practice variant for a fresh attempt: Use a passenger confirmed waiting at origin rather than disconnected after boarding. Require the correct state and onward plan. My next practice task: ____________________________________________________________ Review contact: ____________________________________________________________ ———————————————————————————————————————————————— COMPARE AFTER ANSWERING Only the passengers actually confirmed at reception. Keep the others unconfirmed and investigate the gap; a vessel’s arrival is not four separate passenger confirmations. ———————————————————————————————————————————————— SOURCE AND EDITION Case CS–3: one berth remaining /academy/archives/reception-case Civil Practice case issued by CDR Yuki Tanaka-Reis in 2956. These variants use present-day service responsibilities and new training lists; they are not transcripts of the Pyro Station Alpha response. The lessons are current Academy teaching, not newly discovered historical records. Lex Astra opened in 2891. Historical sources keep their original issuer and date; all case callsigns, quantities, times and conditions are supplied for practice. Course text revised 8 October 2026; fictional teaching edition 2956.3. ———————————————————————————————————————————————— PROFESSIONAL REFERENCES Instruction revised 9 October 2026. Lex Astra cases supply the teaching situations. Professional references inform communication, decision-making and instructional design; they do not confer external qualifications. LIVE capabilities remain subject to the recorded session check. AHRQ · structured team communication https://www.ahrq.gov/teamstepps-program/curriculum/communication/index.html Sphere · accountability and continuity in relief cases https://www.spherestandards.org/handbook/ RSI · verify release notes before live delivery https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— INSTRUCTOR CHECK Try the exercise with the ship and equipment you will use. Brief station assignments, callsigns, channel and recovery point. Explain the command “Stop exercise” before starting. If a bug prevents completion, repeat the affected task when it works. Ask before recording the session; use player handles in your notes. Review rules: /academy/archives/academy-ordinance Teaching basis: /academy/framework#research