Rig Overview
π Notifications
Add Rig
Registered Rigs
Add Equipment Item
Current Inventory
Register Equipment Transfer Between Rigs
Select the item currently at the source rig, the quantity, and the destination rig. This moves stock from the source rig's inventory to the destination rig's inventory and logs the movement below.
Sending equipment to the Warehouse? Just pick your Warehouse location (π¬) as the "To Rig" below β it works exactly the same way and keeps a full record of what went to storage and when.
Sending equipment to the Warehouse? Just pick your Warehouse location (π¬) as the "To Rig" below β it works exactly the same way and keeps a full record of what went to storage and when.
β
Scrap / Retire an Item
Use this when an item is worn out, broken, or lost and is being permanently removed from service β not moved to another rig. It will be deducted from the rig's inventory and recorded in the Scrap Log below with the reason, so you always have a paper trail of what was disposed of, when, and why.
Scrap Log
Transfer History Log
Rig Licenses & Equipment Certificates
Track each rig's operating license card and inspection/calibration certificate, with expiry dates. Status turns amber when a date is within the warning window (set in Notifications) and red once expired.
Notification Settings
This browser can't send email automatically in the background on its own β clicking "Send Reminder Email" opens your email app with the alert summary pre-filled, addressed to the email above, ready for you to hit Send. If you want fully automatic emails (e.g. every morning, with no one needing to open the file), that needs a small backend β for example a Power Automate flow on SharePoint watching this data. Tell me if you'd like me to set that up as a next step.
β Items Needing Attention
π€ Team & Permissions
Honest limitation: this file runs entirely in your browser with no server behind it, so passwords and roles here are an organizational courtesy lock β they stop accidental changes and give you a "who did what" trail, but anyone with technical know-how could view the page source and bypass them. They are not real security. For actual access control (e.g. only specific people can ever open or edit the file), you'd need a backend β for example a proper login system, or a SharePoint/Power Apps version. Ask me if you want to explore that.
Shared App Password (optional)
If set, anyone opening this file must enter this password once before they can sign in as a person below. Leave blank to remove the password gate entirely.
Add Team Member
Team Roster
π Activity Log
Every add, edit, delete, transfer, scrap, and photo/document upload is recorded here with who did it and when (based on who is signed in) β a running accountability trail for the team.
Print Report
This generates a clean, printable report of all rigs, their photos, current inventory, and transfer history. Click "Print / Save PDF" β your browser's print dialog lets you print on paper or "Save as PDF".
Sharing This System on SharePoint / OneDrive
Important: this file stores its data locally in each person's browser (no shared server database). When published as a single HTML file on SharePoint/OneDrive, each person who opens it will see only their own local copy unless data is synced manually.
Recommended workflow for your team:
1. One person (e.g. the Studies office) keeps the "master" file and enters all rig/inventory/transfer data.
2. Use Backup JSON (top-right) regularly to save a snapshot, and upload that JSON file to the shared SharePoint/OneDrive folder alongside the HTML file.
3. Anyone who needs to view or update the latest data opens the HTML file, then uses Import JSON below to load the latest snapshot before making changes, and re-exports/uploads afterward.
4. Use Export Excel or Print Report any time for a read-only report to circulate.
If you'd like a real shared backend so multiple users can edit at the same time without manual JSON syncing, just tell me and I'll build that version.
Recommended workflow for your team:
1. One person (e.g. the Studies office) keeps the "master" file and enters all rig/inventory/transfer data.
2. Use Backup JSON (top-right) regularly to save a snapshot, and upload that JSON file to the shared SharePoint/OneDrive folder alongside the HTML file.
3. Anyone who needs to view or update the latest data opens the HTML file, then uses Import JSON below to load the latest snapshot before making changes, and re-exports/uploads afterward.
4. Use Export Excel or Print Report any time for a read-only report to circulate.
If you'd like a real shared backend so multiple users can edit at the same time without manual JSON syncing, just tell me and I'll build that version.