Skip to main content

Groundhawk Guide for Project Manager

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 Build
  • Ensure build team have 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 such doesn’t exist from support@groundhawk.io providing i) person name, phone number, email, ii) person role (field user, project manager, documenter)   
  • Ensure build team has done Groundhawk user training and certification. See more <link to training course>  
  • Create project and assign users to project. See <portal instructions>  
  • Upload planned route to Groundhawk portal. See <portal instructions>  
During Build

Take a routine to check daily, and take notes to give them feedback on how to improve and what is going well. Potentially use comments functionality to add comment directly on the map  


Especially first days sets the tone, as it is important that the team gets it right and they notice that the mapping and documentation is being used by project manager to ensure quality.

 
Check progress and gaps. Ensure that the team is mapping all that is being built to ensure mapping and reality matches. Compare also that there are no gaps in the mapping especially compared to plan. 


Check build quality from photos portal on 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 first documentation of the first small area after a week or two to ensure everything is captured well.  


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

After Build
Before end of the build, ensure the team really has mapped everything 
Archive when documentation is finished the site can be archived  
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. Think that to prevent most of the mistakes takes only an hour of training whereas an untrained person mapping and making mistakes can easily generate need to later correct the mistakes that 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