VIGTHORIA WORKBENCH

PUBLIC SECTOR · WORKBENCH

5 November 2026 / 5. November 2026


01  Start with a useful result

Municipal and public-service teams need dependable ways to prepare information and check routine work. We propose a supervised evaluation of one well-defined workflow.

A practical starting point

Choose an internal project memo, an expenditure extract or an internal project register. Keep the source small enough to review and compare the result with a known answer.

Keep responsibility clear

A named colleague reviews the output and decides the next action. The pilot is scoped to administrative assistance, without deciding an individual’s rights, eligibility or legal position.

Build from evidence

Agree the permitted data, supported formats and acceptance cases before introducing operational records. Measure the complete task, including checking and preparation.

Vigthoria Workbench — AI support with a defined local processing boundary.


02  Three fictional examples

These examples illustrate the demonstrated workflow; they are not results from a reference authority or a claim about your organisation’s savings.

Budget review

Local CSV/TSV extract → exact arithmetic → source-linked review. Example: €48,000 total, €45,000 limit, €3,000 above the limit. Approval stays with the responsible person.

Completeness review

Local internal register → required-field check → the affected row. Example: DEMO-002, source row 3, is missing a status. A colleague verifies and completes it.

Document question

Local TXT/Markdown excerpt → focused private question → local answer and source comparison. Example: find a named project owner or a meeting date in a fictional memo.

Current evaluation uses approved UTF-8 text and table extracts. Native PDF/OCR, every Office format and entire case archives are not assumed to be supported.


03  Make the data boundary visible

Confidential source contents, private questions and local answers are processed within the demonstrated private workspace. Online planning organises a generic task without needing those contents.

What online planning uses

The general task selection and normal account/connection information are used online. This is a separate flow from selecting and analysing confidential source material locally.

What your IT team verifies

Review the exact package, local AI component, endpoint settings and observed network behaviour. Choose approved devices, user accounts, working directories and export locations.

Where your existing rules apply

Exports into a synchronised folder follow that folder’s sharing rules. Endpoint management, backups, remote support and operating-system services require their own review. Local workspace clearing does not promise forensic erasure.

What happens when a limit is reached

The evaluated local workflow stops or reports a limit rather than silently sending the confidential question to a cloud service. A colleague can change the approved input or continue manually.

Your data policy becomes part of the acceptance plan. The scope is verified together with your IT and data-protection teams.


04  A focused pilot, with clear gates

Suggested scope: one team, one workflow, three to five managed Windows devices and four weeks after the agreed readiness checks. This is a proposal to scope together, not a published product tariff.

Week 1 · Define and prepare

Name the workflow owner, IT reviewer and data-protection contact. Agree data categories, the exact release, approved storage and a small acceptance set. Begin with fictional material.

Week 2 · Demonstrate and check

Run the agreed cases on the managed device profile. Check source accuracy, network boundaries, export, cancellation and failure behaviour. Staff practise review and safe handling.

Week 3 · Compare real work, if approved

Use only records authorised for this scope. Compare complete task time and corrections against the existing method. Keep confidential examples and measurement records in approved locations.

Week 4 · Decide on evidence

Review quality, handling boundaries, user feedback and total costs. Agree a limited next step or finish the evaluation with a return/retention plan. Expansion is a separate decision.

Before any installation: an approved release, endpoint suitability, written scope and your organisation’s authorisation. No production start date is implied by the demonstration.


05  A productive first conversation

Invite the operational owner and, where possible, an IT or data-protection colleague. The aim is to decide whether a small, reviewable pilot fits your requirements.

What should we discuss?

Which task creates avoidable preparation work? What is its current format and volume? Which content must remain on the device? How will people check the answer?

What about cloud and existing systems?

Ordinary Assistant, email, CRM, calendar and other connected features have their own processing behaviour. They are assessed separately. A private-workspace evaluation does not authorise their use with confidential content.

What about compliance and procurement?

The authority reviews the intended use, applicable law, supplier identity, processing arrangements, accessibility and procurement route. The proposed pilot includes that review; it is not a blanket certification or an automatic exemption.

What should we bring?

A description of one representative task, its data policy and the device profile. Fictional extracts are enough for the first demonstration. We can agree the acceptance evidence and scope before a commercial offer.

Contact Vigthoria to plan a 30-minute task and data-policy discussion.
vigthoria@vigthoria.io  ·  vigthoria.io
