Built By DAO
How the Work Gets Coordinated
Task requirements, project review states and resource approvals: how coordinators follow the work from an agreed result to completion.
An Agreed Result and a Team to Carry It Out
Coordination starts with knowing what a project needs, the skills required and what the reviewer will accept as complete. Built By DAO organizes that work through project working groups, bringing trade, technical and operations capabilities into a team.
The operations guilds include project management, finance, communications, facilitation and documentation. They support those skills across projects, while each working group coordinates the particular work in front of it. The dashboard gives that team task requirements, review states and project progress to follow.
Dashboard Previews
Task Details
Task scope, deliverables and review states in the dashboard preview.View Full Preview
Community Workshop
Project milestones and deliverables in the dashboard preview.View Full PreviewThe Task Definition Comes First
The task definition gives the member and reviewer a shared basis for assessing the result. It also tells a coordinator what capability and responsibility the work requires.
Scope
The work to be completed and the expected result.
Deadline
When the agreed result is due.
Skills
The practical capability needed to carry out the work.
Rank
The required organizational responsibility, separately from craft proficiency.
Read the Review State Behind the Project Summary
The Task Details preview shows two approved deliverables and another awaiting review. The project preview shows completed milestones alongside a welcome guide still awaiting review. These are sample project states: they illustrate how completed work and an open review can appear within the same project.
Credit has a further confirmation step. Accepted work can still be awaiting an authorized funded release, good-standing checks or confirmation. A coordinator following those states can distinguish work still being assessed from an accepted result with a remaining credit condition.
Know Which Approval the Work Needs
Ordinary project work runs through operating teams. Major decisions use the proposal system, with the required houses determined by the category. Coordination includes knowing which decisions belong within the project workflow and which need wider approval.
Resource use also depends on the treasury’s allocations, limits and required roles. An authorized funded release is required before contribution credit issues. A task definition, an accepted result and permission to use resources each need to be followed through the appropriate process.
The Foundry’s Planned Coordination Functions
The planned Foundry would bring two flows together: materials being prepared for construction and members learning skills they could apply to site work. Inspection, grading and inventory would prepare materials, while orientation in the Hall and hands-on learning in the Workshop would prepare people.
The Station would support operations, logistics and project coordination across the hub. The Loft would support administration and planning. Detroit and Chicago are the likely first two hub cities; no site has been chosen and no hub is open.
Coordination Is Recognized as Contribution
Eligible, reviewed coordination work follows the contribution process alongside technical work and the trades. It can carry standing and governance weight. The credit cannot be bought, sold or transferred, has no member cash-out and is not pay, legal equity or a direct property share. Recording contribution does not create a job.