NORA prepares. A named person decides.

A sphere of blue ink settles, then divides into six glass orbs: the six steps of a case.

The operating system for the control and tracking of work. Every request becomes a case, checked against your own rules and decided by a named person.

A case moves through six steps.

  1. Open

    A request and its documents become a case.

  2. Check

    NORA checks it against your rules. Every result cites its file and page.

  3. Prepare

    NORA prepares the case for review: the results, what is missing, and who decides.

  4. Decide

    A named person approves, returns or rejects. NORA never decides.

  5. Record

    Every step is recorded and linked. The decision sits on that exact version.

  6. Learn

    NORA proposes lessons from your reviews. A named person approves each one.

  1. One request. One case.

    A supplier asks to be approved. Its documents arrive with it.

  2. Checked against your rules.

    Each rule gives its result and says why.

  3. Every result cites its file and page.

    What NORA cannot read is not verified, never passed.

  4. A named person decides.

    Not NORA, and not the person who sent the case.

  5. Recorded on the exact version.

    Who decided, as which role, when, and on which version.

Change one value.

The version changes, and so does its fingerprint. The approval stays with the version it was given on.

A new version needs a new decision.

Every step is recorded and linked.

Who opened the case, what was checked, who decided, on which version. Each record carries the fingerprint of the one before it, so a change to any of them shows.

Sealed into an evidence pack.

A decided case can be sealed. An inspector verifies the pack without access to NORA, and the checks replay to the same result.

NORA learns. Your people approve.

Each night NORA reads your recent reviews and proposes lessons: a document to ask for when a case opens, a corrected example, a check to review. Nothing changes in how NORA works until a named person approves. Every version of the playbook is kept.

Alongside the systems you already run.

NORA works beside your tools and does not replace them. Every change NORA prepares through a connected tool waits for a named person.

Hosted, or inside your own environment.

Who decided, on which version, and why.

NORA opens for a company after a signed agreement. Tell us what your people approve today.

Book a demo

NORA 準備。 由指定人員決定。

一個藍色墨水球體漸漸靜止,然後分成六個玻璃球:一個個案的六個步驟。

管控及追蹤工作的作業系統。每項申請成為一個個案,按貴公司的規則檢查,由指定人員決定。

一個個案​經過六個步驟。

  1. 開立

    申請及其文件成為一個個案。

  2. 檢查

    NORA 按貴公司的規則執行檢查。每項結果均註明檔案及頁碼。

  3. 準備

    NORA 備妥個案待審核:結果、欠缺甚麼,以及由誰決定。

  4. 決定

    由指定人員批准、退回或拒絕。NORA 從不作出決定。

  5. 記錄

    每一步均已記錄並相連。決定記錄在該版本上。

  6. 學習

    NORA 按貴公司的審核​建議學習項目。每項須由指定人員批准。

  1. 一項申請,一個個案。

    一家供應商申請批准,其文件隨申請一併送達。

  2. 按貴公司的​規則檢查。

    每項規則均列出結果及原因。

  3. 每項結果均註明​檔案及頁碼。

    NORA 未能讀取的內容列為未能核實,絕不列為通過。

  4. 由指定人員決定。

    不是 NORA,也不是提交個案的人。

  5. 記錄在​所審核的版本上。

    誰作決定、以甚麼身份、何時,以及依據哪一版。

更改其中一個數值。

版本隨之改變,指紋亦然。批准仍然留在作出批准時的版本上。

新版本需要新的決定。

每一步均已記錄​並相連。

誰開立個案、檢查了甚麼、誰作決定、依據哪一版。每條記錄都帶有前一條記錄的指紋,任何改動都會顯現。

封存為證據包。

已作決定的個案可以封存。審查人員無需使用 NORA 即可核實證據包,檢查重新執行後結果相同。

NORA 學習,由貴公司的人員批准。

NORA 每晚閱讀貴公司近期的審核,並建議學習項目:開立個案時須索取的文件、更正的範例、需要重新審視的檢查。在指定人員批准前,NORA 的運作方式不會有任何改變。作業手冊的每個版本均會保留。

與貴公司現有的系統並行。

NORA 與貴公司的工具並行運作,並不取代它們。NORA 透過已連接的工具準備的每項變更,均須等待指定人員處理。

可採用託管方式,或部署於貴公司自己的環境。

誰作決定、依據哪一版、原因為何。

NORA 在簽署協議後為公司啟用。請告訴我們,貴公司的人員目前批准哪些事項。

預約示範