Chartawell/Publications

Reports and technical notes
everything the centre finds, including the null results

Centre reports

Technical notes

Short, single-question pieces, four to twelve pages, written for the person who has to make a decision this month. Each is dated and superseded rather than silently edited.

No.TitleIssuedStatus
9Reading pH results from cold extraction without overstating them2026Current
8Tape lifts for mould: sampling, transport and what culture adds2025Current
7Photographing a leaf in transmitted light for perforation counts2025Current
6Loggers on shelves: placement, calibration drift and reading the record2024Current
5Interpreting colourimetry on discoloured paper2023Current
4Bathophenanthroline: what a positive result licenses2022Superseded by no. 9 in part
3Sampling from tear edges without creating new loss2021Current

Guidance

Guidance notes are written with a working group drawn from partner archives, and are the only documents here that recommend rather than report.

  • Surface cleaning: what the evidence supports (2025) — six materials tested for gloss change, colour change and abrasion; two of them should not be in general use.
  • Triage in a wetting incident: the first seventy-two hours (2024).
  • Specifying an environmental survey (2023) — what to ask a contractor for, and how to tell whether you got it.
  • Handling and support for bound volumes under digitisation (2022).

Publication policy

Programme results are published whether or not they support the hypothesis the programme opened with. Three of the six current programmes have produced null or negative findings, and those are written up at the same length as the positive ones. A field that only prints results which worked will slowly fill with methods that do not.

Commissioned reports belong to the institution that commissioned them and are not published by us. Aggregated, anonymised measurements may enter a programme dataset unless the submitting institution opts out, which a small number do each year, and that is recorded in the dataset documentation as a known gap rather than quietly ignored.