Isnad Institutional files and work
From word to page من الكلمة إلى الصفحة

A platform for institutions

Your institution's files, and your team's work on them, in one place.

From the first document to the final decision, Isnad brings the content, the people, the permissions, the live work and the record together in one clear digital file. One foundation serves more than one field in your institution, and each field keeps its own steps and tools.

Fields

Where does Isnad work?

One platform for your institution, and each field of work with its own way of using it. Choose yours to see its steps and tools.

The shared foundation

What do these kinds of work share in Isnad?

Whatever your institution calls the file, the foundation of the work stays the same: ordered documents, people with defined permissions, work on the same content, and a record you can go back to.

A space holding ordered, numbered material, read by a group in which each person has a capacity, led by its owner, producing a record you can go back to.

Press the word you use where you work, and the whole page starts speaking in it — the same foundation, with workflows and terminology suited to your field. That is how the platform itself behaves: we do not ask you to call your own things by our names.

1

Find the document and the page

Ordered material with numbering that holds once it is published: what is inserted afterwards takes a suffix, and what is withdrawn has its number retired, never reused. And an Arabic search that finds the word as it comes to you.

2

Work on the same page

A shared view in the sitting, and comments that sit over the page without changing it — each according to their permissions. The sitting takes its own meaning in each field: a lecture, a meeting or a hearing.

3

Go back to what happened

What happens is written to an event log, and times and attendance are computed from it when asked, rather than typed into a field. A figure that can be checked, not one that has to be believed.

4

Start from your institution's structure

The screen is one screen, and its names come from your profession: the space is called what you already call it, rather than a word borrowed from another trade that you are then asked to get used to.

5

Know who can do what

Who may see, who may file and who may decide is settled in one place rather than in ten scattered settings — so no door is left open because somebody forgot to close it.

From opening to closing

One digital file for each space.

Not nine separate tools joined up by hand, but a single file carrying the space from the day it is opened to the day it is archived — and what is filed at the start is still cited by the same number at the end.

  1. 1Open the space
  2. 2Add the people in it
  3. 3File the material
  4. 4Build the bundle
  5. 5Publish the numbering
  6. 6Search and review
  7. 7Run the sitting
  8. 8Record attendance
  9. 9The outcome and archiving

Try it now

Insert a document into the middle of the bundle

The numbering of this bundle has been published. Add a document between two others, the way it happens in every file that is actually worked on — then watch the published numbers.

Example — a bundle of material Numbering published
    Published numbers changed
    Zero
    Documents inserted
    0

    An inserted document takes a suffix — 2.1, then 2.2 — instead of pushing everything after it down. A withdrawn number is retired, and never reused.

    And there is no export of a draft. Isnad has no "export the bundle as it stands": every file it produces carries a published numbering, because a bundle whose numbers move is the thing all of this exists to keep out of a hearing room.

    Review

    Discuss the document without changing the document

    A comment is a layer over the page, never an edit to it. The page underneath stays the evidence that was filed, carrying the checksum it was filed with.

    • A comment anchors to the page itself, not to its number — so a discussion survives insertion and withdrawal exactly as the numbering does. The same guarantee, applied to what people say about the file.
    • Its coordinates are fractions of the page, not pixels — so the mark sits on the same words at another zoom, on another screen, a year later.
    • And a note stays private until it is shared — sharing is an act somebody takes, not a setting somebody forgets. Until it is deliberately put in front of the room, it is counsel's own working paper.
    • And who a note reaches is settled with you — my team alone, those presiding, or the whole room. Anyone who has worked in a hearing room knows that is not a detail.

    The hearing

    One page in front of everyone, and a record of what happened

    One page

    In front of everyone

    Whoever holds the floor turns the page for the room, and hands the floor on to a named person. What is synchronised is a citable number, not a scroll position on somebody's screen.

    Reading alone

    Visible to the room

    A participant may leave the shared page and read whatever they need — and the room can see that they have, so nobody is addressed about a page they are not on.

    Attendance

    Recomputed, not stored

    Who joined and when, which page was shown, who held the floor — it is written to an event log, and time is computed from it when needed: two devices count as one attendance, and a disconnection stays a disconnection.

    Who is in the space

    Access is granted deliberately, and expires on its own

    Confidentiality here is not a setting configured after installation. It is the shape of the way in: who enters, in what capacity, until when — and who read what once they were inside.

    No self-service signup

    Nobody walks in

    Nobody creates an account for themselves in Isnad. A person enters the space by invitation from someone who already holds authority in it, and the invitation carries the role and the access window with it: a single-use link, of which only a fingerprint is stored, handed over by hand because there is no email to send it by.

    Four roles

    Each sees their own

    Its owner, its secretary, whoever files into it and whoever reads from it — genuinely different permissions over documents, hearings and membership, not titles on paper. And each is shown to each person in their own language, under the name their own profession uses.

    Access that ends

    Without anyone revoking it

    A membership carries a time window: someone admitted for one sitting loses access when that sitting is over, rather than when somebody remembers to withdraw it. And when it ends, what they could see drops off their list entirely — a title alone can say more than it should.

    Who opened this?

    The first question

    Not "what changed?" but "who read this exhibit, and when?" The log records that, and records who tried and was turned away alongside it. A log you can go back to and review.

    Where your data sits

    It can be installed inside your institution's environment

    Our default is the most cautious one, because what sits in the space may be a file that cannot afford to leave it. These are positions we start from, not limits we impose: what suits a school or a training centre is settled with you when it is installed. Where it runs is set in the operating agreement with you; the public demo online is not an installation at your site.

    These are not operational promises but properties of the build — and they can be checked from inside the platform, on a screen that tells you what is not yet safe instead of reassuring you.

    • Nothing is fetched from the internet while it runs — no fonts, no outside libraries. A hearing room or a government building may have no way out to the internet at all, and the screen has to open there exactly as it opens here.
    • Email is not the way in — because a message carrying the name of a case leaks it into an inbox you do not control. An invitation is a link or a code, handed over by someone with the authority to give it. Where that risk does not exist, as in a course, the arrangement is one we go through with you: it is a default, not a doctrine.
    • Scanned pages are read on your own server — no page image is sent out to a service to be read, and the language data is installed beside the system itself.
    • Nobody is tracked — no analytics and no crash reports leave your network, so what happens inside the system stays with you.
    • And a machine reading is not the filed text — a scanned page is read so that it can be found, and it stays marked as an optical reading.

    About us

    About Isnad

    At ZRS Hub Technology we build software that changes how institutions deal with their records. We are an Egyptian software company building for institutions: universities, schools, training centres, government bodies and arbitration centres.

    Our product, Isnad, is a platform where an institution's documents are filed, their numbering published so that it cannot change, and its team works on them in hearings, meetings and lectures — and the contract is always with the institution.

    It was founded by a team with long experience in both technology and legal practice, and our commitment is to improve the way people work with their files. Our mission is to deliver tools that are precise, straightforward and dependable, and that put the integrity of the record first.

    From word to page — join us in the work of keeping what was filed as it was filed: its number does not move, and what it points to does not change.

    Contact

    Request a demo for your institution

    ZRS Hub Technology

    Administrative Building No. 5 — Zizinia Resort, Fifth Settlement, New Cairo, Egypt

    info@zrs-hubtech.com

    +20 2612 4800

    +20 2612 4801

    +20 122 343 3310

    app.isnadeg.com

    www.zrs-hubtech.com