For funders and programmes, MORA screens your applicant database against hard eligibility rules you provide. Each record receives a clear, reviewable outcome.
MORA applies client-defined hard gates consistently to a client-provided applicant database. The workflow is rules-first: your team sets the criteria, MORA screens the records, and your team makes the final decisions. The same approach can be scoped for other categories when records and rules are suitable.
Five reviewable outputs in one workbook. MORA screens against your agreed rules; your team makes every final decision.
Rules are agreed with you in writing before screening starts. A REFER outcome is held for your team to review; MORA does not make the final award or selection decision.
| Applicant | Status | Reason |
|---|---|---|
| APL-1013 | PASS | Meets all agreed hard gates |
| APL-1015 | REFER | Required field missing; human review |
| APL-1018 | REFER | Possible duplicate; confirm |
| APL-1019 | FAIL | Hard gate failed: location not eligible |
| APL-1020 | FAIL | Hard gate failed: age outside stated range |
MORA applies only the rules agreed with the client. It does not score creative or personal merit, verify claims against external sources or decide who receives an award.
Agencies, promoters and bookers receive briefs with hard requirements: budget, genre, location, date and rider. MORA matches a brief against your roster and returns a ranked shortlist with the reason each act made the list or didn't.
Each screening tier covers one applicant intake, one supplied dataset and one agreed ruleset for structured, usable records.
Client inputs: a clean CSV/XLSX with a unique applicant ID and only the fields needed for the rules; written hard gates, thresholds and accepted values; and instructions for missing or unclear information. File clean-up, rule changes, extra review rounds, additional datasets and complex document extraction are scoped separately. Turnaround is confirmed after MORA reviews the complete data and criteria. Final decisions remain with the client.
Before data moves, MORA and the client agree in writing on the screening purpose and handling arrangements. MORA uses applicant data only for that agreed work. MORA's Information Officer oversees internal information-handling practices.
Data is held in access-controlled systems and may be processed by service providers needed to run the service. Relevant providers are identified in the engagement documents before client data is shared.
The engagement agreement sets out how long data is kept and whether it is returned or deleted when the work ends.
MORA is run by its director, Simphiwe Mabaso, whose background is in client service and application processing, where consistent, documented decisions matter. When you work with MORA you deal with him directly, from the first rules conversation to the final workbook.
Send a few details and we will reply with a written quotation. Enquiry details are used to respond; applicant data is handled under the agreed screening arrangements.
Simphiwe Mabaso
Director, MORA