Skip to main content

We updated our eSign templates to include the employee fields such as first name, last name, SSN, etc. However, in our preboarding process, SSN field and other required fields are not populating for the new hire.

  • Mar 31, 2023 4:57 PM UTC
  • Jul 15, 2025 12:51 PM UTC
  • 14 replies
  • 403 views
  • Translate All

For employee fields to be populated in the eSign documents, and not displayed as blank, fields must be completed on the New hire wizard (not on the employee onboarding). 

Please note that the document is created once the new hire wizard is completed. It means that by the time the new hire completes their onboarding, the document request is already there and unfortunately the additional fields new hire completes on their onboarding won't be added to the already created request. 

This topic has been closed for replies.

14 replies

  • Jun 29, 2023 6:42 PM UTC

So, are you saying that the HR Administrator has to have the employee’s full information to complete the new hire wizard first in order for the forms to pull that information?  That doesn’t seem to make sense since the employee is adding their information to their profile during their onboarding steps (e.g., in the US - social security numbers need to be included on tax forms).  But since we don’t have that as a required field for entering a new hire it won’t pull that information into the forms.  Is that correct?

Thanks,

Krissy Mayton

Translate

Lindsay Sinenberg
Bobber

Hi @KMayton! That will be correct. When the employee profile is first created on the platform with the New Hire flow, you can enter in details for the profile (names, site, department, salary, etc). Once the information is added, those fields will be able to be populated into any eSign documents that need to be signed. So by the time the new hire is filling out the forms in the Onboarding flow, the document request is there.

For any information that the HR team does not know (i.e. SSN, etc), this will need to be filled out by the new hire themselves when they complete the onboarding process and a 2nd eSign request can be sent after they start. Only until the new employee adds the personal/sensitive information to their profile can these items be added to a document.

Translate

  • Jun 30, 2023 3:26 PM UTC

Thanks for the response Lindsay!  As a user spending lots of time onboarding new employees, processing new hire paperwork in this manner through Bob kind of defeats the purpose of this part of the system.  The goal of having an HRIS in my opinion is to not only securely storing employee data but automating as many manual administrative tasks as possible. 

So instead of knowing a new employee’s paperwork is completely filled out for our Finance Team to access and use in the payroll system set-up I have to continue reviewing all paperwork for missing information.  Unless I remove all the paperwork containing the information we don’t have initially from the onboarding flow and send after the onboarding flow is completed.  That is half of our new hire paperwork being removed and sent separately which can’t even be triggered as part of the task list.  It just seems like it would make more sense to trigger the eSign documents to be completed after the employee has completed all the sensitive information in their profile during the new hire flow.  Am I missing something or is there a reason for approaching the process in that order?

 

Thanks again,

Krissy

Translate

Lindsay Sinenberg
Bobber

@KMayton We have 2 different flows on the platform - New Hire and Employee Onboarding

-HR team will complete the New Hire flow to create the Bob profile, this is before the new hire starts.
-New employees will complete the Employee Onboarding flow and will fill in their sensitive information. This is completed shortly before their start date.

Only once the onboarding flow is completed by the new hire, will those personal details (SSN, address, etc) will be listed on their Bob profiles and can be auto-filled on any eSign documents.

So if you have documents that you need new employees to complete before their start date like employment contract, this should only include auto-filled information that was filled out by the HR team in the New Hire flow (site, department, salary, for an example). This way you can ensure those fields are not blank, since they’re on the profile.

Feel free to contact our Support team and we can always confirm your specific setup and provide further assistance 😊

Translate

Kati Evart

Hi @Lindsay Sinenberg!

Is there any hope, that in the (near) future populating employee data fields during pre-onboarding and filling eSign will change?
I don’t know, maybe it is our cultural peculiarity, but in our country, we make employment contracts on the first chance after the new hire has said “yes” to our offer. It offers a sense of security that the position belongs to the picked candidate and on the other hand we as the employer has security that the employee comes to join us. Today, I’m collecting needed data manually, and making the employment contracts manually, and after that, I can add employees to the bob. To be honest, it’s not the best solution for preboarding. 

I’m holding my fingers crossed that your team is working to make this process more pleasant! 🤞😇

Translate

  • Jul 5, 2023 10:30 AM UTC

Hi @Lindsay Sinenberg!

Is there any hope, that in the (near) future populating employee data fields during pre-onboarding and filling eSign will change?
I don’t know, maybe it is our cultural peculiarity, but in our country, we make employment contracts on the first chance after the new hire has said “yes” to our offer. It offers a sense of security that the position belongs to the picked candidate and on the other hand we as the employer has security that the employee comes to join us. Today, I’m collecting needed data manually, and making the employment contracts manually, and after that, I can add employees to the bob. To be honest, it’s not the best solution for preboarding. 

I’m holding my fingers crossed that your team is working to make this process more pleasant! 🤞😇

I agree with Kati on this - I spent a long while preparing our contract templates (which include new hire’s address) and have just realised that it’s not going to populate on the contract template. Coupled with new hires not having access to e-sign until their start date, I’m not sure how to proceed…

We could have a free text option for the new hire to insert their address, but then they’d be entering it twice and it feels like we’re bending our processes to work around the e-sign module.

Sorry to piggyback on this, but hopefully we can work out a best practice!

Translate

Lindsay Sinenberg
Bobber

@Jade Neve @Kati Evart 
Currently it is not possible for the platform to auto-fill fields on an eSign document if the information does not exist on the employee profile when the document request is triggered. But I can definitely add both of your companies and use cases to the open feature requests with our Product Team - this has been requested by other users!

For any contracts to be filled in with information automatically, the profiles would need to be created on the platform first. That way the system has information to populate into the selected fields on the template (i.e. job title, start date, site, etc).

If a new hire’s address is required on the contract, this would need to be listed on the profile before the document is triggered. If its not, then it would by default be blank. The workaround would be to add a Text Field as a placeholder in the template so the new employee knows what to include and fill in their address themselves. This information would only be on the document and would not transfer to their Bob profile, so they would then provide their address when completing the pre-onboarding flow.

 

Translate

@Lindsay Sinenberg  Are there any recent updates on this?

I have the same issue - there are many forms our new hires need to complete with their personal information that I do not have when completing the New Hire flow, but that they do enter during their Onboarding flow. For now, I’ve worked around the issue by having free text fields the the form for the employee to fill. However, it seems redundant to have the new hire enter the same information into the form, and then again into their profile via the flow. If I were the new hire I’d be confused and possibly annoyed to have to enter all the same information multiple times when the goal here is automation - not great for their first employee experience!

I’d like to see either the eSign documents sent in the Onboarding flow but after the employee enters their information so it can populate employee fields, or the option for eSign documents to be sent to the new hire’s personal email as part of a task list. As of now I believe they cannot access any eSign docs triggered via a task list until their start date, and these forms are things I need completed during preboarding.

Please let me know if any of my understanding is off here - I’m newer to the process as well. Thanks!

Translate

I have asked for you, @Christa Gewecke. Appreciate your added context too, which I’ve included 😊.

Translate

@The HiBob Community Team  I’m adding my company as a requestor for this feature as I start to build out our onboarding workflows in Bob. I completely agree with Christa’s reply; it is frustrating that we have to ask our new hires to fill in their information several times, when it would make the most sense to have the flow look like: 

  1. HR inputs minimal information - like name + email address + position - into Bob to create the new account,
  2. The new hire completes additional fields, like home address and phone number;
  3. All subsequent E-sign forms populate the information completed in Step 2 for review and signature, without the new hire having to duplicate text entry.

I would really like to see this implemented and hope it is soon! 😊

Translate

Maital Terdiman
Bobber

Thank you for the feedback here @Noah Ismael 

I have gone ahead and added you to the FR, and passed the feedback on to the Product team 🤓

Translate

  • May 29, 2025 2:30 AM UTC

I’d like to jump on this bandwagon.

When looking at the documentation for eSign, it states that the field is ‘synchronized’ to HiBob. One possible solution could be for eSign documents to allow 2-way synchronization. Empty fields are allowed to be empty on sending an eSign, but you can use the eSign to fill in those fields. Required fields are used like required fields in any other type of web form - the form cannot be completed when they are empty.

For example, we have an employment contract that we send to our employee but that employment contract doesn’t collect specific personal information that is required from the employee ahead of their start date, such as their details needed for payroll and to fill out government-issue tax forms. If we were able to send them an eSign request with those fields blank and fillable then we could kill two birds with one stone and get that data input both into Bob and into the required document at the same time.

The other good alternative is to trigger the eSign request after the person has filled out a specific section of the Onboarding flow. Currently when you set up an Onboarding Flow, the Docs step is set up after the Fields step - logically it makes sense for the Docs to be sent after the Fields have been entered (and saved) so that they can be used on any eSign requests.

Long story short - allow for eSign requests to edit Employee Fields (or to map various fields → Employee fields) to extend the usefulness of eSigns.

Please keep me posted when there’s some sort of update.

Translate

Hi, Were there any changes made around this functionality? Could I please be keep up to date on changes around that ? ​@Maital Terdiman 

Translate

Harshil Boparai
Bobber

Hi ​@Anna Irzymska  We appreciate your time and thanks for following up! The best next step would be to share this directly with your CSM. They’ll ensure the full context is captured and keep you informed as things develop.

 

Translate