Skip to main content
GullySystem
Logistics

Resource and Room Booking for Self-storage and storage facilities

Maintain named storage-unit allocations without confusing a provisional hold, active occupancy or returned space.

Bookings and Appointments

Does this function belong in your operation?

Use for actual units or defined spaces assigned to customers. This is a space-allocation record; it is not an inventory of goods inside customer-controlled units.

A rental desk proposes a unit, confirms an allocation or receives a change or move-out request.

Allocate the actual storage unit with provisional holds, confirmed occupancy and maintenance blocks. An open-ended rental must stay occupied until the agreed release evidence exists; a projected departure is not an available slot. Track an accepted transfer across old and new units so neither is accidentally sold twice. The space record does not reveal what sits inside a customer-controlled unit.

Bring the records the workflow depends on.

  • Unit identifier, physical characteristics and maintenance blocks
  • Requested arrival, current renter and open-ended or agreed rental period
  • Provisional hold rules and accepted rental reference
  • Actual move-in, transfer and return-check evidence

Outputs to check

  • Named-unit allocation and occupancy register
  • Provisional holds and unresolved allocation conflicts
  • Returns awaiting readiness review and accepted transfer history

Follow the resource and room booking workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the actual unit

    Match the requested size and access needs to the physical unit. Record unresolved suitability questions and retain unavailable or occupied units outside available capacity.

  2. 2. Record a provisional hold

    Keep the requested arrival and agreed hold conditions identifiable. An enquiry, price discussion or forecast departure must not replace the current occupancy record.

  3. 3. Confirm the allocation

    Record the accepted unit and operative rental reference, with the responsible desk decision. Pass access requirements to the authorised process rather than assuming a calendar entry opens a gate.

  4. 4. Maintain active occupancy

    Record the actual move-in and accepted changes. An open-ended rental stays active until a reviewed release; any projected departure remains a planning assumption.

  5. 5. Transfer or release the space

    Check actual return and readiness before releasing a unit. For transfers, preserve both allocations through the handover so a customer’s goods are not left against an already reassigned space.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Rental coordinator

Records the requested unit and accepted allocation while keeping provisional customer interest separate from occupancy.

Site custodian

Confirms physical readiness and return observations, retaining maintenance blocks until the responsible review is complete.

Allocation reviewer

Resolves competing commitments and approves transfers with the customer’s accepted change and site evidence.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Existing renter has not vacated

Keep occupancy active and review the competing commitment; a forecast departure does not release space.

Unit condition prevents move-in

Retain the block and offer a reviewed alternative. Record customer acceptance before changing the assigned space or terms.

Customer needs a larger unit

Check the alternative’s readiness and agreed terms, preserving the old allocation until the transfer is acknowledged.

Reserved arrival is postponed

Apply the agreed hold-review process and preserve the customer’s revised request without silently cancelling an active rental.

Can this work independently?

The register can operate from a maintained unit list, rental references and site confirmations. Contract terms govern allocation changes; accounts handles charges. Door-access control and managed goods custody require separately defined processes. The calendar does not decide entry rights or property condition.

Systems and records it connects with

  • Contract management: Accepted unit, rental period and amendments.
  • Facility tickets: Readiness blocks and maintenance review evidence.
  • Invoice management: Approved chargeable period or transfer inputs, not inferred billing from a calendar colour.

Configure, test and introduce the workflow.

  • Reconcile the named unit list against current renters and a physical site review.
  • Define separate provisional, occupied, awaiting-return and unavailable states, including rentals without a fixed end date.
  • Test a delayed departure, blocked unit and overlapping transfer; compare both the allocation record and the customer agreement.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • An occupied unit cannot become available solely because a planned end date passes.
  • Transfers identify the old and new unit and the accepted handover status.
  • Readiness blocks remain visible alongside provisional demand.
  • Unit allocation does not create a verified goods list.
Self-storage and storage facilities

How the business operates.

A storage operator sells use of a defined unit, locker or allocated space under an agreed arrangement. The useful operating record connects the customer, actual space, access authority, rental terms and move-out status. In customer-access self-storage, staff do not have a verified inventory of everything behind the customer’s lock. A facility that receives and retrieves goods on the customer’s behalf has a different custody service requiring item-level handovers. This planning scope centres on space rental and facility administration; managed custody needs its own confirmed process before it is included.

Rental desk

Record requested space, intended use, arrival date and access needs before proposing a unit. Distinguish an enquiry or provisional hold from an accepted rental and physically ready space.

Facility operations

Maintain the unit register with actual dimensions, location and access restrictions. Staff record readiness checks and maintenance blocks; a unit that looks vacant on a calendar still needs physical review.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Unit identifier, site, actual size, location and access characteristics
  • Provisional hold, accepted allocation and physical occupancy status
  • Operative rental agreement, approved changes and notice evidence
  • Renter, billing party and separately authorised access contacts

Operational bottlenecks to check

A planned move-out becomes assumed availability

A new customer is promised a unit while the previous renter still occupies it. Keep the old allocation active until the site confirms return and readiness.

Access and payer identities are confused

A family member, mover or employee may need access without authority to change the rental. Record each permission against the actual customer instruction and the facility’s process.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Define the storage request

    Ask what space and access the customer needs and record declared intended use. Refer unsupported items or special conditions for review rather than treating every vacant unit as suitable.

  2. 2. Review the actual space

    Check the unit’s characteristics, current occupancy and readiness. Retain an alternative as a proposal until the customer accepts the changed location or terms.

  3. 3. Confirm the rental

    Record the accepted unit and operative agreement, with the actual payer and authorised contacts. Payment evidence and contract acceptance support the handoff but do not themselves grant facility entry.

  4. 4. Record move-in

    Acknowledge the allocated unit and agreed access arrangements, keeping existing observations visible. Customer declarations remain declarations unless the operator separately receives and checks goods under a custody service.

  5. 5. Maintain the active rental

    Route unit faults and access changes while accounts tracks agreed charges. Review a transfer or extension against both the current allocation and any competing commitment.

  6. 6. Review departure and release

    Keep notice, actual vacating and readiness for another renter separate. Confirm the returned space before releasing capacity and resolve remaining financial questions through the agreed process.

Industry reports to connect with

  • Unit occupancy and provisional holds by site and size
  • Expected departures awaiting actual return checks
  • Unavailable units with maintenance reasons and responsible owners
  • Rental charges, receipt allocations and disputed balances

Questions before implementation.

When should self-storage and storage facilities consider resource and room booking?

Use for actual units or defined spaces assigned to customers. This is a space-allocation record; it is not an inventory of goods inside customer-controlled units. A rental desk proposes a unit, confirms an allocation or receives a change or move-out request.

What should we bring to the requirements discussion?

Bring anonymised examples of Unit identifier, physical characteristics and maintenance blocks; Requested arrival, current renter and open-ended or agreed rental period; Provisional hold rules and accepted rental reference; Actual move-in, transfer and return-check evidence. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Maintain named storage-unit allocations without confusing a provisional hold, active occupancy or returned space. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Space allocation does not verify contents, activate access hardware, establish storage suitability or approve disposal of goods.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. An occupied unit cannot become available solely because a planned end date passes. Use this check when reviewing the first working version.

Talk to us

Discuss resource and room booking for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements