Publication and delivery
This course is published for study. Publication does not confirm an available class, appointed instructor or completed practical validation. Before booking, obtain a session brief naming the organiser, instructor and assessor, equipment access and any independent review arrangements.
Before live assessment, the organiser must record the current LIVE build, validation date, ship and equipment used, tasks checked and any known limitations. If a required mechanic is unavailable, defer the affected assessment rather than certify an unobserved outcome. A material game update calls for a check of affected tasks, not cancellation of earlier academic achievements.
Your brief
For civil coordinators handing work between recovery, transport and reception services.
The case uses the present 2956 responsibilities of Solace Horizon Relief, CradleFleet and HavenGate. It is a teaching extension, not a reconstruction of a historical evacuation.
Arrival is accepted; onward places are not
Practice case · CS 260 · 2956 teaching edition
- Solace hands four participants to CradleFleet for transport after the agreed recovery drill.
- CradleFleet can carry four. HavenGate acknowledges all four on the reception list.
- HavenGate can plan onward places for two in this case; the other two need a later decision.
Before you begin: entry and equipment
Complete these courses
Bring or arrange
The Solace–CradleFleet–HavenGate case and a shared reception record.
The organizer must confirm equipment access before booking. No ship purchase, pledge tier or donation is required.
Technical knowledge and game skills
Practical instruction revision 1 · 9 October 2026
Sustaining a relief group in the game
Inspect the receiving location
Confirm landing access, breathable areas, usable medical care and routes to supplies at the proposed reception site. A map label does not establish that the group can enter or use every service. Walk one person’s journey from ramp to reception and identify where a mobility limitation or missing permission stops it.
Supply immediate playable needs
Organise environmental equipment, food, drink and transport around the actual session. Demonstrate item transfer and confirm that recipients can equip or use the item. Keep helmets on until breathable conditions are confirmed. Medical supplies and symptom relief support movement, but do not erase the need for a bed that can heal an injury.
Separate implemented services from the scenario
Record live transport, item transfer and medical interactions as observed actions. Treat housing allocations, civic placements or longer-term settlement promises as tabletop arrangements unless that exact service is playable and demonstrated. A relief plan can be rigorous without pretending the game implements a permanent resettlement system.
Practical drill
Inspect a reception site, transfer a small practical supply kit and trace one passenger with a simulated mobility limitation to appropriate care. Record onward arrangements separately from completed game interactions.
Observed-skill checks
- Access and essential services are physically checked.
- Recipients can actually use the delivered supplies.
- The record clearly distinguishes live assistance from tabletop commitments.
Use these checks to document the technical evidence supporting the course outcomes in your agreed role. Record what you personally performed, what assistance you needed and what remains unobserved. A discussion or simulated action does not certify live equipment handling; Crew Support evidence does not confer Pilot qualification.
Game references and build-sensitive details
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 — 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.
- Star Citizen Wiki — Cargo
SCU, container geometry, grids and ownership. The page also contains obsolete automatic-loading descriptions and future design intentions; these are not instructions for the present cargo interface.
- Star Citizen Wiki — 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.
Check the official LIVE release notes and record the session build, equipment and observed limitations before practical sign-off.
Learn the method
1. Name the next service and receiver
Solace Horizon Relief handles the recovery and medical-reception side of the case; CradleFleet handles passenger carriage; HavenGate handles onward reception and resettlement planning. Confirm the role accepting the next task, not just the institution named on the destination.
A service chain transfers responsibilities, not merely lists of names. Ask each receiving role to state the task it accepts and the limit of that acceptance. In the case, transport may end at reception while onward placement remains a separate decision; make that boundary visible before the flight is treated as the end of assistance.
- Practise
- Map the handovers across the three services.
- Ready when
- Every stage has an accepting role and a clear limit to what it can provide.
2. Give unmet needs a next decision
List what cannot be provided now, who will follow it up and when the receiving team will review it. Keep a deferred need separate from a completed transfer. Use the case information rather than asking participants for private histories.
Use an open-needs register with a specific next action, responsible role and review point. “Awaiting assistance” does not tell the next coordinator what to do. Prefer “Onward place unconfirmed; reception coordinator to request capacity before the next movement brief,” which preserves both the gap and a practical route to resolving it.
- Practise
- Prepare the open-needs list.
- Ready when
- Every unmet need has an owner and a practical next review action.
3. Match the record to the work performed
Distinguish the passenger movement you actually conduct from the reception and resettlement decisions discussed at the table. Record each for what it demonstrates. A well-written reception plan is useful work, but it is not proof of a service or mechanic that was never performed.
Use the fictional reception setting to examine professional obligations without inventing a game service. Live movement, tabletop allocation and a proposed onward arrangement are different kinds of evidence. The value of the conference is its coherent plan and accepted responsibilities; it need not claim that an unimplemented settlement system performed the work.
- Practise
- Mark which parts of the relief chain were performed and which were discussed.
- Ready when
- The record accurately describes the delivery method and observed work at every stage.
A worked decision
CradleFleet completes the flight. HavenGate accepts a reception planning task but has not assigned onward places. The receiving record keeps that need open.
- Confirm the Solace-to-CradleFleet handover and carry the relevant game-status limits into transport.
- Record four received only after the reception check. Keep the separate onward-placement field at two confirmed and two pending.
- Give the pending pair a HavenGate follow-up role and next review. Do not retain the task vaguely with “civil services” or call the transport incomplete when reception itself was accepted.
Try it yourself
Map the three handovers and complete the open-needs register. Identify which actions you performed and which reception decisions were tabletop work.
What changes during the exercise
The receiver accepts arrival but cannot commit to the next service.
Keep this record
- Sending service / receiving role / exact task accepted
- Transported / received / onward arrangement status
- Unmet need / responsible service and contact / next review
Plain-text worksheet with this case, your working fields and the assessment criteria. Fill it in privately; downloading does not submit work or record completion.
Check your reasoning
HavenGate has acknowledged the passenger list. Does that settle onward placement?
Compare your reasoning
Not unless it accepted that specific task and confirmed the arrangement. Record what it accepted and leave the placement need open with an owner and next update.
Answer first, then compare. In a later session, explain the decision using a changed case without referring to this answer.
How completion is judged
A receiving chain, open-needs list and clearly scoped case conference.
The assessor checks your own work against all three “Ready when” criteria above. Use the observed-skill checks in the technical chapter to establish the applicable game-handling evidence in your agreed role. A successful team result does not replace an action they did not observe.
Findings, another attempt and review
- Demonstrated
- Your observed work meets the criterion in the agreed role.
- Further practice required
- The assessor identifies the observed gap and the specific practice needed.
- Interrupted
- Equipment, staffing or personal circumstances prevented a valid assessment. This is not a failure.
- Not assessed
- There is not yet enough evidence for this outcome.
A fresh attempt
Let HavenGate accept all onward planning but reduce CradleFleet capacity. The unresolved task should move to the correct service.
Reassess the missing outcome, plus any linked skill that needs new evidence. For prior learning, compare existing work with the same criteria and observe any missing practical action.
Ask for the reasons behind a finding. Reviews must be handled by someone independent of the original decision; defer the review if that person is not available.
Read the Academy Ordinance and review rulesFor instructors
Session setup and coaching
Prepare the session
The Solace–CradleFleet–HavenGate case and a shared reception record.
Assign crew stations and tell each learner what they will practise. The instructor must be able to hear the calls and see the action being assessed. Brief the callsigns, channel, route and expected duration. Replace the example locations with the places you will actually use.
- Ask the learner to explain the relevant earlier procedure without notes; correct any gap before the practical.
- Teach and demonstrate the technical chapter using the actual game indications. Run its drill with feedback before connecting those skills to the three methods and worked decision. Use the observed-skill checks to identify missing handling evidence.
- Let the learner complete the normal procedure first, then introduce the change described in the exercise. Give them time to respond without coaching. Keep unrelated failures out of this attempt.
- Record the learner's action against each criterion. Give one specific next step for any gap and transfer unfinished operational work before closing.
What to watch for in CS 260
Ask exactly what each acknowledgement accepts. A signature for arrival is not acceptance of every future service.
If another attempt is needed
Let HavenGate accept all onward planning but reduce CradleFleet capacity. The unresolved task should move to the correct service.
Running the exercise
Before the crew assembles, try the exercise in the ship you intend to use. Check station access, equipment and the route. Brief the crew on any faults that affect the task. If a bug prevents someone completing it, repeat that part once it works; do not record a failure for a broken mechanic.
Brief the command “Stop exercise” before starting. On that call, cease the drill and tell the instructor what needs attention. For weapons practice, identify the participating ships and crew; anyone else entering the area is a reason to hold fire.
Session administration: use player handles in your notes. Ask before recording voice or video, and agree when the recording will be deleted. Academy rules and review procedure.
Sources and edition
Lex Astra · School of Civil Practice
Course CS 260 · edition 2956.3 · 2956 teaching edition · revised course text.
Case CS–3: one berth remaining
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.
Professional references and instructional revision
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.
Editorial context and teaching basis
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.
Your session brief names the instructor, the crew assignments and the equipment provided. Contact the teaching office above to arrange a place.
Course-text revision: 8 October 2026. Educational references were reviewed for the framework on 8 October 2026; they inform the teaching approach, not external accreditation or current game-capability claims.
Teaching research and its limitsWhere this leads
Civil Services requirementsCourses that use this work
Course records retain the edition and role assessed. New teaching text does not erase earlier achievements.