Enterprise DNA

Instead of Slate Admissions

Rethink your Slate Admissions bill. Own your admissions review desk.

We build your version around your intakes and review process, bring supported Slate application exports across and run the desk for you. Your people make the decisions, with the evidence beside them.

Slate Admissions starts at US$30,000 a year below 1,500 submitted applications. The next published band, 1,500 to 7,500 applications, is US$50,000 a year.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The admissions bill

A whole platform subscription around a recurring review desk

Slate covers far more than application review. Compare the work your admissions office actually needs, including the forms and connections that must keep working when you switch.

payments

An annual application-volume licence

The published entry licence is US$30,000 a year for fewer than 1,500 submitted applications. It is an institution licence, not a charge for each reader.

groups

A larger submitted-application band

The published band from 1,500 to 7,500 applications is US$50,000 a year. Compare your actual annual volume and contract before choosing a replacement.

fact_check

Materials and application checklists

Required documents, missing items and received evidence are recurring administrative work. Your owned desk keeps those records with a named owner.

rate_review

Reader forms and review queues

Slate provides a Reader and review forms. The free base tracks assigned readers, due dates and references to completed reviews.

folder_shared

Application records and exports

Slate lets you download query results as CSV. The move begins with a configured application export and a count you can reconcile.

web

Portals and the wider institution

Slate also provides applicant-facing services. Enterprise DNA scopes the forms, communication and connections your version needs before you retire those services.

Your owned admissions desk

The weekly review, shaped around your intake

Materials

Know what is still missing

See the requirement, responsible owner and supporting evidence together.

  • check Required materials and due dates for each application
  • check Received or waived items with evidence references
  • check Checklist confirmation against your own policy
  • check A changed requirement makes the checklist need confirmation again

Readers

Put overdue review work in view

Bring reader assignments into the same record as the file they are reviewing.

  • check Pending reviews by reader
  • check Overdue counts for the weekly meeting
  • check Completion dates with references to the actual review
  • check A private weekly draft that combines readers, outstanding files and record checks

Committee

Keep human decisions attached to evidence

Administrative completeness prepares the file. Authorised people decide the outcome.

  • check Complete materials, reviews and an accuracy check before recording a decision
  • check Named human authoriser and committee evidence reference
  • check Internal committee packets and decision records in your brand
  • check Original decision evidence retained alongside correction notes

Follow-up

Keep the intake moving after committee

See what remains open without guessing that silence means acceptance.

  • check Recorded offers awaiting a response
  • check Response evidence and received dates
  • check Intake counts and elapsed time for recorded decisions
  • check Retention review flags beside the application owner

Make it yours

Design your own Slate Admissions replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Slate Admissions. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Slate Admissions replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Slate Admissions data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Admissions Desk for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Admissions Desk for Claude Code

Connected to your own database

Which applications need attention before the next committee meeting?

APP-104

Owner
Jules
Desk_state
checklist-unconfirmed
Missing_materials
0
Pending_reviews
0

APP-101

Owner
Morgan
Desk_state
materials-outstanding
Missing_materials
1
Pending_reviews
1

APP-105

Owner
Morgan
Desk_state
in-review
Missing_materials
0
Pending_reviews
1

Ask it anything

Ten questions your admissions desk answers

These are working checks in the free version. Slate also supports configurable reporting. Your own version lets you change these checks around the way your office works.

chat_bubble Which applications are overdue and still missing materials?
chat_bubble Which readers have the most overdue work?
chat_bubble Which applications have complete administrative evidence for committee?
chat_bubble Which offers have no recorded response?
chat_bubble Which intake has the largest group waiting for materials?
chat_bubble Which records need an accuracy or retention review?
chat_bubble How long did recorded decisions take by intake?
chat_bubble What source export and independent count support the imported records?
chat_bubble Who confirmed each checklist or recorded a committee decision?
chat_bubble What material, reader and note history belongs to this application?

Switching

How to switch from Slate Admissions

The move involves exporting application records, mapping your local fields and rules, checking the imported data, and keeping the old and new review processes running side by side before you switch.

  1. 1

    Agree what moves

    Decide which application records and review work you want to move, and which parts of Slate you still need. Admissions Desk covers the internal review desk, not Slate applicant portals, forms, communication services or the wider student lifecycle platform. Agree the source query and the history you need before you prepare an export.

  2. 2

    Export Slate applications

    Slate supports CSV downloads from configured queries. Export the cumulative application rows for the intakes you have agreed to move, including the fields you need to map. Check that the export covers the records you expect and keep the original export available. If you are unsure how to download the right records from your account, check with Slate.

  3. 3

    Test, then import

    Map the exported columns to the application records and required fields in Admissions Desk. Start with a dry run, which writes no records, so you can check the import before loading the data. Once the mapping and expected record count are ready, run the import. Extra exported fields are retained as evidence, but they do not replace mapping the fields and rules you use.

  4. 4

    Review the import

    Check the import results, including any records it flags, and reconcile the imported count with the source count from Slate. Resolve mapping or record issues before relying on the new desk. Reader forms, attached documents and decision history need additional mapping, and the import does not infer those from an application status. Keep the source available while you confirm the records you need.

  5. 5

    Run both, then switch

    Use Slate and Admissions Desk side by side for a short period. Compare the application records and review evidence, and confirm that your team can complete the internal review work in the new desk. When the required records and history have moved and the new process is checked, switch off Slate Admissions for that work. Keep any other Slate services you still need.

construction

Where the real effort goes

The main work is usually mapping your own fields, required materials and review rules, then deciding how much history to bring. Reader forms, attachments and decision history need extra mapping, so they should be planned rather than assumed to transfer. If you have Enterprise DNA install and run your version, they handle this mapping and implementation work with you.

Not ready for a call?

Get your Slate Admissions switch plan by email

We will send you the step-by-step plan for moving your business off Slate Admissions, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Run it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and use the admissions commands
  3. 3 Configure your Slate application CSV to the documented headings and test the import
  4. 4 Confirm your material rules and review evidence before recording human decisions
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your intake codes, required materials, fields and review rules
  • check Your Slate data mapped, counted and checked against the source
  • check Applicant forms, review screens and connections scoped to your process
  • check Your preferred technology and branded committee paperwork
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and record controls set up
  • check The weekly review and missing-material drafts prepared for your team
  • check Kept working as your programmes and admissions process change
  • check Operated through Omni by Enterprise DNA alongside the rest of your business
Book a discovery call

Questions

Instead of Slate Admissions, answered

Does this replace every part of Slate? expand_more

The free base covers the internal admissions review desk. Slate also handles applicant portals, forms and wider student services. We agree which work moves, then build the connections and screens your version needs before you retire those services.

Can we bring our Slate applications across? expand_more

Yes. Slate supports CSV downloads from configured queries. The free version imports the documented application layout and retains extra exported fields as evidence. Reader forms, attached documents and decision history need additional mapping. We reconcile the records and keep the source available until the required history has moved.

Will it decide which students to accept? expand_more

No. It tracks administrative completeness and records decisions already made by authorised people. It does not score or rank applicants. A committee-ready file means the required evidence is recorded, not that the applicant should be admitted.

How are applicant records protected? expand_more

The free base is for a trusted operator and checks record accuracy, checklist confirmation and retention review dates. A shared version needs identity, appropriate access, tested backups and privacy controls for your institution. Enterprise DNA scopes and implements those before real applicant records are shared.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer to customise and run your version. We agree the scope around your intakes, history, forms and connections. You can also install and operate the free version yourself.

Bring your admissions bill and your next intake

Spend 30 minutes with Sam looking at the work your office does each week, what Slate costs and what your own version needs to cover. Leave with a clear scope for the review desk and the services around it.

Admissions Desk for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Slate Admissions?

Get your version built