SevaSetu Placement Desk

Demonstration role

Purpose of access

Role picker simulates a session.
Production requires approved sign-in and server permissions.

SAMPLE REGISTER LOOKUP

A code opens the case, not a blank form.

Sample candidate ID

ORIGINAL RECORDS + LATER QUALIFICATIONS

Keep evidence and claims distinct.

No real issuer checks are performed.

Add a qualification after service

Submission creates a pending claim. A matching sample issuer response is required to credit it.

Qualification

Issuing organisation

Certificate reference

Role requirement code

Awarded on

Valid until (if applicable)

Optional test document (PDF, PNG or JPEG; up to 2 MB)

The file is fingerprinted locally. Its bytes are not sent or published. A fingerprint alone does not prove authenticity.

Document fingerprint (SHA-256)

EXPLICIT REQUIREMENTS / TRACEABLE FACTS

Show what is supported, missing or pending.

Sample role

Prepare a CV from the confirmed sample facts

Pending, expired and revoked qualifications are omitted. DOB and last pay are omitted from the CV.

Access and action record

Purpose, actor and outcome are recorded. DOB, pay amounts and document contents are not logged.

TWO OPTIONS / ONE DISCUSSION

Confirm the workflow with its owner.

Careers: candidate-led

A person enters their facts, explores vacancies and prepares a draft CV. The existing demonstration remains separate and stable.

Try Option A ↗

Placement Desk: record-led

A placement worker or an authenticated candidate retrieves an authorised record, checks evidence and compares explicit role requirements. This page demonstrates that proposal with fictional data.

What the published problem supports

PDS 6 in the Army Design Compendium 2025 mentions CV preparation from the existing AWPO database. It does not specify that every service, DOB, pay and qualification field is available through one identifier, or that the application is exclusively staff-facing.

Questions for the responsible team

Should the primary user be a placement counsellor, the candidate, or both?
Which register and identifier can be used, and who controls access?
Which fields are authoritative, current and necessary? Is last pay needed at all?
Who can confirm a new certificate, including one obtained after service?
Which role rules, age cutoffs, relaxations and equivalences must be applied?
Would the team prefer a sample export, sandbox API or supervised pilot before integration?

The prototype compares documented requirements. It does not select or reject people, submit applications or certify real credentials.