Summary
- Reports normally start as drafts and move through review, approval and controlled export.
- The report workflow should preserve revision history and make it clear which revision is current, draft, under review or approved.
Visual overview
Report lifecycle
A compact view of how report revisions move through the controlled workflow.
Draft
Creator completes report data
Submitted
Content is sent for review
Review
Reviewer checks technical content
Approved
Revision becomes controlled
Controlled export with verification
Work Order
WO-002 · Medium Twinarms
Customer: Twinz · Project: Delivery of Twinarms
Reports
5 / 7
created
Approved
2
ready for export
Review
1
waiting
Material
3"
Heat 1234
Planned work
Raw Material Receipt
Template linked to WO-002
Saw Process
Template linked to WO-002
Extrusion Process
Template linked to WO-002
Heat Treatment
Template linked to WO-002
Dimension Control
Template linked to WO-002
Non-Conformance
Template linked to WO-002
Package Report
Template linked to WO-002
Task help
Common tasks in this area
Open the task that matches what you are trying to do. The full article continues below.
Reporting
Create a controlled report
Use this when a Creator needs to create a new report under the correct job context.
Open
Reporting
Create a controlled report
Use this when a Creator needs to create a new report under the correct job context.
- Open the relevant Customer, Project and Work Order.
- Create a report from the correct template, or generate it from Scope of Work if planned reports are used.
- Complete report fields, tables, attachments and comments.
- Review validation feedback before submission.
- Submit the report for review when ready.
Reports should normally be created under a Work Order so job-specific context, validation and review requirements can be applied.
Reporting
Return a report to draft
Use this when a submitted report needs correction before approval.
Open
Reporting
Return a report to draft
Use this when a submitted report needs correction before approval.
- Open the submitted report revision.
- Review comments or validation issues.
- Return or reject the report according to the review workflow.
- Make the required corrections in draft.
- Resubmit the report for review.
When a report returns to draft, the next submission should create or refresh the controlled review snapshot.
Revision control
Create a new revision
Use this when an approved report needs a controlled update.
Open
Revision control
Create a new revision
Use this when an approved report needs a controlled update.
- Open the approved report.
- Create a new revision.
- Apply the required changes.
- Submit the new revision for review.
- Approve and export the new revision when complete.
Approved reports should not be silently overwritten. Use new revisions for controlled changes.
Standard workflow
- Create or open the relevant Work Order.
- Create a report from the correct template.
- Fill in report fields, tables, attachments and comments.
- Review validation warnings or blocking issues.
- Submit the report for review.
- Complete review and approval steps.
- Export the approved revision as controlled PDF.
- Verify the exported document using QR/public verification when required.
Draft stage
Draft reports can be edited before submission. This is where the Originator or Creator completes the technical content.
Drafts may reflect live template or context changes depending on how the report has been created and whether it has already been submitted.
Submitted and review stage
When a report is submitted for review, the system should preserve the review content. This may include a snapshot of report-critical template, context, validation, attachment and selected asset data.
Reviewers should assess the submitted revision, not an uncontrolled future version of the report.
Approved stage
An approved report revision should be treated as controlled documentation. Later changes should normally require a new revision.
Approved reports can be exported as controlled PDFs.