A Portwest FR94 Bizflame 88/12 FR Coverall submittal gives a reviewer the information needed to consider a proposed garment before purchasing. Its purpose is to connect the exact product, the project’s requirements and the evidence used for acceptance.
Assemble the product information
Start with the manufacturer’s model reference and the supplier’s offered variant. The Portwest FR94 page provides product information and document links. Include the documents your reviewer requests rather than assuming a catalog image is sufficient.
Label the package with the project or internal request reference. Keep commercial information identifiable but separate so a technical reviewer can assess the garment without confusing a price revision with a product change.
Present requirements as review questions
List the requirements supplied by the responsible safety team and identify where the supporting information is located. Where an answer is missing, leave it visible as an open question.
Avoid filling gaps with an inferred claim. If the supplier needs to provide additional information, record the question and return it for clarification. The resulting response should remain attached to the same product line.
Control revisions and acceptance
Give revised submittals a clear date or revision reference. Explain which offered details changed so the reviewer does not have to rediscover the difference. Keep earlier records available where your organization’s document process requires them.
Once accepted, carry the approved model and variant into the purchase request. The order should not introduce a new garment description that was absent from the reviewed package.
What belongs in the final acceptance record?
Identify the accepted product, the documents reviewed, the decision date and the responsible reviewer. Include any conditions that must be satisfied before release or issue. This creates a useful handoff from product review to procurement without turning the supplier’s promotional wording into the approval itself.
Assemble an FR94 submittal that another reviewer can follow
A product submittal should connect the offered garment to the decision the employer needs to make. Start with the full FR94 identifier, the exact variant schedule, current manufacturer documents, and the stated requirements. Keep supporting information organized by question rather than sending an unexplained collection of links.
For an illustrative review, include separate entries for model identity, required claims, size and length selections, care information, and proposed decoration. Mark which items are accepted and which still need clarification. This prevents one approval note from being interpreted as acceptance of every later change.
Where a supplier description differs from the manufacturer wording, retain the clarification that connects them. Do not rewrite an unfamiliar claim into a stronger statement or assume an omitted detail applies. Ask TECHACS to identify the relevant evidence for the offered garment.
After approval, attach the accepted submittal reference to the quotation and receiving schedule. If the offered model or variant changes, return the affected information for review. A well-organized FR94 submittal should remain useful after the original buyer is no longer available to explain the selection.
Review the documentation as a connected package
A submittal works best when a reviewer can trace each claim to the proposed garment. Start with a cover sheet identifying the project, supplier, manufacturer and style. Follow it with the actual supporting documents and a concise list of the requirements being reviewed. Keep the supplier’s commercial offer identifiable, but do not use a price revision as the technical approval record.
Check the relationship among document names, model identifiers and garment labels. If the evidence describes a product family rather than the exact offered item, ask the supplier to explain the connection. Record the answer with the original question. An unexplained difference should remain open rather than being resolved by a buyer’s assumption.
Give revised packages a date or revision identifier. State what changed, such as a different offered variant or replacement document, so the reviewer does not have to rediscover it. Preserve the acceptance conditions along with the decision.
At order release, reference the accepted package rather than attaching several inconsistent versions. Receiving staff need the final model description and the documents required at delivery. They should not have to repeat the technical evaluation, but they do need a clear route for reporting a label, model or document that does not match the accepted record.
Build a product identity record that survives a reorder
A useful product record connects the name people recognize with the identifier a supplier actually uses. Keep the manufacturer, style, offered variant and internal item number in separate fields. Attach the source document and the date it was reviewed. This avoids turning a shortened catalog title into the only description available when someone orders a replacement several months later.
When an employee provides a photograph or an old invoice, treat it as identification evidence rather than a complete new specification. Ask which details are readable, which are missing and whether the current request is intended to match the original garment. Resolve an unfamiliar suffix or a different style number with the supplier. Do not assume that two products are equivalent because they share a collection name or similar appearance.
Maintain an alias list for historical descriptions, but give new orders one accepted name. If the purchasing system limits the length of a description, keep the full specification in the linked item record. At receiving, staff should be able to match the delivered identifier to that record without interpreting marketing language.
An effective record also identifies who may approve a substitute. This makes a proposed change a visible decision instead of allowing it to enter the program through an informal email or a handwritten stockroom note.
Separate mandatory specifications from purchasing preferences
Write the requirement in three parts: the product or performance requirement, the requested variants and the commercial conditions. This gives reviewers a clear way to distinguish a technical change from a change in quantity or delivery. A color preference, for example, should not be mixed into the same sentence as a mandatory garment standard unless both have the same approval status.
For each mandatory item, record the evidence the supplier must provide. That might be a manufacturer document, label information or another record requested by the responsible safety reviewer. Identify the applicable edition where the organization’s specification requires one. Avoid making the buyer guess which edition was intended from an old screenshot.
Use a separate column for proposed alternatives. The supplier can then offer an option without silently replacing the requested garment. Require the alternative to identify its own model and documentation rather than referring only to the original product’s claims.
Before release, have the person preparing the purchase order compare it with the accepted quotation. Check that open technical questions have not disappeared during revision. The final instruction should describe what has actually been approved, while unresolved preferences remain visible for a separate decision. This structure makes the specification usable by purchasing, the supplier and receiving staff alike.
Ask the supplier to connect certification evidence to the garment
When a purchasing requirement calls for certification, request the evidence your organization needs for the exact offered product. A logo in a catalog or a general standards list may help identify the question, but it should not be treated as the complete review file.
Ask the supplier to identify the manufacturer, product designation, applicable certification information and label details. If the paperwork names a broader range, request an explanation of how the proposed item falls within it. Keep the explanation with the original documents instead of relying on an undocumented telephone assurance.
Distinguish the roles of a standard, a manufacturer and a certification organization. Do not add a particular certifier’s name to a product description unless that relationship has been verified. Likewise, avoid describing a garment as certified to a workplace program when the available evidence does not support that statement.
Give the responsible reviewer the complete package and preserve any acceptance conditions. If the offer changes after review, determine whether the new item requires a fresh submission. At delivery, compare product identifiers and supplied information with the accepted record. This provides a practical chain from the requirement through the offer to the garment actually issued, without asking receiving staff to perform a new technical certification assessment.
Review decoration before adding it to the purchase order
A company logo introduces another specification into the garment order. Identify the requested artwork, dimensions, placement, and decoration method, then ask for confirmation that the proposed treatment is appropriate for the exact garment and the employer’s requirements. A familiar logo from a previous uniform program does not establish that a new application is acceptable.
Provide a controlled artwork file and keep employee names or department identifiers in a separate approved schedule. Confirm spelling and placement before authorizing production. Where a sample or proof is required, retain the approved version with the order so the receiving team has a reference.
Do not assume that embroidery, transfers, patches, or repairs preserve every garment claim without review. Ask the manufacturer or responsible supplier for applicable instructions, and involve the employer’s reviewer when the proposed treatment affects the specified arrangement. Avoid making unsupported promises about certification after decoration.
Decoration can also change commercial terms. Ask whether approval dates affect the schedule and whether personalized garments have different exchange conditions. Resolve sizing before final customization wherever the ordering process permits. A correct logo on the wrong size still leaves the wearer without the intended issue.
Request your TECHACS quote
Review Portwest FR94 at TECHACS and request a workwear quote. Send your approved specification, quantities by size and fit, requested colors, delivery ZIP code and required date. TECHACS will confirm pricing, availability and terms for the request.