Product Tour
User Guide
OpsFlow Product Tour
This page explains the exact working flow for a User: create the project, add the document, keep tasks moving, record site progress, and close the work cleanly.
AudienceUser
FlowProject to Completion
GoalStandardise daily usage
FormatBook-style walkthrough
Use CaseOnboarding and refresher
Chapter 1
Create the Project First
Every document and task should sit under the right project. Start here so reporting, tracking, and client visibility stay clean.
Open Project Setup
What To Do
1
Create a new project.Enter the project name and connect it to the right client before documents start coming in.
2
Check the project owner and scope.Make sure the project is the correct operational container for the upcoming document and task flow.
3
Use one project per real delivery job.Avoid mixing multiple jobs into one project because downstream task tracking becomes noisy.
Admin Check
Client is correct.
Project naming is clear and searchable.
The job is ready to receive documents.
Suggested Screenshot
Projects add page with the key setup fields visible.
Chapter Image
Create Project
Highlight in screenshot
Project name field
Client assignment
Create/save button
Chapter 2
Create or Upload the Document
The document is the trigger point for operational work. Once uploaded properly, OpsFlow can generate and track execution around it.
Open Document Upload
What To Do
1
Upload or create the document.Use the document upload page and assign it to the project you created in Chapter 1.
2
Review key fields.Check internal number, due date, client, and document type before saving.
3
Confirm the document becomes operational.Once approved or active, task generation and execution tracking should start from here.
Admin Check
Project link is correct.
Due date is realistic.
Document detail page shows the correct file and task status.
Suggested Screenshot
Document upload or auto-add page after project selection.
Chapter Image
Create Document
Highlight in screenshot
Upload area
Project and client fields
Due date and save action
Chapter 3
Update Tasks During Execution
Tasks are the operating engine. Users do not need every detail, but they do need to make sure status is current and delays are visible early.
Open Task View
What To Do
1
Open the document task view.Use the grouped task page to see all execution items linked to the document.
2
Update only what changed.Move tasks from not started to in progress, then to completed as field work moves.
3
Watch late or stuck tasks.If tasks stay pending too long, escalate before the document due date is at risk.
Admin Check
Pending tasks are shrinking, not growing.
Task owners are updating progress regularly.
Critical documents are reviewed from the summary page.
Suggested Screenshot
Grouped task view showing status updates for one document.
Chapter Image
Update Tasks
Highlight in screenshot
Task status area
Pending versus completed counts
Any item needing admin follow-up
Chapter 4
Upload Progress Updates
Use progress albums to show field evidence. This is the cleanest way to record site updates, share them with the client, and maintain a clear timeline.
Open Progress Upload
What To Do
1
Open the document’s Update Photo page.Create a dated progress album such as ProgressUpdate-YYYYMMDD.
2
Upload photos for the latest work done.Keep one album per visit, milestone, or reporting day.
3
Share only when needed.Use the client link or WhatsApp share when the update is ready to be sent outside the team.
Admin Check
Album names are date-based and consistent.
Photos reflect the latest site condition.
The document detail page shows the progress albums clearly.
Suggested Screenshot
Progress upload page with album name and image queue visible.
Chapter Image
Upload Progress
Highlight in screenshot
Dated album name
Upload action
Client-share or album preview controls
Chapter 5
Close the Document Properly
Completion should happen only after execution is genuinely done. The admin goal is to close with confidence, not just clear the screen.
View Completed History
What To Do
1
Check all linked tasks.The document should have no pending task left before you treat it as complete.
2
Confirm progress evidence exists.Make sure the final work condition is visible in the uploaded progress albums.
3
Review the history page.Completed documents should appear in history as a clean completion record.
Admin Check
No pending operational work remains.
Document detail, tasks, and progress story are aligned.
The job is ready for reporting and audit review.
Suggested Screenshot
Completed history or final document state showing clean closure.
Chapter Image
Complete Document
Highlight in screenshot
Completed document reference
All work finished
History record for audit trail
One-Page Flow
How Users Should Use OpsFlow
This is the simplest mental model for daily usage.
Step 1
Create Project
Open the job container first.
Step 2
Create Document
Upload and confirm the working document.
Step 3
Update Tasks
Keep execution status honest and current.
Step 4
Update Progress
Upload dated site evidence as albums.
Step 5
Complete
Close only when tasks and progress are fully aligned.