Inside AttestPod
Agree the local record fields, consent, document formats, roles and approvals. Save a version with each case.
Institution + country teamConfiguration and review
LOCAL REQUIREMENTS, CLEAR WORKFLOWS
Every country has
Every country has
its own rules.
Shape fields, documents, approval routes and external handoffs around the market your institution serves.
01Institution workflowRoles · evidence · approvals
02Country requirementsFields · document variants · wording
03External handoffManual now · official connection when agreed
CONFIGURATION WITH CONTEXT
A local rule should have a clear place to live.
A country pack defines the fields, formats, consent and document rules for a market. The institution adds its own roles and approvals. Each case keeps the version used when it began, so later changes do not silently rewrite history.
Country pack+Institution setup→Case version
UAE WORKFLOW EXAMPLE
A handoff the team can account for.
The UAE example shows a manual MoHESR recognition route. It does not represent a live electronic ministry connection.
01
Approve the record
The institution completes its configured internal reviews and freezes the eligible Original.
02
Prepare the handoff
Staff prepare a traceable package and record how and when it was submitted outside AttestPod.
03
Record the outcome
The external reference, status and recognised result are stored separately from the university-issued record.
Electronic ministry connectionScoped only after official access, technical specifications and
approval are available.
COUNTRY-FIT BLUEPRINT
Know which work lives where.
Use this sample map to distinguish what the institution can configure, what staff handle outside the product, and what needs official electronic access.
Outside the product
Where a manual ministry route applies, staff submit externally and record the reference and result back on the case.
Example: UAE MoHESRManual handoff only
After official access
Only then scope an electronic connection around approved specifications, permissions, failure handling and testing.
Ministry or system ownerAccess and approval required
INTEGRATION APPROACH
Connect with evidence, not assumptions.
Where a system contract exists, a connector can be scoped around its real interface, permissions and failure states. Until then, the workflow still needs a clear manual path.
Talk through your systems ↗
01Map the routeWho submits, which system owns the result, what evidence
returns?
02Define the connectionAgree data, access, security and operational
responsibilities.
03Test the complete journeyHandle corrections, failures and reconciliation as part of
the design.
FROM LOCAL RULE TO SHARED TRUST