Dear Technical Writers,
Would you please help me with a question about "as per"?
In a business writing class in San Diego, a participant wanted to help her team write better technical instructions. Their instructions are wordy, use overly sophisticated language, and do not follow a consistent format.
She made good progress toward her goal, but she--and I--got stuck on "as per." Is "as per" acceptable in technical writing as a substitute for "according to"? Or is there a better way of communicating something like this sentence, which I have made up:
Attach the plate to the rod as per Instruction 3231 on plate-rod assembly.
The idea is that some steps in the instructions refer to other instructions.
In business writing I encourage everyone to replace "as per" with clear language, like this:
As per your requestAs you requested, I have postponed the meeting.
But I am not sure what works effectively in technical writing when the instructions cite another set of instructions that assemblers must follow. Is "as per" a good solution?
I would love your suggestions. And if you can recommend a guide to writing technical instructions for me to add to my library, please do.
Many thanks!
Lynn
Syntax Training

I would never use the phrase "as per", even in technical text. It's a strange hybrid of English and Latin that sounds both wrong and pretentious.
Couldn't we just do a straight translation here of "per" and say "as with"? Or replace "as per" with "according to"?
Posted by: Clare | May 20, 2009 at 09:15 AM
I also cringe at the term "as per". That may be because some of my coworkers use it too often, and many times incorrectly. I think I would use "as stated in Instruction 3231"
Posted by: jade1977 | May 20, 2009 at 09:29 AM
I would use
Attach the plate to the rod following Instruction 3231 on plate-rod assembly.
Posted by: Victor | May 20, 2009 at 05:36 PM
How about simply removing the "as"? I see nothing wrong with:
Attach the plate to the rod per Instruction 3231 on plate-rod assembly.
Posted by: Lester Smith | May 21, 2009 at 07:44 AM
Thanks for your suggestions! Let's see if others have ideas.
Posted by: Lynn | May 21, 2009 at 06:01 PM
The Handbook of Technical Writing from Bedford/St. Martins makes a nice reference book. Here's the advice on using per: "When [per is] used to mean 'according to,' the expression is jargon and should be avoided."
As a technical writer, I would say there's a bigger issue than using as per to reference other instructions. It's an issue of clarity.
Each time you make a reader break from the current set of instructions to find, follow, and return from another set of instructions, you run the risk of losing the reader.
I think there's lots of options to edit "as per" that depends more on the actual context of document than whether or not it's jargon. But that may be just my opinion.
Posted by: Mike Badger | May 22, 2009 at 11:25 AM
Thanks, everyone! I appreciate your suggestions. It sounds as though we agree that "as per" stinks. The suggestions that seem most workable to me are:
--according to
--following
--as stated in
Mike, thanks for commenting and sharing "The Handbook of Technical Writing" advice. I agree that multilayered instructions are wrong-headed. The woman in my class, however, had a reason for using them. In her view, all the assemblers actually know the substeps. They are simply there for reference in case a new assembler is learning the procedure.
Lynn
Posted by: Lynn | May 22, 2009 at 04:04 PM
I would never use "following" due to readability issues, including potential ambiguity. "According to" and "as stated in" are wordy for technical documents. I would simply use "per" and spare the sorry bunch who have to read my docs some text.
Posted by: 1red111 | March 11, 2010 at 01:57 PM
http://www.wsu.edu/~brians/errors/asper.html This explains why "as per" is not necessary.
Posted by: Marza | May 19, 2010 at 11:19 AM