Turns the Adobe Sign form-field export into the Workforce.com user import CSV.
Everything runs in this browser; no data is uploaded anywhere.
1. Drop the Adobe Sign export
In Adobe Sign: Manage → select the agreement or the web form →
Download Form Field Data. Or Reports → New Export for several at once.
Drop the CSV hereor click to choose a file
#
Column name in your file
First row value
Used for
2. Connect to Workforce (optional)
Pulls your teams, locations and pay groups so the values below are
picked from a list rather than typed. Only reference data is read — no staff
records. The token stays in this browser.
3. Fill in what Part B does not ask
These are the same for everyone in the batch, or are yours to set.
They are remembered on this computer for next time. Connect above to turn the
team, location and pay group boxes into dropdowns.
Workforce does not expose position templates through its API, so the
rates live here. Update them whenever your position templates change — they are
saved on this computer.
Position template
Hourly rate
Contracted weekly hours
4. Check the mapping
Matched automatically from the column names. Change anything that
looks wrong — your choices are remembered.
Workforce column
Comes from
Example from row 1
Status
5. Check and download
6. Reference requests
Two satisfactory references are required before anyone starts.
These are built from the referee details on Part B.
7. Welcome email
Send this once the record is created and the onboarding invitation
has gone out. It tells them what to do next.
8. Payroll onboarding spreadsheet
Builds the file your payroll partner expects, for everyone whose
employment start date falls in the month you choose. Run it once the new starters
have completed onboarding, so their bank details and tax codes are in place.
Workforce does not hold the bank name, so it is worked out from the
sorting code. This list covers the banks your staff actually use. Longer prefixes win,
so 040004 beats 04. Anything with no match is left blank
rather than guessed — your payroll partner does not usually need this field.
Sorting code starts with
Bank
How to use this
This tool sits between Adobe Sign and Workforce.com. It takes the answers people
gave on the Part B form and turns them into the CSV that Workforce’s user
import expects, so nobody retypes anything.
When to do this. Only once the DBS has come
back clear and both references are satisfactory. Creating the Workforce record
before that point means committing to a start date you may have to withdraw.
1Get the data out of Adobe Sign
Sign in to Adobe Acrobat Sign and open the Manage tab.
Find the completed Part B agreement in the left-hand filter list, or open
Web Forms and select the Part B web form to get everyone at once.
Select it, then in the right-hand panel choose
Download Form Field Data. A CSV downloads.
Diagram, not a screenshot — the exact
wording moves around between Adobe releases, but the action is always called
Download Form Field Data.
For several starters at once, use Reports → New
Export and choose the Part B web form. That returns every submission as
one CSV, and this tool will handle all the rows together.
2Drop the CSV onto this page
Drag the file onto the dashed box, or click it to browse.
The page tells you how many records and columns it found.
Nothing is uploaded. The file is read inside this browser only.
3Connect to Workforce (optional, but do it once)
In Workforce, go to my.workforce.com/api/oauth/access_tokens
and create a read-only personal access token.
Paste it into the token box here and click Connect and load.
Your teams and locations load into dropdowns.
The token is remembered on this computer, so this is a one-off.
Gender and emergency contacts come from
/personal_details/{user_id}, which needs the user and
personal scopes and requires you to be a manager of that employee. The
version of that endpoint without an id returns your own record instead, so it is
never called. As a safeguard the tool checks the email on whatever comes back
against the employee’s own before merging it.
Positions, rates and pay groups do not come from the
API. Workforce’s API exposes users, rosters, timesheets, shifts, teams,
locations, leave and qualifications — there is no endpoint for position templates,
and wage data is per employee rather than per position. So the position rates are held
in the tool. Use Edit positions and rates under step 3 to keep them in
step with your position templates, and choosing a position then fills the hourly rate
and contracted weekly hours for you.
4Fill in the batch settings
Part B deliberately does not ask for these, so set them here. They apply to
everyone in the batch and are remembered for next time.
Employment start date — agree it only after the checks clear
Base hourly rate and contracted weekly hours
Team, pay group and permission level
5Check the mapping
Each Workforce column shows where its value comes from and an example from the
first record. Most are matched automatically from the column names.
matched — found in the Adobe export
derived — worked out, such as first and last name from the full name
blank on purpose — the reason is given in the middle column
not found — pick the right column from the dropdown; your choice is remembered
6Read the warnings, then download
Before the download button, the tool flags anything that would make a bad record:
missing name, email, position or start date; a date of birth it could not read;
a National Insurance number in the wrong shape; and any date of birth giving an
age under 18.
Fix what it finds, then click Download Workforce CSV.
7Send the reference requests
Two satisfactory references are required before anyone starts. The last section
builds both requests from the referee details given on Part B.
Paste the Adobe Sign reference form link into the box at the
top. This is the form the referee fills in. It is remembered, so this is a
one-off unless the form changes.
Add your name, job title and the reply address. Leave the name blank and the
message signs off as Rdential HR.
Each referee is set to Employer or Character
automatically from the relationship they gave. Change it if the guess is wrong
— the opening paragraph differs.
Create email downloads a .eml file. Double-click it and it
opens as a draft in Outlook with the link already clickable, ready to check
and send.
Open in mail app is quicker but produces plain text, so the
full web address is shown rather than a tidy link.
Preview shows the wording before you commit to it.
If no reference form link has been set, the email says so in
red rather than going out with a broken link.
If the candidate answered No to approaching
their current employer, a red warning appears above their referees. Check which of
the two that is before sending anything.
The referee does not reply by email — they complete the Adobe Sign reference
form, which is where the questions live and which gives you a consistent record
against each candidate.
8Import into Workforce
In Workforce go to Workforce → Staff and choose the
import option.
Upload the CSV this tool produced. Do not rename the column headings.
Check the preview Workforce shows you before confirming.
Then send the onboarding invitation so the new starter enters their own bank
details, emergency contact and tax declaration.
What this tool does not do
Bank details, emergency contact and
tax status are left blank on purpose. The employee enters
those in Workforce, which is both safer and more accurate.
It does not send anything to Workforce. You still do the import yourself, so
you get to check the preview first.
It does not read the signed PDF. Adobe flattens those, so the data has to come
from the CSV export.
If something goes wrong
Columns show “not found” — Adobe has named
them differently. Use the dropdown to point at the right one; it is remembered.
Dates look wrong — someone typed a date in an unusual
way on the form. Correct it in the source CSV and drop it in again.
Workforce rejects the file — check no column headings
were edited, and that the file is still UTF-8 CSV after any trip through Excel.
Teams and pay groups will not load — the token may have
expired. Generate a new one and connect again.
Which version am I using?
The pill beside the title at the top of the page shows the build number.
Click it to see what that build changed. If someone reports a problem that was
supposed to be fixed, check the pill first — a stale copy in Downloads is
the usual explanation.
This build is v2.9, 04 Aug 2026.
Where the data lives
Nothing leaves this browser. The token and your batch settings are stored on this
computer only, and Forget token removes them. The downloaded CSV
contains personal data, so treat it like any other HR file: import it, then delete
it from Downloads.
