Policy Lifecycle and Staff Attestation Engine

Policies were the part of governance most customers still ran outside any system: files in shared folders, owners nobody could name, review dates nobody tracked. The client wanted a full document lifecycle inside its platform, and it wanted it without pulling engineers off the existing roadmap or opening permanent positions.

Intelvision’s Talent as a Service model supplied a dedicated team that worked as part of the client’s product group, so the policy module shipped in parallel with ongoing releases.

Intelvision supplied a dedicated team rather than individual contractors: backend, frontend, QA, architecture and business analysis roles, all working in the client’s own backlog, tools and release process. The client kept product ownership; the team took the policy module from requirements to production.

Because the team built on the platform’s existing multi-tenant foundations, document tooling and background jobs, the module arrived as a native part of the product rather than a bolt-on.

The partnership included:

• Flexibility and Scalability

  a complete team from day one, with roles the client could adjust rather than fixed headcount.

• Comprehensive Services

  analysis, architecture, development and QA covered inside one team, with no hand-offs to other vendors.

• Built-in Quality

  automated tests and a SonarCloud gate on the service, with changed code required to reach more than 80% coverage.

• 1. Capacity Without Headcount

  The team joined the client’s sprints three weeks after the request and worked inside the same backlog as the in-house engineers. The policy module was built as its own service with its own API and delivery pipeline, so it moved in parallel with the rest of the roadmap instead of competing for release slots. The client added a complete team without adding a single permanent position.

• 2. A Governed Document Lifecycle

  Every document now has an owner and moves through six stages from Draft to Retired. A stage only advances when the assigned reviewers and approvers have given consent, and the history log records who did what and when. Scheduled attestation asks staff to confirm they have read each policy, reminders chase the stragglers, and the result is the evidence an auditor wants without anyone compiling it by hand.

• 3. Safe Editing at Tenant Scale

  Reviewers and approvers edit in the browser through the Syncfusion editor while SignalR edit locks stop two people overwriting each other. PDF conversion runs in an isolated PDFTron process so a bad file cannot take the service down. Every version is stored in Azure Blob Storage and can be restored, and every record carries its tenant, which keeps each customer’s documents sealed from the rest.