Working Through the Simulations in Records Management 10th Edition
The simulations that come with Van Hoof's textbook are supposed to walk you through creating a records management program from scratch. In practice, they throw a lot at you at once. I spent an afternoon last month going through the appraisal simulation again because a student asked me about it, and I had forgotten just how many moving parts there actually are. The software itself is decent, but it assumes you already understand the underlying framework, which most people don't when they first open it. You need the standalone simulation application installed on your computer first. It's not browser-based, so if you're relying on cloud storage or a school lab computer that gets wiped between sessions, you're going to have problems. The program comes on a CD or download link from the publisher, and honestly, the installation process itself is a minor hurdle. Make sure your system meets the requirements — Windows 10 or later, .NET Framework 4.8, and at least 4 GB of RAM. Older lab computers sometimes choke on it. Once it's running, you'll pick a scenario. The textbook has four major simulations: appraisal and disposition, retention schedule development, records inventory, and the integrated records management program. Each one is designed to take roughly 90 minutes to 2 hours if you work through it methodically. Don't rush it. The app doesn't save progress automatically between screens the way modern software does. I learned that the hard way on my second run-through when I accidentally closed the application mid-inventory and lost about forty-five minutes of data entry.
The appraisal simulation is probably the most useful one for actual workplace application. It asks you to evaluate records based on their business value, legal requirements, and operational necessity. Here's the thing most guides don't mention: the textbook's framework for appraisal is heavily influenced by the ISO 15489 standard, and the simulation expects you to apply that framework consistently. When I was working through it, I kept defaulting to a purely practical approach — keeping what I'd use and deleting what I wouldn't. The simulation marked that wrong every time because it wanted you to also factor in regulatory retention periods and evidentiary value, not just convenience. That distinction matters in the real world too, by the way. I've seen companies dispose of records they shouldn't have because their employees were thinking operationally instead of legally. The retention schedule simulation is where people usually hit their first wall. The software walks you through building a schedule row by row, but the trick is understanding what qualifies as a record series in the first place. I spent twenty minutes on one exercise trying to figure out why the program wouldn't let me group certain document types together. The issue wasn't a bug — it was that I was treating individual form types as separate series when the simulation wanted me to aggregate them under a common functional category. Once I stopped thinking about individual documents and started thinking about business functions, everything clicked.
The Common Pitfalls
The integrated program simulation combines everything from the earlier exercises, and it's where most students struggle. The software gives you a fictional organization with departments, document types, and compliance requirements scattered across three different regulations. You have to build an appraisal plan, a retention schedule, and a disposition workflow that all work together. The problem is that each section has dependencies on the previous one, and if your earlier answers were even slightly off, the later sections start breaking in confusing ways. I found the best workaround is to keep a separate spreadsheet tracking your decisions across all four simulations. Not the answers themselves — just the reasoning. When the integrated simulation starts flagging inconsistencies, you can go back and trace which decision caused the cascade. Without that trail, you end up guessing at what went wrong and wasting another hour. Another issue nobody warns you about: the simulation's help documentation is practically useless. It explains what each field means but never explains why certain combinations are invalid. The validation logic is buried and undocumented. If you get an error message like "functional requirement not met," there's no way to find out which requirement it's referring to except by systematically eliminating possibilities. That's intentional design — it's meant to force you back to the textbook chapters — but it's frustrating when you're on a deadline.
Get the Full Details
What the Simulations Don't Cover Well
For all their value, these simulations have real blind spots. They treat records management as a static, internal function. There's nothing about cloud storage migration, email archival, or electronic signature compliance. If your workplace deals with any of those, the textbook framework still applies, but the simulation won't prepare you for the actual technical challenges. The retention schedule exercise, for example, uses a simple grid interface. Real-world retention schedules live in enterprise content management systems with complex rule engines, and getting data from one to the other requires skills the simulation never touches. The appraisal section also oversimplifies risk assessment. In practice, deciding whether to keep or dispose of a record often involves legal counsel review, insurance requirements, and ongoing regulatory changes. The simulation presents it as a straightforward classification exercise. That's fine for an academic exercise, but it creates a false sense of confidence if you think the real job works the same way. If you're using these simulations for a class, the most efficient approach is to work through each one twice. The first pass gets you familiar with the interface and the general process. The second pass, with the textbook chapters open beside you, is where the actual learning happens. The textbook explains the "why" behind each simulation step, and the simulation reinforces the "how." They're designed to complement each other, but most people only use one or the other.
