Financial Process: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
=Process Design=
=Process Design Introduction=
 
#'''What?''' This process describes how all funds are handled, accounted, documented, and communicated, and RACI Cubed. Who is responsible/accountable/consulted/informed about the process? Use [[RACI]].
#'''When?''' - When is this process executed (day/time, frequency
#Time Requirements - when executed effectively, how long should this process take per day/week/month?
#Links - What are all the relevant links to the working substance, documentation database, source, list, account information, etc. that allows somebody to execute the process? Note: make special provisions for private database
#Execution - Step by step procedure for executing process
#Documentation - Produce documentation by which anyone in the world can observe the results, see if the process is being executed, and learn how to execute the process itself if needed?


==Specifications==
==Specifications==

Revision as of 20:48, 21 October 2012

Process Design Introduction

  1. What? This process describes how all funds are handled, accounted, documented, and communicated, and RACI Cubed. Who is responsible/accountable/consulted/informed about the process? Use RACI.
  2. When? - When is this process executed (day/time, frequency
  3. Time Requirements - when executed effectively, how long should this process take per day/week/month?
  4. Links - What are all the relevant links to the working substance, documentation database, source, list, account information, etc. that allows somebody to execute the process? Note: make special provisions for private database
  5. Execution - Step by step procedure for executing process
  6. Documentation - Produce documentation by which anyone in the world can observe the results, see if the process is being executed, and learn how to execute the process itself if needed?

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.

edit

Links