CubeSTEM Digital Twin · Report generator (V3.5C+, V3.6C navigation)
Local Mission Report Generator
Generate a clean, printable mission report from your in-browser mission evidence. Choose a template, enter your details, and save or print as PDF using your browser.
Continue your demo
Reports are browser-local. Capture mission evidence first, then paste into the form below. These links avoid dead ends after you print or save.
Space Mission Challenge Pack·Mission hub·Mission Realism Lab·Demo Pack
Try an example
Load a sample report
Load pre-filled example data to see what a completed report looks like. You can edit any field afterwards.
Step 1 — Choose a template
Report template
Select the template that best matches your mission session.
Step 2 — Your details
Student / team details
Enter your name and session details. Fields marked * are required for the preview.
Step 3 — Mission evidence
Paste your mission evidence
Copy evidence from the mission page and paste it here. You can also type a summary in your own words.
Tip: use the 'Copy evidence report' button on the mission page, then paste here.
What did the telemetry panel show? What was unexpected?
What fault or divergence did you identify? What was the cause?
Manual copy only — not auto-filled. Use /twin/missions/realism-lab or the CubeSat–Rover / Lunar Rover realism panels, then paste highlights here.
Step 4 — Preview
Report preview
This is how your report will look when printed or saved as PDF.
CubeSTEM Digital Twin · Local Workshop Artifact
Space Mission Challenge Completion
Fill in the form above to see your report preview here.
Local report only — not an official credential
Local workshop artifact only — not an official academic certificate, not verified by any server, not a formal grade.
CubeSTEM Digital Twin · cubetwin.space
Step 5 — Save or share
Print / export your report
Use your browser's print dialog to save as PDF. Or copy the text to paste into a document or email.
Browser print tip: in the print dialog, select Save as PDF as the destination. Uncheck "Headers and footers" for a cleaner output.
Local report only — boundary note
This is a workshop participation artifact, not an official certificate
- Local only. Reports are generated entirely in your browser. Nothing is sent to a server or stored in the cloud.
- Not verified. There is no server-issued certificate ID, no QR code verification, and no online lookup.
- Not an official grade. Scores shown are formative only — not linked to any academic transcript or official grading system.
- Manual teacher review. Sharing with a teacher or facilitator is done manually — copy the text, share the PDF, or show the screen. No automatic submission system exists.
- Not a credential. This report does not represent a formal qualification, accredited award, or certified STEM assessment.
- Teaching-grade simulation. All mission evidence is derived from a software-only, browser-local teaching prototype — not real satellite hardware or flight operations.
For teachers & facilitators
How to use local reports in a workshop
Workshop completion flow
- Students complete a mission session (Lunar Rover Rescue or CubeSat–Rover Relay).
- Students copy their evidence report from the mission page.
- Students open /twin/reports, choose a template, and paste their evidence.
- Students fill in name, team, date, and reflection.
- Students print or save as PDF for their records.
- Students share PDF with teacher manually (email, Google Drive, print).
What teachers see
- Evidence summary from mission activity
- Telemetry observation and divergence diagnosis
- Formative scorecard band (if entered)
- Student reflection
- Clear local-only boundary footer
What teachers cannot see
- No automatic submission dashboard
- No class roster in this tool
- No server-verified scores
- No live student tracking
Suggested classroom timing
Reserve 5–10 minutes at the end of a mission session for report generation. Students can complete it individually or as a team. For Space Mission Challenge Day events, the report generator serves as the final team deliverable before the debrief discussion.