Manually Triggered Replication?

I've been studying/experimenting with the replication features and though the Updating Susbcribers Replication Model was the answer to my data environment.

What we want: We have a live server (Publisher) that'll serve content to our users, but we want an "offline/data entry" server (Subscriber) that'll pretty much have the exact same data as the live server for data entry and validation purposes. Changes and inserts would be done on the Subscriber locally, vetted through, and once done, it'd be updated to the Publisher.

I've managed to get some semblance of the above working, but the updates are nearly instantaneous. Which means that changes/inserts that may be erroneous on the subscriber machine would almost always be seen on the publisher machine before our operations can do anything about it.

Is there a way to configure the replication process to hold off until the admin triggers it? Or am I using the wrong feature?