Combustible Gas Indicator Daily Bump Test Log
A daily bump test log for combustible gas indicators used before field deployment. It captures zero, span, battery, and pass/fail verification so crews can document the instrument is ready to use.
Trusted by frontline teams 15 years of frontline software
Built for: Utilities · Oil And Gas · Construction · Municipal Public Works
Overview
This template is a daily bump test log for combustible gas indicators used in field operations. It is built to document the checks that matter before a CGI is taken into service: zero response, span response, battery condition, and whether the instrument passed or failed the verification step.
Use it when crews depend on a gas detector for utility locating, leak investigation, confined space entry support, or other work where a false negative or dead battery would create a blocking safety issue. The log gives you a consistent record of who performed the check, which device was used, what gas standard or test method was applied, and whether the instrument was cleared for deployment.
Do not use this template as a substitute for full calibration, sensor maintenance, or manufacturer-directed service intervals. It also should not be used for unrelated atmospheric testing equipment unless your procedure explicitly treats it the same way. If the device fails the bump test, the correct action is to remove it from service and route it for troubleshooting or replacement, not to mark it as complete and continue. The template is most useful when you need a simple, auditable pre-use record that keeps the crew aligned on readiness and prevents an unverified detector from entering the field.
Standards & compliance context
- This template supports pre-use verification practices commonly used for OSHA permit-required confined space programs.
- It aligns with gas detection documentation expectations found in API RP 505-style field safety procedures.
- A bump test log does not replace scheduled calibration, manufacturer service, or site-specific maintenance records.
- If your procedure treats gas detection failure as a stop-work condition, the failed record should be handled as a blocking item.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Enter the CGI asset ID, model, location, date, and the person responsible for the check before the shift starts.
- 2. Verify the instrument powers on, completes the zero check, and responds correctly to the approved test gas or verification method.
- 3. Confirm the battery level is acceptable and record any alarm, sensor, or display issues that appear during the test.
- 4. Mark the device pass or fail, and if it fails, remove it from service and create the required maintenance or replacement follow-up.
- 5. Save the log with the crew record or equipment file so the pre-use verification is available for review, audit, or incident follow-up.
Best practices
- Run the bump test at the start of each shift before the detector leaves the truck or tool crib.
- Use the exact gas standard and procedure required by the manufacturer so the verification step is meaningful.
- Record a clear fail outcome and treat it as blocking until the instrument is repaired, recalibrated, or replaced.
- Keep the checklist items atomic so each response is a simple yes, no, or N/A and not a compound judgment.
- Tie the log to a specific asset ID so recurring sensor problems can be traced to one device instead of the whole fleet.
- Capture the battery check separately from the gas response check so low power does not get hidden inside a general pass.
- Add a photo or note when the detector is used in harsh weather, after impact, or after storage for an extended period.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records the daily bump test and calibration verification for a combustible gas indicator before it goes into service. It is meant for utility locators, gas crews, and other field teams that rely on a CGI to detect combustible atmospheres. The log helps confirm the instrument responds properly at the start of the shift.
How often should the bump test be completed?
Use it daily before field deployment, or more often if your site procedure requires it. Many crews run it at the start of each shift and again after a sensor fault, impact, or extended downtime. If the instrument is shared, the check should be tied to the specific shift or user handoff.
Who should run this checklist?
The person who will use the combustible gas indicator in the field should usually complete and sign the log, unless your procedure assigns that responsibility to a supervisor or equipment custodian. The key is that the DRI is clear and the verification step is done by someone trained on the device. If your program requires a second review, this template can support that without changing the core checklist.
Does this replace full calibration?
No. A bump test verifies that the sensor responds to a known gas concentration and that the instrument is functioning at that moment. It does not replace scheduled calibration, sensor replacement, or manufacturer maintenance intervals. Use this log alongside your calibration record, not instead of it.
What regulations or standards does it support?
It supports documentation practices commonly used for permit-required confined space work and gas detection programs, including OSHA-aligned pre-use verification and API RP 505-style gas detection checks. Your site may also have local utility, environmental, or contractor requirements that call for a daily record. This template helps capture the evidence without overcomplicating the workflow.
What are the most common mistakes with bump test logs?
Common mistakes include skipping the zero check, recording a pass without confirming the span response, and using a device with a weak battery. Another frequent issue is treating a failed bump test as a paperwork problem instead of a blocking condition that takes the instrument out of service. This template is designed to make those failures visible before the crew starts work.
Can I customize this for different CGI models?
Yes. You can add model-specific fields for sensor type, gas standard, alarm setpoints, or manufacturer instructions. If your fleet includes multiple brands, keep the checklist items consistent and use the log fields to capture the device-specific details. That makes the record easier to audit across crews.
How does this fit with digital workflows or integrations?
This template works well as a mobile form with photo attachments, timestamping, and equipment lookup. It can also be linked to asset records, maintenance tickets, or a corrective action workflow when a bump test fails. If your team uses a CMMS or inspection system, the log can serve as the front-end verification step before escalation.
Should a failed bump test stop the job?
Yes, if the CGI is required for the task, a failed bump test is typically a blocking issue until the instrument is corrected or replaced. The crew should not rely on an unverified detector for confined space entry, leak response, or other gas-related work. This template helps document the failure and the follow-up action so the issue is traceable.
Related templates
Ready to use this template?
Get started with MangoApps and use Combustible Gas Indicator Daily Bump Test Log with your team — pricing built for small business.
