When you're ready to turn a successful candidate into a signed contract, you want the data flowing into OneFlow to be accurate from the start. Re-entering details directly in your contracting tool is slow, easy to get wrong, and pulls decisions out of Fill — where they belong.
Fill now adds a contract data confirmation step before sending information to OneFlow. You get one place to review, complete, and validate every field that ends up in the contract — so what's signed matches what you actually agreed.
Why a confirmation step matters
Some details that belong on a contract — cost centre, department, hiring manager contact information — aren't always part of the original request. Until now, those fields had to be filled in directly in OneFlow, which created extra work and meant Fill no longer reflected the full picture of the assignment.
With the confirmation step:
You review and complete missing fields before anything is sent to OneFlow
Updates and corrections happen in Fill, not in your contracting tool
Fill stays the source of truth for assignment details
Your team avoids duplicate data entry and inconsistent records
How the confirmation step works
The confirmation step appears when you start contract creation for a request:
Open the candidate you want to contract and select Create contract
Fill opens a confirmation view showing all the fields that will be sent to OneFlow, pre-filled from the request and assignment
Review every field — required fields are clearly marked
Complete or correct any details that need updating
When everything looks right, confirm to send the data to OneFlow
OneFlow then generates the contract using the validated data, so you don't have to touch those same fields a second time.
What is validated
Fill checks that required fields are present and well-formed before allowing the contract to be sent. Typical fields include:
Assignment dates and workload
Rate and budget information
Cost centre and department
Hiring manager contact details
Candidate and supplier information
If something is missing, Fill flags it directly in the confirmation view so you can fix it on the spot.
How this differs from the assignment extension flow
If you've extended an assignment before, this confirmation step will feel familiar. The extension flow already asked for the additional details needed for a contract — the same idea is now applied to the first contract for a new request, so both flows follow the same pattern.
Frequently asked questions
Can I still edit the contract in OneFlow after sending?
Yes — OneFlow still works the way it always has after the contract is generated. The confirmation step is about getting the data right before generation, not replacing OneFlow's contract editing.
What if I notice an error after sending data to OneFlow?
It's recommended to correct the data in Fill and start a new contract if changes are significant, so Fill remains aligned with what's in OneFlow.
Does this affect the assignment extension flow?
No. The extension flow already collected the additional information needed for contracts. The new confirmation step brings the same pattern to new requests.