novel pdf studio ← back to the website

novel ConnectENTERPRISE

Two people, two cities, one signed contract — every day

HR in Mumbai and Management in Chennai each sign the same contract with their own DSC token, in order, and it comes back doubly signed and filed — without either of them leaving their desk, and without a cloud service ever touching the document.

1 Enterprise licence 2 seats — Mumbai + Chennai Each seat has its own DSC token Fully auditable

Made for contracts & approvals

Any document where two or more people must sign in a fixed order, with legally strong DSC signatures:

Employment contracts — HR then Management Government files — maker–checker Office orders & sanctions Vendor & service agreements Purchase orders Board resolutions NDAs Offer letters

The daily flow

One contract, one signature at each end, in sequence. The same five steps run for every file — a batch of 50 works the same as one.

1

Prepare the contract MUMBAI Prepare

HR opens the PDF and adds two signer boxes — “HR” and “Management” — one under the other, then saves the prepared file. Each person now has a marked place to sign.

2

HR signs first MUMBAI Sign in the box

HR clicks their box and signs with the Mumbai DSC token. The first signature is now locked into the file.

3

Send it to Chennai MUMBAICHENNAI novel Connect

HR assigns the task to Management and attaches the file. It travels over your own office network to the Chennai desk — no emailing, no cloud, fully tracked. (Simpler alternatives below.)

4

Management signs second CHENNAI Sign in the box

Management opens the task, clicks the “Management” box and signs with the Chennai DSC token. The contract now carries both signatures, each with its green validity tick.

5

Filed & recorded CHENNAI Automate

The doubly-signed contract is filed into the right folder and the task is marked done. The audit trail shows who signed, where, and when — your eOffice record.

The government pattern — maker–checker

The same flow is how departmental approvals work: one officer puts up the file, another approves it. Every movement is recorded — the accountability the maker–checker principle exists for.

1

The maker puts up the file DEALING OFFICER Prepare · Sign

The dealing officer prepares the order or note, adds the two signer boxes, and signs first with their own DSC token — the maker’s signature is locked in.

2

Sent up for approval MAKERCHECKER novel Connect

The file moves to the approving officer over the department’s own network — no email attachments, no cloud service, and the movement itself is on record.

3

The checker approves APPROVING OFFICER Sign in the box

The approving officer reviews, clicks their box and countersigns with their DSC. The approved order is filed with a complete audit trail — who signed, in what order, and when. If the file is not in order, it simply goes back to the maker.

Why departments choose this: both signatures are real DSC signatures under the IT Act, the document never leaves the department’s own network, and the sequence itself — maker first, checker second — is enforced by the signer boxes, not by convention.

The structure

Two desks, linked by your own office server over a private site-to-site VPN. Nothing goes to the public internet except licence checks.

SEAT 1 · MUMBAI

HR

Prepares & signs first

  • novel pdf studio Enterprise
  • HR’s DSC token
  • Creates the task, signs box 1
🗄️ Your own server workflow relay (small container) ⇆ private VPN ⇆ queue · files · audit log
SEAT 2 · CHENNAI

Management

Signs second & approves

  • novel pdf studio Enterprise
  • Management’s DSC token
  • Opens the task, signs box 2

How the file travels between offices

Three ways, from full eOffice to zero-setup. Pick by how much automation and audit you want.

Recommended · true eOffice

Team tasks over novel Connect

A small workflow relay on your own office server holds the queue. HR assigns each contract to Management; it appears in their “My tasks”, they sign, it’s filed — every step recorded.

Needs: your own server (one small container — we help you set it up) + a private VPN between offices. Best for daily volume & compliance.

Shared network folder

A “To sign” folder synced to both PCs. HR drops the signed-once file in; it appears in Chennai within seconds; Management signs and moves it to “Done”.

Needs: any synced/shared folder on your file server. Near-real-time, no server software. No built-in audit trail.

Email / WhatsApp — the Sign Packet

HR signs box 1 and sends the encrypted file; Management signs box 2 and sends it back, unlocked with a short code. Works anywhere, today.

Needs: nothing. Manual, but proves the flow before you build the network.

What you need to set up

  • 1 Enterprise licence, 2 seats — activate seat 1 on the Mumbai PC, seat 2 on the Chennai PC. That is exactly what one licence covers.
  • A DSC token at each end — HR’s token in Mumbai, Management’s in Chennai. The app auto-detects whichever is plugged in.
  • A workflow relay on your own server — one small container holding the task queue and audit log; our team helps you set it up.
  • A private VPN between the offices — so the Chennai PC reaches the server privately. The relay is never exposed to the open internet.
  • A filing folder structure on the server — so signed contracts land in the right place automatically.

Start today, build up later. Prove the daily habit with the email or shared-folder method first. Move to Team tasks once the server and VPN are in place — the signing steps for HR and Management stay exactly the same.

novel Connect comes with Enterprise

₹4,100 per year, 2 computers — everything in Business, plus novel Connect, Workflow Automation and team approval routing. Try the whole suite free for 7 days, or talk to us about your signing workflow.

Contract signing · novel pdf studio Enterprise Novel Digital India Solutions Private Limited