Every audit request sends us into three systems and an inbox.

We ran plants, not programs. Singularity for the Public Sector reads your case system, finance and records archive where they sit, and keeps every decision on record with who made it and when. Start with one Module.

  • Grant approval, GR-2291Oldest first in the queue Waiting
  • Before it moves Policy rule checked Program lead signs
  • Every decision kept on record

Today

The auditor wants one file. You build it from three.

The decision sits in the case system, the money in finance, the sign-off in an email. The audit asks for all three.

The systems we connect in a program office

  • Case management Case status, assignments and history, with every case shown next to the money and the sign-off tied to it.
  • Grants ledger Commitments, disbursements and balances, with every payment read next to the grant it came from.
  • Finance Payments and account codes, with a release shown next to the approval that authorized it.
  • Records archive Signed agreements and supporting documents, so an auditor finds the file without calling the program office.
  • Permitting Applications, conditions and inspection results, with a permit's status read next to its case.
  • Email and spreadsheets The tracking sheet and the sign-off buried in an inbox. We read them as they are until you're ready to retire them.

What you can do once they're connected

Hold a payment release until the right person says yes.

Integration Hub + Authority Matrix + Approval Queue

The Integration Hub reads the case system and the grants ledger. The Authority Matrix says whether an Agent may release a payment alone. Anything past that waits in the Approval Queue for a person’s yes.

See how it works

Connected

  • Case system
  • Grants ledger

The modules, in order

  1. Integration HubReads the case system and the grants ledger.
  2. Authority MatrixSays whether an Agent may release a payment alone.
  3. Approval QueueHolds anything past that for a person's yes.

What you see

  • Payment releaseProgram Director and above On
  • Payment release: GR-3318 Above the Agent's authority Waiting 3d 6h
  • Approved by J. Bergeron 13:28

Answer a policy question with the source shown.

Knowledge Library + Q&A Engine

The Knowledge Library holds the policy documents your team uploads. The Q&A Engine answers from them and names the document it came from. Every question and answer is logged.

See how it works

Connected

  • Policy documents
  • Shared drives

The modules, in order

  1. Knowledge LibraryHolds the policy documents your team uploads.
  2. Q&A EngineAnswers from them and names the document it came from. Every question and answer is logged.

What you see

  • Grants policy, section 4.2Source for this answer

Count a decision once, with a record of who made it.

Approval Queue + Notification Center + Governance

The Approval Queue tracks how long a request has waited. The Notification Center lets the approver know it’s there. Governance keeps the trail an auditor can pull by record type and id.

See how it works

Connected

  • Case system
  • Email

The modules, in order

  1. Approval QueueTracks how long a request has waited.
  2. Notification CenterLets the approver know it's there.
  3. GovernanceKeeps the decision with who made it and when.

What you see

  • Permit request: PR-1142 With the approver Waiting 2d 3h
  • Decided by A. Tremblay 11:20
  • On record, counted once
  • Newest exchanges Case system Decision Read Grants ledger Commitment Read Finance Payment Read
  • Last read 09:14

Connections

Read the case system, grants ledger and finance in place

The Integration Hub reads the case system, the grants ledger, finance and the records archive without replacing any of them.

  • Connections set up with your team, one system at a time
  • Data region set at onboarding: Canada or the United States
  • Rule, grant disbursementAbove the Agent's authority Needs a person
  • Checked before it runs

Agent authority

Set what an Agent may do alone, and keep every decision

The Authority Matrix sets what each Agent may do on its own. Governance checks every Agent action against that rule and records who decided and when. Nothing sits pending without a clock on it.

  • Every Agent action checked before it runs, every result logged
  • Pending items ranked by how long they have waited
  • The trail pulled for any record by its type and id
  • Oldest request waiting 3d 6h
  • Release payment, GR-3318

Approval queue

Hold an Agent's action for a person's yes, oldest first

The Approval Queue holds every action an Agent can’t take on its own, oldest first. The approver sees the detail before deciding.

  • Every request shows the time left before it expires
  • Approve twice by mistake and it still counts once
  • The decision kept on record
  • Grant policy, section 4Page 2, cited

Ask

Get answers from program documents, with the source cited

The Q&A Engine answers from the program documents in your Knowledge Library and shows where the answer came from.

  • Refuses to guess when no source meets the bar
  • Scoped to the programs the person may see
  • Every question logged for the auditor

Start with the two or three Modules that pay first.

The Modules we start with in a program office

They collect and keep what your program knows.

  • Integration Hub: the connections to your case system, grants ledger and finance, with every exchange logged.
  • Governance: every Agent action checked against the authority you set, with the decision kept.
  • Approval Queue: every action that needs a person’s yes, oldest first.
  • Knowledge Library: the policy documents and program files your team uploads, held in one place.

So what: every case, grant and audit starts from the same record.

What working with us looks like

Start with a conversation, one Module or the whole operation, and the same team stays from the Scorecard to go-live.

  1. Step 1

    The Scorecard

    Two to four weeks with access to your environment, and no platform purchase. You see where your data lives, where it doesn't, and what the gaps cost.

  2. Step 2

    Connect and lay the foundation

    Foundational Modules go in first. We connect the systems you already run, one at a time, starting with the one the roadmap says pays first.

  3. Step 3

    Turn on the engines

    Workflow Modules start working on that record: answering questions, letting the right person know a decision is waiting.

  4. Step 4

    Add the Agents

    Agents take on the routine work, inside the authority you set. Anything outside it waits for a person.

  5. Step 5

    We stay

    Your people run it on their own screens, not ours. We stay for the next improvement.

FAQ

Bring the decision you'll have to defend.

30 minutes on your program and what you'd need to show an auditor. We'll bring the questions.