Skip to main content

Groundhawk Guide for Project Managers

For project managers, Groundhawk offers real-time visibility and streamlined documentation, making it easy to stay on top of progress - even from a distance.
 
How can Groundhawk support the project manager role, and what is required by the project manager on a site that uses Groundhawk?
 
Note: the role of project manager might be team leader, site manager, or similar role that is primarily managing the project and often not on site. 

Checklist for Project Managers: Key Responsibilities with Groundhawk

Before the Build

Ensure build team has a Groundhawk device with a SIM card


Ensure the users have their own user accounts. Accounts are typically requested from Groundhawk Admin internally, or if one doesn’t exist, from support@groundhawk.io providing i) the person's full name, phone number, email, and ii) the person's role (field user, project manager, documenter)   

 

Ensure build team has done Groundhawk user training and certification. See more here: Course  

 

Create the project and assign users to the project. See Portal Instructions  
During the Build

Make a routine to check daily, and take notes to give field users feedback on how to improve and what is going well. Potentially use the comments functionality to add comment(s) directly on the map  


The first days can really set the tone, as it is important that the team gets it right the first time and they notice that the mappings and documentation are being used by the project manager to ensure quality

 
Check progress and gaps. Ensure that the team is mapping all that is being built to ensure the as-built and plans match


Check build quality from photos in the portal on a daily basis. Typical issues to address are:  

  • Are all network elements mapped E.g. cabinets, markers, joints  
  • Are all interesting quality related work process elements captured with photos (work site protection, overall pictures)  

 

Check with documentation. If you are unsure the team captures everything correctly, it is good practice to do the first documentation after a week or two to ensure everything is captured well


Provide feedback to the team on how they need to improve their mapping and build-out  

After the Build

Before end of the build, ensure the team really has mapped everything 

Archive when documentation is finished the site can be archived  

User Export, use this feature to export the site fully or between any time period, for more information check out our configurations page

Well-Motivated Team

Remember that a well-motivated and trained team makes the project manager's job much easier during the project. It is vital that the users know how to use Groundhawk well before starting.

Consider that preventing most of the mistakes takes only an hour of training, whereas an untrained person mapping and making mistakes can easily generate the need to later correct those mistakes, which can cost and take days of work to fix. 

What Would You Like to Learn Next?

Select the topic from the list and get ready to learn more