Fixed-term contract renewal with dynamic document editing + e-signature — best practice?

[TomohiroT]

Hi all,

I'm building a fixed-term employee contract renewal process in HRSD:
1. Dynamically edit/fill contract content at renewal time (term dates, salary, etc.)
2. Send the finalized contract for E-signature
3. Ideally run this as a Lifecycle Event, since renewal recurs per employee

Has anyone built this? 
- Lifecycle Event vs. standalone HR Case — which did you use, and how did you handle re-triggering per renewal cycle?
- Is HR Document Template actually being deprecated?

Any examples appreciated!

[rahulswami]

Hi @TomohiroT,

Good news on the deprecation question, and there's a real path forward on the Lifecycle Event side too.

HR Document Template is genuinely being deprecated. ServiceNow's own guidance is explicit here, a ServiceNow employee on the community put it plainly: leverage the Document Templates introduced in Rome rather than starting now with HR Document Templates. The newer Document Templates feature supports both HTML and PDF, handles DocuSign integration, allows multiple people filling fields concurrently, and adds reviewer markup that the old HR Document Template never had. There's also an official migration guide if you have existing ones to move over. Do not build anything new on HR Document Template.

On Lifecycle Event vs standalone Case, Lifecycle Events is the documented path for this. Build your contract content in a Document Template with the dynamic fields, term dates, salary, and so on, create a Lifecycle Event Type, and add a Document Signature activity to it. When the event fires, the document generates and routes through My HR Documents for signature. One thing worth knowing, documents in this pattern typically attach to the child case within the lifecycle event rather than the parent event record, so plan your reporting around that.

For the agent review step before the document goes out, there is a documented pattern for that too. Configure the template to require both an agent signature and an employee signature. The agent gets the document first, verifies the populated term dates and salary are correct, can modify if needed, and only then does it route to the employee for their signature. That gives you the review step built into the same workflow rather than needing separate logic.

On re-triggering per renewal cycle, I could not find a thread addressing this exact point, so take it with a bit less confidence. Lifecycle Events are not a one-time-per-employee construct, each trigger creates its own instance, so firing the same Lifecycle Event Type again at the next renewal date should just create a fresh instance rather than conflicting with the prior one. The piece you would still need to build is what fires it, a scheduled job checking upcoming fixed-term end dates and kicking off the event a set number of days out, since HRSD does not have that recurrence baked in natively.