When should I put my database into Production Status?

Please do not rush to put the database into production status. Do sufficient testing by adding Test Records and Test Data. Test that all field validation, calculated field, branching logic, and other settings in your instruments work correctly. If you are using Surveys, send them to yourself and colleagues to ensure your planned distribution method works. If you have set up Automated Survey Invitations or Alerts & Notifications to be delivered immediately after some condition, check that these work properly. If you have Automated Survey Invitations or Alerts & Notifications to be delivered at a future date after some condition, make a test record meet those conditions, then go to Survey Distribution Tools → Survey Invitation Log → Future Invitations. You will see the invitations set here, i.e. if you set an ASI to be delivered six months after an intake form, complete the intake form then see if an invitation for 6 months from today exists in the Survey Invitation Log. If your project is not functioning properly or you are unsure if everything is working properly, please Submit a REDCap Ticket if you need help.

Follow the instructions in How do I move a Project to Production Status? to put the project in production. When you move to production you will have the option to keep the data in your project or erase everything.

If you find you’ve put the database into production status too soon, you can ask the REDCap Administrators to move it back to development status. You can put it back into production when it’s ready.