• Site Hold - this is a booking made via the Sites screen or a web interface.  It does not require you to create a contract first but just places a reservation on a site.
   
• Contract Hold - this is a booking within a user-created Contract.  The booking has a Hold flag placed on it, generally to indicate that we do not yet have a signed contract.

Site Holds:

Many companies will not use Site Holds at all.  The idea is to be able to quickly dive into Sites and place a reservation on a site.  Under the Sites screen, Bookings tab click the New button and a screen similar to the following will appear:

Many users will only have access to the Site Hold tab.  For users with restricted access this allows them to place a site on hold without a contract.  All they need to nominate is their name (usually this would be automatically set and can't be changed) and the reason they are holding the site.  When they click OK it would then proceed to a normal Booking screen.

Internal Contracts:

Site Holds DO, in fact, create a Contract.  SIGNZ will automatically create a hidden contract based on the user's name with an asterisk at the beginning.   In SIGNZ you can see these Internal Contracts within the Contract screen by selecting that option:

Internal contracts can be converted to "normal" contracts by clicking off the Internal flag after Editing the contract.  Normal contracts can't be changed to Internal.  Changing an Internal contract to a normal contract effectively moves ALL current Site Holds (for that user) across to become Contract Holds associated with that 'new' contract. 

Next time the user tries to create some Site Holds SIGNZ would create a new Internal contract for them.

Contract Holds:

A Contract Hold is just a booking in a normal Contract that has a Hold flag placed on it.

In most SIGNZ installations the Hold flag is automatically placed on all bookings when they are created by having the Hold Booking option ticked.

Placing a Hold on a booking achieves the following:

• It will not be invoiced
• It will normally be excluded from installation reports
• It will appear differently in Avails

Each is important but preventing invoicing is the critical one.  Nothing else in the system, not stages, not Confirming a contract ... NOTHING else prevents invoicing except for the Suspend flag on a contract.

Return to top