With all of the information required, not so much by ISO 17025, but by the ASTM standards how do you keep from having a long confusing report to send to the customer? Does anyone have a templete or an actual test report (customer and other pertinent info blocked out of course) that you could post so I can get some ideas on how to "simplify" things and make a neater more reader friendly test report. Thanks. :bigwave:

Do you have a specific test in mind?

With all of the information required, not so much by ISO 17025, but by the ASTM standards how do you keep from having a long confusing report to send to the customer? Does anyone have a templete or an actual test report (customer and other pertinent info blocked out of course) that you could post so I can get some ideas on how to "simplify" things and make a neater more reader friendly test report. Thanks. :bigwave:
Most of the reports I see are overcomplicated, or omit significant information, so I don't have a form I can recommend, but I can give some generic guidelines as to what a report should include:

The name of the lab doing the work, and contact information
The name of the customer
The part number(s) and design record revision level(s)
The type of test being performed
The date(s) of testing
The standard(s) to which the testing is being performed and their change levels.
A summary of the test protocol if it's not evident from the standard.
Number of specimens or parts tested
The specific requirements (pass/fail criteria)
End-of-test pass/fail status, or specific results when no pass/fail criteria have been specified.
Photographs or other similar recorded information (chart recorder graphs, e.g.)
The name and signature of the person who performed the testing.
Type of equipment used, and calibration and traceability information when required
Lab accreditation information, if required.

I understand what is required in the test report. I was just hoping (long shot I know) that someone had a better idea for how to format the report. There isn't a specific test that I need this for. Actually, when there is only one test it isn't so convoluted. It gets messy when there are a dozen or so tests that need reported and it ends up being a short story by the time all of the ASTM requirements are listed not to mention the test results. I am interested in seeing how others set up their reports to get some ideas. My question isn't technical in nature. I just was hoping for ideas on how to simplify the report without leaving out pertinent information. Thanks for everyone's help. :thanx:

Yup - The above is a very good basic list, but again - What specific test? At one time in my life I was involved in a lot of different testing and there were a lot of different forms. For example, vibration test forms often had a 'graph' area where the spectrum/profile was sketched. Same with temperature cycling.

So - Everything JSW05 listed and then some.

EDIT ADD: You say no specific test - so you're looking for a face sheet?

What about making a test report (containing all the information JSW05) listed for each test. Then as a cover page for all the test reports together, make an 'executive summary' that contains:

The name of the lab doing the work
The name of the customer
The part number(s) and design record revision level(s)
A table containing Test Type --- Standard --- Pass/Fail --- Report Page #

That way, the customer could look at the summary sheet to get the basic results, and refer to the attached test reports for the nitty-gritty.

I guess it would be a face sheet. What we do now is list each test separately and all the requirements and then the test results and then list the next test and so on. It's just long and drawn out. I agree with the summary page. I'm just trying to get ideas for listing all of the requirements of the ASTM test. Maybe make each test a separate paragraph that lists everything required for that ASTM and just report the results in an Excel spreadsheet, possibly as an attachment, if applicable. Thanks again for the ideas.

I can give what I often see during assessments.....

The basic part of the report includes the information required by ISO/IEC 17025 clauses 5.10.2 and 5.10.3, and includes sampling information if sampling is performed, and description of the test method(s).

Appendixes will include specific test related information, such as pics, charts, DVD/CD with vids (often used in fire testing now), sub-contractor's reports, and other pertinent information.

This approach, while not universal, seems to be the most favored approach right now due to its simplicity.

The rest of the information reviewed during the assessment for that project, such as records of conversations with the client, is typically maintained in the project file.

Hope this helps.

Hershal