Zeiss LSM 980 Confocal
Asset ID: MIC-012
Reservation (Booked)09:00 - 13:00 (4h)
Actual Usage (Logged)08:45 - 15:15 (6.5h)
2.5h overage detected. Usage record and chargeback updated.
SESSION OPERATOR
SJ
S. JenkinsRESPONSIBLE ENTITY
NSF-GRANT-2023-BUSAGE RECORDS AND ACCOUNTABILITY FOR SHARED EQUIPMENT
Usage Records & Accountability
Dockyard helps shared equipment facilities create a trusted usage record so operators can connect machine activity to the right team, project, startup, or cost center without spreadsheet reconstruction.
- Create a durable record of what happened at the machine
- Assign sessions to the right responsible entity
- Use trusted records for utilization and downstream reporting
When The Record Stops At The Reservation, Accountability Breaks
Shared equipment facilities do not just need calendar history. They need a trustworthy record of who used the machine, when the session happened, and which team, project, startup, or cost center should own that usage.
When that record has to be reconstructed from reservations, notes, and spreadsheets, accountability gets weaker and reporting becomes harder to trust.
Why Spreadsheets And Simple Calendars Break Down
The record often stops at the reservation
Facilities can see planned time without preserving the operational record of what actually happened.
Responsibility gets reconstructed after the fact
Who booked the slot is not always the team, project, startup, or cost center that should own the usage.
Reservation history is not enough for accountability
A calendar can show intent while still leaving operators without a durable usage record tied to the right entity.
Month-end reporting depends on spreadsheet reconstruction
Operators are left stitching together notes, exports, and memory to explain what happened.
What Facilities Actually Need To Know
- Who used the asset
- When the session actually started and ended
- Which team, startup, project, or cost center owned that usage
- What record should drive utilization, reporting, and downstream financial outputs
Responsible Entity Example
A materials engineer books the microscope, but the usage belongs to the resident startup sponsoring the work. The operational record needs to preserve both the session operator and the responsible entity so reporting does not have to be reconstructed later.
Usage Session Record
OperatorDr. Sarah Jenkins
Linked ReservationRES-2041
Responsible EntityNSF-GRANT-2023-B
Actual Runtime04h 12m
Booked vs Actual14:00-17:00 vs 14:02-18:14
Dockyard Creates A Trusted Usage Record
Dockyard distinguishes reservations from actual usage sessions and preserves responsibility alongside the session record. That makes it easier to explain what happened, assign ownership correctly, and use one trusted record for utilization and downstream reporting.
Link Intent To Activity
Keep reservation context connected to the session record instead of leaving it isolated in the calendar.
Preserve A Trusted Record
Preserve machine-level usage as the operational source of truth rather than relying on notes and reconstruction.
Assign Accountability
Use the same record to support responsible-entity reporting, utilization visibility, and downstream outputs.
What A Trusted Usage Record Changes
Less manual reconciliation
Clearer usage accountability
More believable utilization data
Better reporting by responsible entity
Frequently Asked Questions
A calendar can show planned activity, but it does not create a durable operational record of who used the machine, when the session happened, and which entity should own that usage.
Yes. Dockyard can preserve usage alongside the responsible team, startup, project, or cost center so accountability is not reconstructed after the fact.
Yes. Booking calendars show planned time, but they usually do not produce the trusted usage record needed for accountability, utilization visibility, and downstream reporting.
Yes. Even without in-product billing, facilities benefit from a trusted operational record for utilization analysis, reporting, and downstream financial workflows.
See How Dockyard Turns Machine Activity Into A Trusted Record
If your current workflow depends on calendar history and spreadsheet cleanup, Dockyard can help you create a clearer usage record and stronger accountability for what happened at the machine.
Request Early Access