FMTTI Draft Test Report: The Comment Window Explained
Once your machine has actually been through testing at the institute, there's still one stage left before you get a report you can use for a subsidy claim or a tender: the Draft Test Report, or DTR.
It's a short but important checkpoint, and it's the last point where you, as the manufacturer, get formal input into the report before it's finalised. Here's how it fits into the overall sequence.
Where the DTR sits in the process
After your equipment has been received at the institute and a Test Engineer has been assigned, the actual testing happens — physical performance, endurance, safety checks, whatever the category requires. As results come in, the Test Engineer uploads intermediate results along the way.
Once testing is complete, the Test Engineer prepares the Draft Test Report. This isn't the final document — it's a working version that gets internal sign-off first. The institute's Admin reviews and approves the DTR before it goes anywhere near the manufacturer.
The comment window
Once the DTR is approved internally, it's shared with the manufacturer. This is your window to review the findings and submit comments — questions, clarifications, or objections to how something was recorded or tested.
Worth noting: the exact number of days allowed for this comment window isn't something we can state precisely here — it varies, so confirm the specific deadline with your institute when the DTR is issued to you. What matters is what happens with the comments once you've submitted them.
What happens to your comments
Your comments don't go straight back to the Test Engineer. They're submitted through the system, and the Admin forwards them on to the Test Engineer for examination. The Test Engineer then reviews what you've raised and, taking that into account, prepares the Final Test Report (FTR).
That sequence matters: comments get examined, not just filed. If there's a genuine discrepancy — a spec that was recorded incorrectly, for instance — this is the mechanism for catching it before the report becomes final and permanent.
After the Test Engineer prepares the FTR, the Admin examines it, then approves and releases it. At that point, the manufacturer receives the Final Test Report — the document you'll actually use for scheme eligibility, tenders, or general proof of performance.
What if you miss the comment window
The process is built around a linear, one-way flow: DTR issued, comments submitted, comments forwarded, FTR prepared. If the comment stage passes without a response from your side, there's nothing in the process that holds the report back waiting for you — the Test Engineer moves forward and prepares the Final Test Report based on the draft as it stands.
In practice, that means the DTR stage is your one real opportunity to flag something before it's locked in. Once the FTR is released, it's the official record. So it's worth treating the DTR review as a genuine checkpoint rather than a formality — read it carefully, check the figures against what you expected, and raise anything that looks off within whatever window the institute gives you.
Notifications at every step
One practical thing worth knowing: the system sends SMS alerts and email notifications to the applicant at every stage of the process, including when the DTR is ready for comment. That's useful, but it also means the responsibility sits with you to check those notifications and act promptly — a missed email is still a missed window.
Where this fits into the bigger picture
The DTR-to-FTR stage comes near the end of a longer chain: application, scrutiny, fee verification, sample allocation, testing, and only then the draft and final reports. If you're coordinating a test and want help understanding where you are in that sequence, or making sure documentation and comments are submitted correctly and on time, that's the kind of process navigation AgPro Consulting helps manufacturers with — guiding and liaising with the institute throughout, while the testing itself is always carried out by FMTTI's own engineers.