Synod of Chelsea
Open-knowledge reference entry
There were a number of Synods of Chelsea held in Anglo-Saxon England. They were held at Cealchythe, in Kent, generally identified with modern Chelsea, London.
Offa's councils
787
King Offa of Mercia presided over a church council held at Chelsea in the 787. Although it has often been claimed that the council was attended by papal legates, this stems from a conflation of the visit by papal legates to Offa's court and Northumbria in 786. The two legates did attend a council held at Offa's court, but this was not necessarily held at Chelsea.
Two different versions of the Anglo-Saxon Chronicle record the proceedings of the council. The Peterborough Manuscript (Version E) of the Chronicle records the council under the year 785, although the events took place in 787, and states that "here there was a contentious synod at Chelsea and Archbishop Jænberht relinquished some part of his bishopric, and Hygeberht was chosen by King Offa, and Ecgfrith consecrated as king." The Canterbury Manuscript (Version F) has the council under 785 also, and describes the council as "a full synod sat at Chelsey" but otherwise relates much the same events. The historian Nicholas Brooks sees the coupling of the elevation of Lichfield with the consecration of Ecgfrith, who was Offa's son, as significant. He argues that Offa desired to have Ecgfrith consecrated as his successor during Offa's lifetime, but was unable to get Jænberht to agree, and this was another factor in the creation of Lichfield as an archbishopric. Hygeberht consecrated Ecgfrith after Hygeberht's elevation to archiepiscopal status.
Begin with the source’s own compact description: “Synod of Chelsea” is open-knowledge reference entry. The dossier treats that line as a proposition to test through Synod, Chelsea and Open-knowledge, not as a finished interpretation.
Why this record matters
The phrase “open-knowledge reference entry” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jun 7, 2025. The linked authority identifier is Q7662526. None of the 0 selected statements returned an explicit reference.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Synod of Chelsea”, its source revision and the description used here.
- Expand the search: follow Synod of Chelsea primary sources, Synod of Chelsea archive and Synod research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Synod of Chelsea”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Synod of Chelsea” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.