Home/Process library/Technical reports at a technical services company
Process library · Technical servicesFrom site visit to approved report at a technical services company
The report is what the customer pays for. So every report passes a technical check, a language check and, when needed, a translation, before someone approves it and it is recorded with the project.
See the flow Map your own flow
In short
In this scenario a technical services company runs every technical report through a fixed route in M-Files. The report is linked to its project number while it is drafted, then goes to a technical reviewer, to a language check and, when needed, to translation. An approver signs it off, the report is converted to PDF, the signed work order is awaited where needed, and the approved report is recorded with the project. Each step notifies the next person. SoftAdvice designed and documented the process.
The report is the product
The site visit report is done. Technical check, proofreading and translation still to come. It has sat on a desk for a week.
Technicians and engineers visit sites, inspect installations and write a report. For the customer, that report is the result of the work: it has to be technically right, well written and sometimes in another language.
Without a process, drafts travel by e-mail, nobody knows who has the latest version, and a report can reach the customer before anyone checked it.
- Inspection and site reports
- A technical check by a second expert
- Language check and translation
- Linked to the project and the work order
What happens at every step of the work
The rhythm here is the project: every visit leads to a report, every report to a check, every approval to a closed file.
Every visit
A report is drafted
The report is created with its project number, so it belongs to the right project from the start.
Every draft
Technical check
A second expert checks the content and gets a notification when it is their turn.
Every checked report
Language and translation
Spelling is checked, and the report goes to translation when the customer needs another language.
Every approval
Signed off and recorded
The approved report becomes a PDF and is recorded with the project.
Every project
Work order closes the loop
Where a signed work order is needed, the report waits for it before it is final.
From draft to approved report, step by step
Every step has an owner. M-Files notifies the next person and keeps the history.
Draft
The author drafts the report in M-Files, linked to the project number. When it is finished, it moves on.
Technical check
A technical reviewer checks the content and corrects or sends it back.
Language and translation
A colleague checks spelling and style. When a translation is needed, the report goes to translation first.
Approve and record
The approver signs it off, the report is converted to PDF, the work order is awaited where needed, and the report is recorded with the project.
No report leaves without a second pair of eyes
The route is fixed: a report cannot be approved before it passed the technical and the language check. Each person sees only the reports that wait for them.
Every step is recorded, so the company can always show who checked and approved a report, and when.
- Fixed order of checks
- Notification for every next person
- Translation only when needed
- Full history per report
From mailing drafts around to a clear route
Engineers spend their time on the content, not on finding out who has the latest version.
Before
- Drafts sent back and forth by e-mail
- Unclear who checks what
- Reports sent before they were checked
- Report and project stored apart
Now
- One version, one route
- Each person sees what waits for them
- Approval only after every check
- Report recorded with its project
M-Files, linked to the project system
The report lives in M-Files; the project data comes from the project system the company already uses.
Workflow with notifications
Every state has an owner who is notified when a report waits for them.
Project number as metadata
Reports are linked to the project from the start, so everything about a project is in one place.
PDF and version control
The approved version becomes a PDF; earlier versions stay in the history.
Questions about this scenario
Can we skip the translation step?
Yes. Translation is only part of the route when the report needs another language; otherwise the report goes straight to approval after the language check.
Who can approve a report?
The approvers you define per type of report or project. The route makes sure the technical check and language check come first.
Does this help for ISO or quality audits?
Yes. The history shows for every report who checked and approved it, and when, which is the kind of evidence a quality audit asks for.
Is this only for technical services?
No. Any organisation whose report or deliverable must be checked before it reaches the customer can work this way, from engineering to consultancy.
How do your reports reach the customer today?
In Discovery we map your report flow and show where checks and approvals can be built in.
