Docs360

The First Bad Revision

Director Technology

A technology director can tie a patch to evidence by showing how each execution narrowed the revisions that could have introduced a rendering fault.

Download the PDF

The signature device

A fixed page passes on revision F and fails on G after three intermediate tests between known good A and bad I.

Who should choose it

For a software engineering head whose next role depends on owning both the failed output and the release that repairs it.

Who it puts first

The refereeSearch partnerCHRO or head of talent

Director and Head · Annual report · 2 A4 pages

Page 1 of The First Bad Revision, a sample for a fictional Director Technology, Aamir ZelqashiPage 2 of The First Bad Revision, a sample for a fictional Director Technology, Aamir Zelqashi

The design, and its plain companion.

The First Bad Revision, as designed

2 A4 pages, printed as you see them, in real selectable text.

The plain companion

The same record in one column under standard headings, for the portals and applicant systems that can't read a design. A commissioned document comes with one too.

First page of The First Bad Revision
As designed
First page of the plain companion to The First Bad Revision
Plain companion

Aamir Zelqashi, the companies and the institutions on this page are fictional. A commissioned document carries only your own facts, and every figure is one you have confirmed.

Or talk to us first