Projects are the backbone of work
Almost all work in GDDAO belongs to a project. Once you understand how projects connect other features, finding information becomes much more intuitive.
What belongs to a project?
A project usually includes:
- Goals and timeframe: What the project should achieve and how long it will run;
- Members and collaborators: Internal teams and external partners;
- Tasks: What needs to be done, who owns it, when it is due, and what must be delivered;
- Activities: Registration, check-in, volunteers, and field records;
- Questionnaires: Data collection and statistics;
- Knowledge: Documents, photos, recordings, and webpages;
- Outcomes: Reports, presentations, websites, and other outputs.
Activities, questionnaires, and the knowledge base are not isolated tools. They are different kinds of work within the same project. After you run an activity or collect questionnaire responses, AI can use that information directly in a report because it already shares the same context.
Tasks: make ownership explicit
A task can specify:
- An owner and deadline;
- Required deliverables;
- Completion criteria;
- Related files, recordings, or transcripts.
Members can view their tasks on the web or in the mobile app. When they upload deliverables, the information is automatically connected to the relevant knowledge base and audit records.
A project lifecycle
Create a project
→ Set the timeframe, goals, and owner
→ Create tasks or workflows
→ Assign members and external collaborators
→ Connect activities, questionnaires, and knowledge
→ Carry out the work and collect data
→ Let AI organize it and people confirm it
→ Produce a report, presentation, or website
Managers can review all related information and progress within the project at any time, without maintaining a separate Excel tracker.
Next step
To learn how uploaded information is retained and how its source can be found later, read Knowledge base and source traceability.