Registers, reports, results. Just ask for what you need.
No more working out which iSAMS screen, grid or report holds the answer. Memra is being developed so staff can ask in plain English and get a result that shows its source, its time period and the scope they are already permitted to see.
Illustrative early-access experience for teachers—not another dashboard to configure.
One place for the questions behind the school day.
Illustrative answers show the record area and time period used. Results must stay within the signed-in staff member's authorised iSAMS scope.
“Which pupils in my form still need an AM registration mark?”
“What do I need to know before I call this pupil's parent?”
“Which report cards for my classes are still waiting for my comment?”
From an iSAMS question to a report you can use.
Ask in natural language and review the answer on screen. Where the school has enabled report downloads, a head or deputy head whose iSAMS permissions cover the task can export a working copy for a meeting, staff follow-up or further analysis.
Start with the job
Check registration, prepare reports, review conduct or gather context before contacting home.
View the answer
Ask in plain English, then check the answer, source, time period and authorised scope on screen.
Download when authorised
Export a report only when both the user's iSAMS scope and the school's download policy permit it. Viewing an answer does not itself grant export permission.
Edit the working copy
A permitted head or deputy head can add notes or edit the downloaded copy for local analysis. It remains a separate file, must be handled under the school's data-protection rules, and never changes the source iSAMS record.
Less admin without giving up control.
Speed only helps when the right information stays with the right people and every answer can be checked.
Existing permissions remain authoritative
Memra must not expand what someone can see because they ask in different words. Unclear identity, scope or permission means no result.
Show only what the task needs
A teacher gets the minimum relevant context for their authorised pupils; a head or deputy head can see a wider view only where the school has granted it for that role and task.
Make the source visible
Answers identify the underlying record area and time period so staff can understand what the result covers.
Keep changes separate from answers
Viewing an answer, exporting an authorised report and editing its working copy do not authorise a change to iSAMS. Direct write-back requires a separate, verified route and permission check.
Direct iSAMS write-back is separate—and never enabled by default.
Memra does not present direct write-back as available for a school until a supported integration has been verified and that school has enabled it for named roles, defined tasks and limited scopes. Viewing answers, authorised exports and edits to downloaded working copies remain separate from changing an iSAMS record.
Enabled by the school
A user cannot switch on write access for themselves. The school decides whether it is available for named roles, defined tasks and limited data scopes.
Delegation stays narrow
The school names the role, task and data scope. Giving a head or deputy head one responsibility does not turn that person into an iSAMS administrator.
Approval comes before action
A request beyond the user's direct authority remains unapplied until the school-configured approver accepts it. No verified route means no change.
Every decision is attributable
The request, approval, rejection and completed action must identify who did what and when, without exposing unnecessary pupil information.