Reporting
Prepare Investor & Board Reports
Turn reviewed financial context into a reporting output, then make a deliberate decision about what to export or share.
In this guide
Prerequisites
- Reviewed cash, runway, revenue, cost, and planning context for the reporting period.
- A clear audience and disclosure boundary.
- A workspace user responsible for reviewing and initiating the export or sharing action.
Generation is not distribution
RunwayCal can prepare supported reporting outputs. A human still reviews the material and chooses whether it should leave the workspace.
Human-controlled reporting path
- Review financial context
- Prepare report
- Review audience and disclosure
- Export or share
Prepare the reporting output
Open Investor & Board Reports
Use the reporting area available in the current workspace. Do not rely on an older Mission Control sharing path unless the current interface presents it.
Choose the supported output
Select the board deck, point-in-time PDF, or bounded viewer path available for the reporting job.
Review the financial context
Confirm cash, runway, realized revenue, costs, budget context, and eligible planning context included in the output.
Add or review narrative
Use operator narrative where the current reporting surface supports it. Keep explanation distinct from derived values.
Check the audience boundary
Decide which information the audience should receive and whether a retained file or bounded read-only view is appropriate.
Initiate export or sharing
Take the explicit action provided by the current product. Generation alone does not distribute the material.
Review what the output contains
| Item | What it means | Why it matters |
|---|---|---|
| Financial metrics | Supported cash, runway, burn, revenue, cost, statement, or variance context presented by the output. | Provides the quantitative basis for the conversation. |
| Planning context | Budget or scenario context included only where the output supports it. | Explains assumptions without turning hypothetical values into actuals. |
| Operator narrative | Human explanation, notes, or decisions added through supported fields. | Provides context that a metric alone cannot supply. |
| Branding | Workspace identity used where the current output supports it. | Does not change the underlying data or disclosure boundary. |
Use Board Access as a bounded read-only view
Board Access is a focused reporting window, not a second editable workspace. Review which supported modules are visible before granting access.
Editing, planning inputs, and workspace configuration remain outside the read-only reporting job. Follow current settings for creating, managing, or ending access.
This guide omits exact token expiry, revocation timing, login requirements, encryption claims, and delivery guarantees. Confirm current controls before a sensitive disclosure.
Understand files, viewers, and later data changes
| Item | What it means | Why it matters |
|---|---|---|
| Generated file | A retained output prepared from reviewed context at generation time. | Later workspace changes should not be assumed to rewrite an exported file. |
| Read-only viewer | A bounded product view controlled through current Board Access settings. | Its visible information may follow current viewer behavior rather than a static snapshot. |
| Later correction | A change to the underlying workspace after an output was prepared. | Review whether the report must be regenerated or access rechecked. |
Troubleshooting and common questions
| Item | What it means | Why it matters |
|---|---|---|
| A number looks stale | The workspace may have changed after the output was prepared. | Review the source and regenerate or refresh through the current workflow. |
| The viewer exposes too much | Visible modules may not match the intended audience. | Close or revise access before sharing. |
| The file and viewer differ | A retained file and current read-only view can represent different points in time. | State which output is authoritative for the conversation. |
| A recipient cannot open the material | Access or delivery requirements may differ by output type. | Use current guidance and avoid assuming a no-login or email-delivery guarantee. |