Skip to content

Fix a write-up that was sent back

Read what the checker wants changed, correct the same write-up, and send it again.

Checked against the screens:

Every organisation can choose its own words for the people and roles it works with. When you are signed in, this guide uses your organisation’s words. Otherwise it uses the product’s own.

For the mentor who wrote it. A returned write-up is still yours. Fix that one. Do not start a new write-up for the same session.

Steps

  1. Read the message you were sent. Its first line gives the manager's reason.
  2. Open the session. In the Planner press Make requested changes. On the record, the label reads Sent back to you and the button is Make the requested changes.
  3. Read the reason again at the foot of the record, under Sign-off chain.
  4. Correct only what was asked. Check the times, outcome, ratings and words still agree with each other.
  5. If you need to stop, press Save & exit. That keeps your changes but does not send them.
  6. When it is ready, press Resubmit for sign-off.
  7. Reopen the session and check it now says it is waiting for a manager.

If it goes wrong

  • No button to change it? You may be looking at a colleague's write-up. Only its author can fix it.
  • Started a second write-up by mistake? Open the original instead. The form warns you that one exists.
  • Not sure what the manager meant? Ask them. Say which section you are unsure about.
  • Saved but nothing seemed to happen? Saving a draft does not send it. Press Resubmit for sign-off.

Why you fix the same one

A returned write-up was handed back so that it could be edited. If you start a new one, the old one is left stranded and the new one may take the sign-off. The record then shows two accounts of one session.

Where to read the reason

The message you receive begins with the reason, so you can see what to do at a glance. The same reason sits in the sign-off section at the bottom of the record, next to who sent it back and when.

What a good fix looks like

  • It answers what the manager asked, in the box they named.
  • The times, outcome and ratings still match the written account.
  • You have not changed unrelated things to be safe. Extra changes make it harder to check.
  • If you are unsure, say so in the account rather than guess.

Draft or send

Save & exit keeps your work and leaves the write-up as a draft. Resubmit for sign-off is the only button that sends it back. If a section is still missing, the form lists it and keeps your draft.

After it is signed

A signed write-up cannot be edited like a draft. If it still contains an error, ask a manager. They can amend it, and the original history is kept.

A write-up that comes backIt goes round until it is signed.
  1. Sent backWith a reason
  2. You fix itThe same write-up
  3. ResubmitResubmit for sign-off
  4. Signed offBy a manager

How it links together

A return sends you a message and marks the session as sent back in the Planner and on Home. The reason is kept in the sign-off chain on the record. Resubmitting puts it back in the countersign queue. See the guide to the existing write-up warning and the guide to reading a finished write-up.

Questions people ask

How do I know a write-up was sent back?

You get a message that begins with the reason. The record also shows Sent back to you, and the Planner offers Make requested changes.

Can I start a new write-up instead?

No. Fix the returned one. A new one would leave it stranded, and the form warns you if you try.

I changed it, but my manager has not seen it. Why?

You probably saved a draft. Press Resubmit for sign-off to send it.

Where is the reason they gave?

In the message you were sent, and under Sign-off chain at the foot of the record.

Who can fix a returned write-up?

The mentor who wrote it. A colleague can read it, but it is not theirs to change.

What if I disagree with the changes asked for?

Talk to the manager who returned it. If you resubmit unchanged, say why in the account so they can see.