Financial Process: Difference between revisions
Jump to navigation
Jump to search
(→Links) |
|||
| Line 21: | Line 21: | ||
=Links= | =Links= | ||
*Reporting - [[OSE Financial Transparency]] | *Reporting - [[OSE Financial Transparency]] | ||
*See also [[OSE_Process_Map]] | |||
Revision as of 20:45, 21 October 2012
Process Design
Specifications
- Radical Transparency
- ongoing balance sheet updated 24 hours. Visible to Core Team. Shareable with outsiders on demand. Receipts in cabinet according to policy.
- Monthly income and expenses. Visible to world.
- True Fan Revenue - updated every month in a clearly visible graph
- 10 Month Budget is visible. Budget Review Committee meets every 3 months.
- Annual Reports Visible
- Budget Rationale - $2.1M+Org Infrastructure
- Prototyping Cost - Total prototyping money spent vs. number prototypes built. Goal: if the cost falls, that means we are succeeding at collaborative.mission-aligned development.
- Core Project Efficiency (total expenditures vs. prototypes built)
- Receipts saving policy
- Document Retention Policy clear
- Revenue generated from Product Sales.
Links
- Reporting - OSE Financial Transparency
- See also OSE_Process_Map