Managing travel arrangements is a challenge for most exploration companies, both with respect to coordinating future travel, and with respect to being able to find out quickly who traveled where in the past.
CampControl makes these tasks a lot easier by storing all travel arrangements in an organised calendar-based framework. This makes it is easy for travelers, managers and staff who have to take other people's travels into account, to look both forward and backwards in time.
Planning is made easier, as is report-writing, when it helps considerably to quickly be able to scan company travel records.
CampControl's Travel module is fully integrated into its Orders module, thus making it easy to keep track of which Project Codes, Activity Codes and Account Codes different Travel Orders should be charged to. <Click here to see the Travel Activity Diagram in the Activity Diagrams Section>
Travel expenses are often a significant proportion of exploration costs. CampControl makes it easy to implement a system of Travel Authorisations, no matter how much the manager who is designated to authorise travel is away on travel herself or himself. This is because CampControl can manage the Authorisation Requests and Granting of Authorisations over the Internet.
To implement an effective Travel Authorisation system using CampControl: (1) Issue a company directive declaring who is authorised to purchase/fulfill travel reservations, and who is required to authorise them. (2) Give the authorised purchaser/fulfiller the necessary permission on CampControl to fulfill Travel Orders (Note: Expediter and Office Administrator-level CampControl users enjoy this permission by default, although it can be taken away from them); (3) Instruct all staff who wish to travel that their Travel Orders must be entered into CampControl, and that these orders will not be fulfilled unless (a) they activate the Request Authorisation subsection of the Order; (b) the appropriate authority has authorised the Order using the CampControl Authorisation facility, which automatically communicates the Authorisation Request to the indicated party, and lets both the "Order Placer" and the "Order Fulfiller" know once the Order has been authorised (or denied authorisation).