How to suggest a person to turn a page to see more details?

Question

We are building a printed voucher (hard copy) for lab tests which looks like the following :

The lab test center people who take the tests should mark the checkboxes with a pen or a marker against thoses tests which are taken.

However the problem which we are seeing consistently is that sometimes the people at the lab test center forget to turn the page if there are more tests and the users end up getting fewer tests performed than required. we have texts tried texts like "PTO", "please turn over" etc, but it doesnt work 100% of the times.

What we think:

I think we can implement 1/30, 2/30, 3/30 ... 30/30 in the lab test serial no. but for some reason even that doesn't seem right.

Any ideas or suggestions ?

Answer 1

I think a start would be to make it clear the total number of tests and/or total number of cards at the top of each card. And also the breakdown of how many rows you seeing out of that total.

e.g.

• Total Tests: 22

• Page: 1 of 2, showing tests 12 of 22

---

Mockup 1

Answer 2

Simply adding the arrow at the bottom will help. Check the below img

Answer 3

There are many good answers about annotating the bottom of the page clearly (I like Dave Haigh's best), but as an alternative, how about making the last task (on each side) indicate that tests continue on reverse -- that way, it's directly in what they're (meant) to be reading/completing? I don't have an image editor to hand, but instead of:

^{download bmml source – Wireframes created with Balsamiq Mockups}

try:

^{download bmml source}

You could even make it a task in itself:

^{download bmml source}

And if you want to address the "what if someone starts on page 2" problem, you could do a similar thing at the top of the second page:

^{download bmml source}

Essentially, it's like "Carried forward" / "Brought forward" you see on statements or invoices, and obviously (I hope) the idea can be extended to as many pages as needed.

One final point: if the test numbers (1, 2, 3 etc.) -- as opposed to the Test IDs -- have significance, then these could be omitted from the carry-forward / brought-forward lines.

Answer 4

Option 1: Print on multiple pieces of paper

Just out of curiosity, is printing it on two separate pieces of paper an option? Having two papers and a staple indicates clearly to the reader that it isn't a single page document.

Option 2: Add something to the end of the test to indicate it is done

I wonder if there are workflow type triggers that you could use... Maybe you could add a signature and date field as the last item on the test. If people fill out multiple tests, they will be accustomed to signing their name at the end and will not submit the test unless their name has been signed.

Option 3: Present the test in a way that implies it may have multiple pages

How do you provide the tests to people? If it is on a clipboard, the process to turn over the test involves removing it from the clipboard and re-attaching it. If you provided the test to someone in a binder, this implies that the content is multiple pages.

Answer 5

Use workflow and cognitive dissonance to draw the user's attention

• The form workflow is top-to-bottom, left-to-right. So the user will naturally end up at the bottom right of the page.

  • So, place the page-turn indicator on the bottom right since the user's eye will be there.

• The form uses a grid layout, and has a lot of content. Therefore if you use standard font and grid alignment for the page-turn notice, it will be easy for users to miss the page-turn notice because it doesn't stand out.

• Use cognitive dissonance to deliberately break the grid layout and jolt the user into noticing the page turn.

For example...

This layout uses a different/bold color, a grid-breaking icon, and different font size and style to create cognitive dissonance that draws the user's attention to the page turn notice.

It also uses imperative language ("do this") in the page notice to provide clear instruction to the user once she sees the notice.

It's an exaggerated example intended to show different techniques for creating dissonance. You will need to figure out which combination of techniques work for your form.

Answer 6

These are great answers, particularly Dave Haigh's, however none of them seem to address one important issue:

What if the paper initially is placed on their desk with page 2 upwards?

All the suggestions about "turn over to see page 2" don't address the issue of "turn over to see page 1".

For example the big black box "10 more tests" somehow needs to be also on page 2 with something like, er, "10 fewer tests". No, that isn't right!

But there needs to be something, as there could be a 50% chance you just see test 13 onwards and not really notice that you are not starting at test 1.

Something like this for page 2 (I didn't get the numbering right, but it shows the idea):

Answer 7

What happened to the conventional arrows that were correlated to the number of pages there are?

^{download bmml source – Wireframes created with Balsamiq Mockups}

You don't even have to show that left arrow when you're on page one.

Answer 8

There are good and reasonable answers here that explain how to show readers that they must turn the sheet around, but what you really want in medical applications is making sure all necessary tests have been ordered/performed, not superfluous ones and not the wrong ones (for adjacent rows for instance).

That is why I think it is more important to change the single check-box into a double check-box for ‘yes’ and ‘no’ or vice versa. This requires more ticks by the pen user, but every other user can easily check if both sides of the form have been completed and hand it back if not (with some snarky remark or raised eyebrow which constitutes the social pressure that ensures this does happen only this one time).

Also, I would move the column with the fixed-width ID that contains a mnemonic acronym after the full name, next to the check-box so it works as a close-by label. This should reduce row mistakes.

^{download bmml source – Wireframes created with Balsamiq Mockups}

(Unless, of course, I misunderstood the workflow.)

Answer 9

You can add an extra checkbox at the end of the form that says: "All checkboxes are checked" or "Check all test receipts are attached", or something to that effect. For this to be effective, lab workers need to be trained and conditioned to expect a checklist completion checkbox on every checklists they use regularly.

The purpose of this checkbox is to condition the lab tests workers to check that they've actually reached the real end of the checklist and to go through the forms one last time before passing on the workset to the next person or before they move on to the next task.

Answer 10

It may be culturally dependent (Czech Republic), but the sign I've always known, seen, and used to indicate "turn page over" is a (big) percent sign in the bottom right-hand corner. In this particular case, it's not really a percent sign, but indicates a sheet of paper being turned over, or alternatively that there is something on both sides.