Rather than generating an entire document in a single step, users build their documentation gradually by running tasks, reviewing the outputs, refining inputs, and rerunning tasks when needed.
This allows users to progressively improve each section of the deliverable as their project information becomes clearer.
The Iteration Process
Most deliverables are developed using a simple workflow:
run tasks to generate sections of the document
review the generated outputs
refine supporting documentation or project context
rerun tasks to improve the content
This process can be repeated until the documentation reflects the intended outcome.
Improving Outputs Over Time
As projects evolve, new information may become available or existing details may change.
Users can continue refining their deliverables by updating supporting documentation, adjusting their approach, and rerunning tasks to produce improved outputs.
This ensures the documentation remains aligned with the latest project information.
Building Documentation Gradually
Because deliverables are structured into tasks, users can focus on developing one section at a time.
This allows complex documentation to be built in manageable steps rather than attempting to generate an entire document at once.
Users can return to specific sections whenever they need to make improvements.
Approving Deliverables
Once a deliverable has been completed and reviewed, it can be approved as part of the project stage workflow.
Approving a deliverable helps teams track progress and confirm that the documentation for that stage of the project has been completed.
This allows projects to move through stages while maintaining visibility over which deliverables have been finalised.